DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
HHS OCRState AGConfirmed10 filings · 7 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 10 filings

Northwood, Inc. — May 2019 breach

Clustered 10 filings across 7 jurisdictions · filing window Jul 12, 2019 → Jul 16, 2019. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

10 filings

States

7

Affected · reported

86,050

First → last filing

Jul 12, 2019 → Jul 16, 2019

Merge confidence

100%

incident inc_5abd58eb43694dcd · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 10 regulatory filings. Intrusion May 3, 2019–May 6, 2019, discovered May 6, 2019 — the first regulatory filing landed 67 days later (flagged late). 86,050 individuals reported across the linked filings. Data reported: Government ID, PHI, Health (basic), and 5 more. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
67days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Filing span
4days

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 clocksCalifornia✗ CA 60-day late · 74dHIPAA✓ HHS notifiedMassachusetts✓ MA credit monitoring dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

May 3, 2019breach begins
May 6, 2019discovered
notification delay · 67 days
Jul 12, 2019first filing
Jul 16, 2019most 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. JUL 12HHS OCRHHS OCR noticefirst filing · states nationwide total 18,684day 0
  2. JUL 15MA AGMA AG notice1,518 MA residents+3d
  3. JUL 15MT AGMT AG notice180 MT residents+3d
  4. JUL 15NH AGNH AG notice386 NH residents+3d
  5. JUL 15HHS OCRHHS OCR noticestates nationwide total 5,563+3d
  6. JUL 15WA AGWA AG notice1,185 WA residents+3d
  7. JUL 15OR AGOR AG noticestates nationwide total 86,050+3d
  8. JUL 15CA AGCA AG noticeno count stated+3d
  9. JUL 16HHS OCRHHS OCR noticestates nationwide total 583+4d
  10. JUL 16HHS OCRHHS OCR noticemost recent · states nationwide total 3,881+4d
  11. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
May 3, 2019 – May 6, 2019
MT AG
Discovered
May 6, 2019· 3d undetected
MT AG + NH AG + WA AG +1
Data types
Financial account · Health (basic) · Identity (basic) · Government ID · Metadata · PCI · PHI · PII
HHS OCR + MT AG + CA AG +3
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)

86,050

Sum of filed state slices

3,269· 3.8% of stated

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

US86,050
MA1,518
WA1,185
NH386
MT180

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 filing10 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
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

4 days

Cadence

~1 / 0.4d

vs. multi-state median

2.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.