Skip Ribbon Commands
Skip to main content
Skip over global navigation links
U.S. Department of Health and Human Services

Performance Measure HPP-PHEP J.1: Information Sharing


Percent of local partners that requested Essential Elements of Information to the public health/medical lead within the recipient’s timeframe


Recipients are required to report twice for this measure. If you have zero or one data point to report, conduct exercises (including drills) or planned events to obtain two data points for this PM. Only information sharing related to a medical countermeasures (MCM) incident or scenario (including an exercise or drill) will count towards the medical countermeasures Operational Readiness Review (MCM ORR), so make sure this is accomplished at least every other year. In alternate years, consider exercising information sharing related to non-MCM incidents and scenarios to test capabilities for sharing different types of EEI with different local partners.


How is the measure calculated?

Numerator: Number of local partners that reported requested EEI to the public health/medical lead within the requested timeframe

Denominator: Number of local partners that received a request for EEI


Why is this measure important?

The intent of this measure is to assess the extent to which local response entities communicate requested information to the public health/medical lead in order to facilitate situational awareness and the effective management of resources in a timely manner.


What other requirements are there for reporting measure data?

This measure requires submission of self-reported data. Data should be collected and reported by incident (or planned event or exercise). Recipients are required to report at least two data points for this measure. One data point must reflect the recipient’s best performance (highest percentage); the other must reflect performance which, based on a determination from the recipient, calls for focused quality improvement and, if applicable, technical assistance. Recipients are encouraged to submit data on additional incidents, planned events, and exercises. There are no specific reporting requirements or parameters for these additional data points.


How does this measure align with the MCM ORR tool?

Information sharing is essential during responses to all emergencies, and it is particularly important to the facilitation of situational awareness and appropriate allocation of resources during an MCM incident. The MCM ORR tool requires exercising the sharing of EEI every two years during an MCM-related incident. There is an opportunity to work with partners to align EEI sharing processes for the HPP-PHEP J.1 and the MCM ORR by conducting an MCM-oriented exercise or drill every two years and, on alternate years, conducting an exercise or drill to share EEI for other hazards. Data from HPP-PHEP J.1 will apply directly to the MCM ORR.


What data must be reported?

  1. Number of local partners that reported requested EEI to the public health/medical lead within the requested timeframe (numerator) [Max five digits]
    • Performance Measure: Percent of local partners that reported EEI to the public health/medical lead within the requested timeframe (System calculated) [Percentage]

  2. Number of local partners that received a request for EEI (denominator) [Max five digits]

  3. The request for EEI occurred during a/an: [Select one]
    • Incident
    • Full scale exercise
    • Functional exercise
    • Drill
    • Planned event

  4. Please identify the type of incident/exercise/planned event upon which the request for EEI was based.* [Select only one, even if multiple hazards existed in one incident]
    • Extreme weather (e.g., heat wave, ice storm)
    • Flooding
    • Earthquake
    • Hurricane/tropical storm
    • Hazardous material
    • Fire
    • Tornado
    • Biological hazard or disease, please specify [Max 100 characters]
    • Radiation
    • Other, please specify [Max 100 characters]

  5. Was this incident/exercise/planned event MCM-related?
    • Yes
    • No

  6. Please provide the name and date of the incident/planned event/exercise.
    • Name [Max 100 characters]
    • Date [MM/DD/YYYY]

  7. This incident/planned event/exercise utilized or demonstrated one or more functions within the: [Select one]
    • HPP Capability
    • PHEP Capability
    • Both HPP and PHEP Capabilities

  8. Please state how many of each type(s) of local partners responded to the request. [Max five digits for each type]
    • Hospitals
    • Long-term care facilities
    • Community health center
    • Health care organizations (HCOs)
    • Local public health entities

  9. Did “other” types of local partners (not listed above) respond to the request? [Max five “other” types]
    • No
    • Yes
      • Please describe “other” type #1. [Max 100 characters]          
      • How many local partners of “other” type #1 responded to the request? [Max three digits]
      • Please describe “other” type #2. [Max 100 characters]          
      • How many local partners of “other” type #2 responded to the request? [Max three digits]
      • Please describe “other” type #3. [Max 100 characters]
      • How many local partners of “other” type #3 responded to the request? [Max three digits]         
      • Please describe “other” type #4. [Max 100 characters]
      • How many local partners of “other” type #4 responded to the request? [Max three digits]
      • Please describe “other” type #5. [Max 100 characters]
      • How many local partners of “other” type #5 responded to the request? [Max three digits]

  10. Please identify the requesting entity (e.g., public health/medical lead at the state, sub-state regional, or local level). [Select one]
    • State health/medical lead (or designee)
    • Sub-state regional health/medical lead (or designee)
    • Local health/medical lead (or designee)
    • Other, please specify [Max 100 characters]

  11. Please identify the types of EEI requested. [Select all that apply]
    • Facility operating status
    • Facility structural integrity
    • The status of evacuations/shelter in-place operations
    • Status of critical medical services (e.g., trauma, critical care)
    • Critical service/infrastructure status (e.g., electric, water, sanitation, heating, ventilation, and air conditioning)
    • Bed or patient status
    • Equipment/supplies/medications/vaccine status or needs
    • Staffing status
    • EMS status
    • Epidemiological, surveillance, or lab data (e.g., test results, case counts, deaths)
    • School-related data (e.g., closure, absenteeism)
    • Point of Dispensing (POD)/mass vaccine sites data (e.g., throughout, open/set-up status)
    • Other, please specify [Max 100 characters]

  12. Please identify the type of IT or other communication system used to request EEI from local partners. [Select all that apply]
    • Telecommunication (e.g., cell phone, satellite phone, landline)
    • E-mail
    • Online/web interface (e.g., electronic bed or patient tracking, survey tools, Web-Based Emergency Operations Center [WebEOC] or similar)
    • Health Alert Network (HAN)
    • Other, please specify [Max 100 characters]

  13. Continuous Quality Improvement:
    • Were relevant corrective action/improvement plan items from prior responses (including exercises, drills, etc.) related to information sharing incorporated into planning and/or response procedures before this incident/drill took place?
      • Yes
      • No
      • Some
    • Have corrective action/improvement plan items related to information sharing been identified as a result of this incident/drill?
      • Yes
      • No
    • Have they been implemented?
      • Yes
      • No
      • Some

  14. Please indicate any barriers to submitting requested EEI within the requested timeframe. [Select all that apply]
    • Communication
    • Equipment
    • Funding
    • Participation
    • Policies/procedures
    • Resource limitations
    • Staffing
    • Time constraints
    • Training
    • Other, please specify
    • None

  15. [Optional] Please provide any additional clarifying, contextual, or other information [Max ,000 characters]


How is this measure operationalized?

This measure intends to capture information on the communication of incident-specific public health/medical EEI. Determination of which EEI are to be requested or collected during a response, as well as which local entities should report the information and the timeframe in which the information should be reported, should be based on established plans, protocols, and procedures, but are ultimately at the discretion of the incident commander or designee.

If large volumes of EEI are collected in an incident, it is the responsibility of the recipient to determine which of this information was “essential”—and therefore able to count towards the numerator and denominator—for this PM.


Key Measurement Terms

  • EEI: EEI are discrete types of reportable public health or health care-related incident-specific knowledge that are communicated or received concerning a particular fact or circumstance; EEI are preferably reported in a standardized manner or format, which assists in generating situational awareness for decision-making purposes. EEI are often coordinated and agreed upon pre-incident and are communicated to local partners as part of information collection request templates and emergency response playbooks.

  • Local partners: Local partners are entities at the local level that receive requests for EEI. Local partners may differ based on the type of incident/exercise/planned event (e.g., HCOs, local health departments, HCCs).

  • Requested timeframe: Requested timeframe is a recipient-defined period of time for receiving requested EEI (e.g., operational period, set time to meet special request).

  • Responsible entity or entities: A responsible entity (or entities) refers to an organization at the recipient or sub-recipient level that is accountable for completing the specific activity or element associated with one or more PHEP PMs.


<< Previous: Section 4 --------- Top of Page --------- Next: Performance Measure HPP-PHEP J.2 >>

  • This page last reviewed: November 05, 2020