Breach filing
ArchivedMedEvolve: 205,434 individuals, Jul 2018.
MedEvolve reported a breach of unsecured protected health information to the HHS Office for Civil Rights on 10 July 2018. The filing records the organisation as a business associate in Arkansas and lists 205,434 individuals affected, which makes it the 4th largest of the 92 Arkansas filings on the register and the 17th largest of the 369 filings submitted nationally in 2018. Among the 5 Arkansas filings made in 2018 it ranks 1st.
Individuals affected
205,434
As reported to HHS
Modelled cost (IBM 2025)
$32.9M
Upper bound, method shown
Rank in AR
4th
of 92 Arkansas filings
Rank in 2018
17th
of 369 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
- 205,434
- Breach submission date
- 10 July 2018
- Submission year
- 2018
- Type of breach
- Unauthorized Access/Disclosure
- Location of breached information
- Network Server
- Business associate present
- Yes
- State
- Arkansas (AR)
- Portal status
- listed in the HHS OCR breach portal archive
- Rank in Arkansas by size
- 4th of 92
- Rank in 2018 nationally
- 17th of 369
- Arkansas median filing
- 4,800 individuals
- Register id (derived)
- AR-20180710-medevolve
Section F.2 / In context
Where this filing sits in Arkansas and in 2018
OCR classifies the incident as unauthorized access or disclosure, with the breached information held in a network server. Unauthorized Access/Disclosure is the type recorded on 28 of the 92 Arkansas filings (30%) and on 38% of all filings submitted in 2018. Network Server appears on 49% of Arkansas filings.
A business associate is recorded as present on the filing, as it is on 28% of Arkansas filings. At 205,434 individuals the breach is 43 times the Arkansas median filing of 4,800 and 51 times the national median of 4,000 across all 7,884 filings. It is one of 801 filings of 100,000 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.
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 205,434 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 $32.9M; the 2026 edition's $192 gives $39.4M. Both are modelled estimates with the method shown, not costs disclosed by MedEvolve. 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.
Today, the U.S. Department of Health and Human Services' Office for Civil Rights (OCR) announced a settlement with MedEvolve, Inc. ("MedEvolve"), a business associate that provides practice management, revenue cycle management, and practice analytics software services to health care entities. The settlement was signed to resolve a data breach resulting from the misconfiguration of a File Transfer Protocol ("FTP") server that caused the protected health information of 230,572 individuals to be unsecure and accessible on the internet. The potential violations of the Health Insurance Portability and Accountability Act (HIPAA) include the lack of an analysis to determine risks and vulnerabilities to electronic protected health information across the organization, and the failure to enter into a Business Associate Agreement with a subcontractor. As a result MedEvolve paid $350,000 to OCR and agreed to implement a corrective action plan, which identifies steps MedEvolve will take to resolve these potential violations and protect the security of electronic patient health information.
"Ensuring that security measures are in place to protect electronic protected health information where it is stored is an integral part of cybersecurity and the protection of patient privacy," said OCR Director Melanie Fontes Rainer. "HIPAA-regulated entities must ensure that they are not leaving patient health information unsecured on network servers available to the public via the internet."
In July 2018, OCR initiated an investigation of MedEvolve following the receipt of a breach notification report stating that a FTP server containing electronic protected health information was openly accessible to the internet. The information included patient names, billing addresses, telephone numbers, primary health insurer and doctor's office account numbers, and in some cases Social Security numbers.
In addition to the monetary settlement, MedEvolve will undertake a comprehensive corrective action plan that will be monitored for two years by OCR to ensure compliance with the HIPAA Security Rule. MedEvolve has agreed to take the following steps:
• Conduct an accurate and thorough risk analysis to determine risks and vulnerabilities to electronic patient/system data across the organization
• Develop and implement a risk management plan to address and mitigate identified security risks and vulnerabilities identified in the risk analysis
• Develop, maintain, and revise, as necessary, its written policies and procedures to comply with the HIPAA Privacy and Security Rules,
• Augment its existing HIPAA and Security Training Program for all MedEvolve workforce members who have access to protected health information, and
• Report to HHS within sixty (60) days when workforce members fail to comply with MedEvolve's written policies and procedures to comply with the HIPAA Privacy and Security Rules.
Section F.5 / Modelled cost
205,434 individuals through IBM's per-record figures
Modelled cost / method shown, not a disclosed cost
Upper boundIBM 2025 customer PII, $160 per record
$32.9M
205,434 x $160
IBM 2026 customer PII, $192 per record
$39.4M
205,434 x $192
Method: individuals affected, as reported by MedEvolve 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 2018, topped up from other years where 2018 has too few. Filings of 10,000 or more link to their own page.
| Covered entity | Type | Individuals | Submitted | Breach type | Location | BA |
|---|---|---|---|---|---|---|
| ARcare | Healthcare Provider | 345,353 | 25 Apr 2022 | |||
| EngageMED, Inc | Business Associate | 249,297 | 30 Aug 2024 | |||
| Arkansas Oral & Facial Surgery Center | Healthcare Provider | 128,000 | 24 Sep 2017 | |||
| Arkansas Children's Hospital | Healthcare Provider | 4,521 | 29 Jun 2018 | |||
| Baptist Health | Healthcare Provider | 3,453 | 7 May 2018 |
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 4802.
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.