Electronic Case Reporting (eCR), published by HL7 International / Public Health. This guide is not an authorized publication; it is the continuous build for version 3.0.0-ballot built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/case-reporting/ and changes regularly. See the Directory of published versions
| Page standards status: Informative |
The eICR transaction involves the transmission of data identified by a Council of State and Territorial Epidemiologists Task Force as being important to a multi-condition, multi-jurisdiction case report.
eICR documents will usually be automatically initiated by matching EHR data against trigger codes. Note that matching with trigger codes is only an indication of a potentially reportable event. Additional rules processing is required to determine reportability based on the policies and regulatory requirements of the jurisdiction of residence and jurisdiction of care of the initiating event. Whether a specific initiated event is reportable is communicated through the Reportability Response.
The following figure illustrates automatic initiation by trigger matching:
Figure 1: eICR Triggering and Transmission Timing
There are three ways an eICR may be initiated:
The following matrix summarizes the three types of initiation:
| Initiation Type | How is the eICR initiated? | How is the eICR routed on a shared services platform? | eICR Initiation Reason Extension | eICR Initiation Type Extension | Can values exist in eICR trigger code segments? |
|---|---|---|---|---|---|
| Trigger code initiation | An EHR data match against a trigger code value | Reporting to relevant PHAs is based on public health decision support[^1] reportability determinations | Not included | Not included | Yes, one or more must be present |
| Manual initiation | By an action by a provider of care because they suspect there may be a reportable condition | Forced reporting to all involved PHAs regardless of reportability determinations | Includes free text or coded reason(s) for manual initiation | PHC1464 | Yes, if the EHR checks for matches after manual initiation or if the match precedes manual initiation (however, they may not exist) |
| Alternate initiation | EHR / healthcare site "programmed-in" initiation to meet a transient need | Forced reporting to the PHA where care was provided regardless of reportability determinations. Reporting to other jurisdictions may occur if other reportable conditions are present. | Includes free text or coded reason(s) for alternate initiation | PHC2235 | Yes, if the EHR checks for matches after alternate initiation or if the match precedes alternate initiation (however, they may not exist) |
Populating a manually or alternately initiated eICR. In the eICR Composition:
For an automatically (trigger code) initiated eICR, neither extension is present and at least one trigger code flag must be present.
Alternate initiation scenarios.
See the Manually Initiated eICR and Alternately Initiated eICR Composition examples, and the Reportability Response guidance on routing and notification for manually and alternately initiated eICRs.
The eICR also includes pregnancy information, occupational data, therapeutic response to medication, homeless information, a vital signs snapshot, emergency outbreak information, exposure and contact information, disability status, and semi-structured travel history. The eICR is conveyed through an unsolicited push transaction from healthcare to public health (see Transport Options for further details) using a basic RESTful submit and/or FHIR Messaging. The FHIR Messaging bundle can also be transmitted over legacy transport and networks. There may be several different intermediaries involved in the transmission including Health Information Exchanges, Health Information Networks, and other trusted third parties.
A Reportability Response will always be returned to the sending healthcare organization for every eICR received. A Reportability Response may also be sent to PHAs with the FHIR eICR transaction to provide the PHAs with information about what has been determined to be reportable, what PHAs have been sent eICR information, and what else has been communicated to healthcare.
A number of profiles and extensions have been defined for the eICR transactions - see Artifact Index for a listing of these profiles. The eICR Composition profile (which is contained in a eICR Document Bundle) is the starting point for the transaction and all the other profiles are referenced from that profile (see diagram below for the main profile relationships).
![]() |