Bryan County Ambulance Authority — November 2021 breach
Clustered 5 records across 5 jurisdictions: 4 filings and 1 enforcement record · filing window May 18, 2022 → May 24, 2022 (dated filings only). View entity profile → Other incidents for this victim →
incident inc_c3f0429e3489419a · merged by deterministic · confidence 100%
Litigation Timing
Range of discovered_at dates across filings
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.
Sensitive data
identity_governmentIncident timeline
Dashed segments are unestablished, not zero — they fill in as filings merge into this incident. Filings without a recorded filing day, or recorded as filed before the breach they report began, are not placed on this rail.
Member cascade — every filing and enforcement record in this incident
- JAN 1IL AGIL AG noticefiling day not on record · no count stated—
- MAY 18MT AGMT AG noticefirst filing · 1 MT residentsauto-linkedday 0
- MAY 18HHS OCRHHS OCR noticestates nationwide total 14,273auto-linkedday 0
- MAY 24WA AGWA AG notice1 WA residentsauto-linked+6d
- OCT 31HHS OCR enforcementHHS OCR enforcement noticemost recent · no count statedoperator-confirmed+897d
- Watching for additional filings — new sources merge into this incident automatically.
Roll-up facts — reconciled across members
- Breach window
- Nov 24, 2021 – Nov 29, 2021 WA AG
- Discovered
- Nov 21, 2021IL AGNov 24, 2021MT AG + WA AGfilings disagree on discovery
- Data types
- Health (basic) · Identity (basic) · Government ID · PHI · PII MT AG + HHS OCR + WA AG
- Attack vector
- Ransomware 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)
14,273
Sum of filed state slices
2· 0.0% 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
- Reviewed
- operator-reviewed Sep 6, 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 / 3d
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.