HL7 Terminology (THO)
2.1.33 - Continuous Process Integration (ci build)

HL7 Terminology (THO), published by HL7 International - Vocabulary Work Group. This is not an authorized publication; it is the continuous build for version 2.1.33). This version is based on the current content of https://github.com/HL7/UTG/ and changes regularly. See the Directory of published versions

ValueSet: hl7VS-subtypeOfReferencedData

Summary

Defining URL:http://terminology.hl7.org/ValueSet/v2-notAllCodes-0291
Version:2.0.0
Name:Hl7VSSubtypeOfReferencedData
Title:hl7VS-subtypeOfReferencedData
Status:Active as of 2019-12-01
Definition:

A subset of the IANA media subtypes of binary data that are encoded in an ascii structure or stream.

Publisher:HL7, Inc
Copyright:

Copyright HL7. Licensed under creative commons public domain

OID:2.16.840.1.113883.21.193 (for OID based terminology systems)
Source Resource:XML / JSON / Turtle

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-0291 version 2.4.0
    CodeDisplayDefinition
    BASICISDN PCM audio dataISDN PCM audio data
    Source RFC 2046Source RFC 2046
    DICOMDigital Imaging and Communications in MedicineDigital Imaging and Communications in Medicine
    FAXFacsimile dataFacsimile data
    GIFGraphics Interchange FormatGraphics Interchange Format
    HTMLHypertext Markup LanguageHypertext Markup Language
    JOTElectronic ink data (Jot 1.0 standard)Electronic ink data (Jot 1.0 standard)
    JPEGJoint Photographic Experts GroupJoint Photographic Experts Group
    Octet-streamUninterpreted binary dataUninterpreted binary data
    PICTPICT format image dataPICT format image data
    PostScriptPostScript programPostScript program
    RTFRich Text FormatRich Text Format
    SGMLStandard Generalized Markup Language (HL7 V2.3.1 and later)Standard Generalized Markup Language (HL7 V2.3.1 and later)
    TIFFTIFF image dataTIFF image data
    XMLExtensible Markup Language (HL7 V2.3.1 and later)Extensible Markup Language (HL7 V2.3.1 and later)
    x-hl7-cda-level-oneHL7 Clinical Document Architecture Level One documentHL7 Clinical Document Architecture Level One document

 

Expansion

This value set contains 16 concepts

Expansion based on subtypeOfReferencedData v2.4.0 (CodeSystem)

All codes in this table are from the system http://terminology.hl7.org/CodeSystem/v2-0291

CodeDisplayDefinition
BASICISDN PCM audio dataISDN PCM audio data
Source RFC 2046Source RFC 2046
DICOMDigital Imaging and Communications in MedicineDigital Imaging and Communications in Medicine
FAXFacsimile dataFacsimile data
GIFGraphics Interchange FormatGraphics Interchange Format
HTMLHypertext Markup LanguageHypertext Markup Language
JOTElectronic ink data (Jot 1.0 standard)Electronic ink data (Jot 1.0 standard)
JPEGJoint Photographic Experts GroupJoint Photographic Experts Group
Octet-streamUninterpreted binary dataUninterpreted binary data
PICTPICT format image dataPICT format image data
PostScriptPostScript programPostScript program
RTFRich Text FormatRich Text Format
SGMLStandard Generalized Markup Language (HL7 V2.3.1 and later)Standard Generalized Markup Language (HL7 V2.3.1 and later)
TIFFTIFF image dataTIFF image data
XMLExtensible Markup Language (HL7 V2.3.1 and later)Extensible Markup Language (HL7 V2.3.1 and later)
x-hl7-cda-level-oneHL7 Clinical Document Architecture Level One documentHL7 Clinical Document Architecture Level One document

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
Source 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

DateActionCustodianAuthorComment
2020-05-06reviseVocabulary WGTed KleinMigrated to the UTG maintenance environment and publishing tooling.