State Medicaid programs in the US have a terminology problem that few commercial buyers ever see at the same intensity. A single state agency has to serve managed care organizations, fee-for-service plans, screening programs, and external quality review organizations, each with its own value-set expectations. The terminology server underneath has to keep all of that consistent without becoming the slow link in the prior-auth chain. These products keep showing up on Medicaid procurements in 2026 for good reasons.
Read the cornerstone Complete US FHIR Terminology Server Buyer's Guide for 2026 for the buying frame. For the US healthcare IT news hub, the broader desk covers related Medicaid technology stories.
HAPI FHIR for a State-Owned Stack
Several state Medicaid agencies run HAPI-backed terminology services as part of their FHIR data platforms. The reasons are practical. HAPI is open source, which fits a state procurement preference for non-proprietary stacks, and the Java skill set is easy to staff through the system integrators who already work on Medicaid Management Information Systems. The trade-off is operational load. A state agency running HAPI owns LOINC loads, SNOMED CT US Edition refreshes, and version drift control.
Smile Digital Health
Smile Digital Health shows up in Medicaid procurements where the agency wants HAPI mechanics behind a commercial SLA. The pitch is straightforward. Managed LOINC and SNOMED CT loads on a published schedule, audit logs that satisfy CMS and OIG reviewers, and a support contract that has someone on call when a measure season pulls more $expand traffic than the test environment showed.
Ontoserver
Ontoserver has a reputation for clean $translate maps, and for a Medicaid agency that has to cross-walk billing codes between ICD-10-CM and other US vocabularies, that matters. Procurement is more expensive than the open-source route, but for agencies that run multi-vendor MCO ecosystems, the consistency that Ontoserver brings to value-set expansion can pay for itself in fewer measure-season fire drills.
Firely Terminology Server
Firely is a less common Medicaid pick than HAPI or Ontoserver, but it surfaces on shortlists for state agencies running a .NET stack or smaller MCO portfolios. Its FHIR fidelity is strong, and for a Medicaid program that wants a tidy terminology server without operational sprawl, it is worth a real evaluation.
VSAC-Mirrored Local Stack
A pattern that has matured for Medicaid programs is mirroring NLM Value Set Authority Center value sets locally and serving $expand from a HAPI or Ontoserver instance. The agency gets the speed of a local server with the authority of VSAC content. For HEDIS measure work and CMS quality reporting, this pattern keeps the measure logic stable when VSAC publishes mid-cycle updates.
What Actually Drives Medicaid Procurement
The named winner on a Medicaid program rarely reflects a feature-by-feature comparison. The deciding factors usually look like this. Does the agency need a managed vocabulary refresh? Then Smile Digital Health or Ontoserver. Does the agency have a strong system integrator and a preference for open-source stacks? Then HAPI with state ownership of vocabulary ops. Does the agency need clean $translate behavior across the US billing vocabularies? Then Ontoserver gets a closer look.
The Commercial vs Open-Source Terminology Servers for US Payers comparison is a useful next read for state agencies sizing the operational trade-off. The right pick for a US Medicaid program is the one that survives a CMS measure season and a leadership change without anyone losing a weekend, and that filter is more useful than any vendor scorecard.
Sources
- CMS Interoperability and Prior Authorization Final Rule CMS-0057-F - Fact sheet, CMS, 2024
- CMS-0057-F Final Rule fact sheet detailing payer FHIR API requirements - PDF, CMS, 2024
- Updated eCQM specifications and implementation resources for 2026 reporting period - Resource page, eCQI Resource Center / ONC, 2025