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.
What counts as a HIPAA violation in medical billing?
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.
Common HIPAA violations and how to prevent them
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.
2. Opening patient accounts without a work reason
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.
4. Sharing logins or leaving old access switched on
5. Moving PHI into unapproved email, storage, or AI tools
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.
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.
Owner: Security Lead
8. Skipping the security risk analysis, or not acting on it
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.
9. Training on HIPAA in general, but not on billing risks
10. Keeping quiet about a suspected exposure
What to do if a billing mistake exposes patient information
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.
A practical prevention checklist for billing managers
- Records only go to verified recipients, through approved methods.
- Access matches each person's role, and nobody shares a login.
- People who leave lose access to everything, payer portals included, on their last day.
- Any vendor handling PHI has signed a BAA before it gets a single record.
- Paper, screens, and old devices are handled and thrown out safely.
- If something goes to the wrong place, every person on the team knows who to call.
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.
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 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.




