If the vendor that runs your charting or billing has been breached, your patients are still your patients. Ask your vendor how and when it will tell you about a breach, and confirm in writing who is responsible for notifying affected patients. For a medical practice, cybersecurity in that moment comes down to what you control this week: getting written answers from the vendor, reading the business associate agreement you already signed, and locking down your own staff logins and data exports.

Below is a working checklist, with a recent vendor breach as the live example. It is not legal advice; where the rules matter, read the source text or ask counsel.

What happened at CareCloud, and why the count grew tenfold

CareCloud is a publicly traded company that provides electronic health records, medical billing, practice management and revenue-cycle services. It serves more than 45,000 providers, and it handles patient data and billing information on behalf of hospitals, doctor's offices and other medical practices. That is the kind of vendor many small clinics rely on without giving it a second thought, because the records live "in the cloud" and somebody else runs the servers.

Here is the timeline, pieced together from press coverage and follow-up reporting:

That last figure is the headline. ITPro reports the victim count was revised from 350,000 to roughly 3.75 million, and SecurityWeek says the breach affects far more people than first believed. TechCrunch calls it the fifth-largest theft of health data in 2026 so far.

3,756,469
People affected by the breach
45,000+
Providers CareCloud serves
8 hours
Network disruption noted in the SEC filing

What was taken depends on who you read

Slow down here before writing to patients. BleepingComputer notes that, beyond full names, the sample letter shared with authorities does not specify the type of data exposed. Other outlets go further. Compare what different news reports and the company's own notices say was taken, because the lists of exposed data do not always match. TechCrunch lists names, postal addresses, Social Security numbers and medical and health information. SecurityWeek's list includes driver's license numbers, dates of birth and health insurance information.

One more open point: no hacking group took credit for the incident. The Record reports more than 270,000 affected people in Texas, 23,000 in South Carolina and nearly 58,000 in Oregon. So do not assume your patients are in or out of the count based on where you practice. Ask.

Heads up

Our advice: don't copy a news article's list of data types into a patient letter. Get the data elements for *your* patients, in writing, from the vendor. Different outlets list different things, and your notice has to be accurate for the people you are writing to.

Your vendor's breach is still your patients' problem

If your practice no longer runs a server closet, your charting, claims and statements go through a hosted vendor. That shifts where the data sits, not who your patients trust.

That relationship is the point of what follows. Before you let a vendor handle patient data, make sure you have a written agreement with it that requires it to safeguard that information. Those assurances have to be documented in a written contract or other written agreement that meets the requirements of ยง 164.504(e). Think of that contract as your business associate agreement; we'll call it the BAA from here on.

So the clinic chooses the vendor, gets the promises in writing, and answers to patients when those promises fail. Patients don't call the vendor. They call your front desk.

The two clocks you need to know

There are two notification clocks, and they run in sequence:

  1. The vendor's clock. A business associate must notify the covered entity without unreasonable delay and in no case later than 60 calendar days after discovering a breach. A breach counts as discovered on the first day the business associate knows of it, or would have known by exercising reasonable diligence.
  2. Your clock. The notice must be written in plain language.

Then there is one more notice to think about. For smaller breaches, you keep a log and report to HHS no later than 60 days after the end of each calendar year.

California adds its own layer. Any person or business required to send a security breach notification to more than 500 California residents from a single breach must electronically submit a sample copy of that notice, without personal information, to the California Attorney General.

Tip

In a large vendor breach, settle early who actually mails the letters, you or the vendor. Our advice: don't assume. Get a written answer on whether the vendor is notifying your patients and the regulators on your behalf, and keep a copy in your compliance file.

Questions to ask your EHR and billing vendor this week

Send these by email to your account manager and the security or privacy contact in your contract. You'll want the paper trail.

About the incident

About notification

About the future

Hypothetical: a four-provider family practice in Tustin emails these questions on a Monday. By Friday the vendor confirms the practice's data was in scope, sends a patient count and a list of data elements, and says it will mail the letters. The office manager files the reply, updates the risk assessment, and briefs the front desk on what to say when patients call.

BAAs, cyber insurance and who notifies whom

Pull your BAA from the drawer or the vendor portal where you clicked "accept," and look for these clauses:

Clause to findWhat you're looking forWhy it matters now
Breach reportingHow fast the vendor must tell you, and what details it must includeA business associate has at most 60 calendar days; your contract may be shorter
Security incidentsDoes it make the vendor report every security incident, or only confirmed breaches?Review your business associate agreement to confirm it requires the vendor to tell you about security incidents and breaches of unsecured protected health information.
Notification dutiesWho mails the letters, who pays, and who handles the official filingsFollowing discovery of a breach of unsecured protected health information, a covered entity must notify each affected individual.
SubcontractorsWhether your vendor's own subcontractors are bound by the same termsCheck that your business associate agreement also covers any subcontractors that handle ePHI.
Cost allocationWho pays for mailing, call centers, credit monitoringOur view: this is where the money fights happen
Termination and return of dataHow you get your records back if you leaveLeverage if you decide the relationship is over

Cyber insurance

Call your broker or carrier before you spend money responding. Our advice, not a guarantee of coverage: ask whether your policy covers notification costs, legal counsel, forensics and regulatory defense when the breach happened at a vendor, not on your own network. Ask whether you must use the carrier's panel lawyers, and get the answers in writing.

Talk to a healthcare privacy attorney

Your state may add its own privacy rules, and we are not lawyers. If your patients were affected, a short call with a healthcare privacy attorney costs less than sending the wrong letter.

Locking down your own end: logins, MFA, exports

The vendor's fix is the vendor's job. Your logins, devices and exports are yours, and a well-publicized breach is a gift to phishers: emails "from your vendor" asking staff to reset passwords, or calls "from the billing company" asking patients to confirm personal details.

Framing what follows as compliance, not extras, is a useful way to explain the spend to a partner who doesn't want to hear about it:

Exports are the leak nobody watches

Patient lists end up in places nobody tracks: a biller's export file, a spreadsheet emailed to a contractor, a report on a personal laptop. Those copies are entirely your responsibility. Our checklist for this week:

  1. List every person who can run exports or reports in the EHR and billing systems.
  2. Remove export rights from anyone who doesn't need them.
  3. Search shared drives and email for patient spreadsheets, then delete or lock down what you find.
  4. Turn off any old integrations or access keys you no longer use, and rotate the rest.

What we'd do in your first two weeks

If an Orange County practice called us the week a vendor breach hit the news, this is the order we'd suggest:

  1. Right away: send the vendor questions above in writing; pull the BAA and insurance policy; call your broker.
  2. Later that week: turn on multi-factor sign-in everywhere it's available; kill shared accounts; cut export rights; brief staff on vendor-impersonation phishing.
  3. The following week: review the vendor's answers with counsel; decide who notifies whom; update your risk assessment and keep everything in one compliance folder.
  4. After: decide whether the vendor relationship and the BAA terms are still acceptable, and put a calendar reminder to re-review both on a regular schedule.

Some of this can be automated safely: a deadline tracker for vendor requests, a report of who can export what, or an alert for after-hours logins. We build that through our AI automation work, and we'll say so when a spreadsheet is enough.

If you'd rather talk it through first, book a consultation for clinics and small practices: we map your vendors, logins and data flows and give you a prioritized list. You can see how we work with local practices on our Orange County page.

Next step

Open your inbox and send your EHR and billing vendors the questions in this post today. Then turn on multi-factor sign-in for the accounts that would hurt most if someone else logged in.

If you want a second set of eyes on your vendor list, BAA terms and staff access, book a Free Automation Audit. We'll show you where your patient data actually lives, who can get to it, and what we'd fix first.

Sources