CardioNet, Inc.
bd_61221d9b00f15f86 · schema v1 · pii pii-v1
Full breach record for CardioNet, Inc. →3 incidents on fileRegulator's decision — not a breach notification
This record is a regulator's decision, not the organisation's own breach notice. Breach-notification fields (discovery date, notification clock) are structurally absent — what this source establishes is the outcome and the provisions the decision cites.
HHS OCR settled with CardioNet for $2.5 million regarding the impermissible disclosure of unsecured electronic protected health information (ePHI) in violation of HIPAA Privacy and Security Rules.
J jump to incidentP pin to compareR raw source
Incident timeline — partial
? — ?
Breach window unknown
Apr 24, 2017
Filed
—
Corroborated · see linked filings
Compliance clocks stay unassessable until a breach filing is linked. This record is the regulator's action, not a breach notice. Dashed segments fill in automatically when corroboration arrives.
Linked disclosures
Why this link?Regulatory filings (1) · sorted by filing gap
- HHS OCRbd_58eb0549a65c22a22012-01-10 · +1931dCandidate
Filing propagation · 2 filings
View merged incident ↗Pattern: first filing Jan 10 (PA), last Apr 24 — a 1931-day rolling notification. Rolling spreads often mean counsel is filing as thresholds trip per state. Why this link?
Evidence ladder
Attacker assertion only. Establishes: claim date, group, alleged victim.
Unlocks: incident narrative, operational impact. Still no compliance clock.
Unlocks: discovery date, data types, affected count, compliance clock.
Unlocks: materiality, stated response, full audit trail. Ceiling removed.
Source ceiling
- instrument + outcome
- amount as filed (USD)
- CFR provisions
- the breach it recites
- discovery date
- notification clock
The dates the agreement recites belong to the underlying breach, years earlier, and are kept as evidence of WHICH breach rather than as this record’s timeline.