Premise Health Holding Corp., a Brentwood, Tennessee company that runs employer-sponsored healthcare for about 11 million members, has confirmed that one of its own employees misappropriated patient data over a period of months. The company says it fired the employee and reported the incident to law enforcement. State attorney general filings confirm close to 417,000 affected people in five states: 261,654 in Texas, 60,641 in South Carolina, 49,444 in Washington, 43,046 in Massachusetts and 1,948 in Vermont. Premise Health has not published a nationwide total. Several breach-tracking and legal sites put the overall figure at 2,760,238, citing state filings. Healthcare Info Security and HIPAA Journal both describe the confirmed numbers as partial and say the final count could reach into the millions.
What Happened
Premise Health posted a notice on its website and mailed letters dated November 6, 2026. In them, the company says that on September 18, 2026 it found an employee had "violated company information security policies and misappropriated certain company data" starting on or about March 26, 2026. The company says that once it found the activity, it revoked the employee's credentials and system access, checked its security controls and opened an investigation. It received a preliminary analysis of the affected data on October 14. After more work to validate that data, it confirmed which patients were affected and started notifying them by mail on November 6.
The company has drawn a firm line between this incident and an outside attack: "This was not a hacking or ransomware event. There has been no interruption to our operations and our sites remain fully available to serve patients."
Reporting differs on how long the activity lasted:
- The company's letter gives only a start date ("on or about March 26"). As WLTX notes, it does not say when the activity stopped.
- Dapeer Law says the Texas filing lists a breach window of March 26 to March 30, 2026. Almeida Law Group says the California filing also lists a second date of March 30. Both suggest the data was taken on more than one day.
- Paubox measures from the start date to discovery and calls it a 176-day gap. If the Texas dates are correct, the data was taken over about five days in late March and went unnoticed for nearly six months.
Both readings point to the same problem: the company only noticed the data theft about six months after it began.
Disclosure has grown in stages. HIPAA Journal first reported about 68,000 affected. Paubox counted 112,033 across the Washington, South Carolina and Vermont filings made on November 6. Once the Texas and Massachusetts figures were posted, the confirmed total rose to roughly 416,700. Premise Health has also notified California's attorney general, which does not publish counts. Claim Depot reports notifications to Rhode Island, and ClaimMoney lists Oregon among the states notified.
The company says it is not aware of any misuse of the data. WLTX reports that Premise has not said whether anyone has been charged. ClaimMoney reports that a proposed class action, Moore v. Premise Health Holding Corp., was filed on November 13, 2026 in the U.S. District Court for the Middle District of Tennessee. At least two other law firms say they are investigating.
What Was Taken
According to the company's notice, the data varies by person but may include:
- Names and postal addresses
- Dates of birth
- Government ID numbers, including Social Security numbers
- Health insurance information
- Diagnosis and treatment information
- Other information collected to check eligibility for services or about the patient's relationship with Premise Health
This combination is about as harmful as healthcare data gets. Social Security numbers paired with dates of birth make identity theft straightforward. Insurance details make medical identity fraud possible. Diagnosis and treatment records cannot be changed or reissued once they are out. WLTX reports that some letters are addressed to children, so dependents of covered employees are affected as well.
How many people are affected is still unresolved:
- About 417,000 across five states is the confirmed figure from state attorney general postings, as reported by Healthcare Info Security and HIPAA Journal.
- 2,760,238 is the total cited by Claim Depot, ClaimMoney and Dapeer Law. ClaimMoney attributes it to the Oregon and Texas listings, and Dapeer to the Texas attorney general. Neither the company nor the established security press has confirmed this figure. It also does not match the 261,654 Texas residents that Healthcare Info Security reports from the same Texas filing.
Until Premise Health or a federal filing with the HHS Office for Civil Rights gives a total, the honest range is somewhere between 417,000 and about 2.76 million people. Premise operates in 46 states and Guam, so even the higher number may not be final.
Premise Health is offering Experian IdentityWorks credit monitoring and identity restoration. Claim Depot reports this includes $1 million in identity theft insurance, plus Social Security number tracing for minors. The enrollment deadline is February 26, 2027.
Why It Matters
The size of the exposure follows from the business model. Premise runs more than 800 on-site and nearby clinics for employers, unions and health plans. Almeida Law Group says it serves over 2,500 client organizations and merged with Crossover Health in March 2026. That means one employee with broad access could reach patients belonging to many unrelated corporate clients. Each of those employers now has to deal with a breach of its own workforce's health data that it had no control over.
Insiders have legitimate access, so the usual alarms stay quiet. The company says the employee broke policy, not that they broke in. Defences designed to stop intruders, such as perimeter controls, MFA and ransomware detection, are not built to catch someone using their own valid login. The six-month gap before detection shows how long misuse of normal access can go unnoticed when nobody is watching volume and context.
"Not a hack" is not a reassurance. Premise's statement that this was not a hacking or ransomware event is accurate, and it does tell patients that clinics kept running. But this data is just as dangerous for patients as data stolen in an outside attack. In some ways it is worse: the company has not said why the employee took the data or where it went, and nobody has publicly explained what happened to it afterward.
The legal consequences are arriving fast. A federal class action was filed within a week of the first state notices. Several more firms are recruiting plaintiffs. The organisation will also face questions about the delay between discovering the theft in September and notifying patients in November, and about monitoring that missed the activity for months.
The Attack Technique
Premise Health has not said how the employee got the data or how it left its systems. Paubox makes the same point. Here is what is publicly known:
- Access vector: the employee's own legitimate credentials and system access. The company revoked these when it discovered the activity.
- Action: "misappropriated" company data, which HIPAA Journal describes as unauthorised copying.
- Timing: started on or about March 26, 2026. State filings, as reported by legal sites, point to activity continuing through at least March 30.
- Detection: September 18, 2026. The company has not said what triggered it, whether an internal alert, an audit or a tip.
- Motive and destination: not disclosed. Nobody has said whether the data was sold, shared, kept or taken to a competitor.
One detail is often misread. The employee was fired after the activity was discovered, not before. This was not a former employee whose access was left active. It was a current employee misusing access they had legitimately. Each case points to a different control failure. Here the failure is in monitoring, not in offboarding.
What Organizations Should Do
-
Watch for bulk access, not just failed logins. Set a baseline for how many patient records each role normally views or exports. Alert on large queries, report exports, bulk downloads and access to patients outside the user's own clinic or caseload. In this case, a few days of unusual activity went unnoticed for six months.
-
Give each role only the access it needs, and divide it by client. In a multi-tenant care model like Premise's, no single employee should be able to reach records across many client organisations unless that is truly part of the job. Review access regularly and remove permissions people have collected over time.
-
Block and monitor the routes data can leave by. Restrict USB storage, personal cloud sync, personal email and unapproved file transfer tools on endpoints that handle patient data. Use data loss prevention rules tuned to spot Social Security number and medical record patterns.
-
Review audit logs actively. HIPAA already requires audit controls. Assign someone to review patient-record access logs on a set schedule and investigate anything unusual. Logs nobody reads only help reconstruct the damage afterward.
-
Have an insider incident playbook before you need it. Agree in advance how HR, legal, security and compliance will work together on an insider case. That covers preserving evidence, revoking access and referring the case to law enforcement. Have a plan to work out who was affected quickly, so you can notify within regulatory deadlines.
-
Employers that use outsourced clinics should check their vendor's controls. Ask your workplace health provider how it monitors staff access to your employees' records, how quickly it detects bulk access, and what its contract requires it to tell you after a breach.
Sources: Premise Health Insider Breach Could Affect Millions | Insider Data Theft Incident Reported by Premise Health | Premise Health says former employee took data; state lists 60,641 S... | Premise Health Holding Data Breach Notice (2026): What to Do | Premise Health discloses insider breach affecting at least 112k | Premise Health Holding Corp. Data Breach Investigation Almeida Law... | Premise Health Data Breach Impacts 2.7M Individuals | Premise Health data breach: 2.76 million people (2026)