Long Island Jewish Forest Hills Hospital — August 2016 breach
Clustered 3 filings across 3 jurisdictions · filing window Aug 3, 2021 → Aug 6, 2021. View entity profile → Other incidents for this victim →
incident inc_5a4a769dd4fa4d4a · merged by deterministic · confidence 100%
Litigation Timing
SupplementalTime between earliest and latest filing
Not recorded for this incident
Discovery variance · Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster; needs two dated filings.
Sensitive data
identity_governmentIncident timeline
No discovery date is recorded on any filing in this cluster, so the notification delay is not computable. Dashed segments fill in as filings merge.
Member cascade — every filing about this breach
- AUG 3MA AGMA AG noticefirst filing · 9 MA residentsauto-linkedday 0
- AUG 5MT AGMT AG notice1 MT residents+2d
- AUG 6HHS OCRHHS OCR noticemost recent · states nationwide total 10,333auto-linked+3d
- Watching for additional filings — new sources merge into this incident automatically.
Roll-up facts — reconciled across members
- Breach window
- Aug 23, 2016 – Oct 31, 2017 MT AG
- Discovered
- —
- Data types
- Health (basic) · Identity (basic) · Government ID · PHI MA AG + MT AG + HHS OCR
- Attack vector
- Insider MT AG
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)
10,333
Sum of filed state slices
10· 0.1% of stated
100% of the stated total lives in states whose filings carry no count — the dashed share shrinks as filings land.
Evidence ladder — rungs this incident occupies
No leak-site claim on record for this incident.
No press coverage linked yet.
Unlocks: discovery date, data types, affected count, compliance clock.
No SEC filing or victim statement yet.
Merge provenance
- Method
- deterministic
- Confidence
- 1.00 · above the 0.85 auto-merge floor
- 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
3 days
Cadence
~1 / 1.5d
vs. multi-state median
2.7× 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.