Breach filing
ArchivedFrancisco Jaume, D.O.: 14,236 individuals, Oct 2016.
Francisco Jaume, D.O. reported a breach of unsecured protected health information to the HHS Office for Civil Rights on 4 October 2016. The filing records the organisation as a healthcare provider in Arizona and lists 14,236 individuals affected, which makes it the 42nd largest of the 164 Arizona filings on the register and the 66th largest of the 328 filings submitted nationally in 2016. Among the 9 Arizona filings made in 2016 it ranks 3rd.
Individuals affected
14,236
As reported to HHS
Modelled cost (IBM 2025)
$2.28M
Method shown, not disclosed
Rank in AZ
42nd
of 164 Arizona filings
Rank in 2016
66th
of 328 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
- Healthcare Provider
- Individuals affected
- 14,236
- Breach submission date
- 4 October 2016
- Submission year
- 2016
- Type of breach
- Hacking/IT Incident
- Location of breached information
- Network Server
- Business associate present
- No
- State
- Arizona (AZ)
- Portal status
- listed in the HHS OCR breach portal archive
- Rank in Arizona by size
- 42nd of 164
- Rank in 2016 nationally
- 66th of 328
- Arizona median filing
- 3,146 individuals
- Register id (derived)
- AZ-20161004-francisco-jaume-do
Section F.2 / In context
Where this filing sits in Arizona and in 2016
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 94 of the 164 Arizona filings (57%) and on 35% of all filings submitted in 2016. Network Server appears on 43% of Arizona filings.
No business associate is recorded on the filing; 21% of Arizona filings do involve one. At 14,236 individuals the breach is 4.5 times the Arizona median filing of 3,146 and 3.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.
Arizona's breach notification statute (A.R.S. 18-551, 18-552) requires notice to affected residents within 45 days after determining a breach occurred. Its attorney general threshold: more than 1,000 Arizona residents (AG and Dept. of Homeland Security). 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 14,236 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.28M; the 2026 edition's $192 gives $2.73M. Both are modelled estimates with the method shown, not costs disclosed by Francisco Jaume, D.O.. For scale, IBM's 2026 average cost of a healthcare breach is $6.64M, so this filing models at 0.4 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.
Francisco Jaume, D.O. the covered entity (CE), reported a breach of 14,246 patients' protected health information (PHI) when it suffered a ransomware (malware) attack starting on August 22, 2016. The types of PHI involved included patients' names, addresses, medical information, and social security numbers. The CE provided breach notification to affected individuals, the media, and HHS. Immediately after discovering the breach, the CE worked to regain control of its data and investigated the incident using forensic analysis. As a result of the incident and OCR's investigation, the CE implemented additional safeguards, such as regular remote monitoring and monthly reporting of intrusion activity, anti-virus management, changed/strengthened system passwords, and revised backup processes. In addition, the CE trained staff and revised its HIPAA policies and procedures. OCR obtained assurances that the CE implemented the corrective actions above.
Section F.5 / Modelled cost
14,236 individuals through IBM's per-record figures
Modelled cost / method shown, not a disclosed cost
ModelledIBM 2025 customer PII, $160 per record
$2.28M
14,236 x $160
IBM 2026 customer PII, $192 per record
$2.73M
14,236 x $192
Method: individuals affected, as reported by Francisco Jaume, D.O. 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
Arizona statute and the HIPAA rule
State notification statute
Arizona: A.R.S. 18-551, 18-552
- Notice to individuals
- Within 45 days after determining a breach occurred
- Attorney general threshold
- More than 1,000 Arizona residents (AG and Dept. of Homeland Security) (Within the same 45-day window)
- Private right of action
- No: Only the Arizona Attorney General may enforce
- Penalty
- Up to $10,000 per affected individual, capped at $500,000 per breach, under the Consumer Fraud Act
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
Arizona filings closest in size
Neighbours by size rank among Arizona filings in 2016, topped up from other years where 2016 has too few. Filings of 10,000 or more link to their own page.
| Covered entity | Type | Individuals | Submitted | Breach type | Location | BA |
|---|---|---|---|---|---|---|
| Banner Health | Healthcare Provider | 3,620,000 | 3 Aug 2016 | |||
| Valley Anesthesiology Consultants, Inc. d/b/a Valley Anesthesiology and Pain Consultants | Healthcare Provider | 882,590 | 12 Aug 2016 | |||
| MGA Home Healthcare Colorado, Inc. | Healthcare Provider | 3,119 | 19 Oct 2016 | |||
| Emergency Room Associates doing business as Emergency Medicine Associates | Healthcare Provider | 1,067 | 19 May 2016 |
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 5447.
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.