Extensions for Using Data Elements from FHIR R4 in FHIR R4B - Downloaded Version null See the Directory of published versions
| Official URL: http://hl7.org/fhir/uv/xver/ValueSet/R4-v2-0255-for-R4B | Version: 0.1.0 | |||
| Standards status: Trial-use | Maturity Level: 0 | Computable Name: R4V20255ForR4B | ||
This cross-version ValueSet represents content from http://terminology.hl7.org/ValueSet/v2-0255|2.9 for use in FHIR R4B.
This value set is part of the cross-version definitions generated to enable use of the
value set http://terminology.hl7.org/ValueSet/v2-0255|2.9 as defined in FHIR R4
in FHIR R4B.
The source value set is bound to the following FHIR R4 elements:
Note 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://terminology.hl7.org/ValueSet/v2-0255|2.9, defined in FHIR R4 does not have any mapping to FHIR R4B
References
This value set is not used here; it may be used elsewhere (e.g. specifications and/or implementations that use this content)
http://terminology.hl7.org/CodeSystem/v2-0255 version 📍2.9| Code | Display |
| * | (asterisk) Life of the "unit" |
| 12H | 12 hours |
| 1H | 1 hour |
| 1L | 1 months (30 days) |
| 1W | 1 week |
| 2.5H | 2 1/2 hours |
| 24H | 24 hours |
| 2D | 2 days |
| 2H | 2 hours |
| 2L | 2 months |
| 2W | 2 weeks |
| 30M | 30 minutes |
| 3D | 3 days |
| 3H | 3 hours |
| 3L | 3 months |
| 3W | 3 weeks |
| 4D | 4 days |
| 4H | 4 hours |
| 4W | 4 weeks |
| 5D | 5 days |
| 5H | 5 hours |
| 6D | 6 days |
| 6H | 6 hours |
| 7H | 7 hours |
| 8H | 8 hours |
| LU | Life of the "unit" |
| PT | point in time |
This value set expansion contains 27 concepts.
| System | Version | Code | Display | JSON | XML |
http://terminology.hl7.org/CodeSystem/v2-0255 | 2.9 | * | (asterisk) Life of the "unit" | ||
http://terminology.hl7.org/CodeSystem/v2-0255 | 2.9 | 12H | 12 hours | ||
http://terminology.hl7.org/CodeSystem/v2-0255 | 2.9 | 1H | 1 hour | ||
http://terminology.hl7.org/CodeSystem/v2-0255 | 2.9 | 1L | 1 months (30 days) | ||
http://terminology.hl7.org/CodeSystem/v2-0255 | 2.9 | 1W | 1 week | ||
http://terminology.hl7.org/CodeSystem/v2-0255 | 2.9 | 2.5H | 2 1/2 hours | ||
http://terminology.hl7.org/CodeSystem/v2-0255 | 2.9 | 24H | 24 hours | ||
http://terminology.hl7.org/CodeSystem/v2-0255 | 2.9 | 2D | 2 days | ||
http://terminology.hl7.org/CodeSystem/v2-0255 | 2.9 | 2H | 2 hours | ||
http://terminology.hl7.org/CodeSystem/v2-0255 | 2.9 | 2L | 2 months | ||
http://terminology.hl7.org/CodeSystem/v2-0255 | 2.9 | 2W | 2 weeks | ||
http://terminology.hl7.org/CodeSystem/v2-0255 | 2.9 | 30M | 30 minutes | ||
http://terminology.hl7.org/CodeSystem/v2-0255 | 2.9 | 3D | 3 days | ||
http://terminology.hl7.org/CodeSystem/v2-0255 | 2.9 | 3H | 3 hours | ||
http://terminology.hl7.org/CodeSystem/v2-0255 | 2.9 | 3L | 3 months | ||
http://terminology.hl7.org/CodeSystem/v2-0255 | 2.9 | 3W | 3 weeks | ||
http://terminology.hl7.org/CodeSystem/v2-0255 | 2.9 | 4D | 4 days | ||
http://terminology.hl7.org/CodeSystem/v2-0255 | 2.9 | 4H | 4 hours | ||
http://terminology.hl7.org/CodeSystem/v2-0255 | 2.9 | 4W | 4 weeks | ||
http://terminology.hl7.org/CodeSystem/v2-0255 | 2.9 | 5D | 5 days | ||
http://terminology.hl7.org/CodeSystem/v2-0255 | 2.9 | 5H | 5 hours | ||
http://terminology.hl7.org/CodeSystem/v2-0255 | 2.9 | 6D | 6 days | ||
http://terminology.hl7.org/CodeSystem/v2-0255 | 2.9 | 6H | 6 hours | ||
http://terminology.hl7.org/CodeSystem/v2-0255 | 2.9 | 7H | 7 hours | ||
http://terminology.hl7.org/CodeSystem/v2-0255 | 2.9 | 8H | 8 hours | ||
http://terminology.hl7.org/CodeSystem/v2-0255 | 2.9 | LU | Life of the "unit" | ||
http://terminology.hl7.org/CodeSystem/v2-0255 | 2.9 | PT | point in time |
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 |