Release 4

This page is part of the FHIR Specification (v4.0.1: R4 - Mixed Normative and STU) in it's permanent home (it will always be available at this URL). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions . Page versions: R4 R3

V2-0299.cs.xml

Vocabulary Work GroupMaturity Level: N/AStandards Status: Informative

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

FHIR Value set/code system definition for HL7 v2 table 0299 ( Encoding)

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

<CodeSystem xmlns="http://hl7.org/fhir">
  <id value="v2-0299"/> 
  <meta> 
    <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"/> 
  </meta> 
  <language value="en"/> 
  <text> 
    <status value="additional"/> 
    <div xmlns="http://www.w3.org/1999/xhtml">
      <p> Encoding</p> 

      <table class="grid">
        <tr> 
          <td> 
            <b> Code</b> 
          </td> 
          <td> 
            <b> Description</b> 
          </td> 
          <td> 
            <b> Comment</b> 
          </td> 
          <td> 
            <b> Version</b> 
          </td> 
        </tr> 
        <tr> 
          <td> A
            <a name="A"> </a> 
          </td> 
          <td> No encoding - data are displayable ASCII characters.</td> 
          <td/>  
          <td> added v2.3</td> 
        </tr> 
        <tr> 
          <td> Base64
            <a name="Base64"> </a> 
          </td> 
          <td> Encoding as defined by MIME (Multipurpose Internet Mail Extensions) standard RFC 1521.
               Four consecutive ASCII characters represent three consecutive octets of binary data. Base64
               utilizes a 65-character subset of US-ASCII, consisting of both the upper and</td> 
          <td> The Request For Comment (RFC) 1521 standard is available at: http://www.ietf.org/rfc/rfc1521.txt</td> 
          <td> added v2.3</td> 
        </tr> 
        <tr> 
          <td> Hex
            <a name="Hex"> </a> 
          </td> 
          <td> Hexadecimal encoding - consecutive pairs of hexadecimal digits represent consecutive single
               octets.</td> 
          <td/>  
          <td> added v2.3</td> 
        </tr> 
      </table> 

    </div> 
  </text> 
  <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status">
    <valueCode value="external"/> 
  </extension> 
  <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
    <valueInteger value="0"/> 
  </extension> 
  <url value="http://terminology.hl7.org/CodeSystem/v2-0299"/> 
  <identifier> 
    <system value="urn:ietf:rfc:3986"/> 
    <value value="urn:oid:2.16.840.1.113883.18.185"/> 
  </identifier> 
  <version value="2.9"/> 
  <name value="v2.0299"/> 
  <title value="v2 Encoding"/> 
  <status value="active"/> 
  <experimental value="false"/> 
  <publisher value="HL7, Inc"/> 
  <contact> 
    <telecom> 
      <system value="url"/> 
      <value value="http://hl7.org"/> 
    </telecom> 
  </contact> 
  <description value="FHIR Value set/code system definition for HL7 v2 table 0299 ( Encoding)"/> 
  <content value="complete"/> 
  <concept> 
    <code value="A"/> 
    <display value="No encoding - data are displayable ASCII characters."/> 
    <designation> 
      <language value="de"/> 
      <use> 
        <system value="http://terminology.hl7.org/CodeSystem/designation-usage"/> 
        <code value="display"/> 
      </use> 
      <value value="keine Kodierung"/> 
    </designation> 
    <designation> 
      <language value="nl"/> 
      <use> 
        <system value="http://terminology.hl7.org/CodeSystem/designation-usage"/> 
        <code value="display"/> 
      </use> 
      <value value="geen codering - gegevens zijn leesbare ASCII-tekens"/> 
    </designation> 
  </concept> 
  <concept> 
    <extension url="http://hl7.org/fhir/StructureDefinition/codesystem-concept-comments">
      <valueString value="The Request For Comment (RFC) 1521 standard is available at: http://www.ietf.org/rfc/rfc1521.txt">
        <extension url="http://hl7.org/fhir/StructureDefinition/translation">
          <extension url="lang">
            <valueCode value="nl"/> 
          </extension> 
          <extension url="content">
            <valueString value="De Request For Comment (RFC) 1521 standaard is vinden via: http://www.ietf.org/rfc/rfc1521.txt"/> 
          </extension> 
        </extension> 
      </valueString> 
    </extension> 
    <code value="Base64"/> 
    <display value="Encoding as defined by MIME (Multipurpose Internet Mail Extensions) standard RFC 1521.
       Four consecutive ASCII characters represent three consecutive octets of binary data. Base64
       utilizes a 65-character subset of US-ASCII, consisting of both the upper and"/> 
    <designation> 
      <language value="nl"/> 
      <use> 
        <system value="http://terminology.hl7.org/CodeSystem/designation-usage"/> 
        <code value="display"/> 
      </use> 
      <value value="codering zoals gedefinieerd door MIME (Multipurpose Internet Mail Extensions) standaard
         RFC 1521. Vier opeenvolgende ASCII-tekens stellen drie, enkelvoudige octetten binaire
         gegevens voor. Base64 gebruikt een subset van 65-tekens uit US-ASCII, bestaande uit zowel
         de alfabetische hoofd- als de kleine letters, de cijfers &quot;0&quot; tot en met &quot;9&quot;,
         &quot;+&quot;, &quot;/&quot; en &quot;=&quot;."/> 
    </designation> 
  </concept> 
  <concept> 
    <code value="Hex"/> 
    <display value="Hexadecimal encoding - consecutive pairs of hexadecimal digits represent consecutive single
       octets."/> 
    <designation> 
      <language value="nl"/> 
      <use> 
        <system value="http://terminology.hl7.org/CodeSystem/designation-usage"/> 
        <code value="display"/> 
      </use> 
      <value value="hexadecimale codering - paarsgewijze hexadecimale getallen stellen sequentiële, enkelvoudige
         octetten voor"/> 
    </designation> 
  </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.