US Core / 21th Century Cures Act

Overview

Note

Firely Server v5 has been offically certified against §170.315 g(10) 2015 Cures Edition Health IT. For more details, see our CHPL listing. Mandatory disclosures can be found here.

Firely Server can be used out-of-the-box to comply with important criteria for the 21th Century Cures Act. See the Standard referenced section provided by the ONC for a full list of standards working in combination to provide an API conforming to §170.315 g(10) 2015 Cures Edition Health IT.

See How to Test Firely Server on Inferno for more information on how to pass the official 21st Century Cures Act test. See Firely Auth Introduction for details on how to configure a client to interact with Firely Server and Firely Auth.

Supported versions

• Firely provides offical support for the following versions of the US Core ImplementationGuide:

US Core Version	Status	References
US Core 3.1.1	✅	http://hl7.org/fhir/us/core/STU3.1.1/
US Core 4.0.0	✅	http://hl7.org/fhir/us/core/STU4/
US Core 5.0.1	✅	http://hl7.org/fhir/us/core/STU5.0.1/

• All versions of SMART on FHIR and Bulk Data Access approved for the SVAP Process in 2022 are supported by Firely Server:

ImplementationGuide	Status	References
Bulk Data Access 1.0.0	✅	http://hl7.org/fhir/uv/bulkdata/STU1.0.1
Bulk Data Access 2.0.0	✅	http://hl7.org/fhir/uv/bulkdata/STU2
SMART on FHIR 1.0.0	✅	http://hl7.org/fhir/smart-app-launch/1.0.0
SMART on FHIR 2.0.0	✅	http://hl7.org/fhir/smart-app-launch/STU2

Conformance & Configuration

• Firely Server provides full profile and interaction support as defined in “Conforming to US Core”:

  • Firely Server can be populated with resources conforming to US Core

  • All elements defined as must-support by the implementation guide are supported

  • All references between FHIR resources defined as must-support by the implementation guide are supported

  • All search and CRUD interactions defined by US Core are supported, including optional search parameters

• All StructureDefinitions for profiles and extensions (v3.1.1) are loaded by default in the standard SQLite administration database of Firely Server. No additional configuration needed in order to validate against these conformance resources.

• A mapping between USCDI and the US Core profiles can be found in the US Core ImplementationGuide.

Known Limitations

• In order to validate resources claiming to conform to US Core, it is necessary to configure Firely Server to use an external terminology server incl. support for expanding SNOMED CT and LOINC ValueSets. See Terminology services.

• Certain parameters are not implemented for the $docref operation on DocumentReference resources. See Fetch DocumentReference - $docref for more details.

Test Data

Firely provides test data covering all US-Core profiles and all elements marked as Must-Support. In order to load all examples, two transaction bundles need to be posted against the base endpoint of Firely Server. The following Postman collection provides you with the bundles itself, and the bundle entries as individual PUT requests.

The following steps are necessary in order to execute the test collection against our own Firely Server instance:

1. Select “Fork Collection” or “View collection” in the Postman dialog

   

2. Sign-In with your Postman account

3. Create a new Postman environment with a “BASE_URL” variable and adjust the URL to your server endpoint

   

4. Make sure that the newly created environment is selected as the active environment

5. Open the collection “Firely Server - US Core Tests”

   

6. Execute the transaction request, the expected response is “HTTP 200 - OK”.