v2-0299
type: CodeSystem
node role: treeRoot
id:
  v: v2-0299
text:
  status:
    v: generated
  div: Properties This code system defines the following properties for its concepts Code URI Type Description status http://terminology.hl7.org/CodeSystem/utg-concept-properties#status code Status of the concept deprecated http://terminology.hl7.org/CodeSystem/utg-concept-properties#v2-table-deprecated code Version of HL7 in which the code was deprecated v2-concComment http://terminology.hl7.org/CodeSystem/utg-concept-properties#v2-concComment string V2 Concept Comment v2-concCommentAsPub http://terminology.hl7.org/CodeSystem/utg-concept-properties#v2-concCommentAsPub string V2 Concept Comment As Published Concepts This case-sensitive code system http://terminology.hl7.org/CodeSystem/v2-0299 defines the following codes in a Is-A heirarchy: Code Display Definition V2 Concept Comment V2 Concept Comment As Published Deutsch (German, de) A No encoding - data are displayable ASCII characters. No encoding - data are displayable ASCII characters. keine Kodierung Hex Hexadecimal encoding - consecutive pairs of hexadecimal digits represent consecutive single octets. Hexadecimal encoding - consecutive pairs of hexadecimal digits represent consecutive single octets. Base64 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 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 lower case alphabetic characters, digits “0” through “9”, “+”, “/”, and “=”. The Request For Comment (RFC) 1521 standard is available at: http://www.ietf.org/rfc/rfc1521.txt The Request For Comment (RFC) 1521 standard is available at: http://www.ietf.org/rfc/rfc1521.txt
url:
  v: http://terminology.hl7.org/CodeSystem/v2-0299
identifier:
  system:
    v: urn:ietf:rfc:3986
  value:
    v: urn:oid:2.16.840.1.113883.18.185
version:
  v: 2.0.0
name:
  v: Encoding
title:
  v: encoding
status:
  v: active
experimental:
  v: false
date:
  v: 2019-12-01
publisher:
  v: Health Level Seven International
contact:
  telecom:
    system:
      v: url
    value:
      v: http://hl7.org
  telecom:
    system:
      v: email
description:
  v: HL7-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.
purpose:
  v: Underlying Master Code System for V2 table 0299 (Encoding)
copyright:
  v: This 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
case sensitive:
  v: true
value set:
  v: http://terminology.hl7.org/ValueSet/v2-0299
  link: http://terminology.hl7.org/ValueSet/v2-0299
hierarchy meaning:
  v: is-a
compositional:
  v: false
version needed:
  v: false
content:
  v: complete
property:
  code:
    v: status
  uri:
    v: http://terminology.hl7.org/CodeSystem/utg-concept-properties#status
  description:
    v: Status of the concept
  type:
    v: code
property:
  code:
    v: deprecated
  uri:
    v: http://terminology.hl7.org/CodeSystem/utg-concept-properties#v2-table-deprecated
  description:
    v: Version of HL7 in which the code was deprecated
  type:
    v: code
property:
  code:
    v: v2-concComment
  uri:
    v: http://terminology.hl7.org/CodeSystem/utg-concept-properties#v2-concComment
  description:
    v: V2 Concept Comment
  type:
    v: string
property:
  code:
    v: v2-concCommentAsPub
  uri:
    v: http://terminology.hl7.org/CodeSystem/utg-concept-properties#v2-concCommentAsPub
  description:
    v: V2 Concept Comment As Published
  type:
    v: string
concept:
  id:
    v: 2974
  code:
    v: A
  display:
    v: No encoding - data are displayable ASCII characters.
  definition:
    v: No encoding - data are displayable ASCII characters.
  designation:
    language:
      v: de
    use:
      system:
        v: http://terminology.hl7.org/CodeSystem/hl7TermMaintInfra
      code:
        v: preferredForLanguage
    value:
      v: keine Kodierung
  property:
    code:
      v: status
    value:
      v: A
concept:
  id:
    v: 2975
  code:
    v: Hex
  display:
    v: Hexadecimal encoding - consecutive pairs of hexadecimal digits represent consecutive single octets.
  definition:
    v: Hexadecimal encoding - consecutive pairs of hexadecimal digits represent consecutive single octets.
  property:
    code:
      v: status
    value:
      v: A
concept:
  id:
    v: 2976
  code:
    v: Base64
  display:
    v: 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
  definition:
    v: 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 lower case alphabetic characters, digits “0” through “9”, “+”, “/”, and “=”.
  property:
    code:
      v: v2-concComment
    value:
      v: The Request For Comment (RFC) 1521 standard is available at: http://www.ietf.org/rfc/rfc1521.txt
  property:
    code:
      v: v2-concCommentAsPub
    value:
      v: The Request For Comment (RFC) 1521 standard is available at: http://www.ietf.org/rfc/rfc1521.txt
  property:
    code:
      v: status
    value:
      v: A