HL7 FHIR® Implementation Guide: Electronic Case Reporting (eCR) - US Realm
2.1.2 - STU 2 United States of America flag

HL7 FHIR® Implementation Guide: Electronic Case Reporting (eCR) - US Realm, published by HL7 International / Public Health. This guide is not an authorized publication; it is the continuous build for version 2.1.2 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/case-reporting/ and changes regularly. See the Directory of published versions

CodeSystem: US Public Health TriggerDefinition Named Events

Active as of 2020-09-06

Generated Narrative: CodeSystem us-ph-triggerdefinition-namedevents

This case-sensitive code system http://hl7.org/fhir/us/ecr/CodeSystem/us-ph-triggerdefinition-namedevents defines the following codes in a Is-A hierarchy:

LvlCodeDisplayDefinition
1encounter-change Indicates a change in the patient's encounter recordsIndicates a change in the patient's encounter records which includes starting an encounter, closing an encounter, modifying data elements of an encounter. Encounter change events would be triggered by monitoring the Encounter resource.
2  encounter-start Indicates the start of an encounterIndicates the start of an encounter, where in encounter.period.low is populated with the start time.
2  encounter-close Indicates the close of an encounterIndicates the closure of an encounter, where in encounter.period.high is populated with the end time.
2  encounter-modified Indicates modifications to data elements of an encounterIndicates changes to encounter codes, times, reason codes, diagnosis, discharge dispositions, locations etc.
1diagnosis-change Indicates a change in the patient's diagnosisIndicates a change in the patient's diagnosis and it includes new diagnosis or modifications to existing diagnosis. Diagnosis change events would be triggered by monitoring the Condition resource.
2  new-diagnosis New Diagnosis addedIndicates that a new diagnosis has been added to the patient's chart in the EHR
2  modified-diagnosis Existing Diagnosis record has been modifiedIndicates that an existing diagnosis record in the patient's chart has been modified. Sometimes this is equivalent to removing an existing diagnosis record (which may have been entered in error) and adding a new diagnosis record.
1medication-change Indicates a change in the patient's medicationsIndicates a change in the patient's medications and it includes changes to Administered medications or Requested medications or Dispensed medications. Medication change events would be triggered by monitoring the MedicationRequest, MedicationDispense, MedicationStatement and MedicationAdministration resources.
2  new-medication New Medication addedIndicates that a new MedicationRequest or MedicationDispense or MedicationAdministered or MedicationStatement has been added to the patient's chart in the EHR
2  modified-medication Existing Medication record has been modifiedIndicates that an existing medication record in the patient's chart has been modified. Sometimes this is equivalent to removing an existing medication record (which may have been entered in error) and adding a new medication record.
1labresult-change Indicates a change in the patient's labresultsIndicates a change in the patient's lab results and it includes new lab results or modifications to existing lab results. Changes to lab results could be because of change in the lab result values, lab test names, times or other data elements of the Observation resource where the category is laboratory. LabResult events would be triggered by monitoring the Observation resource with an Observation.category=laboratory.
2  new-labresult New Lab Result addedIndicates that a new Lab Result has been added to the patient's chart in the EHR
2  modified-labresult Existing Lab Result record has been modifiedIndicates that an existing lab result record in the patient's chart has been modified. Sometimes this is equivalent to removing an existing lab result record (which may have been entered in error) and adding a new lab result record. Changes to lab results could be because of change in the lab result values, lab test names, times or other data elements of the Observation resource where the category is laboratory.
1order-change Indicates a change in the patient's ordersIndicates a change in the patient's orders and it includes new or modified ServiceRequests. Order change events would be triggered by monitoring the ServiceRequest resource.
2  new-order New Order addedIndicates that a new ServiceRequest has been added to the patient's chart in the EHR
2  modified-order Existing Order record has been modifiedIndicates that an existing ServiceRequest record in the patient's chart has been modified. Sometimes this is equivalent to removing an existing ServiceRequest record (which may have been entered in error) and adding a new ServiceRequest record.
1procedure-change Indicates a change in the patient's proceduresIndicates a change in the patient's procedures and it includes new procedures or modifications to existing procedures. Procedure events would be triggered by monitoring the Procedure resource.
2  new-procedure New Procedure addedIndicates that a new procedure has been added to the patient's chart in the EHR
2  modified-procedure Existing Procedure record has been modifiedIndicates that an existing procedure record in the patient's chart has been modified. Sometimes this is equivalent to removing an existing procedure record (which may have been entered in error) and adding a new procedure record.
1immunization-change Indicates a change in the patient's immunizationsIndicates a change in the patient's immunization and it includes new immunizations or modifications to existing immunization records. Immunization change events would be triggered by monitoring the Immunization resource.
2  new-immunization New Immunization addedIndicates that a new immunization has been added to the patient's chart in the EHR
2  modified-immunization Existing immunization record has been modifiedIndicates that an existing immunization record in the patient's chart has been modified. Sometimes this is equivalent to removing an existing immunization record (which may have been entered in error) and adding a new immunization record.
1demographic-change Indicates change in patient demographicsIndicates that the Patient demographic attributes such as Date of Birth, Race, Ethnicity, Deceased date, Address, Telecom, Names have changed. Demographic change events would be triggered by monitoring the Patient resource.
1received-public-health-report Indicates receipt of a public health reportIndicates that a public health report was submitted and received by a specific system. This event could trigger downstream processing and hence is designated as a named event.
1received-public-health-response Indicates receipt of a public health response for a submitted public health reportIndicates that a public health response was received by a specific system for an already submitted public health report. This event could trigger downstream processing and hence is designated as a named event.
1manual-notification A Practitioner or their representatives notify the application about change in patient dataIn some cases where automated notifications are not supported, a practitioner or their representative can initiate the public health report processing by notifying the application about change in a patient's data.
1timer-event A Timer is setup to kick off processing.Indicates a timer based approach to start processing.
2  periodic-timer Setup Periodic TimerIndicates that processing must be performed periodically based on a specified duration.
2  absolute-timer Setup Absolute TimerIndicates that processing must be performed at a specific time.