Key takeaways
- HIPAA requires you to have and apply appropriate sanctions against workforce members who break privacy or security policies, and to document the sanctions applied.
- Tie the response to culpability: honest mistakes, carelessness, deliberate snooping and misuse for gain deserve very different outcomes.
- Sanctions must never be used to retaliate against people who file complaints or make protected whistleblower disclosures.
- Consistent, documented decisions protect the practice and keep staff willing to report their own mistakes.
What the rules require
HIPAA asks for sanctions in two places. The Privacy Rule says a practice must have and apply appropriate sanctions against members of its workforce who fail to comply with its privacy policies or the rule itself, and must document the sanctions that are applied, if any[1]. The Security Rule includes a required sanction policy for workforce members who fail to comply with security policies and procedures[2].
Neither rule lists specific penalties. That is deliberate: what is appropriate in a six-person dental office differs from a large group. What the rules do insist on is that a policy exists, that it is actually used, and that you can show how it was used. A sanctions section that nobody has ever applied, despite known incidents, is a finding waiting to happen.
The practice's own exposure is the reason this matters. Federal civil money penalties are tiered by culpability, from a did-not-know tier with a low per-violation minimum to willful neglect left uncorrected[3]. A practice that ignores repeated staff violations it knows about is moving itself up those tiers.
$73,011
Minimum civil money penalty per violation when willful neglect is not corrected, after inflation adjustment[3]
Match the response to the behavior
The fairest policies sort incidents by intent and care, not by outcome alone. A receptionist who hands over the wrong after-visit summary on a chaotic Monday and reports it at once made a different choice from a colleague who browses a neighbor's chart out of curiosity, even if the second incident exposed less information.
| Level | What it looks like | Typical response |
|---|---|---|
| 1. Unintentional error | Misdirected fax, wrong patient's paper, an unlocked screen, promptly reported | Coaching conversation, retraining on the step that failed, note on file |
| 2. Careless or repeated error | Ignoring a known procedure, a second similar slip, leaving detailed voicemails after being told not to | Written warning, targeted retraining, closer supervision for a period |
| 3. Deliberate policy violation | Looking at records without a work reason, sharing a password, posting about a patient | Final written warning, suspension or termination depending on facts |
| 4. Malicious or for personal gain | Selling or stealing information, using it to harass someone, concealing a breach | Termination, and referral to law enforcement or licensing boards where appropriate |
Write the levels into the policy with examples, as above, so staff know in advance what to expect. Leave room for judgment: the framework guides the decision, it does not make it automatically.
Factors to weigh in every case
- Intent: was it a mistake, carelessness or a deliberate choice?
- Reporting: did the person report it themselves, promptly and honestly, or was it discovered by others or concealed?
- Training: had they been trained on the procedure that was broken, and when?
- History: is this a first incident or part of a pattern?
- Harm: how sensitive was the information, how many people were affected, and was it recovered?
- Circumstances: was the person covering two roles, working without the usual tools, or following a manager's instruction?
- Consistency: what did the practice do the last time a similar incident happened?
The self-reporting factor deserves special weight. If staff learn that owning up leads to the same outcome as being caught, they stop owning up. Many practices write into the policy that a prompt, honest self-report of an unintentional error will normally be handled with coaching, not discipline.
What a sanctions policy must never do
HIPAA forbids practices from intimidating, threatening, coercing, discriminating against or taking other retaliatory action against people who exercise their rights under the rule or file complaints[1]. A sanction that punishes someone for raising a privacy concern internally, or for complaining to HHS, would itself be a violation.
The rule also protects certain whistleblower disclosures. A workforce member who believes in good faith that the practice is acting unlawfully may disclose patient information to a health oversight agency or public health authority authorized to investigate, or to an attorney they have retained[4]. Your policy should say so plainly, so that a manager does not mistake a protected disclosure for a breach to be punished.
A five-step process
Receive the report
Any staff member can report to the privacy officer or practice manager. Record the date, the reporter and what was reported.
Investigate promptly
Gather the facts: audit logs, documents, a short interview with the person involved. Separate the breach assessment from the sanctions decision.
Decide with the framework
Use the levels and factors above. Where possible, involve a second manager so the decision is not one person's reaction.
Tell the person and document it
Explain the outcome and the reason, and what will change. Record the sanction in writing, as the rule requires.
Fix the process
Ask whether a system or workflow change would prevent a repeat, such as a fax number check, a printer habit or tighter access rights, and make it.
Keep sanctions records, along with the policy and its earlier versions, for six years from creation or from when they were last in effect[1]. Keep personnel details confidential and separate from the general incident log.
What to write down
The documentation requirement is short, but the record should be complete enough that someone who was not there can follow the decision. A one-page form works well for most practices.
- Incident reference, date discovered and date reported, and who reported it.
- What happened, in plain words, with the policy or procedure that was not followed.
- Facts gathered: audit log extracts, documents, interview notes and the dates collected.
- Training history for the person involved, with dates.
- The level assigned and the factors that pushed the decision up or down.
- The sanction applied, who decided, and the date it was communicated.
- Process changes made as a result, and any follow-up check, such as a log review in 90 days.
- A link to the separate breach assessment, if one was needed.
Fair discipline helps you keep good staff
Discipline and retention pull in different directions only when discipline feels arbitrary. Front desk roles are hard enough to keep filled. When MGMA asked practice leaders about their most effective tactics for retaining front desk staff, higher pay and engagement each drew 33% of responses, ahead of flexible schedules at 19%[5]. A clear, predictable sanctions process is part of engagement: people stay where they know the rules and trust that they will be treated the same as everyone else.
Explain the policy during onboarding with the same care you give to the privacy rules themselves. Frame it as a promise as well as a warning: mistakes reported quickly are learning opportunities, and serious misconduct will be dealt with firmly for everyone, including physicians and owners.
The conversation itself
How the decision is delivered shapes how the whole team reacts. Hold the conversation privately, soon after the investigation, with a second manager present for anything above coaching. Describe the facts, the policy, the decision and what happens next, then listen.
Script for a level 1 coaching conversation: Thank you for telling us straight away about the lab order. That is exactly what we want people to do. We have logged it and handled it with the patients. Let us walk through the two-identifier check again together, and I will note on file that we had this conversation and that you reported it yourself.
For higher levels, keep the tone factual and brief, give the written outcome at the meeting, and explain any right to respond under your HR policy. Avoid discussing the case with other staff beyond what they need to know to fix a process.
Example: two incidents, two outcomes
Example (fictional): In the same month, two incidents reach the privacy officer of a family practice. A new receptionist emails a lab order to the wrong patient with a similar name, notices within minutes and reports it. An audit-log review shows that a medical assistant opened the chart of a well-known local resident four times with no work reason.
The receptionist gets a coaching conversation and a short retraining on the two-identifier check, recorded as level 1. The medical assistant's access was deliberate and repeated; after an interview, the practice issues a final written warning under level 3, removes access to records outside her assigned providers' patients and schedules a follow-up log review. Both decisions, the reasons and the factors weighed are documented. Staff see that honesty was treated as honesty and snooping as snooping.
Frequently asked questions
Does HIPAA say what sanctions to use?
No. It requires appropriate sanctions, applied and documented. The practice decides the levels, ideally with a framework tied to intent and harm, and with employment law advice.
Should physicians and owners be covered by the sanctions policy?
Yes. The policy applies to the whole workforce. Uneven treatment of senior staff undermines the policy and makes it hard to defend.
Do we have to fire someone for a HIPAA violation?
Not necessarily. Many incidents are honest errors best handled with coaching and retraining. Termination is usually reserved for deliberate or malicious conduct, or repeated violations after warnings.
Can we discipline someone for reporting us to HHS?
No. HIPAA prohibits retaliation against people who file complaints or exercise their rights, and protects certain good-faith whistleblower disclosures.
References
Legal Information Institute, Cornell Law School (current). 45 CFR § 164.530 - Administrative requirements (opens in a new tab) ↑
Legal Information Institute, Cornell Law School (current). 45 CFR § 164.308 - Administrative safeguards (opens in a new tab) ↑
Legal Information Institute, Cornell Law School (current). 45 CFR § 102.3 - Penalty adjustment and table (opens in a new tab) ↑
Legal Information Institute, Cornell Law School (current). 45 CFR § 164.502 - Uses and disclosures of protected health information: General rules (opens in a new tab) ↑
Medical Group Management Association (MGMA) (2025). 5 proven tactics to retain front-desk staff - and how to do them right (opens in a new tab) ↑