This resource defines the expected capabilities for both client and server participating in eCR exchange

This section describes the expected capabilities of a client consuming eRSD resources including the Reportable Conditions Trigger Codes (RCTC).

Conformance requirements for an eRSD Client

The eRSD Client SHALL:

• Support fetching the eRSD Bundle using the supported RESTful interactions.
• Support processing PlanDefinition and ValueSet resources that are included in the Bundle.

The eRSD Client MAY:

• Support fetching and reading a Person resource.
• Support fetching and reading Subscription resources associated with a Person.

Packages the contents referenced by an asset-collection library such as a quality program release or version manifest.

This Composition profile represents an electronic initial case report (eICR). It is based on and further constrains the US Public Health Composition.

This Composition profile represents the Reportability Response that is created in response to an electronic Initial Case Report Composition.

This Bundle profile represents an RR Document Bundle. It contains an RR Composition.

This profile represents external resources such as a text guidance, link to access forms for additional reporting needs, additional testing and/or laboratory testing needs, treatment and/or prevention resources, Public Health Agency contact information and general additional resources.

This profile represents a relevant reportable condition.

This profile represents reportability information based on the PHA in which is located the patient's home, the provider facility, or both locations.

This profile contains a detailed textual description of the reportable condition(s), including actions the provider needs to take, any supplemental information that may be required, and where the initial case report was sent.

This Organization profile represents the Responsible Agency which is a PHA to which reporting is legally required.

This Organization profile represents the Routing Entity which is a PHA or other organization identified by the PHA (such as an HIE) to which the eICR and/or the Reportability Response will be provided immediately following the creation of the Reportability Response.

This Organization profile represents the Rules Authoring Agency which is the originator of the rules that are being executed in decision support to determine reportability.

This MessageHeader profile represents metadata to support the eCR messaging paradigm.

This Observation profile represents the patient's country of nationality.

This Observation profile represents the patient's country of usual residence.

This Bundle profile represents an eCR Document Bundle. It contains an eICR Composition.

This Encounter profile represents the encounter related to the event. It is based on the US Public Health Encounter profile.

This Procedure profile defines constraints on the US Core Procedure profile for the eICR use case.

This Observation profile represents the eICR processing status.

This Observation profile represents, if the incoming eICR was not successfully processed for a determination of reportability, the reason it was not processed.

This ServiceRequest profile represents eICR laboratory orders and other diagnostics for the eICR event.

This Observation profile represents whether or not the patient has asserted that they have verifiable vaccine credentials.

This PlanDefinition profile 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. The rules for determining reportability described by an eRSD specification involve the use of triggering codes to determine potentially reportable events, and optionally locally evaluated rules for determining suspected reportable events. The final determination of reportability is made by the Public Health Agency or Agencies appropriate for the event, and may be performed by a combination of decisions occurring at various points during the processing of an eICR, as explained in the Reportability Response profile.

Defines the asset-collection library containing the eRSD supplemental assets.

This Extension profile represents an external resource (DocumentReference) pertaining to the condition such as a text guidance, link to access forms for additional reporting needs, additional testing and/or laboratory testing needs, treatment and/or prevention resources, Public Health Agency contact information and general additional resources.

This Extension profile represents the priority given to the whole composition or one or more external resources.

This Extension profile represents that the eICR, was either manually or alternately initiated by the provider.

This Extension profile represents the eICR processing status.

This Extension profile represents the date and time of eICR receipt

This Extension profile represents a flag which, if it is present, indicates that the target reference represents a triggering event and caused the eCR to be generated.

This example set of values contains laboratory observations test names that represent that the patient may have the potentially reportable condition of Chlamydia regardless of the clinical presentation of the condition

This example set of values contains diagnoses or problems that represent that the patient may have a potentially reportable condition regardless of the clinical presentation of the condition

This example set of values contains laboratory observations test names that represent that the patient may have a potentially reportable condition regardless of the clinical presentation of the condition

This example set of values contains laboratory test names for orders that represent that the patient may have a potentially reportable condition regardless of the clinical presentation of the condition

This example set of values contains CVX, RXNORM,and SNOMED medication codes that may represent that the patient may have a potentially reportable condition. These pertain to medications administered and medications prescribed, where the medication, coded in CVX,RXNORM,SNOMED, may be indicative of a reportable condition.

This example set of values contains organism and substance names that represent that the patient may have a potentially reportable condition regardless of the clinical presentation of the condition

This example set of values contains procedure names for orders that represent that the patient may have a received a procedure or that a procedure has been requested.

This example set of values contains suspected diagnoses or problems that represent that the patient may have a potentially reportable condition. For example, these may be diagnoses recorded in an EHR problem list and diagnosis codes used for billing for the encounter.

ACME Codes for Cholesterol: Plasma only

The impact of the content of a message.

The US Public Health Message Types Value Set is a 'starter set' of codes for uniquely identifying messages in MessageHeader instances contained within a reporting bundle.

The US Public Health PlanDefinition Action Value Set is a 'starter set' of codes for uniquely identifying actions in PlanDefinition instances.

This value set contains codes representing pregnancy statuses.

This valueset is a simplified duplicate of the eRSD Endpoint Connection Type valueset created for the purposes of demonstraing, by example, the US Public Health Supplemental ValueSet profile.

The US Public Health TriggerDefinition NamedEvent Value Set is a 'starter set' of codes for identifying named events uniquely in TriggerDefinition instances contained within a PlanDefinition.

This example set of values contains laboratory observations test names that represent Chlamydia tests

This value set contains codes representing release priority for ValueSets.

This value set contains codes that identify the event an eCR message represents.

Set of endpoint connection types

This code system contains codes that identify the event a message represents.

The US Public Health Message Types CodeSystem is a 'starter set' of codes supported for identifying types of messages being exchanged.

The US Public Health PlanDefinition Actions CodeSystem is a 'starter set' of codes supported for identifying actions in PlanDefinition.

The US Public Health TriggerDefinition NamedEvents CodeSystem is a 'starter set' of codes supported for identifying named events to subscribe to in clinical workflows.

This code system contains codes that identify the use context of a ValueSet or Library.

This code system contains codes that identify the use context type of a ValueSet or Library.

This code system contains codes that identify the HL7 FHIR File type.

This code system describes the possible types of jurisdictions that require public health reporting.

This code system describes jurisdictions that require public health reporting.

Example of Country of Nationality Observation

Example of Country of Residence Observation

Example of Device Profile (ECMO)

Example of Disability Status Profile (Eve Everywoman)

Example of Endpoint resource (Salem Medical Center endpoint)

Example of Endpoint resource (YMCA endpoint)

Example of US Core Immunization profile

Example of Last Menstrual Period (Eve Everywoman)

Example of Location resource (City Football Stadium)

Example of MedicationAdministration resource (Eve Everywoman, azithromycin)

Example of MedicationAdministration resource with Therapeutic Medication Response extension (Eve Everywoman: naloxone response)

Example of ODH Employment Status profile (Eve Everywoman)

Example of ODH Past or Present Job profile (Eve Everywoman)

Example of ODH Usual Work profile (Eve Everywoman)

Example of RR Summary profile.

Example RR Document Bundle: One Condition, One PHA

Example of RR DocumentReference profile: Additional reporting needs

Example of RR DocumentReference profile: Zika follow-up

Example of RR DocumentReference profile: Zika info

Example of RR Relevant Reportable Condition Observation profile

Example of RR Reportability Information Observation profile

Example of RR Responsible Agency Organization profile (Health Authority West Responsible Agency)

Example of RR Routing Entity Organization Example profile (Health Authority West Routing Entity)

Example of RR Rules Authoring Agency profile (Health Authority West Rules Authoring Agency)

Example of RR eCIR Processing Status Observation profile

Example of RR eICR Processing Status Reason Observation profile

Example of Reportability Response Composition - One Condition/One PHA with eICR Validation Output

Example of Reportability Response Composition - One Condition/One PHA

This release includes code updates for the existing conditions and adds codes for Parkinson’s disease and 13 enteric conditions. Medication codes have also been added to this version.

An example library with logic for determining whether or not an event or situation is reportable.

Example of Travel History Observation profile (Eve Everywoman)

Example of Travel History Observation profile (Eve Everywoman - October 2016)

Example of Travel History Observation profile (Eve Everywoman - January 2018)

Example of US Core Practitioner (Henry Seven)

Example of US Public Health Lab Result profile (Eve Everywoman: Pertussis)

An example of the US Core Vital Sign Observation profile.

Example of US Public Health Encounter profile (Eve Everywoman: completed inpatient)

Example of US Public Health Encounter profile (Eve Everywoman: current inpatient)

Example of US Public Health Encounter profile (Eve Everywoman, external encounter)

Example of US Public Health Encounter profile (Eve Everywoman: external historical)

Example of US Public Health Encounter profile (Eve Everywoman: outpatient)

Example of US Public Health profile (Salem Medical Center)

Example of US Public Health Organization profile (Acme Labs)

Example of US Public Health Organization profile (Health Authority West)

Example of US Public Health Organization profile (Salem Medical Center)

Example of US Public Health Organization profile

Example of US Public Health Patient profile (Eve Everywoman)

Example of US Public Health PractitionerRole profile (Henry Seven)

Example of Characteristics of Home Environment profile (Eve Everywoman)

Example of Emergency Outbreak Information profile (Eve Everywoman)

Example of US Public Health Exposure Contact Information (Football Game)

Example of US Public Health Lab Result profile (Eve Everywoman, lymphocytes)

Example of US Public Health PlanDefinition profile

Example of US Public Health Postpartum Status profile (Eve Everywoman)

Example of US Public Health Pregnancy Outcome Observation profile (Eve Everywoman)

Example of US Public Health Pregnancy Status Observation profile (Eve Everywoman)

Example of eCR Message Bundle profile (Eve Everywoman, Zika)

Example of the US Public Health Specification Library

Example of the US Public Health Supplemental Library

An example of the US Public Health Supplemental ValueSet Library

Example of US Public Health Transportation Example (Eve Everywoman)

Example of US Public Health ValueSet Library profile

An example of the US Public Health ValueSet Library

Example of Device resource (YMCA software)

Example of eCR MessageHeader profile (Requested eICR)

Example of eICR Composition profile (Eve Everywoman, Pertussis and Zika)

Example of eICR Composition profile (Eve Everywoman, Zika)

Example of eICR Composition profile (Eve Everywoman, Zika, Manual Initiation)

Example of eICR Condition profile (Eve Everywoman: diabetes)

Example of eICR Condition profile (Eve Everywoman: pertussis)

Example of eICR Condition profile (Eve Everywoman: zika)

Example of eICR Condition profile (Eve Everywoman: common cold)

Example of eICR Document Bundle profile (Eve Everywoman, Zika)

Example of eICR Procedure (ECMO)

Example of eICR ServiceRequest profile

Example of eICR ServiceRequest profile (Eve Everywoman - zika

Example of eICR Vaccine Credential Patient Assertion Observation

An example eRSD PlanDefinition

This PlanDefinition is a simplified duplicate of the eRSD PlanDefinition Instance created for the purposes of demonstrating by example the usage of the US Public Health Named Event extension.

An example ersd PlanDefinition

An example eRSD PlanDefinition

Description of library

Description of library

Example of Subscription resource (dxtc)

Example of Subscription resource (lotc)

Example of Subscription resource (ostc)

An example eRSD Specification Bundle

An example eRSD Supplemental Bundle

References US SNOMED CT version.