EHR Implementers - Readiness and Implementation Checklist
√ EHR Readiness
Electronic health record (EHR) readiness involves elements related to your EHR software, its implementation in the specific healthcare setting, the ability to send the electronic initial case report (eICR), and the ability to receive and process a Reportability Response (RR) coming back.
-
Your EHR vendor and/or healthcare technical staff will download and update an Electronic Reporting and Surveillance Distribution (eRSD) (including Reportable Conditions Trigger Codes (RCTC)) from public health that will guide the EHR when and how to send reports. (For more technical information on triggering, visit the EHR Implementers - EHR Triggering page or visit the eRSD site (external site).)
-
The EHR needs to be able to trigger the transmission of eICRs. (For more technical information on triggering, visit the EHR Implementers - EHR Triggering and EHR Implementers - Test Package and Resources pages.)
-
The EHR should be able to create the all-condition, all-jurisdiction eICR in accordance with the standard. (For more technical information on the eICR, visit the EHR Implementers - eICR Creation, Validation, & Standards and EHR Implementers - Test Package and Resources pages.)
-
The EHR should be able to receive and process a RR for each eICR that you send. (For more technical information on the RR, visit the EHR Implementers - Reportability Response Receipt & Use and EHR Implementers - Test Package and Resources pages.)
√ Communicating Intent
When you are moving forward with electronic case reporting (eCR), the clinical care organization will need to communicate intent to participate to your state public health agency (PHA) (For more information on communicating intent, visit the Healthcare Providers - Readiness and Implementation Checklist page.), as well as communicate with the eCR Support Team by contacting the eCR general inquiries team at eCR-Info@aimsplatform.org.
√ Planning Connectivity
Establish technical connectivity through a direct connection to the Association of Public Health Laboratories (APHL) Informatics Messaging Services (AIMS) platform or through a Health Information Exchange (HIE) or Health Information Network (HIN). Which approach is used may depend on policy and membership issues. (For more technical information on connectivity, visit the EHR Implementers - eCR Exchange and Transport and EHR Implementers - Test Package and Resources pages.)
√ Onboarding and Production
When the previous readiness and implementation steps and testing have been completed, you are ready to move into production.
When you are ready to onboard, submit a help desk ticket with the eCR support team by emailing Informatics.Support@aphl.org and include “eCR” in the subject line to ensure proper triage and routing. Depending on your method of connectivity, there may be other endpoint information that needs to be shared as well. (Learn more about technical connection on the Healthcare Providers - Readiness and Implementation Checklist page.) Contact the eCR general inquiries team at eCR-Info@aimsplatform.org with any questions that you may have about the process.
