FHIR CI-Build

This is the Continuous Integration Build of FHIR (will be incorrect/inconsistent at times).
See the Directory of published versions

Example CodeSystem/fhir-format-type (XML)

FHIR Infrastructure Work GroupMaturity Level: N/AStandards Status: Informative

Raw XML (canonical form + also see XML Format Specification)

Definition for Code SystemFHIRFormatType

<?xml version="1.0" encoding="UTF-8"?>

<CodeSystem xmlns="http://hl7.org/fhir">
  <id value="fhir-format-type"/> 
  <meta> 
    <lastUpdated value="2024-10-02T17:31:51.554+00:00"/> 
  </meta> 
  <text> 
    <status value="generated"/> 
    <div xmlns="http://www.w3.org/1999/xhtml">
      <p class="res-header-id">
        <b> Generated Narrative: CodeSystem fhir-format-type</b> 
      </p> 
      <a name="fhir-format-type"> </a> 
      <a name="hcfhir-format-type"> </a> 
      <a name="fhir-format-type-en-US"> </a> 
      <p> This case-sensitive code system 
        <code> http://hl7.org/fhir/fhir-format-type</code>  defines the following codes:
      </p> 
      <table class="codes">
        <tr> 
          <td style="white-space:nowrap">
            <b> Code</b> 
          </td> 
          <td> 
            <b> Display</b> 
          </td> 
          <td> 
            <b> Definition</b> 
          </td> 
        </tr> 
        <tr> 
          <td style="white-space:nowrap">xml
            <a name="fhir-format-type-xml"> </a> 
          </td> 
          <td> XML</td> 
          <td> XML content-type corresponding to the application/fhir+xml mime-type.</td> 
        </tr> 
        <tr> 
          <td style="white-space:nowrap">json
            <a name="fhir-format-type-json"> </a> 
          </td> 
          <td> JSON</td> 
          <td> JSON content-type corresponding to the application/fhir+json mime-type.</td> 
        </tr> 
        <tr> 
          <td style="white-space:nowrap">ttl
            <a name="fhir-format-type-ttl"> </a> 
          </td> 
          <td> TTL</td> 
          <td> RDF content-type corresponding to the text/turtle mime-type.</td> 
        </tr> 
      </table> 
    </div> 
  </text> 
  <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
    <valueInteger value="5"/> 
  </extension> 
  <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-wg">
    <valueCode value="fhir"/> 
  </extension> 
  <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status">
    <valueCode value="normative"/> 
  </extension> 
  <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-normative-version">
    <valueCode value="4.0.0"/> 
  </extension> 
  <url value="http://hl7.org/fhir/fhir-format-type"/> 
  <identifier> 
    <system value="urn:ietf:rfc:3986"/> 
    <value value="urn:oid:2.16.840.1.113883.4.642.4.1911"/> 
  </identifier> 
  <version value="6.0.0-ballot2"/> 
  <name value="FHIRFormatType"/> 
  <title value="FHIR Format Type"/> 
  <status value="active"/> 
  <experimental value="false"/> 
  <date value="2022-08-17"/> 
  <publisher value="HL7"/> 
  <description value="FHIR Format types"/> 
  <jurisdiction> 
    <coding> 
      <system value="http://unstats.un.org/unsd/methods/m49/m49.htm"/> 
      <code value="001"/> 
      <display value="World"/> 
    </coding> 
  </jurisdiction> 
  <caseSensitive value="true"/> 
  <valueSet value="http://hl7.org/fhir/ValueSet/fhir-content-type"/> 
  <content value="complete"/> 
  <concept> 
    <code value="xml"/> 
    <display value="XML"/> 
    <definition value="XML content-type corresponding to the application/fhir+xml mime-type."/> 
  </concept> 
  <concept> 
    <code value="json"/> 
    <display value="JSON"/> 
    <definition value="JSON content-type corresponding to the application/fhir+json mime-type."/> 
  </concept> 
  <concept> 
    <code value="ttl"/> 
    <display value="TTL"/> 
    <definition value="RDF content-type corresponding to the text/turtle mime-type."/> 
  </concept> 
</CodeSystem> 

Usage note: every effort has been made to ensure that the examples are correct and useful, but they are not a normative part of the specification.