US HealthConnect Inc reported a data breach to the Indiana Attorney General. The breach occurred on 2025-01-12 and was reported on 2025-09-04. 14 Indiana residents were affected. 1,914 individuals affected in total.
Affected (this filing): 1,914
Clustered 2 filings across 2 jurisdictions · filed Sep 4, 2025. View entity profile → Other incidents for this victim →
incident inc_e24567742e4c4b47 · 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.
IN NH
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Jan 12, 2025
When the intrusion reportedly occurred, per the linked filings
Jan 25, 2025
Reported by NEW HAMPSHIRE AG filing
US HealthConnect Inc reported a data breach to the Indiana Attorney General. The breach occurred on 2025-01-12 and was reported on 2025-09-04. 14 Indiana residents were affected. 1,914 individuals affected in total.
Affected (this filing): 1,914
US HealthConnect, Inc. notified the New Hampshire Attorney General of a data event affecting one NH resident. On January 25, 2025, suspicious activity was detected, leading to an investigation that found an unauthorized actor accessed systems containing the resident's name and Social Security number. Notice was sent on September 4, 2025, offering 24 months of credit monitoring via Experian. Federal law enforcement was notified.
Affected (this filing): 1
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.