Summary
- The published row has seven columns and one date, the Breach Submission Date — the day the notice arrived. The clock starts at discovery, which the government's form requires and the row does not print.
- The same number sends a breach down two different tracks: 164.408 counts individuals nationally, 164.406 counts residents inside a single state or jurisdiction. A breach can sit in the public register and never trigger a media notice.
Reading the register looks embarrassingly simple. The results page (HHS OCR breach register) shows the covered entity's name, the state, the entity type, the number of individuals affected, the Breach Submission Date, the breach type and the location of the breached information. Seven columns. One date. Not one column called discovery date or incident date.
The single date means what it says: the day the notice was received. A published interpretive guide says so plainly (U.S. network, how to read the OCR register): the submission date is when the report was sent to HHS, not when the breach occurred; the counts are supplied by the covered entity and may be revised; appearing on the list is not a finding that a violation happened. Still, this is not a linguistic problem. The rule that imposes the deadline does not start at receipt.
The rule starts at discovery. 45 CFR 164.404(a)(2) (the rule text as published in the e-CFR) defines discovery as the first day the breach is known to the covered entity, or would have been known by exercising reasonable diligence. It adds that knowledge is imputed from any employee or agent, except the person who committed the breach. The same text says this definition governs 164.404(a)(1), 164.406(a) and 164.408(a). Every clock in this subpart starts at one point: the day the entity knew, not the day it mailed the paperwork.
And 164.404(b) (the section text on eCFR) writes the duty in two limbs, not one: notify affected individuals "without unreasonable delay" and in no case later than 60 calendar days after discovery, except as 164.412 permits. Sixty days is a ceiling bolted onto an existing duty, not the duty itself. A notice that arrives on day 59 does not satisfy the first limb merely because it beat the second.
Then the number appears, and with it the units come apart. 164.408(b) (the section text on eCFR) requires a covered entity, for a breach affecting "500 or more individuals", to notify the Secretary at the same time it notifies individuals under 164.404(a). 164.406(a) (the text as published in the e-CFR) concerns a breach affecting "more than 500 residents of a State or jurisdiction" and requires notice to "prominent media outlets" serving that state or jurisdiction. The two numbers sit next to each other; the units do not match: individuals nationally in the first, residents inside one jurisdiction in the second.
HHS's own example makes the gap concrete. The agency's January 2013 commentary, as republished by a law firm newsletter (Bricker Graydon's republication of the agency commentary on 164.406), posits a breach affecting 600 individuals: 200 in Virginia, 200 in Maryland and 200 in the District of Columbia. No single jurisdiction crossed 500 affected residents, so no media notice under 164.406; yet individual notice under 164.404 and Secretary notice under 164.408 remain required, because the national count reaches 500 or more. The same commentary defines a jurisdiction as an area smaller than a state, such as a county, city or town; says a press release on the covered entity's own website does not satisfy the media duty; and notes that HHS declined to define "prominent media outlet" because what counts varies by affected area.
The same law firm's compilation of the agency's commentary on 164.408 (Bricker Graydon's republication of the agency commentary on 164.408) records how HHS read the statutory word "immediately" on the 500-or-more route — as notice to the Secretary concurrent with individual notice — and notes that the internal log for the under-500 route must be kept for six years under 45 CFR 164.530(j)(2), a provision I did not read in its own text.
The second track reverses the direction of the clock. 164.408(c) (the section text on eCFR) requires a covered entity, for breaches affecting fewer than 500 individuals, to maintain a log or other documentation and to notify the Secretary no later than 60 days after the end of each calendar year for breaches discovered during the preceding year. That is not a second ceiling beside the sixty days; it is one fixed date, 1 March, whose distance changes with the day of discovery. A discovery on 31 December means a notice on the following 1 March, 60 days later. A discovery on 1 January of the same year means a notice on 1 March of the following year, 424 days later. The window runs from 60 to 424 days, and the number that decides which track applies is a number the covered entity supplies and may be an estimate at the moment of filing.
164.412 (the text as published in the e-CFR) adds lawful delay on two different conditions: a written statement from a law enforcement official specifying a time period buys that period as specified, and an oral statement, documented with the official's identity, buys no more than 30 days from the date of the statement unless a written statement arrives within that time.
Then comes the comparison that exposes the structure. HHS OCR's description of its reporting form (the form field description) requires the filer to give a Breach Start Date and Breach End Date for when the breach occurred, and separately a Discovery Start Date and Discovery End Date, along with the date individuals were notified and the expected notification date. The form also collects the approximate number of individuals affected, the type of breach, its location, the type of protected health information involved, a brief description, existing safeguards, and the notifications and actions taken. The fields exist. The agency receives them. They are, apparently, not on the row.
Nor does the problem stop at the present. HHS's annual report to Congress for calendar year 2020 (the annual report) describes the publication as searchable and sortable by covered entity name, business associate name where applicable, state, number of individuals affected, breach date, breach type and location of breached information. The agency described its own register as sortable by breach date — which the table I read on 19 November 2026 does not display. Alongside that, third-party documentation of a download dating from 2015 (Rdatasets documentation of the HHSCyberSecurityBreaches file) lists nine variables in the file, including Breach.Submission.Date, and notes that earlier downloads carried the breach occurrence date alongside the report date. That is documentation of a download file, not the file itself and not the agency publishing it, and I name it as such wherever I lean on it.
On the register itself there are two parallel surfaces: HIPAA breaches and 42 CFR Part 2 breaches (the OCR portal landing page). The agency says a breach that is both protected health information and a Part 2 record is reported twice, once as a HIPAA breach and once as a Part 2 breach. It says it investigates every breach affecting 500 or more individuals, while breaches affecting fewer than 500 may be investigated depending on resources and enforcement priorities. The page also defines its own scope as breaches reported in the last 24 months that remain under investigation, and cites section 13402(e)(4) of the HITECH Act.
The agency's own restatement does not change the structure. An HHS introductory page on the notification rule (HHS's page on breach notification, last reviewed 26 July 2013) restates the media duty in terms of residents of a state or jurisdiction and says the entity will likely do it through a press release to the appropriate outlets. The current filing instructions (HHS instructions for submitting notice to the Secretary, last reviewed 13 February 2026) explain that breaches affecting 500 or more individuals are reported without unreasonable delay and no later than 60 calendar days from discovery through the portal, while smaller breaches are reported within 60 days after the end of the calendar year; they add that an estimate is acceptable when the number is unknown at the moment of filing, and that each incident gets its own notice even when several notices go out the same day.
And yet, with all of that, an outside reader cannot compute a single interval from the published row. The first endpoint of the interval is published, the date of arrival. The second endpoint is not published, the discovery date as 164.404(a)(2) defines it. One endpoint is not an interval. That is the finding that survives everything above: the register proves that a notice exists, not that it was timely, and it does not show which notices required a media alert.
The ceiling has to be stated precisely. In the material I read on 19 November 2026 — the current HIPAA results page, the form field description, the HHS filing instructions, the 2020 report to Congress, third-party documentation of a 2015 download and a secondary interpretive guide — the only date field on the published row is the Breach Submission Date. That is a statement about those public surfaces on that day; it says nothing about what HHS OCR keeps in its own files.
I found no data dictionary, field schema or published description of a dataset behind the export in the material I read; the filing instructions point to the portal and explain deadlines rather than table columns. The CSV and Excel export buttons were not exercised in this pass, so no header line is quoted from the export itself, and the nine variables above rest on third-party documentation and are labelled as such. As for the annual notifications for breaches under 500 individuals, I could not establish whether they are published anywhere; my reading is confined to the surface that describes itself as covering 500 or more.
Nor should the delta from our own coverage pass without measurement. Searching our archive on 19 November 2026 for the literal string "HIPAA" returned five published pieces: one on Congress's 90-day review clock for major rules, one on a grant-cost case at the Indian Health Service, one on a software portal at Grants.gov between 2006 and 2009, one on a CDC consultation about health data brokers, and one on launch readiness for HealthCare.gov. All five read something else: a review clock, a grant cost, a software obstacle, a consultation, a launch.
None reads the breach notification rule, the four clocks it carries, or the public register. The delta is the register itself and the two fields its rule depends on.
The conclusion is not an accusation. What I recommend is a design fix, not an investigation: publish the discovery date the rule's clock starts from, on the same row, or publish a written basis for why the entity's discovery date cannot be published; and publish the basis of the affected-individual count, including whether it was an estimate at the moment of filing. Only then can someone outside the covered entity read the receipt and say something about its timing.
Member Briefing
Read the full trend briefing
Members read the full briefing with the source notes behind every finding.
Strategic Circle
A daily briefing in your language, built from changes we have verified.
Join for USD 20/monthCancel anytime.
Members also get the full research library, a daily briefing on the networks they follow and the private forum.






