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

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 concept identifying the type of encoding used to represent successive octets of binary data as displayable ASCII characters. These are defined by IETF; more information may be found at https://www.ietf.org/rfc/rfc1521.txt. Used in HL7 Version 2.x messaging in the ED datatypes.
              experimentalfalse
                hierarchyMeaningis-a
                  jurisdiction
                    nameEncoding
                      publisherHealth Level Seven International
                        purposeUnderlying Master Code System for V2 table 0299 (Encoding)
                          statusactive
                            titleencoding
                              urlhttp://terminology.hl7.org/CodeSystem/v2-0299
                                version3.0.0
                                  versionNeededfalse

                                    Concepts

                                    CodeDisplaystatusv2-table-deprecatedv2-concCommentv2-concCommentAsPubstatusv2-table-deprecatedv2-concCommentv2-concCommentAsPubComments
                                    ANo encoding - data are displayable ASCII characters.activeactiveactiveactive
                                      HexHexadecimal encoding - consecutive pairs of hexadecimal digits represent consecutive single octets.activeactiveactiveactive
                                        Base64Encoding 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 andactiveactiveThe Request For Comment (RFC) 1521 standard is available at: http://www.ietf.org/rfc/rfc1521.txtThe Request For Comment (RFC) 1521 standard is available at: http://www.ietf.org/rfc/rfc1521.txtThe Request For Comment (RFC) 1521 standard is available at: http://www.ietf.org/rfc/rfc1521.txtThe Request For Comment (RFC) 1521 standard is available at: http://www.ietf.org/rfc/rfc1521.txtactiveactiveThe Request For Comment (RFC) 1521 standard is available at: http://www.ietf.org/rfc/rfc1521.txtThe Request For Comment (RFC) 1521 standard is available at: http://www.ietf.org/rfc/rfc1521.txtThe Request For Comment (RFC) 1521 standard is available at: http://www.ietf.org/rfc/rfc1521.txtThe Request For Comment (RFC) 1521 standard is available at: http://www.ietf.org/rfc/rfc1521.txt