Skip to main content
Inferno on HealthIT.gov Staging Host - NOT FOR PRODUCTION USE
Inferno on HealthIT.gov is for demonstration only. Not for use with is not for use with sensitive data or Protected Health Information (PHI). Data periodically removed.

Inferno on HealthIT.gov

HL7® FHIR® Testing by The Office of the National Coordinator for Health IT

Inferno on HealthIT.gov is a public service for running select FHIR conformance tests built with Inferno. This includes tests relevant to the ONC Health IT Certification Program and tests that target other popular FHIR Implementation Guides.

Learn More Start Testing Now

ONC Health Certification Program

Evaluate a publicly accessible test server to the ONC (g)(10) Standardized API Certification Criterion using this public testing instance of Inferno.

ONC (g)(10) Standardized Test Kit

FHIR Resource Validator

Validate individual FHIR Resources to the base FHIR specification or specific FHIR Profiles

Open Validator

What is Inferno?

Open Source FHIR Testing

Inferno is an open source tool for creating, executing and sharing automated conformance tests for the FHIR Standard. Inferno on HealthIT.gov hosts several tests created with Inferno, but Inferno is designed so anyone can create and host their own tests.

Start Testing Today

Inferno on HealthIT.gov is a public host for the (g)(10) Standardized API Test Kit, which is an approved test method for the §170.315(g)(10) criterion within the ONC Certification Program. It also contains tests for several popular FHIR Implementation Guides. Browse the Test Kit page for a list of tests that are currently available.

Create your own tests

Inferno is as flexible as the FHIR standard, and tests need to be created for each unique FHIR use case. The Inferno Framework provides tools and common approaches to testing systems for FHIR conformance. Visit the Inferno Framework Documentation Site to learn more.

Run your own Inferno Instance

Inferno makes it easy to run tests on your local machine or host a shared copy behind your firewall. Inferno tests are packaged in Test Kits, which are standalone applications tuned to Implementation Guide or certification criteria. Each Test Kit on Inferno on HealthIT.gov provides a link to its repository where you can learn how to download and run it locally.

Integrate with Inferno

Inferno's user interface is powered by an open, full-featured API to enable integration into external tools or continuous integration pipelines. Learn more in the Inferno Framework Documentation Site.

Additional Tools

Comprehensive testing solutions need more than just tests. Inferno provides additional utilities, such as Reference Applications, that can be optionally integrated alongside tests within Inferno Test Kits.

News and Updates

April 2025 Monthly Update

Inferno on HealthIT.gov has been updated to include new versions of following Test Kits:

These updates include changes to the way inputs are managed for SMART App Launch workflows. This change is part of our continued efforts to improve the user experience of Inferno, and to make it easier for test authors to create and maintain tests. For more information, see the announcement regarding these changes.

Update to Authorization Inputs

Inferno is updating the way inputs are managed for SMART App Launch workflows. This change is part of our continued efforts to improve the user experience of Inferno, and to make it easier for test authors to create and maintain tests.

This update to Inferno includes a new compound input type, AuthInfo, which manages OAuth 2.0 inputs for a test. This compound type includes fields for all of the information necessary to perform an authorization workflow, including the authorization workflow type, client ID, client secret, scope, and redirect URI. This change will provide the following benefits:

  • Inferno will intelligently display or hide authorization-related fields based on the selected authorization workflow, making it easier for users to understand which inputs are required for a given test.
  • Test authors can include a single authorization input in their tests, instead of including several for the various components of the OAuth 2.0 authorization workflow.
  • Inferno will automatically perform token refreshes when necessary, without any special attention from the test author or user.

The primary impact for test users is they will notice that OAuth 2.0-related inputs are now organized together, and dynamically update based on selected authorization workflows.

And while we strive for stability and backwards-compatibility for all uses of Inferno today, the following users of Inferno may be affected by this change and may need to adjust their usage accordingly:

  • Users who have created custom presets or sets of saved inputs
  • Users who reuse old test sessions
  • Users who integrate directly with the Inferno JSON API
  • Users who automate Inferno UI interactions

For those that integrate with Inferno using the JSON API, the structure of inputs will change. The JSON representation of inputs which used to look like this:

{
  "name": "standalone_client_id",
  "description": "Client ID provided during registration of Inferno as a standalone application",
  "title": "Standalone Client ID",
  "type": "text",
  "value": "SAMPLE_CONFIDENTIAL_CLIENT_ID"
},
{
  "name": "standalone_client_secret",
  "description": "Client Secret provided during registration of Inferno as a standalone application. Only for clients using confidential symmetric authentication.",
  "title": "Standalone Client Secret",
  "type": "text",
  "value": "SAMPLE_CONFIDENTIAL_CLIENT_SECRET"
},
{
  "name": "standalone_requested_scopes",
  "description": "OAuth 2.0 scope provided by system to enable all required functionality",
  "title": "Standalone Scope",
  "type": "textarea",
  "value": "launch/patient openid fhirUser offline_access patient/*.read*"
}

…will now be structured like this:

{
  "name": "standalone_smart_auth_info",
  "_title": "Standalone Launch Credentials",
  "_type": "auth_info",
  "value": {
    "client_id": "SAMPLE_CONFIDENTIAL_CLIENT_ID",
    "client_secret": "SAMPLE_CONFIDENTIAL_CLIENT_SECRET",
    "requested_scopes": "launch/patient openid fhirUser offline_access patient/*.read"
  }
}

A preview of this change is available on the Inferno on HealthIT.gov QA site. Please reach out to the Inferno team if you have questions regarding this change.

View more news and updates

Upcoming Events

View all events