Inferno (g)(10) Compatibility

How mock.health performs against the ONC (g)(10) Standardized API for Patient and Population Services test suite, and how to run it yourself.

Why rehearse against a sandbox

Inferno is the certification harness, but pointing it at your own half-built server produces failures you can't distinguish from harness setup errors. Running it first against a server known to pass most groups tells you which failures are yours. It also lets you learn the suite's shape — its launch sequences, its terminology assertions, its must-support expectations — before the run that counts.

Current standing

The suite is run against the live sandbox and the results are published rather than claimed. Groups covering standalone launch, EHR launch, and the single-patient API pass; the remaining gaps are documented on this page with the specific assertion that fails and why, so you can tell whether a gap touches your integration at all.

Pointing Inferno at mock.health

Register a SMART app in the sandbox, set the FHIR base URL to https://api.mock.health/fhir, supply the client ID and redirect URI Inferno gives you, and choose a patient id from the sandbox as the single-patient target. The SMART on FHIR guide covers the launch parameters; USCDI compliance covers the data-element side the suite asserts against.