DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
Leak SitePressHHS OCRState AGConfirmed8 filings · 5 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedmoneymessagehigh sensitivity
Merged incident · 8 filings

ANNA JAQUES HOSPITAL — November 2023 breach

Clustered 8 filings across 6 jurisdictions · filing window Jan 19, 2024 → Dec 10, 2024. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

8 filings

States

5

Affected · reported

316,342

First → last filing

Jan 19, 2024 → Dec 10, 2024

Merge confidence

100%

incident inc_9d926fc5c14342a2 · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 6 regulatory filings, 1 press report and 1 unverified claim. The filings describe unauthorized access. Intrusion Nov 17, 2023–Dec 25, 2023, discovered Dec 22, 2023 — the first regulatory filing landed 60 days later (flagged late). 316,342 individuals reported across the linked filings. Data reported: Government ID, PHI, PII, and 4 more. Notifications rolled out on a 351-day schedule across 6 filings beginning Jan 19, 2024. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
60days

Discovered → first regulatory filing

Discovery variance
3days

Range of discovered_at dates across filings

Leak precedence
31days before filing

Days between the first leak-site claim and the first regulatory filing. Positive = the claim came first (public exposure before disclosure). Negative = the claim trailed the filing, so there was no pre-disclosure leak. Counts regulatory filings only — press coverage is not a regulatory disclosure.

Filing span
351days

Time between earliest and latest filing

Not recorded for this incident

Materiality delta · SEC filing delay — no SEC 8-K in this cluster.

Regulatory clocksLeak gap✗ Leak >180dMaine✗ ME AG >90d · 349dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Nov 17, 2023breach begins
Dec 22, 2023discovered · members disagree
notification delay · 60 days
Feb 20, 2024first filing
Dec 10, 2024most 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. JAN 19Leak sitemoneymessage postfirst filing · attacker claim · unverifiedday 0
  2. FEB 20HHS OCRHHS OCR noticestates nationwide total 308,829+31d
  3. DEC 5ME AGME AG noticestates nationwide total 316,342+320d
  4. DEC 5IN AGIN AG noticestates nationwide total 316,342+320d
  5. DEC 5MA AGMA AG notice81,268 MA residents+320d
  6. DEC 5VT AGVT AG noticeno count stated+320d
  7. DEC 10NH AGNH AG noticemost recent · 15,327 NH residents+325d
  8. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Dec 25, 2023
ME AG
Discovered
Dec 22, 2023ME AGDec 25, 2023NH AGfilings disagree on discovery
Data types
Financial · Financial account · Health (basic) · Identity (basic) · Government ID · PHI · PII
HHS OCR + NH AG + ME 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)

316,342

Sum of filed state slices

97,245· 30.7% of stated

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

US316,342
MA81,268
NH15,327
ME637
IN13

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 claim1 member

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

Press / market report1 member

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

State AG / regulator filing6 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
human
Confidence
1.00 · above the 0.85 auto-merge floor
Reviewed
operator-reviewed Aug 22, 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

351 days

Cadence

~1 / 50.1d

vs. multi-state median

43.9× slower

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.