A 90-day declaration that ran for three years

The week

On January 30, 2020, the World Health Organization declared the novel coronavirus outbreak a Public Health Emergency of International Concern. The next day, the US Secretary of Health and Human Services declared a public health emergency under Section 319 of the Public Health Service Act, effective from January 27. The administration also announced restrictions on entry for many foreign nationals who had recently been in China. At the time there were only a handful of confirmed US cases, and the declaration was widely read as a precaution that would let federal agencies move resources and use certain flexibilities. A Section 319 declaration lasts 90 days and can be renewed.

Emergency declarations are designed to be temporary. This one was renewed for more than three years. For agency program directors and CIOs, the January 2020 declaration matters less for what it said than for what came to depend on it. Its influence divides into three parts: it was a trigger that combined with other authorities, a condition that Congress wrote into new law, and a clock that ran in 90-day increments. Each created a different kind of technology and compliance debt, and each had to be paid down separately when the emergency ended.

A trigger for other authorities

A Section 319 declaration on its own gives the Secretary limited tools. Its reach comes from what it combines with. Section 1135 waivers of certain Medicare, Medicaid and CHIP requirements, for example, need both a public health emergency and a separate presidential emergency declaration, which came in March 2020. Once both were in place, the federal government could relax a long list of requirements on providers and states.

Other instruments ran on separate tracks. A declaration under the PREP Act, issued in early 2020 and amended many times, provided liability protections for countermeasures such as tests and, later, vaccines. Emergency use authorizations by the Food and Drug Administration rested on yet another determination. Each had its own duration and amendment history. For an agency running a testing or vaccination program, the practical question was which instrument covered which activity, and when each would lapse.

State Medicaid agencies and health departments therefore operated under rules that changed by reference to other documents. Systems had to be configured for waived requirements, and staff had to track which flexibility rested on which authority. Few agencies kept a register that mapped each operational change to its legal basis. A register needs only a handful of fields: the change, the program, the authority relied on, the system configuration affected, the owner and the expected end. Its absence made the eventual unwinding much harder.

A condition written into new law

In March 2020, the Families First Coronavirus Response Act gave states additional federal Medicaid funding. The condition was that they keep most enrollees covered continuously until the end of the month in which the public health emergency ended. That tied eligibility processing in every state to the declaration. Redeterminations that would normally remove people who no longer qualified were largely paused, and enrollment rose substantially.

This is where the declaration turned into a systems issue. Eligibility platforms had to suppress normal terminations while continuing to process changes that kept people covered. They also had to record who would otherwise have lost coverage, and keep the contact information and case details needed to renew them later. Mailing addresses aged during the pause, because people moved while no renewal notices were being sent.

Agencies that kept clean records of deferred actions, and that kept updating addresses through other programs and data sources, were far better placed when the pause ended. Those that simply switched rules off faced a backlog of unknown size, with stale contact data and caseworkers who had not processed a normal renewal in years.

The same pattern affected workforce planning. Staff who had handled renewals were reassigned to other work during the pause, and some left. Training materials and system knowledge faded. An agency that wanted to restart renewals at scale needed caseworkers, call center capacity and notices tested against current system logic, all at the same moment. Planning for that restart had to begin long before the end date was known, which meant budgeting for capacity against a date that kept moving.

Vendors were caught up as well. Eligibility system contractors had built suppression logic under change orders, and reversing it required further change orders and full testing cycles. Agencies that had asked vendors to document every emergency modification could scope the reversal quickly. Others had to reconstruct what had been changed.

A clock that ran in 90-day increments

Because a Section 319 declaration lasts 90 days, the emergency was renewed repeatedly. The federal government said it would give states advance notice before ending it, but agencies still could not plan beyond a few months with confidence. Temporary arrangements, from staffing models to vendor contracts to system configurations, stayed temporary in name while becoming permanent in practice.

Short horizons push agencies toward workarounds. Contract modifications, manual overrides and spreadsheet trackers accumulate when nobody can justify a proper change for a rule that might end next quarter. Each workaround is a small liability that must be found and removed later, often by staff who were not there when it was created. Vendor contracts extended in 90-day steps also cost more and left agencies little room to negotiate.

A better pattern is to design emergency changes as reversible from the start. Configuration flags that can be switched off cleanly, test scripts for the return to normal rules, and a scheduled review of every emergency change each quarter keep the eventual exit manageable. Counsel should confirm which authority applies to which change, because the answer is rarely obvious and often differs by program. The same discipline applies to any declared emergency, whether a pandemic, a natural disaster or a financial shock.

With hindsight

The federal public health emergency was renewed many times and ended on May 11, 2023. Congress had already decoupled the Medicaid continuous enrollment condition through the Consolidated Appropriations Act, 2023, which ended continuous coverage on March 31, 2023. States then began an eligibility renewal effort of a scale the program had never seen, and many struggled with backlogs, procedural terminations and system defects. In August 2023, CMS found that about 30 states were running automatic renewals at the household level rather than for each individual. It required them to pause procedural terminations, fix their systems and reinstate almost 500,000 people.

That finding is the clearest evidence for the argument here. The defect sat in renewal logic that had barely been exercised for three years, and it surfaced only when the rules were switched back on at scale. The declaration that looked like a precaution in January 2020 shaped three years of program operations and a difficult year of unwinding.