Breach filing
ArchivedGlobal Care Delivery, Inc.: 18,213 individuals, Jun 2015.
Global Care Delivery, Inc. reported a breach of unsecured protected health information to the HHS Office for Civil Rights on 12 June 2015. The filing records the organisation as a business associate in Texas and lists 18,213 individuals affected, which makes it the 178th largest of the 633 Texas filings on the register and the 32nd largest of the 270 filings submitted nationally in 2015. Among the 24 Texas filings made in 2015 it ranks 3rd.
Individuals affected
18,213
As reported to HHS
Modelled cost (IBM 2025)
$2.91M
Method shown, not disclosed
Rank in TX
178th
of 633 Texas filings
Rank in 2015
32nd
of 270 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
- 18,213
- Breach submission date
- 12 June 2015
- Submission year
- 2015
- Type of breach
- Theft
- Location of breached information
- Laptop
- Business associate present
- Yes
- State
- Texas (TX)
- Portal status
- listed in the HHS OCR breach portal archive
- Rank in Texas by size
- 178th of 633
- Rank in 2015 nationally
- 32nd of 270
- Texas median filing
- 4,055 individuals
- Register id (derived)
- TX-20150612-global-care-delivery
Section F.2 / In context
Where this filing sits in Texas and in 2015
OCR classifies the incident as theft, with the breached information held in a laptop. Theft is the type recorded on 90 of the 633 Texas filings (14%) and on 30% of all filings submitted in 2015. Laptop appears on 8% of Texas filings.
A business associate is recorded as present on the filing, as it is on 27% of Texas filings. At 18,213 individuals the breach is 4.5 times the Texas median filing of 4,055 and 4.6 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 18,213 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 $2.91M; the 2026 edition's $192 gives $3.50M. Both are modelled estimates with the method shown, not costs disclosed by Global Care Delivery, Inc.. For scale, IBM's 2026 average cost of a healthcare breach is $6.64M, so this filing models at 0.5 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.
Five password-protected, but unencrypted laptop computers were stolen from Global Care Delivery, a business associate (BA) of the covered entity (CE), North Shore LIJ Health System in September 2014. The laptops contained the protected health information (PHI) of 18,213 individuals, including names, dates of birth, insurance identification numbers (which contained social security numbers), and diagnoses and/or treatment codes related to claims. The BA notified police at the time of the incident, but did not notify the CE until May 11, 2015. The BA retained Knoll, Inc. to assist with individual notification and provide call center services to answer questions from individuals impacted by the breach. Breach notification was provided to HHS and affected individuals, and the BA offered complimentary one-year identity theft protection services. The business relationship between the CE and BA ended effective May 11, 2015. The BA has closed its business.
Section F.5 / Modelled cost
18,213 individuals through IBM's per-record figures
Modelled cost / method shown, not a disclosed cost
ModelledIBM 2025 customer PII, $160 per record
$2.91M
18,213 x $160
IBM 2026 customer PII, $192 per record
$3.50M
18,213 x $192
Method: individuals affected, as reported by Global Care Delivery, 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 2015, topped up from other years where 2015 has too few. Filings of 10,000 or more link to their own page.
| Covered entity | Type | Individuals | Submitted | Breach type | Location | BA |
|---|---|---|---|---|---|---|
| AT&T Group Health Plan | Health Plan | 50,000 | 23 Mar 2015 | |||
| Seton Family of Hospitals | Healthcare Provider | 39,000 | 24 Apr 2015 | |||
| Children's Medical Clinics of East Texas | Healthcare Provider | 16,000 | 28 Oct 2015 | |||
| Emergence Health Network | Healthcare Provider | 11,100 | 16 Oct 2015 |
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 5817.
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.