This page is part of the FHIR Specification v6.0.0-ballot1: Release 6 Ballot (1st Draft) (see Ballot Notes). The current version is 5.0.0. For a full list of available versions, see the Directory of published versions
Example CodeSystem/observation-triggeredbytype (XML)
Raw XML (canonical form + also see XML Format Specification)
Definition for Code SystemTriggeredBytype
<?xml version="1.0" encoding="UTF-8"?>
<CodeSystem xmlns="http://hl7.org/fhir">
<id value="observation-triggeredbytype"/>
<meta>
<lastUpdated value="2023-12-18T15:12:07.602+11:00"/>
<profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"/>
</meta>
<text>
<status value="generated"/>
<div xmlns="http://www.w3.org/1999/xhtml">
<p> This case-sensitive code system
<code> http://hl7.org/fhir/observation-triggeredbytype</code> defines the following codes in a Is-A heirarchy:
</p>
<table class="codes">
<tr>
<td style="white-space:nowrap">
<b> Code</b>
</td>
<td>
<b> Display</b>
</td>
<td>
<b> Definition</b>
</td>
</tr>
<tr>
<td style="white-space:nowrap">reflex
<a name="observation-triggeredbytype-reflex"> </a>
</td>
<td> Reflex</td>
<td> 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.</td>
</tr>
<tr>
<td style="white-space:nowrap">repeat
<a name="observation-triggeredbytype-repeat"> </a>
</td>
<td> Repeat (per policy)</td>
<td> Performance of the same test again with the same parameters/settings/solution.</td>
</tr>
<tr>
<td style="white-space:nowrap">re-run
<a name="observation-triggeredbytype-re-run"> </a>
</td>
<td> Re-run (per policy)</td>
<td> Performance of the same test but with different parameters/settings/solution.</td>
</tr>
</table>
</div>
</text>
<extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-wg">
<valueCode value="oo"/>
</extension>
<url value="http://hl7.org/fhir/observation-triggeredbytype"/>
<identifier>
<system value="urn:ietf:rfc:3986"/>
<value value="urn:oid:2.16.840.1.113883.4.642.4.2098"/>
</identifier>
<version value="6.0.0-ballot1"/>
<name value="TriggeredBytype"/>
<title value="triggered Bytype"/>
<status value="active"/>
<experimental value="true"/>
<date value="2022-03-16T16:55:11+11:00"/>
<publisher value="HL7 (FHIR Project)"/>
<contact>
<telecom>
<system value="url"/>
<value value="http://hl7.org/fhir"/>
</telecom>
<telecom>
<system value="email"/>
<value value="fhir@lists.hl7.org"/>
</telecom>
</contact>
<description value="Codes providing the triggeredBy type of observation."/>
<jurisdiction>
<coding>
<system value="http://unstats.un.org/unsd/methods/m49/m49.htm"/>
<code value="001"/>
<display value="World"/>
</coding>
</jurisdiction>
<caseSensitive value="true"/>
<valueSet value="http://hl7.org/fhir/ValueSet/observation-triggeredbytype"/>
<hierarchyMeaning value="is-a"/>
<content value="complete"/>
<concept>
<code value="reflex"/>
<display value="Reflex"/>
<definition value="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."/>
</concept>
<concept>
<code value="repeat"/>
<display value="Repeat (per policy)"/>
<definition value="Performance of the same test again with the same parameters/settings/solution."/>
</concept>
<concept>
<code value="re-run"/>
<display value="Re-run (per policy)"/>
<definition value="Performance of the same test but with different parameters/settings/solution."/>
</concept>
</CodeSystem>
Usage note: every effort has been made to ensure that the
examples are correct and useful, but they are not a normative part
of the specification.