The FHIR vendor landscape in 2026 splits into seven categories. Understanding the taxonomy prevents solution-shopping confusion.
Category 1: FHIR servers
HAPI FHIR, Aidbox, Medplum, Firely Server, Microsoft FHIR Server. Store and serve FHIR resources via REST.
Category 2: Terminology servers
Ontoserver, HAPI Terminology, Aidbox Terminology. Handle $expand, $validate-code, $translate.
Category 3: EHR vendors with FHIR APIs
Epic, Cerner, Athenaclinicals, Meditech. Expose FHIR APIs on top of proprietary EHRs.
Category 4: Integration engines
Rhapsody, Mirth Connect, InterSystems IRIS. HL7v2-to-FHIR conversion.
Category 5: SDC form builders
LHC-Forms, Aidbox Formbox, Smile CDR SDC. Author and render SDC Questionnaires.
Category 6: MPI systems
Verato, NextGate, Aidbox MDM. Patient identity resolution across sources.
Category 7: Conformance testing
Inferno, MITRE cqf-ruler. Verify implementations against IGs.
Categorization tips for buyers
1. Start with the primary need — server, terminology, integration, forms, MPI, or conformance. 2. Most non-trivial deployments touch 3-5 categories. 3. Some vendors span categories (Aidbox has server + terminology + forms + MPI). 4. Best-of-breed (assemble) vs. bundled (single vendor) is a trade-off.
Typical multi-vendor stack (mid-2026)
| Layer | Vendor example |
|---|---|
| FHIR server | Aidbox or HAPI |
| Terminology | Ontoserver or Aidbox |
| Auth | Keycloak or built-in |
| SDC forms | Aidbox Formbox or LHC-Forms |
| MPI | Verato or Aidbox MDM |
| Conformance | Inferno |
Buyer questions per category
1. Server: throughput, bulk data, terminology fit. 2. Terminology: SNOMED/LOINC/RxNorm depth, update cadence. 3. Integration engine: HL7v2 volume, protocol coverage. 4. Forms: SDC conformance, $extract support, mobile UX. 5. MPI: match sophistication, merge tooling, volume.
FHIR vendor landscape in 2026 is mature enough that most needs match a specific category. Match your problem to the category before evaluating vendors.
