Physician Associates, LLC — October 2015 breach

One linked filing — more sources may join as they report · filed Jul 3, 2018. View entity profile → Other incidents for this victim →

Determination

Confirmed

Members

1 filing

States

Affected · reported

710

First → last filing

Jul 3, 2018

incident inc_8edd7ae2e13040ba · merged by deterministic

Part of the CoPilot Provider Support Services supply-chain incident (2017) — at least 4 organizations filed notifications naming this third party.

Confirmed breach. Intrusion Oct 1, 2015–Oct 31, 2015, discovered Aug 7, 2017 — the first regulatory filing landed 330 days later (flagged late). 710 individuals reported across the linked filings.

Litigation Timing

Notification delay

330days

Discovered → first regulatory filing

Not recorded for this incident

Discovery variance · Leak precedence · Materiality delta · SEC filing delay · Filing span — no leak-site claim in this cluster; no SEC 8-K in this cluster; needs two dated filings.

Regulatory clocksHIPAA✗ HHS report late · 330dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Oct 1, 2015breach begins

Aug 7, 2017discovered

notification delay · 330 days

Jul 3, 2018first & only filing

—watching for filings

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident.

Member cascade — every filing about this breach

JUL 3HHS OCRHHS OCR noticeonly filing · states nationwide total 710day 0
Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window: Oct 1, 2015 – Oct 31, 2015
Discovered: Aug 7, 2017· 676d undetected
Data types: PHI · Health (basic) · Identity (basic) · Government ID · Financial account
Attack vector: Unauthorized Access
Response: Ceased using CoPilot as a vendor · Re-educated its leadership on business associate (BA) agreements · Reviews vendor lists on a monthly basis to ensure that appropriate BA agreements are in place

Each fact cites the member filing that establishes it; when filings conflict, every value shows with its source.

Evidence ladder — rungs this incident occupies

Leak-site claim

No leak-site claim on record for this incident.

Press / market report

No press coverage linked yet.

State AG / regulator filing1 member

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

SEC 8-K / victim statement

No SEC filing or victim statement yet.

About this clustering

DisclosureLens links filings into incidents through layered matchers: deterministic rules (same source document, multistate filings of one breach, tight-window same-victim pairs), a weighted-similarity scorer for cross-source candidates, and an operator review queue for everything uncertain. Each link records its own method and confidence — shown per filing in the timeline below. The system defaults to NOT merging when uncertain, because a false merge (collapsing two unrelated breaches) is more harmful than a false split (showing related filings separately); uncertain pairs route to human review instead of auto-merging. Filing summaries shown in the timeline are AI-generated extracts — verify each against its linked source.