| eicr-condition |
The Electronic Case Reporting Condition profile is based on the **US Core-Condition** profile and establishes the core elements, extensions, vocabularies and value sets for representing the following for electronic case reporting:
- Initial Case Report signs, symptoms and diagnoses related to an event. |
| ecr-patient |
This profile represents an eCR Patient. It is based on the US Core Patient and further restricts that profile to allow masking of some elements. |
| ecr-practitionerrole |
|
| rr-relevant-reportable-condition-plandefinition |
The Relevant Reportable Condition Information PlanDefinition establishes the core elements, extensions, vocabularies and value sets for representing the following for electronic case reporting:
- The Reportability Response case definitions and reporting requirements which include:
- The data that are needed to determine reportability
- For a given condition , the mandated timeframe in which the condition should be reported to the PHA.
- The name of the Responsible Agency(ies) in which the condition was determined to be or not be reportable
- The External Resources (text and links)in association with specific conditions |
| rr-communication |
This Reportability Response Communication will be created in response to an electronic Initial Case Report Composition and the sharing of the Reportability Response with clinical care will serve several functions, including to:
- Communicate the reportability status, for the responsible PHA(s)of each condition included in the electronic Initial Case Report (eICR)
- Identify who (a PHA or an intermediary) prepared the Reportability Response
- Indicate whether the eICR has been sent to one or more PHA(s)
- Identify which PHA(s) has/have been sent the eICR
- Provide contact information for the responsible PHA(s)
- Provide suggested or required clinical follow-up activities from the responsible PHA(s), including any additional reporting needs or infection control activities
- Provide access to clinical support resources suggested by the responsible PHA(s) for identified reportable conditions
- Confirm eICR receipt and processing
A Reportability Response will also, when requested, be shared with the responsible PHAs (when they have not constructed it) for their internal use, so they understand what has been shared with clinical care and, and to monitor/audit decision support algorithm effectivesness and implementation. When a condition is considered reportable to more than one PHA, the Reportability Response can be helpful in communicating reporting that has been done to other PHAs.
The Reportability Response Communication is also structured to allow:
- Notification, alerting, routing and queueing in work or message management systems for healthcare personnel
- Dynamic and static URIs for supplemental data collection and the provision of information resources |
| eicr-travel-history |
The Electronic Case Reporting Travel History profile establishes the core elements, extensions, vocabularies and value sets for representing the following for electronic case reporting:
- The Initial Case Report subject's travel history as a string, an address or a coded location.
- Observation.effectiveTime contains the date or period of time spent in the location.
- It is possible to have multiple Observation.components, each containing a different location, but there is only a single effectiveTime. This allows for cases where a patient cannot remember exact dates of travel (e.g. I traveled to London, Paris, and Berlin in July and August 2016). However, most uses will involve a single component (location).
- Free text describing the travel history details and location can be entered using the Observation.component.valueCodeableConcept.text element
- Use component.codeableConcept to record a coded location
- Use component.extension to record a specific address |
| eicr-procedurerequest |
The Electronic Case Reporting Lab Orders profile establishes the core elements, extensions, vocabularies and value sets for representing the following for electronic case reporting:
- Initial Case Report laboratory orders and other diagnostics for the reported event. |
| pregnancy-status |
The Electronic Case Reporting Pregnancy profile establishes the core elements, extensions, vocabularies and value sets for representing the following for electronic case reporting:
- Current or prior pregnancy status enabling investigators to determine if the subject of the case report was pregnant during the course of a condition. |
| eicr-occupationhistory |
The Electronic Case Reporting Occupational History profile is establishes the core elements, extensions, vocabularies and value sets for representing the following for electronic case reporting:
- The Initial Case Report subject's occupational history. |
| eicr-location |
The location/facility in which care was provided when the case was triggered. |
| eicr-encounter |
The Electronic Case Reporting Encounter profile is based on the Encounter resource and establishes the core elements, extensions, vocabularies and value sets for representing the following encounters for electronic case reporting:
- Initial Case Report encounter related to the reported event. |
| eicr-composition |
The Electronic Case Reporting Composition profile establishes the core elements, extensions, vocabularies and value sets for representing an electronic initial case report (eICR). It describes the content requirements for the initial Case Report including:
- Patient demographics
- Patient pregnancy status
- Patient occupation and travel history
- Provider and Facility information
- Laboratory orders tests and results
- Signs and Symptoms and Diagnosis
- Medication and Immunization History
- Flags for the existence of reportable condition trigger codes in diagnoses and ordered/resulted laboratory tests. |
| ecr-organization |
The Electronic Case Reporting Organization profile is based on the **US Core-Organization** profile and establishes the core elements, extensions, vocabularies and value sets for representing the following organizations for electronic case reporting:
- Initial Case Report source provider facility/office name
- Initial Case Report source facility
- Reportability Response recipients
- Reportability Response responsible agency
- Reportability Response routing entity
- Reportability Response rules authoring agency |
| rr-eicr-processing-status |
Indicates the eICR processing status. If it was not processed or was processed with a warning, the reason and details will be contained in the related eICR Processing Status Reason resource. |
| rr-eicr-processing-status-reason |
If the incoming eICR was not successfully processed for a determination of reportability, contains the reason it was not processed. If any of the trigger codes used to generate the eICR are from an outdated version of the RCTC or the codes are marked as inactive in the latest version of the RCTC, these are flagged and component observations will hold the details of the outdated and expected versions of the RCTC. |
| rr-responsible-agency |
The Responsible Agency profile is based on the US Core Organization and sets the type to 'Responsible Agency'. A Responsible Agency is a PHA to which reporting is legally required. This represents the PHA for the location in which care was provided and/or where the patient lives. |
| rr-rules-authoring-agency |
The Rules Authoring Agency profile is based on the US Core Organization and sets the type to 'Rules Authoring Agency'. The Rules Authoring Agency is whose rules are being executed in decision support to determine reportability. This may be a State or Local PHA. In the majority of cases the Rules Authoring Agency will be the same as the Responsible Agency. Usually, a Local Public Health Agency will inherit rules from its relevant State agency, but a Local agency can adopt, replace or supplement relevant state rules. |
| rr-routing-entity |
The Routing Entity profile is based on the US Core Organization and sets the type to 'Routing Entity'. |
| ecr-knowledge-distribution |
Defines the logic and rules around determining: whether or not a condition is reportable to public health, which jurisdiction(s) is/are responsible, which jurisdiction(s) need to be notified, and if the condition is reportable, gives timing information, next steps and condition information to the clinician. |
| knowledge-distribution-valueset-library |
Defines the library containing the Reportable Condition Trigger Code value sets. These are used in Public Health as trigger codes to kick off creation of electronic initial case reports and reportability responses. |