Overview
FHIR Subscription is a FHIR resource enabling event-driven notifications when FHIR resources change — specifically on creation, update, or deletion of resources matching subscriber-defined criteria. Subscriptions replace polling patterns (where clients repeatedly query for changes) with push notifications (where servers notify clients immediately when relevant changes occur). This enables real-time clinical and administrative workflows and reduces network and computational overhead compared to polling.
Subscription architecture: A client creates a Subscription resource specifying the trigger criteria (a FHIR search expression identifying the resource types and filters of interest), channel (how the server should notify — REST hook, WebSocket, email, SMS), endpoint (the URL to notify), and payload type (whether the notification includes the full changed resource, a reference, or just an alert). The server monitors data changes against the subscription criteria. When matches occur, the server notifies the client per the channel and payload specification.
FHIR R4 Subscription vs. R5 Subscription (Topic-Based): FHIR R4 Subscription uses free-form FHIR search criteria, providing flexibility but inconsistent implementation across servers. FHIR R5 introduces Subscription Topics — a more structured approach where publishers define named topics with specific criteria, and subscribers subscribe to topics rather than writing custom criteria. Subscription Topics improve interoperability by standardizing event types across implementations. Healthcare industry is transitioning toward Subscription Topics over time.
Use cases span clinical and operational workflows. Clinical decision support: subscribe to new lab results or vital signs and trigger alerts when values exceed thresholds. Care coordination: subscribe to hospital admission events and notify primary care providers. Quality monitoring: subscribe to outcome events (readmissions, complications) and trigger quality review. Public health: subscribe to reportable condition diagnoses and notify health departments. Utilization management: subscribe to admission events and trigger concurrent review. Claims processing: subscribe to encounter completion and trigger claim preparation workflow.
For HIE and interoperability, Subscriptions enable real-time data exchange across organizations. Hospitals can subscribe to emergency department events at affiliated hospitals to support patient follow-up. HIEs can use Subscriptions to push notifications to providers about patient events at other participating organizations. Payers can subscribe to encounter data for timely claims processing and risk stratification.
Implementation considerations include: server support (not all FHIR servers support Subscriptions equally; support is improving but varies), channel selection (REST hook most common; WebSocket for high-volume real-time; email/SMS for patient-facing notifications), endpoint security (endpoints receiving notifications must authenticate and authorize to prevent spoofing or unauthorized data flow), reliability (handling delivery failures, retries, and ordering), and scalability (high-volume subscriptions can strain servers and clients).
FHIRcast is a related specification enabling subscription-based workflow coordination between applications. While FHIR Subscriptions notify about data changes, FHIRcast coordinates user context across applications — when a clinician opens a patient in one app, FHIRcast can notify other apps to synchronize their display. FHIRcast leverages subscription-like mechanics for cross-application coordination.
For RCM operations, FHIR Subscriptions enable real-time revenue cycle workflows: new encounter subscriptions trigger claim preparation, denial subscriptions trigger workflow assignment, payment subscriptions update patient accounting, eligibility change subscriptions trigger verification workflow. Real-time workflow reduces latency between clinical events and RCM response compared to batch-based integration patterns.
Vendor support is evolving. Major EHRs increasingly support Subscriptions with varying capability depth. FHIR platforms (Microsoft Azure API for FHIR, Google Cloud Healthcare API, Firely) provide Subscription support. HIEs and interoperability platforms (Redox, Particle Health) offer subscription-based integration. Full Subscription Topic-Based implementation is an evolving area; early adopters are piloting implementations while the industry works toward broader adoption.
Industry benchmark
FHIR R4 Subscription: flexible but inconsistent. FHIR R5 Subscription Topics: structured, standardized. Use cases: CDS, care coordination, quality, utilization management, RCM.
Worked example
A primary care practice subscribes to emergency department admission events for its attributed patients at the regional HIE. When a patient is admitted to an affiliated ED, the HIE pushes a notification to the practice's care coordination system via REST hook. The care coordinator receives the alert within minutes of admission, contacts the patient's care team, coordinates post-discharge follow-up, and arranges timely primary care visit. Compared to batch-based daily admission reports, real-time notifications improve transitional care outcomes and reduce readmissions.
Frequently asked questions — FHIR Subscription
What's the difference from polling?
Polling has clients repeatedly query for changes — inefficient and latent. Subscriptions have servers push notifications when changes occur — efficient and real-time. Subscriptions significantly reduce network/computational overhead for change-tracking workflows.
What notification channels are supported?
REST hook (HTTP POST to client endpoint), WebSocket (persistent connection), email, SMS, and others. REST hook is most common for system-to-system integration.
Is FHIR Subscription widely supported?
Support is increasing but varies. Major EHRs and FHIR platforms support Subscriptions with varying capability depth. FHIR R5 Subscription Topics is standardizing the pattern; adoption continues to mature.
Disclaimer
This glossary entry is operational reference for revenue-cycle and medical-billing professionals. It is not legal, clinical, or contractual advice. Industry benchmarks cite named public sources where available; always verify against the current guidance from the authority body before relying on a number in a contract, policy, or compliance filing.