IHE FormatCode Vocabulary
1.3.0 - normative
This page is part of the IHE FormatCode Vocabulary (v1.3.0: Publication - Normative) based on FHIR (HL7® FHIR® Standard) R4. This is the current published version in its permanent home (it will always be available at this URL). For a full list of available versions, see the Directory of published versions
Official URL: https://profiles.ihe.net/fhir/ihe.formatcode.fhir/ImplementationGuide/ihe.formatcode.fhir | Version: 1.3.0 | |||
Active as of 2024-05-23 | Computable Name: IHE_FORMATCODE |
This Implementation Guide publishes the IHE vocabulary for FormatCode and the IHE managed ValueSet for FormatCode. Given that the FormatCode is contributed to by many IHE domains, this IG is dedicated to the publication and management of the FormatCode vocabulary.
FormatCode is a metadata element for identifying the technical format that a document follows. This is related to mimeType, but is more specific to the content requirements than the encoding requirement. Therefore a document following a FormatCode may have many mimeType encodings. The FormatCode is also related to the document type (e.g. LOINC document type), but is more specific to the requirements (constraints) of the content.
The main sections of this IG are:
This is an R4 IG. None of the features it uses are changed in R4B, so it can be used as is with R4B systems. Packages for both R4 (ihe.formatcode.fhir.r4) and R4B (ihe.formatcode.fhir.r4b) are available.
IG | Package | FHIR | Comment |
---|---|---|---|
ihe.formatcode.fhir#1.3.0 | R4 | ||
hl7.terminology.r4#5.5.0 | R4 | Automatically added as a dependency - all IGs depend on HL7 Terminology | |
hl7.fhir.uv.extensions.r4#5.1.0 | R4 | Automatically added as a dependency - all IGs depend on the HL7 Extension Pack |
Package hl7.fhir.uv.extensions.r4#5.1.0 This IG defines the global extensions - the ones defined for everyone. These extensions are always in scope wherever FHIR is being used (built Sat, Apr 27, 2024 18:39+1000+10:00) |
This publication includes IP covered under the following statements.
There are no Global profiles defined