Release 4

This page is part of the FHIR Specification (v4.0.1: R4 - Mixed Normative and STU) in it's permanent home (it will always be available at this URL). 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

Codesystem-trigger-type.json

FHIR Infrastructure Work GroupMaturity Level: N/AStandards Status: Informative

Raw JSON (canonical form + also see JSON Format Specification)

Definition for Code System TriggerType

{
  "resourceType" : "CodeSystem",
  "id" : "trigger-type",
  "meta" : {
    "lastUpdated" : "2019-11-01T09:29:23.356+11:00"
  },
  "text" : {
    "status" : "generated",
    "div" : "<div>!-- Snipped for Brevity --></div>"
  },
  "extension" : [{
    "url" : "http://hl7.org/fhir/StructureDefinition/structuredefinition-wg",
    "valueCode" : "fhir"
  },
  {
    "url" : "http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status",
    "valueCode" : "trial-use"
  },
  {
    "url" : "http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm",
    "valueInteger" : 5
  }],
  "url" : "http://hl7.org/fhir/trigger-type",
  "identifier" : [{
    "system" : "urn:ietf:rfc:3986",
    "value" : "urn:oid:2.16.840.1.113883.4.642.4.104"
  }],
  "version" : "4.0.1",
  "name" : "TriggerType",
  "title" : "TriggerType",
  "status" : "draft",
  "experimental" : false,
  "date" : "2019-11-01T09:29:23+11:00",
  "publisher" : "HL7 (FHIR Project)",
  "contact" : [{
    "telecom" : [{
      "system" : "url",
      "value" : "http://hl7.org/fhir"
    },
    {
      "system" : "email",
      "value" : "fhir@lists.hl7.org"
    }]
  }],
  "description" : "The type of trigger.",
  "caseSensitive" : true,
  "valueSet" : "http://hl7.org/fhir/ValueSet/trigger-type",
  "content" : "complete",
  "concept" : [{
    "code" : "named-event",
    "display" : "Named Event",
    "definition" : "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."
  },
  {
    "code" : "periodic",
    "display" : "Periodic",
    "definition" : "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."
  },
  {
    "code" : "data-changed",
    "display" : "Data Changed",
    "definition" : "The trigger occurs whenever data of a particular type is changed in any way, either added, modified, or removed.",
    "concept" : [{
      "code" : "data-added",
      "display" : "Data Added",
      "definition" : "The trigger occurs whenever data of a particular type is added."
    },
    {
      "code" : "data-modified",
      "display" : "Data Updated",
      "definition" : "The trigger occurs whenever data of a particular type is modified."
    },
    {
      "code" : "data-removed",
      "display" : "Data Removed",
      "definition" : "The trigger occurs whenever data of a particular type is removed."
    }]
  },
  {
    "code" : "data-accessed",
    "display" : "Data Accessed",
    "definition" : "The trigger occurs whenever data of a particular type is accessed."
  },
  {
    "code" : "data-access-ended",
    "display" : "Data Access Ended",
    "definition" : "The trigger occurs whenever access to data of a particular type is completed."
  }]
}

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.