This page is part of the FHIR Specification (v3.3.0: R4 Ballot 2). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions . Page versions: R4 R3 R2
Imaging Integration Work Group | Maturity Level: 0 | Informative | Use Context: Any |
This is a value set defined by the FHIR project.
Summary
Defining URL: | http://hl7.org/fhir/ValueSet/instance-availability |
Name: | InstanceAvailability |
Definition: | Availability of the resource |
Committee: | Imaging Integration Work Group |
OID: | 2.16.840.1.113883.4.642.3.286 (for OID based terminology systems) |
Copyright: | These codes are excerpted from Digital Imaging and Communications in Medicine (DICOM) Standard, Part 16: Content Mapping Resource, Copyright 2011 by the National Electrical Manufacturers Association |
Source Resource | XML / JSON |
This value set is not currently used
This value set includes codes from the following code systems:
http://dicom.nema.org/resources/ontology/DCM
Code | Display | Definition |
ONLINE | Online | Resources are immediately available. |
OFFLINE | Offline | Resources need to be retrieved by manual intervention. |
NEARLINE | Nearline | Resources need to be retrieved from relatively slow media. |
UNAVAILABLE | Unavailable | Resources cannot be retrieved. |
See the full registry of value sets defined as part of FHIR.
Explanation of the columns that may appear on this page:
Lvl | A few code lists that FHIR defines are hierarchical - each code is assigned a level. For value sets, levels are mostly used to organize codes for user convenience, but may follow code system hierarchy - see Code System for further information |
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). If the code is in italics, this indicates that the code is not selectable ('Abstract') |
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 |