PENNSYLVANIAPhysicalHealthcareHealthcareTheftCustomer Data InvolvedHealth (basic)Identity (basic)Medium

CardioNet, Inc.

bd_58eb0549a65c22a2 · schema v1 · pii pii-v1

Severity

Medium

Discovered

—

Filed

Jan 10, 2012

To disclose

—

Affected

1,300

Linked

2 filings

Confidence

95%

Full breach record for CardioNet, Inc. →3 incidents on file

CardioNet, Inc. (PA) reported to HHS OCR on 2012-01-10 a Theft incident affecting 1,300 individuals. Breached information was located on a Laptop. No business associate was identified. The covered entity is a healthcare provider offering cardiac monitoring services based in Pennsylvania.

J jump to incidentP pin to compareR raw source

HIPAA clock✓ HHS notified

⚠ no discovery dateNo discovery date was extracted, so no notification clock can be evaluated.

⚠ No discovery dateThe OCR public portal omits the discovery date, so the 60-day notification clock cannot be evaluated from this source — only that the filing was submitted.

Incident timeline — partial

? — ?

Breach window unknown

Jan 10, 2012

Filed

—

Corroborated · see linked filings

Compliance clocks stay unassessable until a regulatory filing lands. Dashed segments fill in automatically when corroboration arrives.

This filing is one of 2 about the same incident.View merged incident

Linked disclosures

Why this link?

Regulatory filings (1) · sorted by filing gap

HHS OCR enforcementbd_61221d9b00f15f862017-04-24 · +1931dVerified by operator

Name: CardioNet, Inc.
norm: cardionet
Industry: Health Care Services

Name: CardioNet, Inc.
norm: cardionet
Industry: Health Care Services
Industry: Healthcaresource default

Discovered: Not extracted — the OCR public portal omits it
Materiality determined: —
Notification sent: —
Affected individuals: 1,300nationwide
Data types: Health (basic)Identity (basic)
HHS breach type: Theft
Where the data lived: Laptop
Covered-entity type: Healthcare provider
Attack vector: Unauthorized Access
MITRE ATT&CK: T1052 Exfiltration Over Physical Medium
Threat actor: External

Compliance flags: HHS notified
Discovery-date grounding: no discovery dateNo discovery date was extracted, so no notification clock can be evaluated.
Clock breakdown: Statute Window Elapsed Threshold Status
HIPAA
Discovered: not extracted
→ Notified: not extracted
— regulatory submission HHS notified

Statute	Window	Elapsed	Threshold	Status
HIPAA	Discovered: not extracted → Notified: not extracted	—	regulatory submission	HHS notified

Status: No extraction artifact recorded for this disclosure.

Filing propagation · 2 filings

View merged incident ↗

HHS OCRJan 10 · first · this page

HHS OCR enforcement+1931d

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

Leak-site claim

Attacker assertion only. Establishes: claim date, group, alleged victim.

Press / market report

Unlocks: incident narrative, operational impact. Still no compliance clock.

State AG / regulator filingThis record

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statement

Unlocks: materiality, stated response, full audit trail. Ceiling removed.

Source URL: https://ocrportal.hhs.gov/ocr/breach/breach_report.jsf
DisclosureLens renders the full SEC/HHS filing inline below from the originating regulator’s public record (§4.5 fair report privilege).
Filed at: Jan 10, 2012
Raw hash: 34ac5abb11057d59dfbaddfb02dc438c439bf5d4af7ae2f9efcc1a53361a239d

AI-assisted summary above. The structured extract on this page was generated from the document below. Inspect the source to verify or correct any field.

text/html950 B

Download View at source

Linked disclosures

Regulatory filings (1) · sorted by filing gap

Reporting entityCardioNet, Inc.

Victim entityCardioNet, Inc.

IncidentUnauthorized Access

ComplianceHHS notified

Extraction provenanceno artifact recorded

Source provenanceocrportal.hhs.gov

Source filing