Form: Cost-of-Breach DisclosureSource: IBM Cost of a Data BreachFiled: 28 Apr 2026
DataBreachCost.comOpen calc
Independent breach-cost research, read by security and risk leaders.Sponsor this site →
Filing TX-20141110-visionworksHHS OCR Breach Register, Texas

Breach filing

Archived

Visionworks Inc.: 74,944 individuals, Nov 2014.

Visionworks Inc. reported a breach of unsecured protected health information to the HHS Office for Civil Rights on 10 November 2014. The filing records the organisation as a health plan in Texas and lists 74,944 individuals affected, which makes it the 82nd largest of the 633 Texas filings on the register and the 17th largest of the 314 filings submitted nationally in 2014. Among the 27 Texas filings made in 2014 it ranks 3rd.

Individuals affected

74,944

As reported to HHS

Modelled cost (IBM 2025)

$12.0M

Method shown, not disclosed

Rank in TX

82nd

of 633 Texas filings

Rank in 2014

17th

of 314 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
Health Plan
Individuals affected
74,944
Breach submission date
10 November 2014
Submission year
2014
Type of breach
Loss
Location of breached information
Network Server
Business associate present
No
Portal status
listed in the HHS OCR breach portal archive
Rank in Texas by size
82nd of 633
Rank in 2014 nationally
17th of 314
Texas median filing
4,055 individuals
Register id (derived)
TX-20141110-visionworks

Section F.2 / In context

Where this filing sits in Texas and in 2014

OCR classifies the incident as loss of records or equipment, with the breached information held in a network server. Loss is the type recorded on 21 of the 633 Texas filings (3%) and on 10% of all filings submitted in 2014. Network Server appears on 45% of Texas filings.

No business associate is recorded on the filing; 27% of Texas filings do involve one. At 74,944 individuals the breach is 18 times the Texas median filing of 4,055 and 19 times the national median of 4,000 across all 7,884 filings. It sits in the 10,000 to 99,999 band, which holds 1,938 filings.

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.

Texas's breach notification statute (Tex. Bus. & Com. Code 521.053) requires notice to affected residents without unreasonable delay, no later than the 60th day after determining a breach occurred. Its attorney general threshold: 250 or more Texas 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 74,944 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 $12.0M; the 2026 edition's $192 gives $14.4M. Both are modelled estimates with the method shown, not costs disclosed by Visionworks Inc.. For scale, IBM's 2026 average cost of a healthcare breach is $6.64M, so this filing models at 2.2 times the sector average.

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.

The covered entity (CE), Visionworks Inc., mislaid a partially encrypted, decommissioned computer server from its in-store lab in Annapolis, Maryland which was not recovered. The server's hard drive contained the unencrypted protected health information (PHI) of approximately 74,000 individuals. The PHI on the server contained demographic, financial, and clinical information. Following the breach, the CE fully encrypted all servers at all of their locations and replaced servers. The CE provided breach notification to HHS, affected individuals, and the media, and offered one year of free credit monitoring. The CE also sent letters to each State Attorney General and posted information on the CE's website regarding the server incident. In addition, the CE re-trained workforce members, instituted new training requirements on privacy and security awareness, and provided refresher training on incident management. Following OCR's investigation, the CE secured servers with cable locks and tested and installed a maximum security system that encrypts all hard drives on each server. Additionally, the CE completed a company-wide server inventory and hard drive destruction and performed a physical audit of all servers' boxes. In addition, the CE created a comprehensive system disposal plan.

Section F.5 / Modelled cost

74,944 individuals through IBM's per-record figures

Modelled cost / method shown, not a disclosed cost

Modelled

IBM 2025 customer PII, $160 per record

$12.0M

74,944 x $160

IBM 2026 customer PII, $192 per record

$14.4M

74,944 x $192

Method: individuals affected, as reported by Visionworks 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

Texas statute and the HIPAA rule

State notification statute

Texas: Tex. Bus. & Com. Code 521.053

Notice to individuals
Without unreasonable delay, no later than the 60th day after determining a breach occurred
Attorney general threshold
250 or more Texas residents (No later than the 30th day after determining a breach occurred)
Private right of action
Limited: Indirect recovery via the Deceptive Trade Practices Act (up to treble economic damages for knowing violations)
Penalty
$2,000-$50,000 per violation; additional up to $100 per individual per day, capped at $250,000 per breach

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

Texas filings closest in size

Neighbours by size rank among Texas filings in 2014, topped up from other years where 2014 has too few. Filings of 10,000 or more link to their own page.

Covered entityTypeIndividualsSubmitted
Xerox State Healthcare, LLCBusiness Associate2,000,00010 Sep 2014
St Joseph Health SystemHealthcare Provider405,0005 Feb 2014
Onsite Health Diagnostics (OHD)Business Associate60,5828 Aug 2014
Visionworks Inc.Health Plan47,68321 Nov 2014

Index / Companion schedules

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 5982.

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.