Blog · HIPAA
The Core Privacy and Security Principles of HIPAA, Explained
What the Privacy Rule, the Security Rule and breach notification actually require — in plain English for small medical and dental practices.
Ask ten people at a medical or dental office what HIPAA requires, and you'll get ten answers: "don't talk about patients in the hallway," "use encrypted email," "sign the forms." All of those are part of it, but none of them is the whole picture.
HIPAA rests on a few core principles. Once you understand them, the individual rules stop feeling arbitrary, and it becomes much easier to see where your practice is protected and where it isn't. This article explains those principles in plain English, with a focus on what they mean for a small healthcare practice and its IT.
This article is general information, not legal advice. For decisions about your specific situation, talk to a healthcare attorney or compliance professional.
What HIPAA is, and who it applies to
The Health Insurance Portability and Accountability Act became law in 1996. The parts most people mean when they say "HIPAA" are the rules written under it by the U.S. Department of Health and Human Services (HHS):
- The Privacy Rule governs how protected health information may be used and shared, and gives patients rights over their own information.
- The Security Rule requires specific safeguards for health information kept or sent electronically.
- The Breach Notification Rule says who must be told, and how fast, when health information is exposed.
The HITECH Act of 2009 and the 2013 Omnibus Rule strengthened all three, raised penalties, and extended direct liability to vendors. The HHS Office for Civil Rights (OCR) enforces them.
HIPAA applies to two groups:
- Covered entities: health plans, healthcare clearinghouses, and healthcare providers who transmit health information electronically (for example, to bill insurance). Practically every medical, dental, chiropractic, therapy or specialty practice that takes insurance is a covered entity.
- Business associates: vendors that create, receive, store or transmit health information on a covered entity's behalf, such as billing companies, EHR and cloud providers, and IT companies with access to your systems. They are directly responsible for complying with the Security Rule and must sign a Business Associate Agreement (BAA).
What HIPAA protects: PHI and ePHI
Protected health information (PHI) is any individually identifiable information about a person's health, care or payment for care. Examples include a diagnosis, an appointment time, an insurance ID or a billing record. It counts as PHI when it is held by a covered entity or business associate and can be tied to a specific person.
"Identifiable" covers far more than a name. Addresses, dates (other than the year) such as a birth or visit date, phone numbers, email addresses, medical record numbers, photos and device identifiers can all make information identifiable.
Electronic PHI (ePHI) is PHI that is created, stored or sent electronically: in your EHR, practice management system, email, scanned documents, backups, phones and laptops. The Privacy Rule covers PHI in every form (paper, spoken and electronic). The Security Rule covers ePHI.
The Privacy Rule: five principles
1. Use and disclose only what is permitted
PHI may be used or shared without the patient's written permission only for specific purposes. The main ones are treatment, payment and healthcare operations, plus certain public-interest situations defined in the rule, such as some public health reporting or legal requirements. Almost everything else, including most marketing, needs the patient's written authorization.
In day-to-day terms: sending records to a referring specialist is treatment, sending a claim to an insurer is payment, and both are allowed. Sharing a patient's story in a promotional email is not.
2. Minimum necessary
When PHI is used or shared for purposes other than treatment, you must limit it to the minimum necessary to get the job done. The front desk needs the schedule and insurance details, not full clinical notes. A billing vendor needs billing data, not the whole chart.
Of all the privacy principles, this one maps most directly onto IT. Role-based access in your EHR, separate user accounts and limited file-share permissions are how "minimum necessary" actually happens.
3. Patients have rights over their own information
The Privacy Rule gives patients enforceable rights:
- Access: to see and get a copy of their records, generally within 30 days of the request (with one 30-day extension), in the format they ask for if it is readily producible, including electronic copies. Fees are limited to a reasonable, cost-based amount.
- Amendment: to ask for corrections to information they believe is wrong.
- Accounting of disclosures: to get a list of certain disclosures of their information.
- Restrictions: to request limits on uses and disclosures. A practice must agree not to share information with a health plan about care the patient paid for in full out of pocket.
- Confidential communications: to ask to be contacted in a particular way or at a particular place.
Patients learn about these rights through your Notice of Privacy Practices, which must be given to them and posted.
4. Accountability is assigned, documented and trained
Every covered entity must designate a privacy official. It must also have written policies, train its workforce, apply sanctions when policies are broken, and keep documentation for six years. "We all know what to do" is not enough; the rule expects it written down and practiced.
5. De-identified information is outside the rule
Information that has been properly de-identified, either by removing specified identifiers or through an expert's determination, is no longer PHI. This is what makes it possible to use data for reporting or research without putting individuals at risk.
The Security Rule: protecting ePHI
Where the Privacy Rule is about who may see and share health information, the Security Rule is about keeping electronic health information safe. It is built around three goals, often called the CIA triad:
- Confidentiality: ePHI is available only to authorized people.
- Integrity: ePHI is not altered or destroyed improperly.
- Availability: ePHI is accessible when it is needed for care.
That third goal is easy to forget. Ransomware that locks your EHR for three days is a security failure even if no data ever leaves the building, because patients can't be treated properly without their records.
The rule is deliberately flexible and scalable. It doesn't name products. A three-provider dental office and a hospital system face the same requirements, but each chooses measures that fit its size, complexity, technology and risks. Some specifications are required. Others are addressable, which means you must implement them if they are reasonable and appropriate, or document why not and use an equivalent alternative. "Addressable" has never meant "optional."
The safeguards fall into three groups.
Administrative safeguards
These are the management side of security, and they carry the most weight.
- Risk analysis: an accurate, thorough assessment of the risks to the ePHI you hold. It covers where it lives, how it moves, and what could go wrong. This is the foundation of the whole rule, and a missing or outdated risk analysis is the most common problem OCR finds in investigations.
- Risk management: acting on the risk analysis to bring risks down to a reasonable level.
- A designated security official responsible for the program.
- Workforce security and access management: granting access based on role, and removing it promptly when someone leaves or changes roles.
- Security awareness training, including phishing, passwords and malware.
- Incident procedures for identifying and responding to security incidents.
- A contingency plan: data backups, disaster recovery and emergency-mode operation, so care can continue when systems fail.
- Periodic evaluation of whether your safeguards still work.
- Business associate agreements with every vendor that handles ePHI.
Physical safeguards
These protect the places and devices where ePHI lives:
- Facility access controls (who can get into the server closet and the office after hours).
- Workstation use and security (screens facing away from the waiting room, locked when unattended).
- Device and media controls (tracking laptops and drives, and securely wiping or destroying them before disposal or reuse).
Technical safeguards
These are the controls built into your systems:
- Access control: a unique user ID for every person (no shared logins), emergency access procedures, automatic logoff, and encryption of stored data.
- Audit controls: logging who accessed which records, and reviewing those logs.
- Integrity controls that protect ePHI from improper changes.
- Person or entity authentication: verifying that users are who they say they are. Today that realistically means multi-factor authentication (MFA), especially for email, remote access and cloud systems.
- Transmission security: protecting ePHI sent over networks, such as encrypted email and secure connections.
In January 2025, HHS proposed the first major update to the Security Rule in years. The proposal would make most safeguards mandatory rather than addressable and explicitly require measures such as MFA, encryption, an asset inventory and regular technical testing. Check the current status before relying on it. Either way, the direction is clear, and these controls are already what OCR and cyber insurers expect.
Breach notification: what happens when something goes wrong
A breach is an impermissible use or disclosure of PHI that compromises its privacy or security. Under the rule, an incident is presumed to be a breach unless a documented risk assessment shows a low probability that the information was compromised. That assessment weighs four factors: what information was involved, who received it, whether it was actually acquired or viewed, and how far the risk was mitigated.
If a breach of unsecured PHI occurs:
- Affected individuals must be notified without unreasonable delay, and no later than 60 days after discovery.
- HHS must be notified. For breaches affecting 500 or more people, notice is due within 60 days. Smaller breaches can be reported in an annual log, within 60 days after the end of the calendar year.
- Prominent media in the area must be notified when a breach affects more than 500 residents of a state or jurisdiction.
- Business associates must notify the covered entity of breaches they discover.
There is an important safe harbor. Notification rules apply to unsecured PHI. If a lost laptop was properly encrypted to HHS guidance standards and the key wasn't compromised, the loss generally isn't a reportable breach. Few security measures pay for themselves as clearly as full-disk encryption.
Enforcement and penalties
OCR investigates complaints and breach reports and can impose civil monetary penalties in four tiers, from violations the organization didn't know about to willful neglect that went uncorrected. Penalty amounts are adjusted for inflation every year. At the top tier they can exceed $2 million per year for each type of violation. Many cases end in resolution agreements with a payment and a multi-year corrective action plan. Criminal penalties, prosecuted by the Department of Justice, apply to knowingly obtaining or disclosing PHI improperly.
For a small practice, the bigger costs are often indirect: downtime, recovery, notification letters, legal fees and lost patient trust.
Turning the principles into practice: a starting checklist
For a small practice, these steps cover most of the ground:
- Map where PHI lives and moves: EHR, email, scanners, file shares, phones, backups and every vendor.
- Do a documented risk analysis, and repeat it at least yearly and after major changes.
- Give everyone their own login, with access matched to their role. Remove access the day someone leaves.
- Turn on MFA for email, remote access and cloud systems.
- Encrypt laptops, phones and backups. Use secure email for PHI.
- Keep backups you have actually tested restoring, with at least one copy offline or immutable, so ransomware can't take it too.
- Patch and monitor: keep systems updated, use endpoint protection, and review access logs.
- Train your staff, especially on phishing, which is the most common way attackers get in.
- Sign BAAs with every vendor that touches PHI, including your IT provider.
- Write it down: policies, decisions about addressable specifications, incidents and training records.
The bottom line
HIPAA's privacy principles come down to using and sharing health information only as needed and respecting patients' rights over it. Its security principles come down to keeping electronic health information confidential, accurate and available, based on an honest assessment of your risks. Most of the work is ordinary, well-run IT: unique logins, MFA, encryption, tested backups, patching and training, all documented.
Not sure where your practice stands? RedCube helps medical and dental practices in Delaware, Pennsylvania and New Jersey with HIPAA risk analysis, gap assessments and remediation, as well as day-to-day IT that keeps patient records safe. We work in plain English and sign a BAA. You can also start with our free domain security check to see whether your email domain is protected against spoofing. Contact us to talk it through.
Common HIPAA misconceptions
Can a practice be "HIPAA certified"? +
There is no official HIPAA certification for practices or vendors. Compliance is an ongoing program you can document, not a badge.
Does our EHR vendor handle HIPAA compliance for us? +
The vendor secures its own systems. You are still responsible for your users, devices, network, email, backups, policies and risk analysis.
Does HIPAA forbid email and texting with patients? +
It doesn't. Patients can be contacted electronically with reasonable safeguards, and patients may choose unencrypted communication after being told the risks. What matters is having safeguards and documented choices.
Is the risk assessment we did when we opened enough? +
A risk analysis has to be kept current, especially after changes like a new EHR, a move to the cloud, new locations or remote work.
Not sure where your practice stands?
We help medical and dental practices in Delaware, Pennsylvania and New Jersey with HIPAA risk analysis, remediation and everyday IT — in plain English, and we sign a BAA.