CodeSystem Comparison between http://terminology.hl7.org/CodeSystem/v2-0211 vs http://terminology.hl7.org/CodeSystem/v2-0211

Messages

Metadata

NameValueComments
.caseSensitivetrue
    .compositionalfalse
      .contentcomplete
        .copyrightThis material derives from the HL7 Terminology (THO). THO is copyright ©1989+ Health Level Seven International and is made available under the CC0 designation. For more licensing information see: https://terminology.hl7.org/license.html
          .date2019-12-01
            .descriptionHL7-defined code system of concepts used to specify the character set(s) in use. Includes both single-byte and double-byte characters sets, and used in Version 2.x messaging in the MSH segment.
              .experimentalfalse
                .hierarchyMeaningis-a
                  .jurisdiction
                    .nameAlternateCharacterSets
                      .publisherHealth Level Seven International
                        .purposeUnderlying Master Code System for V2 table 0211 (Alternate Character Sets)
                          .statusactive
                            .titlealternateCharacterSets
                              .urlhttp://terminology.hl7.org/CodeSystem/v2-0211
                                .version2.0.0
                                  .versionNeededfalse

                                    Concepts

                                    CodeDisplaystatusdeprecatedv2-concCommentv2-concCommentAsPubHL7usageNotesstatusdeprecatedv2-concCommentv2-concCommentAsPubHL7usageNotesComments
                                    .JAS2020A subset of ISO2020 used for most Kanjii transmissionsAA2.92.9AA2.92.9
                                      .JIS X 0202ISO 2022 with escape sequences for KanjiiAA2.92.9AA2.92.9
                                        .ASCIIThe printable 7-bit ASCII character set.AA(This is the default if this field is omitted)(This is the default if this field is omitted)(This is the default if this field is omitted)(This is the default if this field is omitted)AA(This is the default if this field is omitted)(This is the default if this field is omitted)(This is the default if this field is omitted)(This is the default if this field is omitted)
                                          .8859/1The printable characters from the ISO 8859/1 Character setAAAA
                                            .8859/2The printable characters from the ISO 8859/2 Character setAAAA
                                              .8859/3The printable characters from the ISO 8859/3 Character setAAAA
                                                .8859/4The printable characters from the ISO 8859/4 Character setAAAA
                                                  .8859/5The printable characters from the ISO 8859/5 Character setAAAA
                                                    .8859/6The printable characters from the ISO 8859/6 Character setAAAA
                                                      .8859/7The printable characters from the ISO 8859/7 Character setAAAA
                                                        .8859/8The printable characters from the ISO 8859/8 Character setAAAA
                                                          .8859/9The printable characters from the ISO 8859/9 Character setAAAA
                                                            .8859/15The printable characters from the ISO 8859/15 (Latin-15)AAAA
                                                              .ISO IR6ASCII graphic character set consisting of 94 characters.AAhttp://www.itscj.ipsj.or.jp/ISO-IR/006.pdfhttp://www.itscj.ipsj.or.jp/ISO-IR/006.pdfhttp://www.itscj.ipsj.or.jp/ISO-IR/006.pdfhttp://www.itscj.ipsj.or.jp/ISO-IR/006.pdfAAhttp://www.itscj.ipsj.or.jp/ISO-IR/006.pdfhttp://www.itscj.ipsj.or.jp/ISO-IR/006.pdfhttp://www.itscj.ipsj.or.jp/ISO-IR/006.pdfhttp://www.itscj.ipsj.or.jp/ISO-IR/006.pdf
                                                                .ISO IR14Code for Information Exchange (one byte)(JIS X 0201-1976).AANote that the code contains a space, i.e., "ISO IR14".Note that the code contains a space, i.e., "ISO IR14".Note that the code contains a space, i.e., "ISO IR14".Note that the code contains a space, i.e., "ISO IR14".AANote that the code contains a space, i.e., "ISO IR14".Note that the code contains a space, i.e., "ISO IR14".Note that the code contains a space, i.e., "ISO IR14".Note that the code contains a space, i.e., "ISO IR14".
                                                                  .ISO IR87Code for the Japanese Graphic Character set for information interchange (JIS X 0208-1990),AANote 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.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.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.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.AANote 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.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.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.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.
                                                                    .ISO IR159Code of the supplementary Japanese Graphic Character set for information interchange (JIS X 0212-1990).AANote that the code contains a space, i.e., "ISO IR159".Note that the code contains a space, i.e., "ISO IR159".Note that the code contains a space, i.e., "ISO IR159".Note that the code contains a space, i.e., "ISO IR159".AANote that the code contains a space, i.e., "ISO IR159".Note that the code contains a space, i.e., "ISO IR159".Note that the code contains a space, i.e., "ISO IR159".Note that the code contains a space, i.e., "ISO IR159".
                                                                      .GB 18030-2000Code for Chinese Character Set (GB 18030-2000)AADoes not need an escape sequence.Does not need an escape sequence.Does not need an escape sequence.Does not need an escape sequence.AADoes not need an escape sequence.Does not need an escape sequence.Does not need an escape sequence.Does not need an escape sequence.
                                                                        .KS X 1001Code for Korean Character Set (KS X 1001)AAAA
                                                                          .CNS 11643-1992Code for Taiwanese Character Set (CNS 11643-1992)AADoes not need an escape sequence.Does not need an escape sequence.Does not need an escape sequence.Does not need an escape sequence.AADoes not need an escape sequence.Does not need an escape sequence.Does not need an escape sequence.Does not need an escape sequence.
                                                                            .BIG-5Code for Taiwanese Character Set (BIG-5)AADoes 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.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.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.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.AADoes 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.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.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.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.
                                                                              .UNICODEThe world wide character standard from ISO/IEC 10646-1-1993AADeprecated. Retained for backward compatibility only as v 2.5. Replaced by specific Unicode encoding codes.Deprecated. Retained for backward compatibility only as v 2.5. Replaced by specific Unicode encoding codes.Deprecated. Retained for backward compatibility only as v 2.5. Replaced by specific Unicode encoding codes.Deprecated. Retained for backward compatibility only as v 2.5. Replaced by specific Unicode encoding codes.Available from The Unicode Consortium, P.O. Box 700519, San Jose, CA 95170-0519. See http://www.unicode.org/unicode/consortium/consort.htmlAvailable from The Unicode Consortium, P.O. Box 700519, San Jose, CA 95170-0519. See http://www.unicode.org/unicode/consortium/consort.htmlAADeprecated. Retained for backward compatibility only as v 2.5. Replaced by specific Unicode encoding codes.Deprecated. Retained for backward compatibility only as v 2.5. Replaced by specific Unicode encoding codes.Deprecated. Retained for backward compatibility only as v 2.5. Replaced by specific Unicode encoding codes.Deprecated. Retained for backward compatibility only as v 2.5. Replaced by specific Unicode encoding codes.Available from The Unicode Consortium, P.O. Box 700519, San Jose, CA 95170-0519. See http://www.unicode.org/unicode/consortium/consort.htmlAvailable from The Unicode Consortium, P.O. Box 700519, San Jose, CA 95170-0519. See http://www.unicode.org/unicode/consortium/consort.html
                                                                                .UNICODE UTF-8UCS Transformation Format, 8-bit formAAUTF-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).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).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).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).AAUTF-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).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).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).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).
                                                                                  .UNICODE UTF-16UCS Transformation Format, 16-bit formAA2.92.9UTF-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.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.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.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.AA2.92.9UTF-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.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.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.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.
                                                                                    .UNICODE UTF-32UCS Transformation Format, 32-bit formAA2.92.9UTF-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.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.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.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.AA2.92.9UTF-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.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.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.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.