Clustered 3 filings across 3 jurisdictions · filing window Feb 10, 2023 → Feb 24, 2023. View entity profile → Other incidents for this victim →
incident inc_91ca19acd9174f4a · 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.
Identity (basic) · Government ID · Health (basic)
CA FL MT
HHS OCR · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Dec 15, 2022
When the intrusion reportedly occurred, per the linked filings
Dec 15, 2022
Reported by CALIFORNIA AG filing
Reventics, LLC reported a data breach to the Montana Attorney General. The breach was reported on 2023-02-10. The breach occurred on 12/15/2022. 2,856 Montana residents were affected.
Affected (this filing): 2,856
Reventics, LLC reported to HHS on 2023-02-10 a Hacking/IT Incident affecting 4212823 individuals. Breached information located on Network Server. Business Associate present.
Affected (this filing): 4,212,823
Reventics, LLC, a revenue cycle management company, detected a cyber-intruder who encrypted and potentially accessed information on its servers on December 15, 2022. The incident involved the unauthorized acquisition of PII and PHI, including names, SSNs, medical record numbers, and clinical data. Reventics engaged forensic consultants, contained the threat, and is offering identity protection services to affected individuals.
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.