The FHIRcast specification describes the APIs used to synchronize disparate healthcare applications' user interfaces in real time, allowing them to show the same clinical content to a user (or group of users).
These are categories of potential users, implementers, or other interested parties such as those that are indicated on the Project Scope Statement under “Stakeholders/Vendors/Providers”. Select those that are applicable, or suggest others:
Standards Development Organizations (SDOs)
EHR, PHR, Health Care IT, Clinical Decision Support Systems, Lab, HIS
• Enables standards-based support for modern, simple application context synchronization
• Supports patient safety in multi-application workflows such as imaging integration with EMR and dictation systems
• Reduces provider burden in multi-application workflows
• Improves security over current application integration mechanisms
Once the subscribing app knows about the session, the app may subscribe to specific workflow-related events for the given session. The subscription is verified and the app is notified when those workflow-related events occur; for example, by the clinician opening a patient's chart. The subscribing app may initiate context changes by accessing APIs exposed by the Hub; for example, closing the patient's chart. The app deletes its subscription to no longer receive notifications. The notification message describing the workflow event is a simple json wrapper around one or more FHIR resources.
FHIRcast enables a subscriber to receive notifications either through a webhook or over a WebSocket connection. FHIRcast recommends the HL7 SMART on FHIR launch protocol for both session discovery and API authentication.