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
Vocabulary Work Group | Maturity Level: N/A | Standards Status: Informative |
Raw XML (canonical form + also see XML Format Specification)
FHIR Value set/code system definition for HL7 v2 table 0211 ( Alternate Character Sets)
<?xml version="1.0" encoding="UTF-8"?> <ValueSet xmlns="http://hl7.org/fhir"> <id value="v2-0211"/> <meta> <profile value="http://hl7.org/fhir/StructureDefinition/shareablevalueset"/> </meta> <language value="en"/> <text> <status value="additional"/> <div xmlns="http://www.w3.org/1999/xhtml"> <p> Alternate Character Sets</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> 8859/1 <a name="8859.471"> </a> </td> <td> The printable characters from the ISO 8859/1 Character set</td> <td/> <td> added v2.3</td> </tr> <tr> <td> 8859/15 <a name="8859.4715"> </a> </td> <td> The printable characters from the ISO 8859/15 (Latin-15)</td> <td/> <td> added v2.6</td> </tr> <tr> <td> 8859/2 <a name="8859.472"> </a> </td> <td> The printable characters from the ISO 8859/2 Character set</td> <td/> <td> added v2.3</td> </tr> <tr> <td> 8859/3 <a name="8859.473"> </a> </td> <td> The printable characters from the ISO 8859/3 Character set</td> <td/> <td> added v2.3</td> </tr> <tr> <td> 8859/4 <a name="8859.474"> </a> </td> <td> The printable characters from the ISO 8859/4 Character set</td> <td/> <td> added v2.3</td> </tr> <tr> <td> 8859/5 <a name="8859.475"> </a> </td> <td> The printable characters from the ISO 8859/5 Character set</td> <td/> <td> added v2.3</td> </tr> <tr> <td> 8859/6 <a name="8859.476"> </a> </td> <td> The printable characters from the ISO 8859/6 Character set</td> <td/> <td> added v2.3</td> </tr> <tr> <td> 8859/7 <a name="8859.477"> </a> </td> <td> The printable characters from the ISO 8859/7 Character set</td> <td/> <td> added v2.3</td> </tr> <tr> <td> 8859/8 <a name="8859.478"> </a> </td> <td> The printable characters from the ISO 8859/8 Character set</td> <td/> <td> added v2.3</td> </tr> <tr> <td> 8859/9 <a name="8859.479"> </a> </td> <td> The printable characters from the ISO 8859/9 Character set</td> <td/> <td> added v2.3</td> </tr> <tr> <td> ASCII <a name="ASCII"> </a> </td> <td> The printable 7-bit ASCII character set.</td> <td> (This is the default if this field is omitted)</td> <td> added v2.3</td> </tr> <tr> <td> BIG-5 <a name="BIG-5"> </a> </td> <td> Code for Taiwanese Character Set (BIG-5)</td> <td> Does not need an escape sequence. BIG-5 does not need an escape sequence. ASCII is a 7 bit character set, which means that the top bit of the byte is “0�. The parser knows that when the top bit of the byte is “0�, the character set is ASCII. When it is “1�, the following bytes should be handled as 2 bytes (or more). No escape technique is needed. However, since some servers do not correctly interpret when they receive a top bit “1�, it is advised, in internet RFC, to not use these kind of non-safe non-escape extension.</td> <td> added v2.5</td> </tr> <tr> <td> CNS 11643-1992 <a name="CNS11643-1992"> </a> </td> <td> Code for Taiwanese Character Set (CNS 11643-1992)</td> <td> Does not need an escape sequence.</td> <td> added v2.5</td> </tr> <tr> <td> GB 18030-2000 <a name="GB18030-2000"> </a> </td> <td> Code for Chinese Character Set (GB 18030-2000)</td> <td> Does not need an escape sequence.</td> <td> added v2.5</td> </tr> <tr> <td> ISO IR14 <a name="ISOIR14"> </a> </td> <td> Code for Information Exchange (one byte)(JIS X 0201-1976).</td> <td> Note that the code contains a space, i.e., "ISO IR14".</td> <td> added v2.3.1</td> </tr> <tr> <td> ISO IR159 <a name="ISOIR159"> </a> </td> <td> Code of the supplementary Japanese Graphic Character set for information interchange (JIS X 0212-1990).</td> <td> Note that the code contains a space, i.e., "ISO IR159".</td> <td> added v2.3.1</td> </tr> <tr> <td> ISO IR6 <a name="ISOIR6"> </a> </td> <td> ASCII graphic character set consisting of 94 characters.</td> <td> http://www.itscj.ipsj.or.jp/ISO-IR/006.pdf</td> <td> added v2.7</td> </tr> <tr> <td> ISO IR87 <a name="ISOIR87"> </a> </td> <td> Code for the Japanese Graphic Character set for information interchange (JIS X 0208-1990),</td> <td> Note that the code contains a space, i.e., “ISO IR87�. The JIS X 0208 needs an escape sequence. In Japan, the escape technique is ISO 2022. From basic ASCII, escape sequence “escape� $ B (in HEX, 1B 24 42) lets the parser know that following bytes should be handled 2-byte wise. Back to ASCII is 1B 28 42.</td> <td> added v2.3.1</td> </tr> <tr> <td> JAS2020 <a name="JAS2020"> </a> </td> <td> A subset of ISO2020 used for most Kanjii transmissions</td> <td> deprecated</td> <td> added v2.3, removed after v2.3</td> </tr> <tr> <td> JIS X 0202 <a name="JISX0202"> </a> </td> <td> ISO 2022 with escape sequences for Kanjii</td> <td> deprecated</td> <td> added v2.3, removed after v2.3</td> </tr> <tr> <td> KS X 1001 <a name="KSX1001"> </a> </td> <td> Code for Korean Character Set (KS X 1001)</td> <td/> <td> added v2.5</td> </tr> <tr> <td> UNICODE <a name="UNICODE"> </a> </td> <td> The world wide character standard from ISO/IEC 10646-1-1993</td> <td> Deprecated. Retained for backward compatibility only as v 2.5. Replaced by specific Unicode encoding codes.</td> <td> added v2.3</td> </tr> <tr> <td> UNICODE UTF-16 <a name="UNICODEUTF-16"> </a> </td> <td> UCS Transformation Format, 16-bit form</td> <td> UTF-16 is identical to ISO/IEC 10646 UCS-2. Note that the code contains a space before UTF but not before and after the hyphen.</td> <td> added v2.5, removed after v2.7.1</td> </tr> <tr> <td> UNICODE UTF-32 <a name="UNICODEUTF-32"> </a> </td> <td> UCS Transformation Format, 32-bit form</td> <td> UTF-32 is defined by Unicode Technical Report #19, and is an officially recognized encoding as of Unicode Version 3.1. UTF-32 is a proper subset of ISO/IEC 10646 UCS-4. Note that the code contains a space before UTF but not before and after the hyphen.</td> <td> added v2.5, removed after v2.7.1</td> </tr> <tr> <td> UNICODE UTF-8 <a name="UNICODEUTF-8"> </a> </td> <td> UCS Transformation Format, 8-bit form</td> <td> UTF-8 is a variable-length encoding, each code value is represented by 1,2 or 3 bytes, depending on the code value. 7 bit ASCII is a proper subset of UTF-8. Note that the code contains a space before UTF but not before and after the hyphen. Since UTF-8 represents the full UNICODE character set, the following restriction apply to its use: 1. UTF-8 must be the default encoding of the message, UTF-8 cannot be specified as an additional character set in MSH-18 2. There are no other character sets allowed in a message where UTF-8 is the default encoding in the message. In other words, UNICODE UTF-8 can only be specified as a single value in MSH-18 3. A message encoded in UTF-8 must not use a Byte Order Mark (BOM).</td> <td> added v2.5</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/ValueSet/v2-0211"/> <version value="2.9"/> <name value="v2.0211"/> <title value="v2 Alternate Character Sets"/> <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 0211 ( Alternate Character Sets)"/> <immutable value="true"/> <compose> <include> <system value="http://terminology.hl7.org/CodeSystem/v2-0211"/> </include> </compose> </ValueSet>
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.