Summary

  • Change Healthcare filed its breach report on 19 July 2024 identifying 500 individuals as the approximate number affected, then notified the Office for Civil Rights on 31 July 2025 that approximately 192.7 million individuals had been impacted.
  • The 60-calendar-day deadline runs from "discovery", which the same section defines as the first day the breach was known or by reasonable diligence would have been known — so the filing date on the public record is not the date the clock started.
  • Across the two sections reviewed here, nothing obliges the filer to publish a final count, correct one on any schedule, or disclose the discovery date. The number on the portal is a field the filer supplies, and it can move.

The first number appeared in a federal record on 19 July 2024. "Change Healthcare's breach report to OCR identifies 500 individuals as the 'approximate number of individuals affected'," the Department of Health and Human Services says on its own Change Healthcare incident page. The second appeared thirteen months later, in a sentence from the same page: "On July 31, 2025, Change Healthcare notified OCR that approximately 192.7 million individuals have been impacted." That is 377 days between them, by my count of the two printed dates. Divide the larger figure by the smaller and you get about 385,400 — a ratio between two numbers a filer reported, not a measure of anyone's harm, and not growth in a population.

What governs the gap is not a story about a company being slow. It is a story about what the regulation asks for, and what it does not.

The deadline is precise. 45 CFR 164.404(b) requires notice to affected individuals "without unreasonable delay and in no case later than 60 calendar days after discovery of a breach." Sixty days is a hard ceiling, and it is not the interesting part.

The interesting part is the word the clock hangs on. In the same section, 164.404(a)(2) treats a breach as discovered "as of the first day on which such breach is known to the covered entity, or, by exercising reasonable diligence would have been known to the covered entity." The sixty days do not begin when an intruder enters, or when an investigation concludes, or when a filing is prepared. They begin on a day that turns on what the organisation knew — a standard about knowledge, measured from the inside.

Now put the two pieces together. A reader of the public record can see that a report was filed on 19 July 2024. A reader cannot see from that record what day the clock started. If the breach was known on 19 July, the sixty days would have expired on 17 September 2024; that is arithmetic on a date that may have nothing to do with the discovery date, which is exactly the point. The filing tells you when the form arrived. The obligation attaches to something earlier, and the earlier fact is not on the page.

The filing route is set by size, and it is set by one number. 45 CFR 164.408(b) requires a covered entity, for breaches "involving 500 or more individuals", to notify the Secretary "contemporaneously with the notice required by § 164.404(a) and in the manner specified on the HHS Web site." Below that line, 164.408(c) substitutes a log kept through the year and a single filing within sixty days of the calendar year's end.

Five hundred is therefore a dividing line between two administrative routes — a filing line, not a harm line. And the first report in this case landed exactly on it, at 500 individuals, which is the least a filer can report while still using the contemporaneous route.

Here is where the design shows a seam. Across the two sections reviewed for this article, nothing states that the affected-individual count must be final. Nothing sets a date by which a published count must be corrected. Nothing requires the entity to disclose the discovery date that would let a third party test the sixty days. The count is content the filer supplies; the portal is where the department posts it; the revision happens when the filer sends a new one. That is not a loophole. It is simply what the text asks for, and it is less than an accountability record.

The instructive comparison is inside the same rule. For the small-breach route, the regulation demands that the entity "maintain a log or other documentation of such breaches" — a record obligation, written down. No equivalent obligation to maintain and publish a revision log attaches to the big-breach route, where the numbers are largest and the public stakes highest. The log requirement sits where the volume is low. The public number sits where the volume is enormous.

So what would turn a claim into a measurement? Three disclosures, none of them exotic. First, the discovery date, so the sixty days can be checked by someone other than the filer. Second, a stated final count carrying the date it was fixed, so a figure in a portal has a status rather than an implication. Third, a revision register, so a reader can see that 500 became something else and when. A regulator could ask for all three tomorrow without drafting a new rule; a filer could publish all three voluntarily and be better off for it.

One boundary belongs beside these claims. The two figures here come from the department's published Change Healthcare question-and-answer page, not from my own reading of the portal table, which returned no readable field values; and the analysis is confined to 45 CFR 164.404 and 164.408 as retrieved, so it says nothing about the rest of the rule, nothing about the exception those sections cross-reference, and nothing about whether any enforcement action exists.

I also tried three times to read the company's own quarterly filing on the cost of the attack and could not, so no dollar figure appears anywhere above and no comparison is drawn to one.

This piece adds a specific instrument to what BTW has already published on this company. A search of the archive on 16 November 2026 returned one earlier article — a research analysis published 12 July 2026, filed under global institutional coverage and topics spanning SME service continuity, cloud service dependency and public-sector continuity, reading the outage as a test of whether small clinics and pharmacies could still convert care into payment. That article worked the disruption and the dependency. This one works the count: the clock's trigger, the two filing routes, and a public figure that can be revised without anyone being obliged to say when or why. The company itself is tracked in the UnitedHealth Group Incorporated directory entry, which records its association with AS25690.