US CORE

  • Tested Version: Firely Server has been tested against US Core Version 3.1.1 - STU3 Release

  • All StructureDefinitions for profiles and extensions 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.

  • Firely Server provides full “Profile Support and Interaction Support”:

    • Firely Server can be populated with resources conforming to US Core, including all elements marked as Must-Support

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

See How to Test Firely Server on Inferno for more information on how to pass the official 21st Century Cures Act test.

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.

  • The $docref operation is not yet supported on DocumentReference resources

  • No conformance claim is added by default to CapabilityStatement.instantiates

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

    ../_images/Compliance_ForkTestCollectionPostman.png

  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

    ../_images/Compliance_EnvironmentTestCollectionPostman.png

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

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

    ../_images/Compliance_USCoreTestCollectionPostman.png

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