Breach filing
ArchivedConnexin Software, Inc.: 2,846,039 individuals, Nov 2022.
Connexin Software, Inc. reported a breach of unsecured protected health information to the HHS Office for Civil Rights on 11 November 2022. The filing records the organisation as a business associate in Pennsylvania and lists 2,846,039 individuals affected, which makes it the 1st largest of the 339 Pennsylvania filings on the register and the 4th largest of the 718 filings submitted nationally in 2022. Among the 38 Pennsylvania filings made in 2022 it ranks 1st.
Individuals affected
2,846,039
As reported to HHS
Modelled cost (IBM 2025)
$455M
Upper bound, method shown
Rank in PA
1st
of 339 Pennsylvania filings
Rank in 2022
4th
of 718 filings nationally
Section F.1 / The filing
As posted by HHS OCR
Every value below is the portal's own field for this filing, plus its rank within the register.
- Covered entity type
- Business Associate
- Individuals affected
- 2,846,039
- Breach submission date
- 11 November 2022
- Submission year
- 2022
- Type of breach
- Hacking/IT Incident
- Location of breached information
- Network Server
- Business associate present
- Yes
- State
- Pennsylvania (PA)
- Portal status
- listed in the HHS OCR breach portal archive
- Rank in Pennsylvania by size
- 1st of 339
- Rank in 2022 nationally
- 4th of 718
- Pennsylvania median filing
- 3,905 individuals
- Register id (derived)
- PA-20221111-connexin-software
Section F.2 / In context
Where this filing sits in Pennsylvania and in 2022
OCR classifies the incident as a hacking or IT incident, with the breached information held in a network server. Hacking/IT Incident is the type recorded on 228 of the 339 Pennsylvania filings (67%) and on 79% of all filings submitted in 2022. Network Server is the most common location in the state, appearing on 51% of Pennsylvania filings.
A business associate is recorded as present on the filing, as it is on 34% of Pennsylvania filings. At 2,846,039 individuals the breach is 729 times the Pennsylvania median filing of 3,905 and 712 times the national median of 4,000 across all 7,884 filings. It is one of 149 filings on the register of one million or more individuals.
As of 28 August 2026 the case is listed in the HHS OCR breach portal archive. OCR's closing summary of the case is reproduced in full below.
Pennsylvania's breach notification statute (73 Pa. Stat. 2301 et seq.) requires notice to affected residents without unreasonable delay. Its attorney general threshold: more than 500 Pennsylvania residents. The HIPAA Breach Notification Rule ran alongside it: notice to affected individuals and to HHS without unreasonable delay and no later than 60 days after discovery, which is the clock that put this filing on the portal.
Multiplying 2,846,039 individuals by IBM's $160 customer-PII cost per record (Cost of a Data Breach 2025, the figure the site's calculator uses) gives a modelled $455M; the 2026 edition's $192 gives $546M. Both are modelled estimates with the method shown, not costs disclosed by Connexin Software, Inc.. Because the filing is above the roughly 100,000-record range in which the per-record figure is reliable, the result is an upper bound, not an estimate: fixed costs are spread across far more records at this scale.
Section F.3 / OCR closing summary
The portal's archived description, in full
Written by the Office for Civil Rights when the case was closed and reproduced verbatim from the HHS export.
Connexin Software, the business associate (BA), reported that it experienced a cyberattack that compromised the protected health information (PHI) of 2,675,934 individuals. The PHI involved in the incident included names, addresses, dates of birth, social security numbers, claims information, diagnoses/conditions, lab results, medications, and other treatment information. The BA notified HHS, affected individuals, and the media. In response to this incident, the BA updated its HIPAA policies and procedures to help prevent future security incidents and implemented new administrative and technical safeguards, such as muti-factor authentication.
Section F.5 / Modelled cost
2,846,039 individuals through IBM's per-record figures
Modelled cost / method shown, not a disclosed cost
Upper boundIBM 2025 customer PII, $160 per record
$455M
2,846,039 x $160
IBM 2026 customer PII, $192 per record
$546M
2,846,039 x $192
Method: individuals affected, as reported by Connexin Software, Inc. to HHS, multiplied by IBM's customer-PII cost per record (Cost of a Data Breach 2025 Figure 6 and the 2026 edition). No cost has been disclosed by the entity for this filing; the figure is a planning estimate, not a fact about the breach. IBM's per-record figures come from mid-volume breaches and IBM cautions against applying them to breaches involving millions of records; the site's per-record page explains where the multiplication holds and where it breaks down.
Context: IBM's average cost of a healthcare breach is $6.64M in the 2026 report ($7.42M in 2025); the global average across all sectors was $4.44M in 2025.
Cost per record: method and limits / Healthcare breach cost, IBM 2026
Section F.6 / Notification clock
Pennsylvania statute and the HIPAA rule
State notification statute
Pennsylvania: 73 Pa. Stat. 2301 et seq.
Breach of Personal Information Notification Act (amended by Act 33 of 2024)
- Notice to individuals
- Without unreasonable delay
- Attorney general threshold
- More than 500 Pennsylvania residents (Without unreasonable delay (online portal))
- Private right of action
- Yes: Treated as an unfair or deceptive practice; consumers may pursue civil suits
- Penalty
- AG enforcement via civil actions, injunctive relief, civil penalties, and restitution
The HIPAA Breach Notification Rule runs alongside the state statute: notice to affected individuals and to HHS without unreasonable delay and no later than 60 days after discovery.
Section F.7 / Peer filings
Pennsylvania filings closest in size
Neighbours by size rank among Pennsylvania filings in 2022, topped up from other years where 2022 has too few. Filings of 10,000 or more link to their own page.
| Covered entity | Type | Individuals | Submitted | Breach type | Location | BA |
|---|---|---|---|---|---|---|
| Geisinger | Healthcare Provider | 1,276,026 | 21 Jun 2024 | |||
| Iron Mountain Data Products, Inc. (now known as | Business Associate | 800,000 | 19 Jul 2010 | |||
| Allegheny County | Healthcare Provider | 689,686 | 28 Jul 2023 | |||
| Maternal and Family Health Services | Healthcare Provider | 461,070 | 8 Aug 2022 | |||
| Keystone Health | Healthcare Provider | 235,237 | 14 Oct 2022 |
Index / Companion schedules
13 HHS breach register
→Hub: every filing, by state, year and entity.
04 Biggest breaches
→Mega-breaches with primary-source cost figures.
Industry / Healthcare
→IBM 2026: $6.64M average, 13 years at #1.
Regulation / HIPAA penalties
→OCR enforcement tiers and the 60-day rule.
11 50-state laws
→Deadline, AG threshold and penalties per state.
Cost / Per record
→Where the per-record model is reliable.
Provenance
Source: U.S. Department of Health and Human Services, Office for Civil Rights, Breach Portal (breaches affecting 500 or more individuals), retrieved 2026-08-28. Public domain. Individuals affected and dates as reported by the covered entity.
Portal: ocrportal.hhs.gov breach report. Statutory basis: HITECH Act section 13402(e)(4): the Secretary must post a list of breaches of unsecured protected health information affecting 500 or more individuals. Breaches affecting fewer than 500 individuals are reported to OCR annually and are not posted, so they are not on this register. Status wording follows the portal's two tabs ("Cases Currently Under Investigation" and "Archive") as of 28 August 2026; a filing moves to the archive when OCR closes the case. Modelled costs on this site are a method applied to the reported count, using IBM Cost of a Data Breach per-record figures, and are never a cost disclosed by the entity. This row: hhs-breach-archive__2026-08-28.csv, export row 2102.
Corrections: if you represent a listed entity and the portal row has been amended, email [email protected] with the portal entry and we will re-pull the export.