CDS Hooks is the FHIR-native pattern for clinical decision support in EHR workflow. In 2026, three hook types ship in production; two others are aspirational. Understanding which is which affects integration timelines. Production-ready hooks 1. patient-view. Fires when a clinician opens a patient chart. CDS returns cards with alerts, reminders, and links to more context. […]
Digital forms for healthcare revolutionize data capture. Build agile, interoperable systems with our FHIR-powered platform.
GraphQL vs REST for FHIR: 5 Questions to Decide
FHIR GraphQL is a real spec option in 2026, and some servers (HAPI, Aidbox, Medplum) support it alongside REST. GraphQL isn't better than REST — it's better for specific patterns. Five questions decide the fit. 1. Do you have complex nested queries with heavy _include chains? GraphQL's shape-driven query is cleaner than iterative REST _include:iterate. […]
Connecting Patients and Providers through the FHIR Gateway Revolution in Digital Health Care
The American healthcare landscape is undergoing a massive transformation, driven by technology’s relentless march forward. We see a shift from paper-based processes to electronic health records (EHRs), from in-person visits to telehealth consultations. But what fuels this digital revolution, and how can we ensure that patients and providers are truly connected? The answer, in many […]
Which FHIR Resources Actually Matter for EHR Integration
FHIR defines 140+ resources but production EHR integrations touch a smaller set. Understanding which resources are the workhorse and which are edge-case avoids overinvesting in exotic resource support. Tier 1: Core clinical (must-have for any US integration) - Patient — identity, demographics - Encounter — visits and admissions - Observation — labs, vitals, notes - […]
FHIR Subscription in R5: SubscriptionTopic Practical Notes
FHIR R5 Subscription replaced R4's per-endpoint criteria-and-hook model with a topic-based model where multiple subscribers reference shared SubscriptionTopic definitions. This scales much better in production; understanding the model matters for anyone building event-driven FHIR integrations. SubscriptionTopic structure A SubscriptionTopic defines: resourceTrigger (what change fires the topic), notificationShape (which fields ride the notification), and canFilterBy (filter […]
FHIR Experts − Reshaping Digital Healthcare in the USA
Digital healthcare is rapidly changing how medical services are delivered, accessed, and managed in the United States. This transformation hinges on interoperability, the seamless exchange of information between different healthcare systems. At the heart of this movement are FHIR experts, who are revolutionizing how healthcare data is handled, ultimately improving patient outcomes and experiences. The […]
FHIR Data Validation: How `$validate` Actually Works in Production
FHIR `$validate` operation validates a resource against a profile and returns an OperationOutcome. In production the operation is invoked in three modes, each with different semantics and different failure modes. Mode 1: Write-time validation. POST or PUT with x-fhir-request-headers: return=OperationOutcome. The server validates, rejects on error, and returns the OperationOutcome with issues. Best for strict […]
- Older Posts
- 1
- 2
- 3
- 4