DisclosureLens
HHS OCRState AGConfirmed5 filings · 5 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedmoderate sensitivity
Merged incident · 5 filings

Advocare Brandywine Pediatrics — October 2016 breach

Clustered 5 filings across 5 jurisdictions · filing window Dec 23, 2016 → Dec 29, 2016. View entity profile → Other incidents for this victim →

Determination

Confirmed

Members

5 filings

States

5

Affected · reported

26,873

First → last filing

Dec 23, 2016 → Dec 29, 2016

Merge confidence

100%

incident inc_d17118bdaaf04c0e · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 5 regulatory filings. The filings describe malware. Intrusion Oct 11, 2016, discovered Oct 11, 2016 — the first regulatory filing landed 73 days later. 26,873 individuals reported across the linked filings. Data reported: PII, Identity (basic), PHI, and 2 more. Notifications rolled out on a 6-day schedule across 5 filings beginning Dec 23, 2016. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
73days

Discovered → first regulatory filing

Discovery variance
14days

Range of discovered_at dates across filings

Filing span
6days

Time between earliest and latest filing

Not recorded for this incident

Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster.

Regulatory clocksHIPAA✓ HHS notifiedFull clock table in Litigation Timeline

Incident timeline

Oct 11, 2016breach begins
Oct 11, 2016discovered · members disagree
notification delay · 73 days
Dec 23, 2016first filing
Dec 29, 2016most recent filing

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

Member cascade — every filing about this breach

  1. DEC 23MT AGMT AG noticefirst filing · 1 MT residentsday 0
  2. DEC 23HHS OCRHHS OCR noticestates nationwide total 26,873day 0
  3. DEC 23NH AGNH AG notice10 NH residentsday 0
  4. DEC 23MA AGMA AG notice49 MA residentsday 0
  5. DEC 29SC AGSC AG noticemost recent · 25 SC residents+6d
  6. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Oct 11, 2016
HHS OCR
Discovered
Oct 11, 2016HHS OCROct 25, 2016MT AG + NH AG + SC AGfilings disagree on discovery
Data types
Financial account · Health (basic) · Identity (basic) · PHI · PII
MT AG + NH AG + SC AG +2
Attack vector
Unauthorized Access
HHS OCR

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

Count reconciliation

per-state reported counts

Nationwide (stated in a filing)

26,873

Sum of filed state slices

85· 0.3% of stated

100% of the stated total lives in states whose filings carry no count — the dashed share shrinks as filings land.

US26,873
MA49
SC25
NH10
MT1

State AGs report only their own residents; teal bars show each state's reported slice. The gray US row is the nationwide total reported in a linked filing.

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 filing5 members

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

SEC 8-K / victim statement

No SEC filing or victim statement yet.

Merge provenance

Method
deterministic
Confidence
1.00 · above the 0.85 auto-merge floor
Reviewed
operator-reviewed Jun 12, 2026 · at least one link edge was human-adjudicated
Audit
Every link edge records its method, confidence and model + prompt versions (100% is the strongest edge).

Merges are reversible — a wrong link can be detached with its audit trail intact. How merging works.

Filing velocity

Spread

6 days

Cadence

~1 / 1.5d

vs. multi-state median

1.0× faster

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. This page states only what the linked filings agree on; each filing's own account stays on its own record, linked from the timeline below.

The weekly clock on records like this one

The Disclosure Clock is a weekly briefing on what landed in the disclosure record, and the gap between the criminals' post and the regulator's filing — measured on the whole record, with the method shown.

Weekly. Double opt-in, one-click unsubscribe, and the address goes nowhere else.