Common HIPAA Violations in Medical Billing and How to Prevent Them

Common HIPAA Violations in Medical Billing and How to Prevent Them
November 16, 2026

Dana has been chipping away at denials all afternoon, and it’s 4:50 on a Friday. She attaches three pages of visit notes to an appeal, types the payer rep’s email from memory, and hits send. That rep stopped using the address two years ago. Where the records ended up is anyone’s guess.

She was not careless in any dramatic way, and that’s the point. Most common HIPAA violations in medical billing don’t come from bad actors. They come from busy people doing routine work quickly. Below are ten mistakes that keep turning up in billing offices, each with a practical fix and a named owner. (Dana, like every example here, is made up. The patterns aren’t.)

What counts as a HIPAA violation in medical billing?

PHI, short for protected health information, is anything that ties a patient to their health, their care, or what they paid for it. That covers a lot more than charts. A claim counts. So does a patient statement, or an A/R report listing names next to balances. In billing, HIPAA problems tend to come in two flavors. There’s the obvious kind, where PHI ends up with someone who had no business seeing it. Then there’s the quieter kind, like a practice that never did a security risk analysis or a team of five sharing one login. Nothing has to leak for that second kind to count as a violation.

People also use three words as if they meant the same thing, and they do not. A violation means a HIPAA requirement wasn’t followed. A security incident is an attempted or successful unauthorized access, use, or change of information, or interference with a system. A reportable breach is narrower: it’s a conclusion reached after an assessment, and it’s the one that triggers notices. One bad afternoon can involve all three, or only one.
None of this makes billing itself risky territory. The HHS Privacy Rule generally lets practices use and share PHI for payment without asking the patient for a separate authorization. What it doesn’t do is give billing staff a free pass to open or send whatever they like. Our guide to HIPAA compliance in medical billing covers the bigger picture.

1. Violation

2. Security Incident

3. Reportable Breach

People also use three words as if they meant the same thing, and they do not. A violation means a HIPAA requirement wasn’t followed. A security incident is an attempted or successful unauthorized access, use, or change of information, or interference with a system. A reportable breach is narrower: it’s a conclusion reached after an assessment, and it’s the one that triggers notices. One bad afternoon can involve all three, or only one.

None of this makes billing itself risky territory. The HHS Privacy Rule generally lets practices use and share PHI for payment without asking the patient for a separate authorization. What it doesn’t do is give billing staff a free pass to open or send whatever they like. Our guide to HIPAA compliance in medical billing covers the bigger picture.

Common HIPAA violations and how to prevent them

These aren’t ranked by how often they happen. They roughly follow the path a claim takes through your office, from the first handoff to the last.
1. Priority: Critical Disclosure Risk
2. Owner: Billing Supervisor

1. Sending billing information to the wrong recipient

Dana’s appeal is the textbook case, but misdirected PHI turns up in plenty of other ways. A fax goes to a number that’s one digit off. A statement lands at an address the patient moved out of last spring. An attachment meant for one payer ends up with another.

What prevents it is pretty boring. Before anything goes out, whoever is sending it checks the recipient against a current record (not memory, not autofill) and makes sure the patient name, account number, and attachment all belong together. For mailed statements, add one more step and confirm there’s no request on file to send mail somewhere else. Setting up that check, and spot-reviewing it now and then, is a job for the billing supervisor.
Priority: High Privacy Violation
Owner: Practice Manager & System Admin

2. Opening patient accounts without a work reason

Kevin works on the billing team. One morning he spots his neighbor’s name on the appointment list, and curiosity wins, so he opens the account to see what she came in for. He never mentions it to anyone. He still looked at PHI for no work reason, and that’s the violation.
Two things make this kind of snooping a lot less likely. Permissions should follow the job, so a payment poster can’t wander into charts they’ll never need. Someone should also look through access logs from time to time, watching for things like staff opening coworkers’ or relatives’ accounts. Just telling the team those reviews happen does half the work.
The practice manager should own this, with help from whoever runs the billing system.
Priority: Minimum Necessary Rule
Owner: Privacy Lead & Billing Manager

3. Sharing more information than the task requires

A plan rep calls about one $180 balance and asks for documentation. Exporting the whole chart is quicker than picking out the two pages that matter, so that’s what gets sent. Under the HHS minimum necessary requirement, that’s usually too much. Payment disclosures, like most others, should be limited to what the task reasonably needs. The rule does have exceptions. Disclosures to the patient are exempt, as is anything the law requires, and so is the data a standard transaction like a claim has to carry. People sometimes stretch the treatment exception, which covers sharing with another provider to treat the patient, over billing work too. It does not reach that far. An appeal is a payment activity, so the minimum necessary still applies.

Most of the fix is one habit: read what the request actually asks for, then send that and nothing extra. Put it in your policy, and have the privacy lead and billing manager make sure it sticks.
Priority: Critical Access Control
Owner: IT & Offboarding Lead

4. Sharing logins or leaving old access switched on

Separate accounts seemed like a pain to set up. Five billers, one login. Then you export a massive patient report to a device that nobody knows and the manager questions who did it. Nor can anybody else, nor can the system tell.
For this precise reason the Security Rule requires that each user have a unique ID. Set up individual accounts for each user and review the access list every few months. When an employee departs, access should be cut off on their final day as part of the offboarding procedure. Also check the logins people forget, such as the payer portals and the clearinghouse. Those are the ones still working six months down the road.”
Priority: Critical Shadow IT & AI Risk
Owner: Privacy & Security Leads

5. Moving PHI into unapproved email, storage, or AI tools

A biller has a denial letter that needs a stronger appeal. She pastes the whole thing, patient name and all, into a free AI chatbot and asks it to rewrite her response. Nobody at the practice has reviewed that tool, there’s no business associate agreement, and no one knows what happens to what she pasted.
Email and AI tools are not banned under HIPAA. The problem here is the unapproved tool. Before patient information goes into any email platform, cloud drive, or AI service, someone needs to check what it keeps, who can get to it, whether the company uses the data for itself, and whether a BAA is needed. Keep a short approved list so nobody has to guess. For practice drafts, fake patient details work just as well.
That approved list belongs to the privacy and security leads.
Priority: High Vendor Compliance
Owner: Named Contracting Lead

6. Giving a billing vendor PHI without a BAA

Per HHS business associates advice, a firm that handles PHI to conduct billing, collections or claims work for you is typically a business partner. You have to sign a business associate agreement (BAA) before releasing any PHI, and the vendor has to have BAAs with its own subcontractors that have access to your data. But a signed BAA is merely the start. It won’t tell you how the vendor genuinely manages access, file transfers, or issues, so ask. Ideally this belongs to one named contracting lead, not whoever happens to have a free afternoon.

Priority: Physical & Workstation Security
Owner: Office Manager

7. Leaving paper records or screens exposed

Not everything comes down to screens and servers. Printed statements can sit on the shared printer by the waiting room for an hour. A remote biller can get up for coffee with a patient account open on the laptop while the kids wander past.

The HHS Security Rule outlines physical precautions for workstations and devices that contain e-PHI, while the Privacy Rule also requires reasonable safeguards for paper. That involves capturing print jobs immediately away (or secure print release), locking paper up at night, putting screens to lock after a few idle minutes, shredding instead of trashing, and cleaning old devices correctly before they leave the office, day to day. The office manager is usually best placed to own it.

Priority: High Audit & Governance Risk

Owner: Security Lead

8. Skipping the security risk analysis, or not acting on it

A practice does its security risk analysis and covers the EHR carefully. Nobody brings up the billing reports staff downloads to their laptops every Monday, so those files never make it into the analysis, and nothing protects them.

The Security Rule requires an accurate and thorough risk analysis of all the electronic PHI (ePHI) you create, receive, maintain, or transmit, along with action to reduce whatever it finds. An analysis that lists problems and then sits in a folder isn’t doing its job. It also isn’t the same as a billing audit. A billing audit asks whether coding and payments are right, while a security risk analysis asks how patient data could leak, get changed, or disappear. HHS has proposed changes to the Security Rule, but for now the current rule is the one in force. Running the analysis and following up on it falls to the security lead.

Priority: Staff Readiness & Training
Owner: Training Lead & Privacy Lead

9. Training on HIPAA in general, but not on billing risks

Everyone on the billing team passed the yearly HIPAA course. A month later they’re dropping screenshots of patient accounts into a group chat to sort out claim errors faster, and nobody sees a problem, because the course never mentioned anything like it.
HIPAA does require training, but there’s no single annual deadline that covers everyone. The Privacy Rule says new staff should be trained within a reasonable time of starting, and anyone whose job changes because of a new policy should be trained on that change. Training lands better when it’s about the work billers actually do, like sending appeals, taking patient calls, and exporting reports. Use your own close calls, too. Five minutes on last month’s misdirected statement will stick longer than an hour of slides. Put the training lead and privacy lead in charge of keeping it current.
Priority: Critical Incident Escalation
Owner: Designated Incident Response Lead

10. Keeping quiet about a suspected exposure

A biller realizes she just emailed an account report to the wrong person. She deletes it from her sent folder, breathes out, and doesn’t tell anyone. The report is still sitting in the other person’s inbox.
Deleting your copy doesn’t take back the disclosure, and staying quiet means nobody gets the chance to contain it. Reporting has to feel easy and normal. Staff should know exactly who to tell, and that an honest mistake reported right away won’t get them in trouble. From there, that person works on containment, saves the evidence, and documents an assessment.
That person is the designated incident response lead, and everyone on the team should know their name.
First Hour Protocol
Immediate Containment Workflow

What to do if a billing mistake exposes patient information

Mistakes happen. When one does, the first hour counts for more than getting every detail right.

Stop it from spreading

Don't forward the message to anyone "just to check," and if the same slip could happen on the next claim, pause that workflow.

Call the designated privacy or security contact

Do it right away, before trying to investigate on your own.

Hang on to the records

The sent email, the fax confirmation, the timestamps: leave them where they are, because someone will need them later.

Help contain it

Often that means asking whoever received the information to send it back or destroy it, and getting them to confirm in writing that they did.

Here’s the part that surprises people. Under the HHS Breach Notification Rule, HIPAA starts from the assumption that an impermissible use or disclosure is a breach. To conclude otherwise, an exception has to apply, or someone has to document a risk assessment showing a low probability that the information was compromised. That assessment looks at what the information was, who ended up with it, whether they actually opened or took it, and how well the risk was brought down afterward. None of that is the biller’s call, and she shouldn’t be left to make it alone. Your privacy and security team decides. They’ll also know that patients, HHS, and sometimes the media each have their own notice timelines. The 60-day limit for patient notices is a ceiling, and reading it as a waiting period is a common mistake.

Interactive Audit Tool
0 of 6 verified

A practical prevention checklist for billing managers

We’d start any workflow review with these six checks. They’re not a full compliance audit, just the handoffs where trouble usually begins.

Strengthen privacy in your billing workflow

Here’s some homework. This week, choose one process – appeals, patient statements or claim corrections – and track one patient’s information through that workflow from the time it comes into your office until the time it goes out. At each handoff, ask who checks on the receiver, who can see it, and who hears about it if anything goes wrong. The weak points come out quickly. If you’d rather have a second set of eyes on it, talk to Swift Billing Solutions. We handle billing for independent practices for a flat 3% of collections, and there are no setup fees or long-term contracts to sign. This is general information, not legal advice. Have a qualified compliance professional review your own policies.

Swift Billing Solutions
If you’d rather have a second set of eyes on it, talk to Swift Billing Solutions. We handle billing for independent practices for a flat 3% of collections, and there are no setup fees or long-term contracts to sign.
Flat 3% of collections • $0 setup fee • No long-term contracts
This is general information, not legal advice. Have a qualified compliance professional review your own policies.

Frequently asked questions

Usually, yes. A bill shows who was seen and what they owe, so a stranger reading it has seen PHI. Whether it counts as a reportable breach is a separate question. An envelope that comes back sealed is a very different situation from a neighbor who opened it and read the charges. Report it either way and let your privacy lead you to sort it out.

They can. HIPAA doesn't ban email, it asks for reasonable safeguards, and HHS even allows unencrypted email to a patient who asks for it after being warned about the risks. Emails to payers and vendors are a different story. Those should go through whatever secure method your practice has approved, and your risk analysis is what should decide which methods make that list.

Almost always. If the company sees patient information to do your billing, it's a business associate, and the BAA should be signed before the first file goes over. The rare exception is a vendor whose work never involves PHI at all.

No, HIPAA has a few restricted exclusions. There is the case of an employee who, in good faith and in the course of their duties, opens something they should not have opened, provided it doesn't go any further. One is information sent to someone who could not reasonably have kept it, such as a letter returned unopened. Except for certain restrictions, any information is deemed a breach unless there is a recorded determination that the information was not compromised with a low likelihood.

Swift Billing Solutions

Swift Billing Solutions Team

Our team shares practical guidance on medical billing, coding, denial management, and revenue cycle operations. We write for physicians and practice managers who want to understand billing challenges, reduce avoidable errors, and keep payments moving.

Our claim acceptance rate is
0 %

Sales

+1 (512) 678-3078

Email

info@swiftbillingsolutions.com

Office

5900 Balcones Drive STE 100 Austin, TX 78731-4298, USA

Toll Free

+1 (888) 315-0532

Swiftie

Swift Billing Solutions
Hello! I am Swiftie, your AI assistant for Swift Billing Solutions. How can I assist you with your practice's RCM, Medical Billing, or Coding today?

Get in Touch with an RCM Specialist

Fill out the form below to get in touch.

Start the Conversation

Let’s Talk About Your Practice