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 the available 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
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. Please also note these tests are limited to trigger code matching, and exclude any functionality related to timing of triggering and or eICR creation. Learn More About Triggering
The purpose of this test package to confirm which Reportability Responses (RRs) have reportable, may be reportable, not reportable or no rule met eICRs. “Reportable” and “may be reportable” should be attached to the patient chart OR placed in the appropriate provider / support staff work queue or are communicated to them through some other internal EHR communications. But when an eICR does not meet reporting requirements, providers should not be burdened with those Reportability Responses at all. The “not reportable” and “no rule met” Reportability Responses are only for EHR system administrators to use to confirm that reporting is functioning and to be notified of errors and warnings. Learn More About RR
This test package confirms the full connectivity workflow of eCR. This test builds on the testing identified above, needs the sending healthcare facility to identify its location to associate appropriate rules, and should be started after the previous test packages have been successfully completed (PHI should still not be included in this testing step). It confirms triggering, eICR creation, connectivity and delivery, and RR receipt and processing. Additionally, information on facility and patient data requirements, and potential reportability response examples are provided. Learn More About AIMS Connectivity
End to End Content Testing
When all of the test suites have been successfully completed, onboarding providers then move to content testing with the Public Health Agency in their jurisdiction. Requirements and processes may vary by jurisdiction.