This page is part of the FHIR Specification (v4.5.0: R5 Preview #3). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions . Page versions: R5 R4B R4 R3
FHIR Infrastructure Work Group | Maturity Level: N/A | Standards Status: Informative |
Raw XML (canonical form + also see XML Format Specification)
Definition for Code System TriggerType
<?xml version="1.0" encoding="UTF-8"?> <CodeSystem xmlns="http://hl7.org/fhir"> <id value="trigger-type"/> <meta> <lastUpdated value="2020-08-20T17:41:31.970+10:00"/> </meta> <text> <status value="generated"/> <div xmlns="http://www.w3.org/1999/xhtml"> <p> This code system http://hl7.org/fhir/trigger-type defines the following codes:</p> <table class="codes"> <tr> <td> <b> Lvl</b> </td> <td style="white-space:nowrap"> <b> Code</b> </td> <td> <b> Display</b> </td> <td> <b> Definition</b> </td> </tr> <tr> <td> 1</td> <td style="white-space:nowrap">named-event <a name="trigger-type-named-event"> </a> </td> <td> Named Event</td> <td> The trigger occurs in response to a specific named event, and no other information about the trigger is specified. Named events are completely pre-coordinated, and the formal semantics of the trigger are not provided.</td> </tr> <tr> <td> 1</td> <td style="white-space:nowrap">periodic <a name="trigger-type-periodic"> </a> </td> <td> Periodic</td> <td> The trigger occurs at a specific time or periodically as described by a timing or schedule. A periodic event cannot have any data elements, but may have a name assigned as a shorthand for the event.</td> </tr> <tr> <td> 1</td> <td style="white-space:nowrap">data-changed <a name="trigger-type-data-changed"> </a> </td> <td> Data Changed</td> <td> The trigger occurs whenever data of a particular type is changed in any way, either added, modified, or removed.</td> </tr> <tr> <td> 2</td> <td style="white-space:nowrap"> data-added <a name="trigger-type-data-added"> </a> </td> <td> Data Added</td> <td> The trigger occurs whenever data of a particular type is added.</td> </tr> <tr> <td> 2</td> <td style="white-space:nowrap"> data-modified <a name="trigger-type-data-modified"> </a> </td> <td> Data Updated</td> <td> The trigger occurs whenever data of a particular type is modified.</td> </tr> <tr> <td> 2</td> <td style="white-space:nowrap"> data-removed <a name="trigger-type-data-removed"> </a> </td> <td> Data Removed</td> <td> The trigger occurs whenever data of a particular type is removed.</td> </tr> <tr> <td> 1</td> <td style="white-space:nowrap">data-accessed <a name="trigger-type-data-accessed"> </a> </td> <td> Data Accessed</td> <td> The trigger occurs whenever data of a particular type is accessed.</td> </tr> <tr> <td> 1</td> <td style="white-space:nowrap">data-access-ended <a name="trigger-type-data-access-ended"> </a> </td> <td> Data Access Ended</td> <td> The trigger occurs whenever access to data of a particular type is completed.</td> </tr> </table> </div> </text> <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-wg"> <valueCode value="fhir"/> </extension> <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status"> <valueCode value="trial-use"/> </extension> <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm"> <valueInteger value="5"/> </extension> <url value="http://hl7.org/fhir/trigger-type"/> <identifier> <system value="urn:ietf:rfc:3986"/> <value value="urn:oid:2.16.840.1.113883.4.642.1.104"/> </identifier> <version value="4.5.0"/> <name value="TriggerType"/> <title value="TriggerType"/> <status value="draft"/> <experimental value="false"/> <date value="2020-08-20T17:41:31+10: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="The type of trigger."/> <caseSensitive value="true"/> <valueSet value="http://hl7.org/fhir/ValueSet/trigger-type"/> <content value="complete"/> <concept> <code value="named-event"/> <display value="Named Event"/> <definition value="The trigger occurs in response to a specific named event, and no other information about the trigger is specified. Named events are completely pre-coordinated, and the formal semantics of the trigger are not provided."/> </concept> <concept> <code value="periodic"/> <display value="Periodic"/> <definition value="The trigger occurs at a specific time or periodically as described by a timing or schedule. A periodic event cannot have any data elements, but may have a name assigned as a shorthand for the event."/> </concept> <concept> <code value="data-changed"/> <display value="Data Changed"/> <definition value="The trigger occurs whenever data of a particular type is changed in any way, either added, modified, or removed."/> <concept> <code value="data-added"/> <display value="Data Added"/> <definition value="The trigger occurs whenever data of a particular type is added."/> </concept> <concept> <code value="data-modified"/> <display value="Data Updated"/> <definition value="The trigger occurs whenever data of a particular type is modified."/> </concept> <concept> <code value="data-removed"/> <display value="Data Removed"/> <definition value="The trigger occurs whenever data of a particular type is removed."/> </concept> </concept> <concept> <code value="data-accessed"/> <display value="Data Accessed"/> <definition value="The trigger occurs whenever data of a particular type is accessed."/> </concept> <concept> <code value="data-access-ended"/> <display value="Data Access Ended"/> <definition value="The trigger occurs whenever access to data of a particular type is completed."/> </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.