A master patient index in a US healthcare deployment is one of those infrastructure pieces that quietly decides whether the rest of the stack holds together. Get it right and patient data flows cleanly across encounters, departments, and ex
FHIR Form Builders for US Hospitals: What You Need to Know in 2026
A FHIR form builder in a US hospital is one of those decisions that looks straightforward in procurement and gets complicated three weeks into integration. Vendors all show the same demo: a QuestionnaireResponse rendering into a clean dropd
Choosing a FHIR Terminology Server: A Buyer's Guide for US Healthcare
Picking a FHIR terminology server for a US healthcare deployment looks like a checklist exercise on paper, and then it stops looking simple about three weeks into integration. The vendor pages all promise the same set of operations: hosting
FHIR Bundle Semantics: batch vs transaction, and Why It Matters
FHIR Bundle resources ship four types that matter operationally: transaction, batch, searchset, and collection. Confusing them or misusing atomicity semantics is where production integrations quietly break. Transaction Bundle: all-or-nothing writes. POST to / with type: transaction executes all entry operations atomically. Any failure rolls back all. Supports URN placeholder references (urn:uuid:temp-patient-1) that resolve to real […]
Achieving Seamless Digital Health with a Terminology Server
The digital revolution has profoundly altered many aspects of our lives, and healthcare is no exception. From electronic health records (EHRs) to telemedicine platforms, technology promises to make healthcare more accessible, efficient, and personalized. But what happens when different systems speak different languages? This is where a terminology server enters the picture, acting as a […]
FHIR ServiceRequest for Order Entry: 4 Patterns EHR Vendors Ship
Order entry in FHIR uses the ServiceRequest resource, not MedicationRequest (that's for meds). Four patterns cover how EHR vendors implement clinical order workflows in 2026. Pattern 1: Single ServiceRequest per order. Simple lab orders and imaging orders map one-to-one with a single ServiceRequest. code identifies the test, subject is the Patient, requester is the Practitioner, […]
CDS Hooks for FHIR: What Actually Works at Point of Care
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. […]
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 - […]
- Older Posts
- 1
- …
- 3
- 4
- 5
- 6
- Newer Posts