This page is part of the FHIR Specification (v5.0.0-ballot: R5 Ballot - see ballot notes). 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: N | Normative (from v4.0.0) | Use Context: Any |
This is a value set defined by the FHIR project.
Summary
Defining URL: | http://hl7.org/fhir/ValueSet/observation-triggeredbytype |
Version: | 5.0.0-ballot |
Name: | triggeredBytype |
Title: | triggeredBytype |
Status: | active |
Definition: | Codes providing the type of triggeredBy observation. |
Committee: | Orders and Observations Work Group |
OID: | 2.16.840.1.113883.4.642.3.3265 (for OID based terminology systems) |
Flags: | Immutable |
This value set is used in the following places:
http://hl7.org/fhir/observation-triggeredbytype
This expansion generated 10 Sep 2022
This value set contains 3 concepts
Expansion based on triggeredBytype v5.0.0-ballot (CodeSystem)
Code | System | Display | Definition |
reflex | http://hl7.org/fhir/observation-triggeredbytype | 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 | http://hl7.org/fhir/observation-triggeredbytype | Repeat (per policy) | Performance of the same test again with the same parameters/settings/solution. |
re-run | http://hl7.org/fhir/observation-triggeredbytype | Re-run (per policy) | Performance of the same test but with different parameters/settings/solution. |
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 |