Union of http://terminology.hl7.org/CodeSystem/v2-0299 and http://terminology.hl7.org/CodeSystem/v2-0299

This is the CodeSystem that contains all the codes in encoding (http://terminology.hl7.org/CodeSystem/v2-0299) and encoding (http://terminology.hl7.org/CodeSystem/v2-0299). E.g. what you have to deal with if you get resources containing codes in either of them

CodeSystem

Generated Narrative: CodeSystem 5127f8b7-6ff3-42d1-85bd-471f7469a43a-2168

Properties

This code system defines the following properties for its concepts

NameCodeURITypeDescription
statusstatushttp://terminology.hl7.org/CodeSystem/utg-concept-properties#statuscodeStatus of the concept
deprecateddeprecatedhttp://terminology.hl7.org/CodeSystem/utg-concept-properties#v2-table-deprecatedcodeVersion of HL7 in which the code was deprecated
V2 Concept Commentv2-concCommenthttp://terminology.hl7.org/CodeSystem/utg-concept-properties#v2-concCommentstringV2 Concept Comment
V2 Concept Comment As Publishedv2-concCommentAsPubhttp://terminology.hl7.org/CodeSystem/utg-concept-properties#v2-concCommentAsPubstringV2 Concept Comment As Published
statusstatushttp://terminology.hl7.org/CodeSystem/utg-concept-properties#statuscodeStatus of the concept
deprecateddeprecatedhttp://terminology.hl7.org/CodeSystem/utg-concept-properties#v2-table-deprecatedcodeVersion of HL7 in which the code was deprecated
V2 Concept Commentv2-concCommenthttp://terminology.hl7.org/CodeSystem/utg-concept-properties#v2-concCommentstringV2 Concept Comment
V2 Concept Comment As Publishedv2-concCommentAsPubhttp://terminology.hl7.org/CodeSystem/utg-concept-properties#v2-concCommentAsPubstringV2 Concept Comment As Published

Concepts

This code system http://hl7.org/fhir/comparison/CodeSystem/5127f8b7-6ff3-42d1-85bd-471f7469a43a-2168 defines codes, but no codes are represented here

CodeDisplayDefinitionstatusV2 Concept CommentV2 Concept Comment As PublishedstatusV2 Concept CommentV2 Concept Comment As PublishedDeutsch (German, de)
A No encoding - data are displayable ASCII characters.No encoding - data are displayable ASCII characters.A, AA, Akeine Kodierung
Hex Hexadecimal encoding - consecutive pairs of hexadecimal digits represent consecutive single octets.Hexadecimal encoding - consecutive pairs of hexadecimal digits represent consecutive single octets.A, AA, A
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 andEncoding 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 “=”.A, AThe 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.txtThe 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.txtA, AThe 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.txtThe 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