EHR Implementers - Test Package and Resources
These tests seek to confirm that electronic initial case reports (eICRs) generated by electronic health record (EHR) systems are correctly constructed, populated, and conform to the standard specification. The test package instructions outline resources for testing the eICR creation process. These resources apply to both new development and implementation of electronic case reporting (eCR) features within an existing EHR system. Learn more about eICR creation on the EHR Implementers - eICR Creation, Validation, & Standards page.
The purpose of these tests is to confirm that eICRs are triggered correctly based on trigger code value sets (Reportable Conditions Trigger Codes (RCTC)) found in the Electronic Reporting and Surveillance Distribution (eRSD). This test suite is focused specifically on triggering, and not eICR creation or delivery. Note that these tests are limited to trigger code matching and exclude any functionality related to timing of triggering or eICR creation. Learn more about triggering on the EHR Implementers - EHR Triggering page.
The purpose of this test package is to test which Reportability Responses (RRs) are correctly routed in response to submitted eICRs. “Reportable” and “may be reportable” should be attached to the patient chart, placed in the appropriate provider/support staff work queue, or communicated to the provider through some other internal EHR communication process.
However, when an eICR does not meet reporting requirements, providers should not be burdened with those RRs. The “not reportable” and “no rule met” RRs are for EHR system administrators to use to confirm that reporting is functioning. In addition, these RRs will notify system administrators of errors (file was not reported due to validation failure or other error, provider must report manually) and warnings (processable deviations). Learn more about the RR on the EHR Implementers - Reportability Response Receipt & Use page.
This test package tests the full connectivity workflow. This test builds on the testing above, requires the sending healthcare facility to identify its location for rules processing, and should be started after the previous test packages have been successfully completed (Personally identifiable information should still not be included in this testing step). It confirms that triggering, eICR creation, connectivity and delivery, and RR receipt and processing are working correctly. Additionally, information on facility and patient data requirements, as well as RR examples, are provided. Learn more about AIMS connectivity on the EHR Implementers - eCR Exchange and Transport page.
End-to-End Content Testing
When all of the test suites have been successfully completed, providers then move to content testing with the public health agency in their jurisdiction. Contact the AIMS eCR team to inquire about contact information for any particular PHA.
This test package contains sample eICR and RR messages for five COVID-19 scenarios, including HTML and XML files for each. The test files are labeled based on what they would have triggered on – problem/observation, diagnosis, lab order, lab test negative, and lab test positive.