FHIR Cross-Version Extensions package for FHIR R4 from FHIR R5
0.0.1-snapshot-2 - informative International flag

FHIR Cross-Version Extensions package for FHIR R4 from FHIR R5 - Version 0.0.1-snapshot-2. See the Directory of published versions

ValueSet: Cross-version VS for R5.Hl7VSEncoding for use in FHIR R4

Official URL: http://hl7.org/fhir/5.0/ValueSet/R5-v2-0299-for-R4 Version: 0.0.1-snapshot-2
Standards status: Informative Maturity Level: 0 Computable Name: R5_v2_0299_for_R4

This cross-version ValueSet represents concepts from http://terminology.hl7.org/ValueSet/v2-0299 2.0.0 for use in FHIR R4. Concepts not present here have direct equivalent mappings crossing all versions from R5 to R4.

References

This value set is not used here; it may be used elsewhere (e.g. specifications and/or implementations that use this content)

Logical Definition (CLD)

  • Include these codes as defined in http://terminology.hl7.org/CodeSystem/v2-0299 version 2.1.0
    CodeDisplayDefinition
    ANo encoding - data are displayable ASCII characters.No encoding - data are displayable ASCII characters.
    HexHexadecimal encoding - consecutive pairs of hexadecimal digits represent consecutive single octets.Hexadecimal encoding - consecutive pairs of hexadecimal digits represent consecutive single octets.
    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 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 “=”.

 

Expansion

This value set expansion contains 3 concepts.

CodeSystemDisplayDefinition
  Ahttp://terminology.hl7.org/CodeSystem/v2-0299No encoding - data are displayable ASCII characters.No encoding - data are displayable ASCII characters.
  Hexhttp://terminology.hl7.org/CodeSystem/v2-0299Hexadecimal encoding - consecutive pairs of hexadecimal digits represent consecutive single octets.Hexadecimal encoding - consecutive pairs of hexadecimal digits represent consecutive single octets.
  Base64http://terminology.hl7.org/CodeSystem/v2-0299Encoding 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 “=”.

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