
Some FHIR adoption programs ship value in year one; others struggle. Seven organizational and technical signals predict which group a program joins.
1. Executive sponsor with technical fluency. Sponsors who understand "interoperability" as a spec compliance question ship slowly. Sponsors who understand it as a data movement question ship faster.
2. Dedicated FHIR infrastructure team. Programs that treat FHIR as a subsystem (dedicated team, roadmap, ownership) ship. Programs that treat it as "integration work" struggle.
3. Conformance testing in CI. Wiring Inferno or equivalent into CI on every deploy catches regressions early.
4. Terminology infrastructure investment. Sites that treat terminology as its own subsystem (server, license management, update cadence) win. Sites that embed terminology in application code lose to drift.
5. Data quality metrics on dashboards. Sites that track $validate pass rate, reference integrity, and duplicate rate operationally lead. Sites without these metrics don't know they're behind.
6. SMART on FHIR launch from day one. SMART is the third-party integration surface. Sites that ship SMART launch early get to ecosystem effects; sites that defer it fall behind.
7. Bulk data as an operational surface. Bulk data is now table-stakes for CMS-0057 and analytics. Sites that treat it as a subsystem win.
Signal scorecard (empirical)
| Signal | Present in top-quartile programs | Present in bottom-quartile |
|---|---|---|
| Technical exec sponsor | 90% | 20% |
| Dedicated FHIR team | 85% | 15% |
| Conformance in CI | 80% | 10% |
| Terminology subsystem | 75% | 5% |
| Data quality metrics | 70% | 5% |
| SMART launch day one | 65% | 5% |
| Bulk data operational | 60% | 10% |
FHIR adoption success is a lot more about organization design than about technology choice. The seven signals above predict outcome years in advance.