This profile represents information that is required during a public health emergency/outbreak. This information can be highly variable, so a generic structure has been chosen to represent it.

This Encounter profile represents the encounter related to the event.

This Observation profile represents potential patient exposure and contact information.

This Location profile represents the location/facility in which care was provided.

This Organization profile represents an organization involved in public health.

This Patient profile represents a US Public Health Patient.

This profile describes the US Public Health PlanDefinition.

This PractitionerRole profile represents the roles and organizations a practitioner involved in public health is associated with.

This Procedure profile defines constraints on the US Core Procedure profile for US Public Health use cases.

This profile describes the US Public Health value sets.

This Observation profile represents transportation details such as the type of transport (plane, train, ship, etc.) along with any associated information (e.g. name of cruise ship, flight number, airport, seat number, cabin number, etc.).

This Bundle profile represents an US Public Health Specification Bundle.

An extra warning about the correct use of the value set.

This Bundle profile represents a US Public Health Supplemental Bundle.

Defines a computable value set as one that SHALL have an expression-based definition (i.e. a value set defined intensionally using expressions of the code systems involved) and MAY have an expansion included. The expression-based definition SHALL be represented in only one of three ways; using the compose element, using the expression extension, or using the rules-text extension to provide a step-by-step process for expanding the value set definition

The computable library profile sets the minimum expectations for a computable CQL library.

This profile sets the minimum expectations for an executable CQL library. Specifically, the profile requires that the library contain one of ELM XML or JSON content, the compiled representation of the CQL logic.

Defines an executable value set as one that SHALL have an expansion included, as well as a usage warning indicating the expansion is a point-in-time snapshot and must be maintained over time for production usage.

This profile describes the US Public Health Triggering value set.

Defines the library containing the US Public Health triggering value sets.

This profile describes the US Public Health Supplemental value set.

Defines the library containing the US Public Health supplemental value sets.

Defines the library containing US Public Health value sets.

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

This extension represents an US Public Health Alternative Expression

This Observation profile represents characteristics of the patient’s home environment.

This profile represents the Disability Element defined here: https://aspe.hhs.gov/basic-report/hhs-implementation-guidance-data-collection-standards-race-ethnicity-sex-primary-language-and-disability-status

This Composition profile represents an electronic initial case report (eICR).

This Condition profile represents the signs, symptoms, and diagnoses related to an eICR event.

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

This extension contains an explanation for the manual or alternate initiation of the eICR.

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

This profile represents the postpartum status of a patient.

This profile represents a result of the pregnancy such as live birth, still birth, miscarriage, etc.

This profile represents current and/or prior pregnancy statuses and their date ranges, enabling investigators to determine if a patient was pregnant, possibly pregnant, not pregnant or whether the pregnancy status was unknown during a particular date range.

This Observation profile represents a patient’s travel history.

Example of Location resource (City Football Stadium)

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

This Extension profile represents the determination of reportability.

This Extension profile represents the reason for the determination of reportability.

This Extension profile represents a rule that led to the determination of reportability.

This Extension profile represents the eICR processing status.

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 PlanDefinition in the Reportability Response transaction represents reportability information for a condition-jurisdiction pair, based on the PHA in which is located the patient’s home, the provider facility or both locations.

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 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.

This Bundle profile represents an eRSD Specification Bundle. It contains the eRSD Specification.

This Bundle profile represents an eRSD Supplemental Bundle. It contains the eRSD Supplements.

CQL FHIR Helpers Library

RCTC Library

Instance of eRSD PlanDefinition profile

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

This Bundle profile represents an eICR Message Bundle.

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

This Task profile represents the state of completion of the eCR activity.

Indicates the types of named events to subscribe to from the EHR.

The date a status or observation was determined (date of determination).

The date a status or observation was recorded (recorded date).

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

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 Extension profile represents relationships with other structures that already exist

This Extension profile represents the date and time of eICR receipt

This Extension profile represents the type/category of one or more external resources.

This Extension profile represents a code indicating whether the responsible PHA is relevant because of the patient’s home address, the provider facility address, or both.

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

This extension represents an RR Responsible Agency Organization

This extension represents an RR Routing Entity Organization

This extension represents an RR Rules Authoring Agency Organization

This Extension profile represents represents a therapeutic response (as opposed to an undesired reaction) to the administration of a medication.

This Extension profile represents where the patient traveled to or visited as an address e.g.: country, state, city, street address (if applicable).

This Extension profile represents an affiliated tribe name and whether or not the patient is an enrolled member

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 Emergency Outbreak Information profile (Eve Everywoman)

Example of US Public Health Procedure (ECMO)

Example of US Public Health Transportation Example (Eve Everywoman)

Example of US Public Health PlanDefinition profile

Example of US Public Health ValueSet Library profile

An example of the US Public Health Specification Bundle

An example of the US Public Health Supplemental Bundle profile.

Description of library

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.

Example of Characteristics of Home Environment profile (Eve Everywoman)

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

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

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

Example of eICR ServiceRequest profile

Example of eICR ServiceRequest profile (Eve Everywoman - zika

Example of US Core Immunization profile

Example of MedicationAdministration resource (Eve Everywoman, azithromycin)

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

Example of Last Menstrual Period (Eve Everywoman)

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

Example of ODH Usual Work profile (Eve Everywoman)

Example of Postpartum Status profile (Eve Everywoman)

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 Results profile (Eve Everywoman, lymphocytes)

Example of US Core Results profile (Eve Everywoman: Pertussis)

Example of Pregnancy Outcome Observation profile (Eve Everywoman)

Example of Pregnancy Status Observation profile (Eve Everywoman)

Example of US Core Practitioner (Henry Seven)

Example of Disability Status Profile (Eve Everywoman)

Example of US Core Device Profile (ECMO)

Example of Reportability Response Communication collection bundle

Example of RR eCIR Processing Status Observation profile

Example of RR eICR Processing Status Reason Observation profile

Example of RR Communication profile (One condition, one PHA

Example of RR Communication profile (One condition, one PHA, with validation output)

Example of RR Relevant Reportable Condition PlanDefinition 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)

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.

This Bundle profile represents an eRSD Supplemental Bundle. It contains the eRSD Supplements.

This Bundle profile represents an eRSD Specification Bundle. It contains the eRSD Specification.

Example of Subscription resource (dxtc)

Example of Subscription resource (lotc)

Example of Subscription resource (ostc)

Example of Device resource (YMCA software)

Example of eCR MessageHeader profile (Requested eICR)

Example of Endpoint resource (Salem Medical Center endpoint)

Example of Endpoint resource (YMCA endpoint)

Example of eCR Task profile

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.

This code system contains codes that describe the business status of a task.

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

This code system describes jurisdictions that require public health reporting.

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

This code system contains codes that describe the executable task types.

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

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 type of a valueset.

This code system contains codes that identify the use context of a valueset.

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

Set of endpoint connection types specified as being supported by APHL

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 CVX vaccine codes that may represent that the patient may have a potentially reportable condition. These pertain to vaccines administered and prescribed, where the vaccine, coded in CVX, may be indicative of a reportable 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

Defines the status of pregnancy. Extended pregnancy status VSAC link

This value set contains codes representing pregnancy statuses.

This value set contains codes that describe the eCR task businessStatus.

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 procedure names for orders that represent that the patient may have a received a procedure or that a procedure has been requested.

Model definition for the FHIR R4 (v4.0.1) Model

References US SNOMED CT version.