All incidents View linkage analytics →Get the evidence package — $79

Confirmed2 filings · 2 statesUnverified claimConfirmedEnforcedmoderate sensitivity

Merged incident · 2 filings

Community Based Care of Brevard — December 2025 breach

Clustered 2 filings across 2 jurisdictions · filed Jul 17, 2026. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

2 filings

States

Affected · reported

8,151

First → last filing

Jul 17, 2026

Merge confidence

100%

incident inc_de724453062c41be · merged by deterministic · confidence 100%

Confirmed breach. One breach, 2 legal records. Intrusion Dec 4, 2025–Jan 2, 2026, discovered May 19, 2026 — the first regulatory filing landed 59 days later. 8,151 individuals reported across the linked filings. This page is the deduped roll-up; each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay

59days

Discovered → first regulatory filing

Filing span

0days

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

Regulatory clocksHIPAA✓ HHS notifiedFull clock table in Litigation Timeline

Incident timeline

Dec 4, 2025breach begins

May 19, 2026discovered

notification delay · 59 days

Jul 17, 2026first 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 17NH AGNH AG noticefirst filing · 5 NH residentsauto-linkedday 0
JUL 17HHS OCRHHS OCR noticemost recent · states nationwide total 8,151auto-linkedday 0
Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window: Dec 4, 2025 – Jan 2, 2026
Discovered: May 19, 2026· 166d undetected
Data types: PHI · Health (basic) · Identity (basic)
Attack vector: Unauthorized Access
Response: Launched an investigation with the assistance of third-party forensic specialists · Review the potentially copied files to determine whether they contained any sensitive information · Provided written notice of this incident to five (5) New Hampshire residents

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)

8,151

Sum of filed state slices

5· 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

Leak-site claim

No leak-site claim on record for this incident.

Press / market report

No press coverage linked yet.

State AG / regulator filing2 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

0 days

vs. multi-state median

20.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. Filing summaries shown in the timeline are AI-generated extracts — verify each against its linked source.