Clustered 3 filings across 3 jurisdictions · filing window Jun 16, 2022 → Jun 23, 2022. View entity profile → Other incidents for this victim →
incident inc_ea1f48b884744373 · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
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.
MD MT WA
HHS OCR · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Apr 17, 2022
Reported by WASHINGTON AG filing
Jun 6, 2022
When the intrusion reportedly occurred, per the linked filings
New Schryver, LLC d/b/a/ TridentCare reported to HHS on 2022-06-16 a Theft affecting 6190 individuals. Breached information located on Other Portable Electronic Device. Hard drives containing PHI (names, SSNs, DOB) were stolen in a burglary. The entity provided credit monitoring and enhanced security safeguards.
Affected (this filing): 6,190
New Schryver, LLC dba TridentCare reported a data breach to the Montana Attorney General. The breach was reported on 2022-06-23. The breach occurred on 6/6/2022. 4 Montana residents were affected.
Affected (this filing): 4
New Schryver, LLC d/b/a TridentCare, a health sector entity reported a theft or mistake incident to the Washington Attorney General. The organization became aware of the incident on 2022-04-17 and filed notice on 2022-06-23. 554 Washington residents were affected. 67 days elapsed between awareness and notification. 0 days to identify the breach. 0 days to contain the breach.
Affected (this filing): 554
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.