Confirmed breach. Intrusion Oct 24, 2023–Oct 26, 2023, discovered Oct 26, 2023 — the first regulatory filing landed 57 days later. 1,053 individuals reported across the linked filings.
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 clocksMaine⏱ ME AG >30d · 63dHIPAA✓ HHS notifiedFull clock table in Litigation Timeline
HHS OCRState AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedmoderate sensitivity
Affected (total reported)
1,053
Data types
2
PII · PHI
Jurisdictions
2
ME TN
Linked filings
2
HHS OCR · State AG
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
Oct 24, 2023 → Oct 26, 2023
When the intrusion reportedly occurred, per the linked filings
Breach discovered
Oct 26, 2023
Reported by MAINE AG filing
57 days
🇺🇸TNHHS OCRFirst filinglinked via same-victim cross-source · 100%
RevSpring, Inc. reported to HHS on 2023-12-22 a Unauthorized Access/Disclosure affecting 1,053 individuals. Breached information located on Network Server. A software coding error allowed PHI (names, addresses, diagnoses, treatment info) to be viewable by others. The BA implemented additional safeguards and retrained workforce.
Affected (this filing): 1,053
HHS notified
🦞Maine State AGMost recentlinked via same-victim cross-source · 100%
An internal error at RevSpring, Inc. resulted in mismatched patient statements being viewable by a limited set of other patients. This incident occurred between October 24, 2023, and October 26, 2023, and was discovered on the same day it ended. The breach impacted 3 Maine residents. In response, the company offered 12 months of complimentary credit monitoring services to those affected.
Affected (this filing): 3
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.