This page is part of the FHIR Specification (v5.0.0-snapshot3: R5 Snapshot #3, to support Connectathon 32). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions
Orders and Observations Work Group | Maturity Level: 1 | Trial Use | Use Context: Country: World, Not yet ready for Production use, Not yet ready for Production use |
Official URL: http://hl7.org/fhir/ValueSet/transport-status-reason
|
Version: 5.0.0-snapshot3 | |||
draft as of 2020-12-28 | Computable Name: TransportStatusReason | |||
Flags: Experimental, Immutable | OID: 2.16.840.1.113883.4.642.3.3037 |
This value set is used in the following places:
Status reason of the transport.
http://hl7.org/fhir/transport-status-reason
This expansion generated 14 Dec 2022
This value set contains 7 concepts
Expansion based on TransportStatus v5.0.0-snapshot3 (CodeSystem)
Code | System | Display | Definition |
declined-by-patient | http://hl7.org/fhir/transport-status-reason | Declined by patient | Patient declined transport. |
refused-by-recipient | http://hl7.org/fhir/transport-status-reason | Refused by recipient | Transport was refused by recipient. |
patient-not-available | http://hl7.org/fhir/transport-status-reason | Patient not available | The patient was not available for transport. |
specimen-not-available | http://hl7.org/fhir/transport-status-reason | Specimen not available | The specimen was not available for transport. |
wrong-request-data | http://hl7.org/fhir/transport-status-reason | Wrong request data | Wrong data in the transport request. |
in-route-accident | http://hl7.org/fhir/transport-status-reason | In route accident | An accident has occurred in route. |
request-not-acknowledged | http://hl7.org/fhir/transport-status-reason | Request not acknowledged | The transport request was not acknowledged. |
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 |