eCR Now FHIR App

Introduction

A production version of the eCR Now FHIR App and its source code are now available for EHR companies and other implementors to download and implement. The App provides COVID-19 electronic case reporting capabilities for EHRs that heretofore did not have it. It can also be configured to do full electronic case reporting for a full set of reportable conditions when COVID-19 is a diminished focus.

The App is different from many commercial apps in both its attributes and its provisioning. It was designed to be implemented now and work with the substantial infrastructure that is in place for electronic case reporting. The eCR Now technical team will partner with implementors that choose to use the App, but the team will not be hosting it or processing it through all the different EHR app stores.

This page provides context and lays out the planned process and communication channels to use the eCR Now FHIR App to meet the critical electronic case reporting needs of the COVID-19 pandemic.

The current version of the App and its source code can be found here:

GitHub App Source Code

Context

Electronic case reporting (eCR) involves “the automated identification of reportable health events in electronic health records and their transmission to state and local public health authorities for review and action.” Reporting is a legal requirement for COVID-19 and many other conditions, but the specific laws vary by state. Triggering case reports out of EHRs does not, by itself, definitively establish that something is reportable or which public health agencies should receive it if it is.

To address the complexity of reporting requirements, the Centers for Disease Control and Prevention (CDC), the Council of State and Territorial Epidemiologists (CSTE), and the Association of Public Health Laboratories (APHL) have implemented shared eCR services on the APHL AIMS platform including provisioning, decision support, routing, and delivery infrastructure to provide electronic case reports to public health agencies for integration into their surveillance systems. The eCR Now App is constructed to connect to, and take advantage of, this existing infrastructure to support appropriate reporting even though neither it, nor public health agencies, currently support production HL7 FHIR services.

eCR Infrastructure

Implementation

The eCR Now App is intended to run as a background process during patient encounters and to report automatically to appropriate public health jurisdictions and their surveillance systems though the APHL AIMS shared service infrastructure. In this way it should not burden or disrupt healthcare provider workflows. On the EHR side, the App is built to leverage the work the Argonaut Project, HL7, and ONC that have advanced the FHIR APIs that are now implemented in EHRs.

The app supports HL7 FHIR DSTU2 - EHR access because that is the level of FHIR API that is in many installed EHRs. The App also now supports HL7 FHIR R4 because some EHRs now have that API implemented and it is more robust from a data access standpoint. The app can also be made to use HL7 FHIR STU3.

On the “public health side” of the App, it produces an HL7 CDA eICR 1.1. This is the initial case report standard that can be received by the APHL AIMS shared services platform, can be processed by the RCKMS system, and then can be integrated into the public health agency surveillance systems or rendered for them in viewable HTML documents.

Other App attributes include:

  • By configuration can do full electronic case reporting in addition to COVID-19
  • Produces fully validated outgoing HL7 CDA eICRs v1.1
  • Transport out to the APHL AIMS shared services platform
    • Included support for Direct
    • An interface for XDR and other transport
  • It receives and sorts the returned Reportability Responses to identify those that should be notified to the provider of record and attached to the patient’s chart from those that support EHR system administration needs
  • It consumes up-to-date trigger codes and reporting parameters from the electronic Reporting and Distribution (eRSD) system minimizing health system and EHR trigger code management
  • Local storage of eICRs that have been sent
  • Automated launch possibilities for complete background operations:
    • No UI SMART on FHIR App Launch
    • System API launch when provided with patient ID, encounter ID, FHIR Server URL
  • Can trigger on all of the following:
    • Lab orders
    • Lab result test names
    • Lab result values
    • Conditions in problem list
    • Conditions in Dx
    • Medications

Teaming and Release Process

If an EHR presents a capable FHIR API, App implementation is not difficult. At a recent HL7 FHIR Connectathon, all participants who tried to implement the app were successful even though they had possession of the app for less than a week.

The eCR Now App is being developed with the intent of its sharing, with its source code, for implementation by EHR vendors and other implementors. The first production release of the eCR Now app occurred on June 3rd 2020.

Next Steps

  1. Access the App and source code from the GitHub site
  2. Download and implement the app in your local development sandbox following instruction on the GitHub site
  3. Verify that the app runs successfully in your local development sandbox
  4. Post any issues or question to the Zulip chat channel
  5. Add COVID-19 data into your development sandbox EHR for testing purposes and test all of the different triggering circumstances
  6. Connect with the eCR team via the ecr-info@aimsplatform.org early to plan an onboarding and coordination process
  7. Continue to check here for subsequent App updates

 

Communication Channels and Resources

eCR Now App Discussion on Zulip

electronic Reporting and Surveillance Distribution System (eRSD)

GitHub App Source Code