HL7 FHIR® Implementation Guide: Electronic Case Reporting (eCR) - US Realm
1.1.0 - STU 2 Ballot

This page is part of the electronic Case Reporting (eCR) (v1.1.0: STU 2 on FHIR R4 Ballot 1) based on FHIR R4. The current version which supercedes this version is 2.1.0. For a full list of available versions, see the Directory of published versions

Relationship to Other Standards

Previous Page - Rule Filter Generation

In coordination with the publication of this FHIR standard, an updated version 3.0 of the HL7 CDA R2 Electronic Initial Case Report (eICR) Standard for Trial Use (STU) IG (see the link under “STU Documents” for STU 3.0) is also being published. The FHIR eICR transaction in this implementation guide and the separately published CDA eICR implementation guide standard will continue to be maintained in tight coordination with each other.

In order to get data as readily as possible from clinical care and minimize provider burden, the CDA eICR was built extensively on published HL7 Consolidated CDA Templates for Clinical Notes (C-CDA R2.1) templates. The FHIR eICR transaction reuses many of the HL7 FHIR US Core Implementation Guide v3.1.1: STU 3 profiles, and has been mapped to both the Common Clinical Data Set (CCDS), and now, the (U.S. Core Data for Interoperability) USCDI. There are some eICR data, critical to public health activities, that are in the eICR transaction but not in the USCDI at this time. As well,some USCDI data are not legally authorized for delivery to public health agencies in the context of case reporting, but every effort will be made in an ongoing way to minimize variations from the USCDI. The following table illustrates a high-level mapping from USCDI v1 to eICR:

USCDI-Mapping

Both the CDA and FHIR versions of the eICR are intended to be used as an all-jurisdiction, all-condition report to public health agencies from EHRs. The eICR was created from a Council of State and Territorial Epidemiologists (CSTE) Task Force recommendation that identified necessary data to support case reporting. There is also an existing HL7 CDA R2 Reportability Response (RR) STU IG that supports several functions for providing information back to clinical care in response to received eICRs. A FHIR version of the CDA Reportability Response transaction is included in this eCR FHIR implementation guide.

This aggregate FHIR electronic case reporting STU implementation guide (hereby known as FHIR eCR) also includes an electronic Reporting and Surveillance Distribution (eRSD) transaction that includes the Reportable Condition Trigger Codes (RCTC) and other reporting guidance. A distribution service for the eRSD transaction including the RCTC trigger codes can be found at https://ecr.aimsplatform.org.

XSLT transforms will be made available to facilitate the conversion of eICR and RR transactions between CDA and FHIR formats. These transforms and other supportive material can be found in GForge in the FHIR_IG_eCR SVN folder.

Next Page - Acknowledgements