Breach filing
ArchivedENT and Allergy Center: 16,200 individuals, May 2016.
ENT and Allergy Center reported a breach of unsecured protected health information to the HHS Office for Civil Rights on 31 May 2016. The filing records the organisation as a healthcare provider in Arkansas and lists 16,200 individuals affected, which makes it the 26th largest of the 92 Arkansas filings on the register and the 59th largest of the 328 filings submitted nationally in 2016. Among the 9 Arkansas filings made in 2016 it ranks 4th.
Individuals affected
16,200
As reported to HHS
Modelled cost (IBM 2025)
$2.59M
Method shown, not disclosed
Rank in AR
26th
of 92 Arkansas filings
Rank in 2016
59th
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
- 16,200
- Breach submission date
- 31 May 2016
- Submission year
- 2016
- Type of breach
- Hacking/IT Incident
- Location of breached information
- Network Server
- Business associate present
- No
- State
- Arkansas (AR)
- Portal status
- listed in the HHS OCR breach portal archive
- Rank in Arkansas by size
- 26th of 92
- Rank in 2016 nationally
- 59th of 328
- Arkansas median filing
- 4,800 individuals
- Register id (derived)
- AR-20160531-ent-and-allergy-center
Section F.2 / In context
Where this filing sits in Arkansas 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 50 of the 92 Arkansas filings (54%) and on 35% of all filings submitted in 2016. Network Server appears on 49% of Arkansas filings.
No business associate is recorded on the filing; 28% of Arkansas filings do involve one. At 16,200 individuals the breach is 3.4 times the Arkansas median filing of 4,800 and 4.0 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.
Arkansas's breach notification statute (Ark. Code Ann. 4-110-101 et seq.) requires notice to affected residents in the most expedient time and manner possible and without unreasonable delay. Its attorney general threshold: more than 1,000 Arkansas 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 16,200 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.59M; the 2026 edition's $192 gives $3.11M. Both are modelled estimates with the method shown, not costs disclosed by ENT and Allergy Center. 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.
One or more hackers attacked the data servers of Bizmatics, a business associate (BA) for the covered entity (CE), ENT & Allergy Center, which resulted in unauthorized access to Bizmatics' customer records including those of the CE. Approximately 16,200 patient's electronic medical records were compromised. The types of protected health information involved in the breach included demographic and clinical information. OCR opened an investigation of the CE to determine if the CE complied with the HIPAA Privacy and Security Rules with respect to business associate contracts. OCR reviewed the business associate agreement between the CE and BA and determined that it appears to be consistent with the requirements of the Privacy and Security Rules. OCR initiated a separate investigation of Bizmatics.
Section F.5 / Modelled cost
16,200 individuals through IBM's per-record figures
Modelled cost / method shown, not a disclosed cost
ModelledIBM 2025 customer PII, $160 per record
$2.59M
16,200 x $160
IBM 2026 customer PII, $192 per record
$3.11M
16,200 x $192
Method: individuals affected, as reported by ENT and Allergy Center 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
Arkansas statute and the HIPAA rule
State notification statute
Arkansas: Ark. Code Ann. 4-110-101 et seq.
Personal Information Protection Act
- Notice to individuals
- In the most expedient time and manner possible and without unreasonable delay
- Attorney general threshold
- More than 1,000 Arkansas residents (At the time of individual notice or within 45 days of a harm determination, whichever is first)
- Private right of action
- No: No express private right of action under PIPA
- Penalty
- Up to $10,000 per violation under the Deceptive Trade Practices Act; willful violations are a misdemeanor
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
Arkansas filings closest in size
Neighbours by size rank among Arkansas 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 |
|---|---|---|---|---|---|---|
| Pain Treatment Centers of America | Healthcare Provider | 19,397 | 11 Apr 2016 | |||
| Dr. Q Pain and Spine d/b/a Arkansas Spine and Pain | Healthcare Provider | 17,100 | 11 Jul 2016 | |||
| Walmart Stores, Inc. | Healthcare Provider | 4,800 | 1 Mar 2016 | |||
| Pulaski County Special School District-Employee Benefits Division | Health Plan | 2,602 | 12 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 5556.
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.