Event Message
| Type | Use Cases | Suggested Standards |
|---|---|---|
| Multiple Resources | A method of sending multiple resources in one interaction which is particularly suited situations where time is important. | FHIR Workflow AdHoc Option D |
HL7 FHIR recommends the use of FHIR Workflow as the main method of interaction framework between systems and providers.
This typically involves the use of Query Patient Care Data, Event Notifications and Task (/Requests) patterns. These all use FHIR Restful interactions.
FHIR Messaging which is used in this pattern is known to be more complicated to implement and is not well supported by suppliers.
Certain use cases will want to perform the event and patient data sharing in one interaction. This is often between two providers and so is not considered a generic method of sharing Patient Care Data. This exchange method also has concurrency issues as it contains a point in time EHR snapshot.
Specific use cases include:
- Sending a pathology report
- Transmission of an Emergency Care Summary
- Transmission of Child Health Data
- Populating a longitudinal patient record
Events Messages and Send Document will generally use Messaging.
Example Implementations
- Booking and Referral - FHIR API
- Digital Child Health - FHIR
- Personal Demographics Service Notifications - FHIR
- Electronic Prescription Service - FHIR API
- National Event Management Service - FHIR API
- Transfer of Care Emergency Care Discharge - FHIR
- Transfer of Care Inpatient Discharge - FHIR
- Transfer of Care Mental Health Discharge - FHIR
- Transfer of Care Outpatient Clinic Letter - FHIR
- Digital Medicine - FHIR