Mandate FHIR Subscriptions for Event-Driven Workflows

Recommendation: Certified Health IT must implement support for a defined starter set of FHIR Subscription topics to enable event-driven data synchronization and application workflows, reducing inefficient polling and supporting timely notifications. Rationale & Specifics: Real-time awareness of data changes is crucial for many clinical and patient-facing applications.

  1. Core Subscription Topics: At a minimum, support should include topics such as "Patient data updates" (for changes to key USCDI resources associated with a patient) and "Encounter data update" (for new or updated encounters). ONC should align these with industry efforts like the Argonaut Project's US Core Patient Data feed design.
  2. Technical Standards: Implementations should align with stable versions of FHIR Subscription specifications (e.g., FHIR R4 Subscriptions Backport IG).
  3. Use Cases: This enables use cases like patient apps receiving updates without constant polling, public health systems being notified of reportable encounters, and clinical systems triggering workflows based on new data availability.
  4. Certification: Testing should verify the ability to create subscriptions to defined topics and receive notifications when corresponding events occur.