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-observation-triggeredbytype-for-R4B | Version: 0.1.0 | |||
| Standards status: Trial-use | Maturity Level: 5 | Responsible: Orders and Observations | Computable Name: R5ObservationTriggeredbytypeForR4B | |
This cross-version ValueSet represents content from http://hl7.org/fhir/ValueSet/observation-triggeredbytype|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/observation-triggeredbytype|5.0.0 as defined in FHIR R5
in FHIR R4B.
The source value set is bound to the following FHIR R5 elements:
Observation.triggeredBy.typeNote 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/observation-triggeredbytype|5.0.0, defined in FHIR R5 does not have any mapping to FHIR R4B
References
http://hl7.org/fhir/observation-triggeredbytype version 📍5.0.0| Code | Display | Definition |
| re-run | Re-run (per policy) | Performance of the same test but with different parameters/settings/solution. |
| reflex | Reflex | Performance of one or more other tests depending on the results of the initial test. This may include collection of additional specimen. While a new ServiceRequest is not required to perform the additional test, where it is still needed (e.g., requesting another laboratory to perform the reflex test), the Observation.basedOn would reference the new ServiceRequest that requested the additional test to be performed as well as the original ServiceRequest to reflect the one that provided the authorization. |
| repeat | Repeat (per policy) | Performance of the same test again with the same parameters/settings/solution. |
This value set expansion contains 3 concepts.
| System | Version | Code | Display | Definition | JSON | XML |
http://hl7.org/fhir/observation-triggeredbytype | 5.0.0 | re-run | Re-run (per policy) | Performance of the same test but with different parameters/settings/solution. | ||
http://hl7.org/fhir/observation-triggeredbytype | 5.0.0 | reflex | Reflex | Performance of one or more other tests depending on the results of the initial test. This may include collection of additional specimen. While a new ServiceRequest is not required to perform the additional test, where it is still needed (e.g., requesting another laboratory to perform the reflex test), the Observation.basedOn would reference the new ServiceRequest that requested the additional test to be performed as well as the original ServiceRequest to reflect the one that provided the authorization. | ||
http://hl7.org/fhir/observation-triggeredbytype | 5.0.0 | repeat | Repeat (per policy) | Performance of the same test again with the same parameters/settings/solution. |
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 |