Must-Support is the FHIR concept most often misread as "required." It is not. It is a signal to implementers that…
Read More
Must-Support Elements and What Implementers Actually Do
The Extension Model: When a FHIR Resource Is Silent on Your Data
Every FHIR resource has fields the spec author picked. Every implementation has data the spec author did not pick. The…
Read More
Profiles and Slicing at a Glance
FHIR profiles are how one resource type serves many implementation contexts. US Core Patient, International Patient Summary, and CARIN Blue…
Read More
Reference vs Contained: When to Embed and When to Link
FHIR R4 gives two ways to connect one resource to another. Reference points at a resource by URL or logical…
Read More
Top 5 MPI Engines for Payer-Driven Patient Reconciliation in 2026
Payer-driven patient reconciliation has become a distinct MPI workload in 2026. CMS interoperability rules pushed payers into FHIR exchange, and…
Read More
The Ten FHIR Resources You Should Learn First
FHIR R4 lists around one hundred forty resource types. A working knowledge of ten of them covers the vast majority…
Read More
Navigating FHIR R4 Resources When You Know DomainResource But Not Much Else
A developer who has skimmed the FHIR overview knows two things: there is a base class called Resource, and there…
Read More
Top 5 FHIR Questionnaire Engines for Surgical Pre-Op Intake
Surgical pre-op intake sits at the intersection of clinical risk, regulatory consent, and procedural scheduling. The Questionnaire is longer than…
Read More
Top 5 HL7 v2 to FHIR Conversion Engines for US Hospitals
HL7 v2 messaging is still the backbone of intra-hospital clinical communication in 2026, and the path from v2 to FHIR…
Read More
Top 6 Patient Matching Tools for FHIR-Native Healthcare Platforms
FHIR-native healthcare platforms have a narrower set of MPI choices than legacy hospital systems. The platform's data model is FHIR…
Read More