Data-Driven Readiness: Protecting Electricity-Dependent Populations

Why This Matters

Critical Reality: Thousands of people rely on electricity for life-sustaining medical equipment.

When power fails:

The Challenge: How do emergency responders find these people before it’s too late?

The Solution: Data-driven readiness systems that identify at-risk populations before disasters strike.

The US Model: HHS emPOWER Program

Official Resource: empowerprogram.hhs.gov

What is emPOWER?

Definition: A federal program that uses Medicare claims data to identify people who depend on electricity-powered medical equipment.

Data Source: Centers for Medicare & Medicaid Services (CMS)

Coverage: Medicare beneficiaries only (approximately 65 million people)

Equipment Tracked

emPOWER identifies people using:

Two Views of emPOWER: Planning vs. Response

View 1: The Planning View (De-identified Data)

What It Is: Aggregated, anonymized data showing the density of electricity-dependent residents by geographic area.

Who Can Access:

Key Features:

How It’s Used - “Cold-Start” Resource Staging:

Before an emergency happens, planners use de-identified data to:

  1. Optimize Shelter Placement
    • Choose shelter locations with high-capacity backup generators
    • Position shelters near concentrations of at-risk residents
    • Calculate oxygen supply needs per shelter
  2. Stage Critical Resources
    • Pre-position mobile oxygen hubs in high-density zip codes
    • Stockpile backup batteries for medical equipment
    • Stage portable generators near vulnerable populations
    • Position charging stations for electric wheelchairs
  3. Grid Prioritization
    • Share density maps with utility companies
    • Prioritize power restoration for critical transformers
    • Identify which substations serve the most at-risk residents
    • Plan for targeted “islands of power” during extended outages
  4. Resource Allocation
    • Calculate how many backup generators to acquire
    • Determine oxygen supply chain requirements
    • Plan transportation logistics for high-need areas

Example Use Case:

A county emergency manager sees that zip code 12345 has 500 residents with oxygen concentrators.

Actions Taken:

View 2: The Response View (Identified Data)

What It Is: Real, identifiable data with names, addresses, and specific equipment needs.

Who Can Access:

Access Requirements:

Legal Framework:

Access is governed by:

How It’s Used - Emergency Response:

During an active emergency, responders use identified data to:

  1. Conduct Targeted Wellness Checks
    • Contact individuals within 2 hours of power loss
    • Prioritize visits based on equipment criticality
    • Verify functional status of backup power
    • Offer immediate evacuation if needed
  2. Execute Priority Evacuations
    • Identify residents who must evacuate first
    • Arrange accessible transportation
    • Ensure medical equipment can travel with patient
    • Confirm arrival at equipped shelter
  3. Track and Follow-Up
    • Maintain contact throughout event
    • Check in every 4-6 hours during prolonged outages
    • Document status and needs
    • Coordinate with medical providers

Example Use Case:

Hurricane warning issued 48 hours before landfall.

Actions Taken:

Ethical Protocols: Balancing Speed and Privacy

The Crisis Dilemma

Tension: People need help fast, but their medical information is private.

Balance: Use the minimum necessary information to save lives.

Best Practices for Handling Identified Data

1. Access Control

2. Time Limits

3. Communication with Residents

4. Data Security

5. Staff Training

Important Limitations

What emPOWER Does NOT Include

Population Gaps:

Equipment Gaps:

The Zero-Baseline Warning

Critical Understanding: emPOWER data shows the minimum number of at-risk people, not the total.

Why This Matters:

If emPOWER shows 500 people in a county:

Real number could be:

Action: Always plan for 2-3x the emPOWER count to account for gaps. This multiplier is a recommended practice based on field experience—track your actual vs. registered populations to refine it for your community.

Global Alternatives: International Functional-Needs Systems

Different countries use different models to identify and protect electricity-dependent populations.

Overview Table

Note: For screen reader users, a list-based version follows the table.

Country System Name Model Type Who Maintains Responder Access
USA emPOWER Healthcare Claims Federal Government (HHS) Emergency managers via data-use agreement
UK Priority Services Register (PSR) Utility-Managed Energy Companies Responders coordinate with utility companies
Australia Life Support Equipment Registers Retailer-Managed Energy Retailers Emergency services request from retailers
Japan Hinan Kodo Yoshien-sha Municipal Census Local Governments Community support workers and neighbors
France Registre Nominatif Voluntary Municipal Town Halls (Mairies) Local emergency services direct access

List Format:

United Kingdom: Priority Services Register (PSR)

Model: Utility-Managed

Legal Basis: Energy Industry regulations require energy companies to maintain registries of vulnerable customers.

Who’s Included:

How It Works:

  1. Registration:
    • Customers self-register with their energy supplier
    • Can register online, by phone, or by mail
    • Free service, no eligibility verification
  2. Data Management:
    • Energy companies maintain individual registries
    • Data is NOT centralized nationally
    • Each supplier manages their own customers
  3. Emergency Access:
    • During power outages, utilities contact PSR registrants first
    • Utilities may share data with emergency services during major events
    • Responders coordinate through utility company liaisons

Responder Protocol:

During an emergency:

Limitations:

Australia: Life Support Equipment Registers

Model: Energy Retailer-Managed

Legal Basis: National Energy Retail Rules require retailers to maintain registers of customers using life support equipment.

Who’s Included:

How It Works:

  1. Registration:
    • Customer notifies energy retailer
    • Medical practitioner provides confirmation
    • Retailer registers customer as “life support”
  2. Protections:
    • Retailer must give 4 days’ notice for planned outages
    • Cannot disconnect for non-payment without extra protections
    • Priority restoration during unplanned outages
  3. Data Sharing:
    • Retailers share registers with distribution network operators
    • Data can be shared with emergency services during disasters
    • Governed by state privacy laws

Responder Protocol:

During an emergency:

Limitations:

Japan: Hinan Kodo Yoshien-sha (Evacuation Support Registry)

Model: Community-Led Municipal Census

Translation: “People requiring assistance with evacuation actions”

Legal Basis: Disaster Countermeasures Basic Act (revised 2013)

Who’s Included:

How It Works:

  1. Registration:
    • Municipalities conduct census of vulnerable residents
    • Community welfare officers visit households
    • Voluntary participation with strong social encouragement
    • Creates individual evacuation plans
  2. Support Network:
    • Each registrant assigned community supporters (family, neighbors)
    • Supporters responsible for checking on person during disaster
    • Pre-arranged evacuation assistance plans
    • Local evacuation centers identified
  3. Data Management:
    • Maintained at municipal level (cities/towns)
    • Shared with local community associations
    • Pre-authorized access for support persons
    • Updated annually

Responder Protocol:

During an emergency:

Strengths:

Limitations:

France: Registre Nominatif (Nominative Registry)

Model: Voluntary Municipal Registration

Legal Basis: Plan Communal de Sauvegarde (Municipal Safeguard Plan) - mandated by national law

Who’s Included:

How It Works:

  1. Registration:
    • Residents register with local town hall (mairie)
    • Simple form, no medical documentation required
    • Can register in person, by phone, or online
    • Registry managed by municipal emergency services
  2. Data Collected:
    • Name, address, contact information
    • Type of vulnerability (mobility, medical, sensory)
    • Emergency contact information
    • Preferred communication method
  3. Access:
    • Municipal emergency services have direct access
    • Firefighters and civil protection teams authorized
    • Data not shared outside municipality without consent

Responder Protocol:

During an emergency:

Strengths:

Limitations:

Implementation Best Practices: Building Your Own Registry

The Resilience Checklist

Use this checklist to evaluate or build a functional-needs registry:

✅ Registration Accessibility

✅ Data Management

✅ Privacy Protections

✅ Emergency Protocols

✅ Data Quality and Refresh

Critical Success Factors

1. Data Refresh Rate

The Challenge: People’s needs change constantly.

Estimated Decay Rates (Based on Municipal Experience):

Note: These are approximations based on emergency management experience, not rigorous research. Your community’s rates may vary.

Why Data Decays:

Best Practice:

Gold Standard (emPOWER):

2. Balancing Privacy and Speed

The Tension: Privacy laws protect people, but can slow emergency response.

Framework:

Situation Access Level Legal Basis
Planning (pre-event) De-identified data only Public health authority
Imminent threat (24-48 hrs) Identified data with safeguards Emergency declaration
Active emergency (ongoing) Full access for authorized responders Immediate danger to life
Post-event (recovery) Limited access, case-by-case Specific authorization

Key Principle: Use the minimum necessary information to accomplish the task.

Examples:

3. The Zero-Baseline Principle

Core Truth: No registry is ever 100% complete.

Why Registries Are Incomplete:

  1. Voluntary participation barriers:
    • Privacy fears
    • Distrust of government
    • Stigma around disability
    • Language barriers
    • Digital access issues
  2. Rapid population changes:
    • People move
    • Needs change
    • New equipment prescribed
    • Equipment no longer needed
  3. System exclusions:
    • Undocumented residents
    • Homeless populations
    • People without formal healthcare
    • Informal medical equipment
    • Temporary medical needs

Operational Impact:

If your registry shows 500 people:

Note: The 2-3x multiplier is a recommended practice based on field experience. Your community may need a different multiplier based on local opt-in rates and demographic factors. Track actual vs. registered populations during each event to refine your multiplier.

Mitigation Strategies:

  1. Multi-Channel Outreach:
    • Don’t rely solely on registry
    • Door-to-door checks in high-risk areas
    • Partner with community organizations
    • Alert systems for entire population
  2. Flexible Resource Planning:
    • Overstock critical supplies by 50%
    • Mobile response teams for unexpected needs
    • Rapid procurement contracts for surge
  3. Continuous Improvement:
    • After-action reviews: Who did we miss?
    • Community feedback: Why didn’t you register?
    • Data analysis: Where are the gaps?
    • Partnership expansion: Who else knows vulnerable residents?

Integration with Other Systems

Utility Companies:

Healthcare Providers:

Social Services:

911/311 Systems:

Shelters:

Measuring Success

Key Performance Indicators (KPIs)

Registration Metrics:

Outreach Metrics:

Response Metrics:

Outcome Metrics:

Case Study: Putting It All Together

Scenario: Hurricane Approaching Coastal County

T-48 Hours (Planning View):

T-36 Hours (Response View):

T-24 Hours (Execution):

T-12 Hours (Transportation):

T-0 Hours (Landfall):

Post-Event:

Resources for Implementation

US Resources

Research and Guidance

International

Summary: Data-Driven Readiness Saves Lives

The Core Message:

Data-driven readiness is about knowing who needs help before disaster strikes.

Key Principles:

  1. Multiple Data Sources: Don’t rely on one system
  2. Plan for Incompleteness: Registries are minimum baselines, not complete lists
  3. Balance Privacy and Speed: Protect data, but don’t let red tape kill people
  4. Continuous Improvement: Learn from every event, expand your reach
  5. Community Trust: People must believe you’ll protect their information

The Goal:

Zero preventable deaths among electricity-dependent populations during emergencies.

The Reality:

We’re not there yet. But data-driven readiness gets us closer with every disaster.

Related: Digital data only captures people who are visible online. Learn how to identify and reach populations that fall outside digital systems in Data Fidelity and Ethical Mapping.

Questions? Feedback? Corrections?

This guide aspires to be comprehensive and accurate, but we recognize we’re continuously learning from real-world implementations.

If you have experience with functional-needs registries, especially from international contexts, please share your knowledge through issues or pull requests.

Your expertise helps make this guide more trustworthy and useful for emergency managers worldwide.