How do I learn FHIR? Learn the IG's!
To be or not to be
Most people in health tech talk about FHIR like it’s a single API spec.
It’s not.
FHIR is a platform of standards and the real magic happens inside Implementation Guides (IGs).
But here’s the thing no one tells you: 90% of IGs don’t matter for real-world interoperability.
Let’s cut through the noise.
If you’re building anything that needs to work in the U.S. ecosystem these are the only five that matter.
🇺🇸 1. US Core >< The Non-Negotiable
Think of US Core as the FHIR Constitution.
Every other U.S. guide extends or constrains it.
Why it matters
It defines the canonical profiles for exchanging patient-level data — labs, meds, allergies, encounters, you name it.
Without it, your FHIR data isn’t “U.S.-FHIR.” It’s just JSON cosplay.
Why everyone gets it wrong
Teams validate against old versions (v3 or v4) while US Core v7+ now enforces strict references and tighter bindings.
They break interoperability before they even start.
FHIR IQ Take
If your FHIR pipelines, validators, or analytics aren’t US Core-compliant, you’re building sandcastles in a data tsunami.
2. CARIN Blue Button » The Payer Goldmine
This one sounds “payer-only.”
It’s not.
CARIN-BB is claims data on FHIR.
The foundation for transparency, consumer access, and cost analytics.
Why it matters
Defines how payers share EOBs, claims, and coverage data with patients and apps.
It’s the compliance backbone for Patient Access APIs.
The contrarian truth
CARIN isn’t about compliance — it’s about monetization.
Whoever masters CARIN controls the financial insight layer of healthcare.
FHIR IQ Take
Combine CARIN + US Core, and you have the holy grail: a unified clinical + financial view of the patient journey.
3. CCDA on FHIR The Bridge Everyone Underestimates
Yes, CCDA is “legacy.”
Yes, it’s messy.
But it’s still how 90% of providers exchange documents today.
🔗 Why it matters
The CCDA-on-FHIR IG maps those legacy XML blobs into FHIR-structured resources.
That’s the real bridge between yesterday’s EHRs and tomorrow’s APIs.
The contrarian truth
FHIR purists mock it.
Real implementers rely on it.
If you can normalize CCDA → FHIR cleanly, you’ve solved healthcare’s dirtiest secret: legacy data debt.
💡 FHIR IQ Take
CCDA-on-FHIR isn’t old tech.
It’s survival. And it provides context that could be missing elsewhere to make your AI sing.
4. Bulk Data / Flat FHIR The Money IG
Everyone loves APIs.
But healthcare runs on populations, not patients.
Why it matters
Bulk Data (aka Flat FHIR) lets you extract entire populations millions of patients via NDJSON exports.
It’s the only way to make FHIR useful for analytics, AI, and reporting.
The contrarian truth
The “Patient Access API” gets the PR.
The Bulk Data API gets the ROI.
FHIR IQ Take
If your data platform doesn’t speak Flat FHIR, it’s not enterprise-grade — it’s a demo.
5. Da Vinci PAS The Quiet Revolution
Prior authorization is healthcare’s most hated workflow.
Da Vinci PAS is how we finally fix it.
Why it matters
PAS defines the FHIR-based workflow for automated prior auth — integrating with payers, EHRs, and X12 in real time.
The contrarian truth
It’s not about shaving days off approvals — it’s about unlocking automated payer-provider workflows at scale.
PAS will quietly become the new “claims clearinghouse” layer of healthcare.
FHIR IQ Take
The future of payer APIs is PAS.
Ignore it, and you’ll be building around the new rails instead of on them.
NOTE: THANKS TO Benji Graham for note on Da Vinci PAS and the WHOLE Burden Reduction track, that being CRD, DTR, and PAS
https://build.fhir.org/ig/HL7/davinci-crd/burden.html
TL;DR The Real FHIR Hierarchy
Implementation Guide
What It Really Does
1️⃣US Core Defines the clinical backbone
2️⃣CARIN BB Unlocks financial transparency
3️⃣CCDA on FHIR Bridges legacy to modern
4️⃣Bulk Data Scales FHIR for analytics & AI
5️⃣Da Vinci PAS Automates payer-provider workflows
“The biggest FHIR misunderstanding? That the standard itself is what matters. It’s not. The Implementation Guides are where the rules, profiles, and value sets turn theory into business value.”
The FHIR IQ Premium Playbooks
1. “US Core Survival Kit”
What it is:
A concise, visual + narrative walkthrough of the US Core profiles, bindings, and dependencies.
What it includes:
Profile relationship map (Patient → Encounter → Condition → Observation)
“Gotchas” checklist (e.g., common validation failures, cardinality traps)
Example JSON and realistic NDJSON bundles
Template mapping spreadsheet: “Legacy → US Core Resource → Target Element”
Implementation design doc sample (editable for client delivery)
2. “CARIN Blue Button in 7 Days”
What it is:
A practical guide to publishing a member-facing claims API step-by-step.
What it includes:
Simplified data flow diagrams (payer → FHIR → consumer app)
Overview of all CARIN EOB resource profiles and elements
Annotated sample FHIR bundles for professional and institutional claims
Common value set mismatches explained
“CARIN BB → US Core merge map” to align clinical + financial data
API Blueprint (OpenAPI spec template + FHIR endpoints)
3. “CCDA-to-FHIR Mapping Playbook”
What it is:
A Rosetta Stone for turning old CCDA XML into clean, structured FHIR.
What it includes:
Full mapping matrix: CCDA section → FHIR resource → key elements
“CDA gotchas” (narrative sections, extension handling, reference structure)
Code snippets for parsing and transformation (Python + Node examples)
Downloadable test bundles (before/after conversion)
Visual flow diagram showing CCDA → FHIR → downstream analytics
4. “Bulk Data Masterclass: Scaling FHIR for Analytics”
What it is:
A technical and business guide to mastering FHIR Bulk Data.
What it includes:
Visual architecture diagrams for export, manifest, and job flow
Step-by-step setup guide using public sandbox endpoints
Sample NDJSON bundles with 10k+ synthetic patients
Data load scripts for Databricks/Snowflake
Benchmarks for performance tuning and parallelism
Test server access with population-based export jobs preconfigured
5. “Da Vinci PAS Implementation Blueprint”
What it is:
A system architect’s guide to automating prior authorization with FHIR.
What it includes:
Workflow diagrams linking FHIR → X12 → EHR integration points
Annotated PAS request/response examples
Explanation of CQL/DTR integration and SMART on FHIR extension
“Validation traps” (e.g., missing coverage, service type mismatches)
End-to-end demo flow design document
Test dataset (mock payer + provider + PAS API)



