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 checklistHIPAA 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.
People use “HIPAA” to mean several different rules. The two that shape daily operations are:
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 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:
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.
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.
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.
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:
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.
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.”
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.