eICR Process and Process Diagram

When engaging with our electronic case reporting (eICR) module for Public  Health Agency (PHA) reporting, the process uses an automated trigger code table built into OfficeEMR to determine when to build and automatically send an eICR. OfficeEMR is currently using AIMS Version: eICR Data Quality Schematron 2.0. The sending of the eICR uses the practice's direct mail and sends out to the AIMS Platform who acts as a clearinghouse of sorts that validates the file sent, forwards on to the appropriate PHA, and returns a Reporting Response (RR) to the practice. The process steps are as follows:

User Saves Signed Note OR Saves Lab Results

Evaluate Against Case Reporting Trigger Table
No Match
END

MATCH → Continue

Stage eICR CCDA Table for Sending
OfficeEMR - Backend Process

Scheduled Job Detects Staged eICRs for Transmission
OfficeEMR - Backend Process

Automated Send of eICR to AIMS via Practice's SES Direct Secure Messaging
OfficeEMR - Backend Process

AIMS Receives and Validates eICR Document
AIMS Process

AIMS Routes eICR to RCKMS for Reportability Evaluation
AIMS/RCKMS Process

AIMS Generates RR and routes messages -except errors- to PHA
AIMS Process

AIMS Sends RR Back to Practice via Direct Messaging
AIMS - Transmission to Practice

Inbound Message Handler Receives RR
OfficeEMR - Backend Process

OfficeEMR will Parse RR and Extract Key Determination Data for reporting dashboard
OfficeEMR - Backend Process

Match RR to Original eICR (if possible) for patient association and reporting dashboard
OfficeEMR - Backend Process

Store RR Document for practice use
OfficeEMR - Backend Process

Route Communication and Attach RR to Patient Timeline under Health Exchange
OfficeEMR - Visible in UI

Handle RR Errors and Warnings
(Auto-Generate Support Message for Salesforce Case Creation)
OfficeEMR - Backend Support Alert

Display RR in New Case Reporting Dashboard in Report Portal
OfficeEMR - Visible in UI