Release 4 R5 Final QA

This page is part of the FHIR Specification (v4.0.1: R4 (v5.0.0-draft-final: Final QA Preview for R5 - Mixed Normative and STU see ballot notes ) in it's permanent home (it will always be available at this URL). ). 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: R5 R4B

R4 R3

4.3.2.421 CodeSystem http://hl7.org/fhir/CodeSystem/devicedispense-status-reason Content

Orders and Observations icon Examples Work Group   Maturity Level : 0 Detailed Descriptions Informative Use Context : Country: World
Official URL : http://hl7.org/fhir/CodeSystem/devicedispense-status-reason Version : 5.0.0-draft-final
active as of 2023-03-01 Computable Name : DeviceDispenseStatusReasonCodes
Flags : CaseSensitive, Complete OID : 2.16.840.1.113883.4.642.4.2110

This Code system is used in the following value sets:

8.14.9 4.3.2.421.1 Definition

DeviceDispense Status Reason Codes

4.3.2.421.2 Resource Device - R3/R4 Conversions Content

This code system http://hl7.org/fhir/CodeSystem/devicedispense-status-reason defines the following codes:

Maturity Level : N/A Standards Status : Informative Compartments : Not linked R3 : R4 Conversion maps for Device. Functional status for this map: 9 tests that all execute ok. All tests pass round-trip testing 8.14.9.2
Code Orders and Observations Display Definition Copy
out-of-stock Work Group Out of Stock The device was not dispensed because it was not available. btn   btn
off-market Off market The device was not dispensed because it is of-market - for example not authorized, withdrawn or recalled. btn   btn Security Category : Business
contraindication Contraindication The device was not dispensed because a contraindication was found - for example pregnancy, allergy to any defined compartments a device component... btn   btn
incompatible-device Incompatible device The device was not dispensed because an incompatibility has been found with the device or between the device and 1 r3 resources are invalid (0 errors). other devices being used in the same context. btn ( see documentation)   btn 8.14.9.1
order-expired Order expired The device was not dispensed because the order has expired or been invalidated. btn R3 to R4   btn
verbal-order map "http://hl7.org/fhir/StructureMap/Device3to4" = "R3 to R4 Conversions for Device" uses "http://hl7.org/fhir/3.0/StructureDefinition/Device" alias DeviceR3 as source uses "http://hl7.org/fhir/StructureDefinition/Device" alias Device as target imports "http://hl7.org/fhir/StructureMap/*3to4" group Device(source src : DeviceR3, target tgt : Device) extends DomainResource <<type+>> { src.identifier -> tgt.identifier; src.udi as vs0 -> tgt.udiCarrier as vt0 then { vs0.deviceIdentifier -> vt0.deviceIdentifier; vs0.name as vs -> tgt.deviceName as vt, vt.name = vs, vt.type = 'udi-label-name'; vs0.jurisdiction -> vt0.jurisdiction; vs0.carrierHRF -> vt0.carrierHRF; vs0.carrierAIDC -> vt0.carrierAIDC; vs0.issuer -> vt0.issuer; vs0.entryType -> vt0.entryType; }; src.status -> tgt.status; src.type -> tgt.type; src.lotNumber -> tgt.lotNumber; src.manufacturer -> tgt.manufacturer; src.manufactureDate -> tgt.manufactureDate; src.expirationDate -> tgt.expirationDate; src.model -> tgt.modelNumber; src.version as vs -> tgt.version as vt, vt.value = vs; src.patient -> tgt.patient; src.owner -> tgt.owner; src.contact -> tgt.contact; src.location -> tgt.location; src.url -> tgt.url; src.note -> tgt.note; src.safety -> tgt.safety; } Verbal order The device not dispensed because there was a verbal order. btn R4 to R3   btn
map "http://hl7.org/fhir/StructureMap/Device4to3" = "R4 to R3 Conversion for Device" uses "http://hl7.org/fhir/StructureDefinition/Device" alias Device as source uses "http://hl7.org/fhir/3.0/StructureDefinition/Device" alias DeviceR3 as target imports "http://hl7.org/fhir/StructureMap/*4to3" group Device(source src : Device, target tgt : DeviceR3) extends DomainResource <<type+>> { src.identifier -> tgt.identifier; src.udiCarrier as vs0 -> tgt.udi as vt0 then { vs0.deviceIdentifier -> vt0.deviceIdentifier; vs0.jurisdiction -> vt0.jurisdiction; vs0.carrierHRF -> vt0.carrierHRF; vs0.carrierAIDC -> vt0.carrierAIDC; vs0.issuer -> vt0.issuer; vs0.entryType -> vt0.entryType; }; src.status -> tgt.status; src.type -> tgt.type; src.lotNumber -> tgt.lotNumber; src.manufacturer -> tgt.manufacturer; src.manufactureDate -> tgt.manufactureDate; src.expirationDate -> tgt.expirationDate; src.modelNumber -> tgt.model; src.version as vs -> tgt as vt then { vs.value -> tgt.version; }; src.deviceName as vs -> tgt.udi as vt then { vs.name -> vt.name; }; src.patient -> tgt.patient; src.owner -> tgt.owner; src.contact -> tgt.contact; src.location -> tgt.location; src.url -> tgt.url; src.note -> tgt.note; src.safety -> tgt.safety; }

 

See the full registry of code systems defined as part of FHIR.

Explanation of the columns that may appear on this page:

8.14.9.3 R4 Validation Errors <p>No validation errors - all conversions are clean</p>
Level A few code lists that FHIR defines are hierarchical - each code is assigned a level. 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