|
1 | | -# Inferno Template Test Kit |
| 1 | +# Central Cancer Registry Reporting |
| 2 | + |
| 3 | +The Central Cancer Registry Reporting (CCRR) Test Kit is a testing tool for Health IT systems |
| 4 | +seeking to meet the requirements of the STU 1.0.0 version of the HL7® FHIR® |
| 5 | +[Central Cancer Registry Reporting IG](https://hl7.org/fhir/us/central-cancer-registry-reporting/STU1/). |
2 | 6 |
|
3 | | -Inferno template [Inferno](https://github.com/inferno-community/inferno-core) Test Kit |
4 | | -for FHIR testing. |
5 | 7 |
|
6 | | -## Inferno Developers Notes |
7 | | -The generator is not capable of bringing the test kit to its current state. It is used to generate tests that are then organized manually. |
| 8 | +This test kit currently contains suites that verify the conformance of systems playing the following roles: |
| 9 | +- **Health Data Exchange App (HDEA) Report Generator**: Verifies that the Health IT system can generate |
| 10 | + conformant and complete reports to send to a cancer registry. |
| 11 | +- **Electronic Health Record (EHR) Data Source**: Verifies that the Health IT system can respond to queries |
| 12 | + for the data needed to create a cancer registry report. |
8 | 13 |
|
9 | | -## Instructions for Developing Your Test Kit |
| 14 | +## Status |
10 | 15 |
|
11 | | -Refer to the Inferno documentation for information about [setting up |
12 | | -your development environment and running your Test Kit](https://inferno-framework.github.io/docs/getting-started/). |
| 16 | +These tests are a **DRAFT** intended to allow CCRR IG implementers to |
| 17 | +perform preliminary checks of their implementations against the IG's requirements and provide feedback |
| 18 | +on the tests. Future versions of these tests may validate other requirements and may change how these |
| 19 | +are tested. |
13 | 20 |
|
14 | | -More information about what is included in this repository can be [found here](https://inferno-framework.github.io/docs/getting-started/repo-layout-and-organization.html). |
| 21 | +## Known Limitations |
15 | 22 |
|
16 | | -## Documentation |
| 23 | +This test kit does not currently include test suites for all actors and all capabilities defined by the CCRR IG. |
| 24 | +Out of scope areas of the IG include the Cancer Registry and Trusted Third Party actors and details related to the use of the |
| 25 | +[MedMorph framework](https://hl7.org/fhir/us/medmorph/STU1/) by all actors to coordinate reporting triggering, |
| 26 | +report content, and report delivery requirements. |
| 27 | + |
| 28 | +The existing HDEA and EHR suites focus on report content and do not currently test most details of |
| 29 | +the report exchange workflow. The following areas are not tested: |
| 30 | +- EHR requirements around authentication and authorization and the use of Subscriptions to provide |
| 31 | + notifications to HDEAs. |
| 32 | +- HDEA requirements around the gathering of report contents from EHRs and the delivery of completed reports |
| 33 | + using FHIR APIs. |
| 34 | + |
| 35 | +For additional details on suite-specific limitations, see the suite documention in the running tests or the |
| 36 | +corresponding content in the source repository ([EHR suite limitations](https://github.com/inferno-framework/cancer-registry-reporting-test-kit/blob/main/lib/cancer_registry_reporting_test_kit/docs/ehr_suite_description.md#current-limitations), |
| 37 | +[HDEA suite limitations](https://github.com/inferno-framework/cancer-registry-reporting-test-kit/blob/main/lib/cancer_registry_reporting_test_kit/docs/hdea_suite_description.md#current-limitations)) |
| 38 | + |
| 39 | +## Repository and Resources |
| 40 | + |
| 41 | +The Central Cancer Registry Reporting Test Kit can be [downloaded](https://github.com/inferno-framework/cancer-registry-reporting-test-kit/releases) |
| 42 | +from its [GitHub repository](https://github.com/inferno-framework/cancer-registry-reporting-test-kit). |
| 43 | + |
| 44 | +## Providing Feedback and Reporting Issues |
| 45 | + |
| 46 | +We welcome feedback on the tests, including but not limited to the following areas: |
| 47 | +- Validation logic, such as potential bugs, lax checks, and unexpected failures. |
| 48 | +- Requirements coverage, such as requirements that have been missed, tests that necessitate features that the |
| 49 | + IG does not require, or other issues with the interpretation of the IG’s requirements. |
| 50 | +- User experience, such as confusing or missing information in the test UI. |
| 51 | + |
| 52 | +Please report any issues with this set of tests in the [issues section](https://github.com/inferno-framework/cancer-registry-reporting-test-kit/issues) |
| 53 | + of the repository. |
| 54 | + |
| 55 | +## Inferno Documentation |
17 | 56 | - [Inferno documentation](https://inferno-framework.github.io/docs/) |
18 | 57 | - [Ruby API documentation](https://inferno-framework.github.io/inferno-core/docs/) |
19 | 58 | - [JSON API documentation](https://inferno-framework.github.io/inferno-core/api-docs/) |
20 | 59 |
|
21 | | -## Example Inferno Test Kits |
22 | | - |
23 | | -A list of all Test Kits registered with the Inferno Team can be found on the [Test Kit Registry](https://inferno-framework.github.io/community/test-kits.html) page. |
24 | | - |
25 | 60 | ## License |
26 | 61 | Copyright 2024 TODO |
27 | 62 |
|
|
0 commit comments