The Da Vinci Documentation Templates and Rules (DTR) STU 2.0.1 Test Kit validates the conformance of systems to the DTR STU 2.0.1 FHIR IG. The test kit includes suites targeting the following actors from the specification:
- Payer Servers: Inferno will act as a client and make a series of requests to the server under test requesting questionnaires.
- DTR SMART App: Inferno will act as a server implementing the payer server and light EHR capabilities and responding to requests for questionnaires and clinical data made by the app under test.
- DTR Full EHR: Inferno will act as a server implementing the payer server responding to requests for questionnaires made by the EHR under test.
- DTR Light EHR: Inferno will act as a DTR SMART App that will connect to the DTR Light EHR system under test and make requests to the Light EHR under test.
In each case, content provided by the system under test will be checked individually for conformance and in aggregate to determine that the full set of features is supported.
This test kit is open source and freely available for use or adoption by the health IT community including EHR vendors, health app developers, and testing labs. It is built using the Inferno Framework. The Inferno Framework is designed for reuse and aims to make it easier to build test kits for any FHIR-based data exchange.
These tests are a DRAFT intended to allow DTR implementers to perform preliminary checks of their implementations against DTR IG requirements and provide feedback on the tests. Future versions of these tests may validate other requirements and may change how these are tested.
The DTR specification is complex and evolving and these tests do not yet cover the full scope of the specification. In particular, tests have been started but not yet released Light DTR EMR actors responsible for launching a DTR SMART App and serving data that the app can use to populate questionnaires.
For the implemented actors, see suite-specific documentation on current limitations for the payer server, DTR SMART App, DTR Full EHR tests DTR Light EHR
Use either of the following methods to run the suites within this test kit. If you would like to try out the tests but don’t have a DTR implementation, the test home pages include instructions for trying out the tests, including
- For payer server testing: running the tests against the DTR SMART App tests in this Test Kit
- For DTR SMART App testing: a sample postman collection
- For DTR Full EHR testing: sample postman collection
Detailed instructions can be found in the suite descriptions when the tests are run or within this repository for the payer server, DTR SMART App, DTR Full EHR, and DTR Light EHR.
You can run the DTR test kit via the ONC Inferno website by choosing the “Da Vinci Documentation Templates and Rules (DTR) Test Kit” test kit.
- Download the source code from this repository.
- Start or identify an Inferno Reference Server instance for Inferno to use for simulation (only needed if planning to run the DTR SMART App test suite).
- Open a terminal in the directory containing the downloaded code.
- In the terminal, run
setup.sh. - In the terminal, run
run.sh. - Use a web browser to navigate to
http://localhost.
The DTR SMART App test suite needs to be able to return responses to FHIR read and search APIs. These responses can be complex and so the suite relies on a full FHIR server to provide responses for it to provide back to systems under test. The test kit was written to work with the Inferno Reference Server
- loaded with patient pat015
- accepting bearer token
SAMPLE_TOKENfor read access.
The test kit can be configured to point to either a local instance of the reference server or to a public instance. The location of the The following are valid configuration approaches:
- Point to a public instance of the Inferno reference server at either
https://inferno.healthit.gov/reference-server/r4/orhttps://inferno-qa.healthit.gov/reference-server/r4/: update theFHIR_REFERENCE_SERVERenvironment variable in the appropriate environment file (.evn.productionwhen running in docker as above, orenv.developmentwhen running the test kit in Ruby). - Run a local instance of the Inferno Reference Server, either with docker or without docker (NOTE: this decision can be made independently from whether to run the test kit with docker or using Ruby).
We welcome feedback on the tests, including but not limited to the following areas:
- Validation logic, such as potential bugs, lax checks, and unexpected failures.
- Requirements coverage, such as requirements that have been missed and tests that necessitate features that the IG does not require.
- User experience, such as confusing or missing information in the test UI.
Please report any issues with this set of tests in the issues section of this repository.
To make updates and additions to this test kit, see the Inferno Framework Documentation, particularly the instructions on development with Ruby.
To support testing that clients can fetch, populate, and complete various questionnaires with different features, the test kit includes a framework for building different iterations of these tests. At a high-level, the framework includes the ability to associate a set of fixtures with a group of tests including
- a questionnaire that will be sent back when the client makes a $questionnaire-package request
- a questionnaire response that contains expected pre-populated and overriden items. These are indicated by the origin.source extension on items with link ids corresponding to items in the questionnaire with cql expressions for pre-population. When it is
autothat is the expected answer based on data Inferno has. When it isoverridethat is the answer that would be present if the pre-populated answer were used, but Inferno will check that a different value is present since the tester will be expected to override the answer.
See logic in mock_payer, dtr_questionnaire_response_validation, and fixture_loader, among others.
To exercise the test kit for the purposes of demoing or debugging, one option is to use the HL7 Da Vinci Documentation Requirements Lookup Service (DRLS) reference implementation. Instructions to set up the reference implementation can be found here. This setup includes downloading five different git repositories. Note that changes are currently necessary to these components to allow them to send requests to Inferno for the purposes of testing.
Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.
HL7, FHIR and the FHIR [FLAME DESIGN] are the registered trademarks of Health Level Seven International and their use does not constitute endorsement by HL7.