Compliance Guide

HIPAA for small medical & dental practices

What the Privacy and Security Rules expect of a small practice’s technology, what a real risk analysis looks like, and the safeguards that matter most — explained without the jargon.

Jump to the checklist

Last reviewed · For physician, dental, chiropractic, therapy, and other small covered-entity practices and the vendors that serve them.

Not legal advice. This guide is general educational information from an IT provider, current to the best of our knowledge as of September 24, 2026. Regulations, standards, and official guidance change, and how they apply depends on your specific facts. Confirm your obligations with a qualified attorney, compliance professional, or the relevant regulator or standards body before relying on it. PinellasIT does not certify compliance.

HIPAA doesn’t hand you a list of products to buy. It sets out outcomes: patient information stays private, stays accurate, and is there when you need it. It then expects you to show that you thought about your own risks and did something reasonable about them. For a five- or fifteen-person practice, that’s very doable. It just has to be done on purpose and written down.

Privacy Rule vs. Security Rule

People use “HIPAA” to mean several different rules. The two that shape daily operations are:

  • The Privacy Rule covers protected health information (PHI) in every form: paper charts, conversations, faxes, and electronic records. It governs who may use or disclose PHI and why, the “minimum necessary” standard, patients’ right to access their records, and your Notice of Privacy Practices.
  • The Security Rule covers only electronic PHI (ePHI), meaning the data in your practice-management and EHR systems, imaging, email, backups, and laptops. It requires administrative, physical, and technical safeguards to protect the confidentiality, integrity, and availability of that data.

Most IT work falls under the Security Rule, but the two overlap. Access controls, for example, are how you enforce the Privacy Rule’s “minimum necessary” standard in software.

The required risk analysis

The Security Rule requires an accurate and thorough assessment of the risks to the ePHI you create, receive, maintain, or transmit, followed by risk management: reducing those risks to a reasonable level. This is the step small practices most often skip, and it’s one the HHS Office for Civil Rights (OCR) frequently cites in enforcement actions. A useful risk analysis:

  1. Inventories where ePHI lives: EHR and PM systems, imaging devices, workstations, phones, email, cloud apps, backups, and anything a vendor hosts for you.
  2. Identifies realistic threats, such as ransomware, phishing, a stolen laptop, a departing employee, a failed server, or a hurricane.
  3. Rates likelihood and impact against the safeguards you already have.
  4. Produces a remediation plan with owners and dates, then gets revisited when something significant changes (new EHR, new office, new cloud service) and at least periodically.

HHS and ASTP/ONC (formerly the Office of the National Coordinator) publish a free Security Risk Assessment Tool designed for small practices. It’s a reasonable framework, but the tool only works if the answers reflect how your office actually runs.

Administrative, physical & technical safeguards

Some Security Rule specifications are “required” and others are “addressable.” Addressable does not mean optional. It means you implement the safeguard, implement a reasonable alternative, or document why neither is reasonable for you.

Administrative safeguards

  • A named security official responsible for the program (in a small practice, often the practice manager).
  • Written policies and procedures, kept for six years.
  • Workforce security-awareness training, with a record of who completed it and when.
  • Onboarding and offboarding procedures so accounts are created with the right access and disabled the day someone leaves.
  • A contingency plan: data backup, disaster recovery, and emergency-mode operations. In Florida, that means planning for hurricanes too.
  • A security incident procedure: who to call and what to document.

Physical safeguards

  • Controlled access to the server or network closet.
  • Workstation placement and screen privacy in patient-facing areas.
  • Device and media controls: an inventory, and secure wiping or destruction of old drives, copiers, and phones.

Technical safeguards

  • Unique user IDs with no shared logins, plus automatic logoff on unattended workstations.
  • Multi-factor authentication on email, remote access, and cloud EHR portals. It’s among the most effective controls against account takeover.
  • Audit controls: logs that record who accessed which records, and someone who actually reviews them.
  • Integrity and transmission security: encryption in transit, secure email for PHI leaving the practice, and protection against tampering.
  • Endpoint protection and patching so known vulnerabilities don’t sit open for months.

Business associate agreements

Any vendor that creates, receives, maintains, or transmits PHI on your behalf is a business associate and needs a signed business associate agreement (BAA) before it touches that data. For most practices that list includes the EHR vendor, cloud email provider, backup service, answering service, billing company, shredding company, and your IT provider. Keep a list of vendors and their BAAs, and treat “we’re HIPAA certified” as a marketing phrase: there is no official government HIPAA certification.

Breach notification

An impermissible use or disclosure of unsecured PHI is presumed to be a reportable breach unless a documented risk assessment shows a low probability that the information was compromised. If it is a breach:

  • Affected individuals must be notified without unreasonable delay and no later than 60 calendar days after discovery.
  • HHS must be notified. For breaches affecting 500 or more people, that notice is due within the same 60-day window. Smaller breaches can be logged and reported to HHS within 60 days after the end of the calendar year.
  • Prominent media outlets must also be notified when a breach affects more than 500 residents of a state or jurisdiction.

Florida’s own breach law, the Florida Information Protection Act, can apply alongside HIPAA and has its own timelines and Attorney General notice threshold. Involve legal counsel early. Our overview of Florida’s data breach law and our guide to the first 24 hours after a breach are good starting points.

Encryption as a safe harbor

Breach notification applies to unsecured PHI. HHS guidance treats PHI encrypted consistent with NIST standards as “secured,” provided the decryption key wasn’t compromised with it. In practice, a lost laptop with properly managed full-disk encryption usually isn’t a notifiable breach, while the same laptop unencrypted very likely is. That makes encrypting laptops, workstations, phones, removable media, and backups one of the best investments a practice can make. Keep proof that it’s turned on, such as a management console report, not just a note that it “should be.”

The proposed Security Rule update

In January 2025, HHS published a notice of proposed rulemaking (NPRM) to update the Security Rule. Among other things, the proposal would largely remove the required/addressable distinction and spell out expectations such as encryption, multi-factor authentication, a technology asset inventory and network map, and tested restoration. It is a proposal. As of this guide’s review date, check HHS’s Security Rule page for its current status rather than assuming it has taken effect. Either way, most of the proposed controls are already good practice, and the risk analysis you do today should consider them.

Practical HIPAA checklist for a small practice

  • A security official is named in writing, and policies are reviewed at least annually.
  • A documented risk analysis exists, is less than a year old or updated after major changes, and has a remediation plan with dates.
  • An inventory lists every system, device, and vendor that stores or touches ePHI.
  • Every staff member has a unique login. No shared accounts, and access matches the role.
  • MFA is on for email, remote access, and cloud EHR/PM portals.
  • Full-disk encryption is enabled and verified on laptops, workstations, and mobile devices, and backups are encrypted.
  • Backups follow the 3-2-1 approach, include an offline or immutable copy, and a restore has actually been tested.
  • Patches and endpoint protection are managed centrally, with reports you can show.
  • Audit logging is enabled on the EHR and key systems, and someone reviews it on a schedule.
  • Signed BAAs are on file for every vendor that handles PHI.
  • Security-awareness training is completed at hire and at least annually, with records kept.
  • Offboarding disables accounts and collects devices on the employee’s last day.
  • A written incident response and breach notification procedure names who does what.
  • A contingency plan covers ransomware, hardware failure, and hurricanes, including how to see patients if systems are down.
  • Old drives, copiers, and phones are wiped or destroyed, with a certificate or log.

How PinellasIT helps

We support small medical and dental offices with the technical side of the Security Rule: putting the safeguards in place, keeping them running, and giving you the documentation to show it. Where our work gives us access to PHI, ask us about a business associate agreement.

  • Free security assessment — a practical review of your technical safeguards that feeds straight into your risk analysis.
  • Cybersecurity — MFA, endpoint detection and response, email filtering, and security-awareness training.
  • Backup & disaster recovery — encrypted, monitored backups with tested restores and a hurricane-ready contingency plan.
  • Managed IT services — patching, device encryption, onboarding and offboarding, and asset inventory handled for you.
  • Cloud & Microsoft 365 — securely configured email and file sharing with encryption and audit logging turned on.

We're a locally owned managed IT provider serving Pinellas and Pasco County businesses since 2010. We handle the technical safeguards and the documentation that shows they're in place; your attorney, auditor, or compliance advisor handles the legal judgment calls. See all of our compliance guides.

Frequently asked questions

Does HIPAA apply to my small practice?

If you are a health care provider that transmits health information electronically in connection with standard transactions, such as billing insurance electronically, you are generally a covered entity regardless of size. Vendors that handle PHI for covered entities are business associates and have direct Security Rule obligations too. Confirm your status with counsel if you’re unsure.

Is there such a thing as HIPAA-certified software or a HIPAA certification?

No. HHS does not certify products or organizations as HIPAA compliant. A vendor can support your compliance and sign a BAA, but compliance depends on how your practice configures, uses, and documents its systems.

How often do we need to do a risk analysis?

The current rule requires an accurate, thorough risk analysis and ongoing risk management but doesn’t set a fixed interval. Common practice is to review it at least annually and whenever you make a significant change, such as a new EHR, office move, or cloud service. The January 2025 proposed update would set more specific expectations, but it is still a proposal.

Can we email patient information?

Yes, with appropriate safeguards. Use an email platform covered by a BAA and encryption for PHI sent outside the practice. Patients may request unencrypted email after being warned of the risk, and you should document that preference.

If a laptop is stolen, do we have to report it?

It depends on whether the PHI was “secured.” If the device used encryption consistent with HHS guidance and the key wasn’t compromised, notification is generally not required. If it was unencrypted, you likely have a reportable breach. Document the incident and your analysis either way, and talk to counsel.

Is the proposed 2025 Security Rule update in effect?

HHS published it as a proposed rule (NPRM) in January 2025. This guide treats it as proposed. Check HHS for its current status before making decisions based on it.

Want a second set of eyes on your safeguards?

Our free security assessment reviews the technical controls this guide covers and gives you a plain-English list of gaps, in priority order. No obligation and no sales pressure.

Prefer email? Reach us at info@pinellasit.com.