Summary

  • 16 CFR 318.4(a) gives a covered party exactly one interval: notice without unreasonable delay and no case later than 60 calendar days after discovery, with discovery defined by the party's own knowledge.
  • The Federal Trade Commission's public notices list prints the discovery date and no arrival date; the Department of Health and Human Services breach report prints a submission date and no breach date, so neither record carries both ends of the interval.
  • The number 500 decides whether a case gets a per-case record at all, and the Commission's own filing form still instructs filers with a ten-business-day deadline the 2024 amendments replaced.

The verb that starts the clock

Part 318 does not open with a breach. It opens with knowledge. Under 16 CFR 318.3(c), a breach is discovered on the first day it is known or reasonably should have been known to the vendor of personal health records, the PHR related entity or the third party service provider — and that knowledge is drawn from any employee, officer or agent other than the person who committed the breach.

What counts as a breach is drawn just as widely. Section 318.2 treats the acquisition of unsecured PHR identifiable health information without the individual's authorization as a breach of security, presumes that unauthorized access is unauthorized acquisition unless there is reliable evidence to the contrary, and says in terms that acquisition resulting from a data breach or an unauthorized disclosure is inside the definition.

Then comes the sentence that decides what the whole instrument is worth. 16 CFR 318.4(c) puts the burden on the regulated entity to demonstrate that every required notification was made — including evidence justifying any delay. The party that fixes the start of the clock also holds the file that would test it. Nobody outside that party has ever been handed the second half of that sentence.

One interval, and where it ends

The Rule measures one thing. Section 318.4(a) requires the individual notice, the media notice where the threshold is met, and the service-provider notice to go out without unreasonable delay and in no case later than 60 calendar days after discovery. Calendar days, not business days: nothing in the text converts the unit, and no one should perform that conversion on the Rule's behalf.

Section 318.4(b) ties the Commission's notice to the individual notice: for 500 or more individuals the Commission is told contemporaneously with the people affected. Section 318.4(d) carves out a delay for law enforcement keyed to 45 CFR 164.528(a)(2). And section 318.6 says what the notice must carry, to the extent possible: what happened, the date of the breach, the date of discovery if known, the information involved, what the person should do, what the entity is doing, and two or more contact channels.

Read that list against the register published below and the shape of the problem appears. The Rule requires a party to state its own discovery date in writing. The regulator requires a title, a deadline and a channel count. Almost none of the arithmetic is produced anywhere a stranger can reach.

Two registers, one endpoint each

The Commission publishes a list of health breach notices received, limited to the notices owed where 500 or more individuals are affected. Each entry carries the entity, its city and state, an approximate number of individuals affected, the date the breach was discovered, the type of breach and the type of information. The retrieved entries run from a discovery date of 09/24/2010 to 2026 dates. There is no field for the date the Commission received the notice.

The Department of Health and Human Services publishes its own breach report, required under section 13402(e)(4) of the HITECH Act for breaches affecting 500 or more individuals. Its row prints seven columns: Name of Covered Entity, State, Covered Entity Type, Individuals Affected, Breach Submission Date, Type of Breach, Location of Breached Information. There is no column for the date of the breach.

Put the two side by side and the interval the Rule operates on has no home. The Commission's row knows when the party says it knew and not when the party told the Commission. The Department's row knows when the party filed and not when the breach happened. A reader with both tabs open still cannot subtract arrival from discovery for any single case, because no published row in either register carries both numbers.

That is not an accusation that either register is hiding anything. It is a statement about what each page prints, measured on the material read on 20 November 2026. The Commission's list carries no visible last-updated date in the retrieved text and the entries were truncated in retrieval, so its currency is not established here; the statement that no GoodRx or Easy Healthcare entry appears on it is bounded to that retrieved text.

What 500 decides before it decides timing

The number appears twice in Part 318 and it counts two different things. The Commission-notice limb in 318.4(b) runs on 500 individuals. The media limb in 318.3(a)(3) runs on 500 residents of a State or jurisdiction. A single reader who carries one clean 500 away from this piece has lost the argument. Units are the article here, and the two obligations fire on different populations.

Below 500 individuals, the duty changes species rather than shortening. Section 318.5(c) says the entity "may maintain a log" of breaches and submit it annually, documenting breaches from the preceding calendar year. Section 318.4(b) gives that annual filing its window: no later than 60 calendar days following the end of the calendar year. Under 500 individuals there is no per-case notice to the Commission at all — a permissive log rather than a required filing, and the deadline runs from 31 December rather than from anything the firm discovered.

So the threshold decides whether a per-case record exists before it decides anything about timing. Above it, a case is created by the filing. Below it, a year is created by the filing, and only if the entity chooses to keep the log.

The page that routes nothing, and the form that still prints a dead deadline

Section 318.5(c) hands the mechanics of Commission notice to "instructions at the Federal Trade Commission's website." The Commission's Health Breach Notification Rule resource page describes the Rule, notes that certain breaches involving 500 or more people require media notice, links the rule text, the Federal Register notices and the notices file, and prints no filing address or submission instruction in the text retrieved here. The page describes the duty. It does not route the notice.

The routing lives on the Commission's Notice of Breach of Health Information form, OMB Control No. 3084-0150. It offers two routes: postal mail to the Associate Director – HBN in the Division of Privacy & Identity Protection at Mail Stop CC-8232, Washington DC, or an encrypted electronic transmission arranged first by a written request to the Commission's electronic filings mailbox, with a fixed subject line and no breach details in that request. It tells filers not to include the personally identifiable information involved in the breach.

And for breaches involving 500 or more people, that same form still instructs the filer to send it within 10 business days of discovering the breach.

The Commission's own 2024 final rule is the proof that this instruction is out of date. Published on 30 May 2024, it describes the 2009 rule as requiring Commission notice "as soon as possible and in no case later than ten business days" after discovery for breaches affecting 500 or more, and lists among its amendments altering the timing requirement for notifying the Commission. Seventeen years of arithmetic separate the 2009 text from the 2026 form, and the paper a filer actually downloads still measures in business days a deadline that now runs in calendar days from the same event, tied to the notice the individual receives.

Two clocks that look similar are not similar. Ten business days expires sooner than sixty calendar days in every ordinary span, so the form's instruction is not merely stale drafting — it is a stricter deadline than the Rule imposes, printed by the regulator, on the filing the regulator receives. A compliance officer who follows the form is early. A compliance officer who follows the Rule is lawful. Only one of them is following the document on the Commission's own site.

What the price actually fell on

The enforcement record is thinner than the register, and it says something different from what a reader might expect. In the GoodRx complaint, the Health Breach Notification Rule appears as Count VIII: the Commission alleges GoodRx is a vendor of personal health records under 318.2 and that it failed to give the required notices to individuals, to the Commission and to media outlets — a violation described as ongoing because users had not been notified. A syndicated reproduction of the Commission's release states that GoodRx agreed to pay a 1,500,000 dollar civil penalty and characterises the action as the first under the Rule; that figure travels here from the syndicated carrier, not from a press release page read in this run. In the Easy Healthcare stipulated order, judgment of 100,000 dollars is entered as a civil penalty, joint and several, alongside notice obligations to individuals, the Commission and, where 500 or more residents of a state are affected, prominent media outlets. The two figures are separate penalties in separate actions; they are not comparable rates and should not be added.

Neither document frames the charge as a notice late by a stated number of days. The pleated conduct is no notice at all. That is the finding worth carrying: the instrument's one measurable interval has not, in the two actions reviewed here, been the thing priced. What was priced was silence. The penalty route is written in the Rule itself: 16 CFR 318.7 makes any violation of Part 318 a violation of a rule under section 18 of the Federal Trade Commission Act, which is how a missed notice becomes a civil penalty. The arithmetic that would make lateness expensive — discovery date minus arrival date, per case, in calendar days — sits in a burden of proof that no published register lets anyone audit.

What is actually new here

This publication's coverage of the Federal Trade Commission has been entity, routing and enforcement-event work on the Commission's directory entry, including a 2023 Equifax enforcement item and a recent data-deletion item. My own health-breach reporting read the Department of Health and Human Services register and found the arrival date printed with the discovery anchor collected and never published. No piece located in that search opens Part 318's clocks, its sub-500 log, or the Commission's own notices list, and none sets the two federal registers beside each other to ask which endpoint each one prints. The comparison above is that work, bounded to the fourteen documents read on 20 November 2026.

The boundary on these findings

Three limits travel with the claims. The Part 318 section text was obtained by indexed retrieval of the eCFR pages rather than by a direct page fetch, quotations are kept short and the linked sections hold the verbatim, and punctuation was not re-verified against the rendered page. The Commission's notices list showed no visible last-updated date in the retrieved text and its entries were truncated, so its currency is not established and no absence claim about it is universal.

The Commission's frequently-asked-questions page was not readable in this run, so nothing here rests on it — including any per-violation or per-day penalty figure, which this article does not assert. The Department's row labels are a snapshot at retrieval on 20 November 2026, ahead of a scheduled maintenance window.