Extensions for Using Data Elements from FHIR R5 in FHIR R4B
0.1.0 - STU
Extensions for Using Data Elements from FHIR R5 in FHIR R4B
0.1.0 - STU
Extensions for Using Data Elements from FHIR R5 in FHIR R4B - Downloaded Version null See the Directory of published versions
| Official URL: http://hl7.org/fhir/uv/xver/ValueSet/R5-transport-status-reason-for-R4B | Version: 0.1.0 | |||
| Standards status: Trial-use | Maturity Level: 1 | Responsible: Orders and Observations | Computable Name: R5TransportStatusReasonForR4B | |
This cross-version ValueSet represents content from http://hl7.org/fhir/ValueSet/transport-status-reason|5.0.0 for use in FHIR R4B.
This value set is part of the cross-version definitions generated to enable use of the
value set http://hl7.org/fhir/ValueSet/transport-status-reason|5.0.0 as defined in FHIR R5
in FHIR R4B.
The source value set is bound to the following FHIR R5 elements:
Transport.statusReasonNote that all concepts are included in this cross-version definition because no concepts have compatible representations
Following are the generation technical comments:
FHIR ValueSet http://hl7.org/fhir/ValueSet/transport-status-reason|5.0.0, defined in FHIR R5 does not have any mapping to FHIR R4B
References
http://hl7.org/fhir/transport-status-reason version 📍5.0.0| Code | Display | Definition |
| declined-by-patient | Declined by patient | Patient declined transport. |
| in-route-accident | In route accident | An accident has occurred in route. |
| patient-not-available | Patient not available | The patient was not available for transport. |
| refused-by-recipient | Refused by recipient | Transport was refused by recipient. |
| request-not-acknowledged | Request not acknowledged | The transport request was not acknowledged. |
| specimen-not-available | Specimen not available | The specimen was not available for transport. |
| wrong-request-data | Wrong request data | Wrong data in the transport request. |
This value set expansion contains 7 concepts.
| System | Version | Code | Display | Definition | JSON | XML |
http://hl7.org/fhir/transport-status-reason | 5.0.0 | declined-by-patient | Declined by patient | Patient declined transport. | ||
http://hl7.org/fhir/transport-status-reason | 5.0.0 | in-route-accident | In route accident | An accident has occurred in route. | ||
http://hl7.org/fhir/transport-status-reason | 5.0.0 | patient-not-available | Patient not available | The patient was not available for transport. | ||
http://hl7.org/fhir/transport-status-reason | 5.0.0 | refused-by-recipient | Refused by recipient | Transport was refused by recipient. | ||
http://hl7.org/fhir/transport-status-reason | 5.0.0 | request-not-acknowledged | Request not acknowledged | The transport request was not acknowledged. | ||
http://hl7.org/fhir/transport-status-reason | 5.0.0 | specimen-not-available | Specimen not available | The specimen was not available for transport. | ||
http://hl7.org/fhir/transport-status-reason | 5.0.0 | wrong-request-data | Wrong request data | Wrong data in the transport request. |
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 |
| System | 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 |
IG © 2025+ FHIR Infrastructure. Package hl7.fhir.uv.xver-r5.r4b#0.1.0 based on FHIR 4.3.0. Generated 2026-03-20
Links: Table of Contents |
QA Report
| Version History |
|
Propose a change