HL7 Terminology (THO)
6.0.2 - Continuous Process Integration (ci build)
HL7 Terminology (THO), published by HL7 International - Vocabulary Work Group. This guide is not an authorized publication; it is the continuous build for version 6.0.2 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/UTG/ and changes regularly. See the Directory of published versions
Official URL: http://terminology.hl7.org/ValueSet/v2-0299 | Version: 2.0.0 | |||
Active as of 2019-12-01 | Responsible: Health Level Seven International | Computable Name: Hl7VSEncoding | ||
Other Identifiers: OID:2.16.840.1.113883.21.197 | ||||
Copyright/Legal: 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.html |
Concept identifying the type of IETF encoding used to represent successive octets of binary data as displayable ASCII characters.
References
This value set is not used here; it may be used elsewhere (e.g. specifications and/or implementations that use this content)
Generated Narrative: ValueSet v2-0299
http://terminology.hl7.org/CodeSystem/v2-0299
Generated Narrative: ValueSet
Expansion based on codesystem encoding v2.0.0 (CodeSystem)
This value set contains 3 concepts
Code | System | Display | Definition |
A | http://terminology.hl7.org/CodeSystem/v2-0299 | No encoding - data are displayable ASCII characters. | No encoding - data are displayable ASCII characters. |
Hex | http://terminology.hl7.org/CodeSystem/v2-0299 | Hexadecimal encoding - consecutive pairs of hexadecimal digits represent consecutive single octets. | Hexadecimal encoding - consecutive pairs of hexadecimal digits represent consecutive single octets. |
Base64 | http://terminology.hl7.org/CodeSystem/v2-0299 | 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 “=”. |
Explanation of the columns that may appear on this page:
Level | A few code lists that FHIR defines are hierarchical - each code is assigned a level. In this scheme, some codes are under other codes, and imply that the code they are under also applies |
System | The source of the definition of the code (when the value set draws in codes defined elsewhere) |
Code | The code (used as the code in the resource instance) |
Display | The display (used in the display element of a Coding). If there is no display, implementers should not simply display the code, but map the concept into their application |
Definition | An explanation of the meaning of the concept |
Comments | Additional notes about how to use the code |
History
Date | Action | Custodian | Author | Comment |
2023-11-14 | revise | TSMG | Marc Duteau | Add standard copyright and contact to internal content; up-476 |
2020-05-06 | revise | Vocabulary WG | Ted Klein | Migrated to the UTG maintenance environment and publishing tooling. |