Why hospital COVID reporting turned out to be infrastructure
In July 2020, HHS told hospitals to stop sending COVID-19 capacity data to the CDC and report through a new HHS pathway. The switch showed that reporting depends on definitions, pipelines and governance, and that hospitals relying on manual counts paid for every change.
Looking Back revisits one week at a time, from January 2020 to today, and asks what it meant for the banks, health systems and public agencies we serve. The series was written in 2026, with the benefit of hindsight, and each article says which week it looks back on.
The week
On July 10, 2020, the Department of Health and Human Services updated its guidance for hospitals on reporting COVID-19 data. Hospitals were directed to stop reporting through the CDC’s National Healthcare Safety Network. From July 15, they were to submit daily data on capacity, patients and supplies through a system run for HHS by the contractor TeleTracking, or through their states where the state reported on their behalf. HHS said the change would produce more complete and timely data for allocating supplies and treatments such as remdesivir. Public health experts and others criticized the move, raising concerns about transparency, the sidelining of the CDC and the burden on hospitals of changing systems mid-surge. For a period after the switch, some CDC public data pages stopped updating.
Hospital capacity data had rarely been news before 2020. That year it guided the allocation of treatments, supplies and staff, and shaped public decisions about reopening. The July switch made visible a pipeline that had been built quickly and largely by hand. For health system data leaders and public health agencies, the pipeline has three layers: definitions of what is counted, the mechanics of collecting and submitting data, and the governance of who receives and publishes it. The switch touched all three at once, which is why hospitals with weak foundations felt it so sharply.
Definitions: what counts as a COVID bed
Reporting depends on shared definitions. What counts as a confirmed or suspected COVID patient, a staffed bed, an ICU bed, an available ventilator? Small differences in definition produce large differences in totals. During 2020, definitions changed several times as guidance evolved, and hospitals read some fields differently. Comparisons across facilities and over time were therefore weaker than published charts suggested.
Each reported field should map to a written definition and to a specific source in the hospital’s systems. A staffed ICU bed, for example, might be derived from the bed management system’s unit list, minus beds blocked for staffing, as of a fixed time each day. When a definition changes, the mapping must change with it, and someone must check whether historical comparisons still hold. A data dictionary for external reporting, owned by a named analyst, is a modest investment that pays off every time a requirement changes.
Timing belongs in the definition too. A census taken at midnight differs from one taken at noon. Reporting the same snapshot time every day, and recording it, made trends meaningful and stopped day-to-day noise from being read as surges.
Clinical definitions raised harder questions. Whether a patient counted as a suspected case depended on documentation that clinicians entered for care, not for reporting. Results that arrived after the snapshot changed yesterday’s numbers. Hospitals had to decide whether to revise past submissions or report only forward, and to apply the choice consistently. Writing those rules down, and telling recipients which rule the hospital followed, prevented later disputes about apparent discrepancies.
Collection: the manual effort behind daily numbers
Many hospitals compiled daily reports by hand. Staff counted patients and beds from census reports and spreadsheets, then keyed totals into web forms. Some health systems automated extraction from EHR and bed management systems; many could not do so quickly. Changing the destination meant changing forms, credentials, file formats and validation rules, sometimes with days of notice, while staff were stretched by patient care.
The durable fix is automated extraction from source systems, with validation before submission. Validation catches the obvious errors, such as more occupied beds than staffed beds or a sudden drop to zero. A well-built pipeline separates three steps: extracting from source systems, transforming to the required definitions, and submitting to the destination. When the destination changes, only the last step needs rework. That design pays off beyond any single requirement, because quality measures, registry submissions and payer reporting can share the same plumbing.
Health systems with several hospitals had a further choice. Central submission by a system data team ensured consistency but depended on every hospital’s source systems being mapped. Local submission was faster to start but produced inconsistent numbers across the system. Centralizing cost more up front and less every time a requirement changed afterwards.
Resilience mattered as well. A daily submission that depends on one analyst, one spreadsheet or one login fails when that person is ill. Documented runbooks, a trained backup and monitoring that alerts when a submission is late kept reporting steady through staff absences. Credentials for external portals should belong to a role mailbox or service account where permitted, not to one employee.
Governance: who receives and publishes the data
The controversy was largely about governance: which agency held the data, who could see it and how it would be published. Public health agencies, researchers and the public had relied on CDC data, and the change interrupted that access. States also ran their own reporting and sometimes received data by different routes than federal agencies. That produced conflicting numbers for the same hospitals.
For hospitals, governance questions are practical. Which recipient is authoritative for each requirement? Does one submission satisfy several? If a state submits on a hospital’s behalf, who is responsible for accuracy? Written answers prevent duplicate reporting and contradictory figures, and they protect the hospital if its numbers are later questioned. A single internal owner for all external reporting, with authority to approve definition changes, ties the three layers together. Hospitals that had invested in these foundations absorbed the July switch with modest effort. Those relying on manual counts found every change expensive, and their staff paid in overtime at the worst possible moment.
With hindsight
The HHS reporting system remained the main route for hospital COVID data for much of the pandemic. In December 2020, HHS began publishing facility-level capacity data that researchers and journalists used widely. In 2020, CMS also made COVID-19 reporting a condition of participation in Medicare and Medicaid for hospitals, turning reporting from a request into a requirement.
After the emergency, reporting moved back toward the CDC. From November 2024, CMS made reporting of respiratory illness data to the National Healthcare Safety Network an ongoing condition of participation for hospitals. The CDC’s Data Modernization Initiative funded improvements to public health data systems, though progress was uneven. That return to the CDC was itself another destination change, the case the three-layer design above is meant to absorb.