CH LAB-Order (R4)
3.0.0-ballot - ballot
CH LAB-Order (R4)
3.0.0-ballot - ballot
This page is part of the CH LAB-Order (R4) (v3.0.0-ballot: STU 3) based on FHIR (HL7® FHIR® Standard) R4. This is the current published version. For a full list of available versions, see the Directory of published versions
| Official URL: http://fhir.ch/ig/ch-lab-order/ValueSet/observation-triggeredby-type | Version: 3.0.0-ballot | |||
| Active as of 2025-05-22 | Computable Name: ObservationTriggeredByTypeVS | |||
Copyright/Legal: CC0-1.0 |
||||
Possible reasons why an observation was triggered by another.
References
Generated Narrative: ValueSet observation-triggeredby-type
http://fhir.ch/ig/ch-lab-order/CodeSystem/triggeredby-type
ValueSet
Expansion performed internally based on codesystem Observation TriggeredBy Type CodeSystem v3.0.0-ballot (CodeSystem)
This value set contains 7 concepts
| Code | System | Display (en-US) |
| follow-up | http://fhir.ch/ig/ch-lab-order/CodeSystem/triggeredby-type | Follow-up test |
| confirmatory | http://fhir.ch/ig/ch-lab-order/CodeSystem/triggeredby-type | Confirmatory test |
| monitoring | http://fhir.ch/ig/ch-lab-order/CodeSystem/triggeredby-type | Monitoring test |
| reflex | http://fhir.ch/ig/ch-lab-order/CodeSystem/triggeredby-type | Reflex test |
| repeat | http://fhir.ch/ig/ch-lab-order/CodeSystem/triggeredby-type | Repeat test |
| add-on | http://fhir.ch/ig/ch-lab-order/CodeSystem/triggeredby-type | Add-on test |
| other | http://fhir.ch/ig/ch-lab-order/CodeSystem/triggeredby-type | Other test |
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 |