HIPAA IT compliance, in plain English

HIPAA asks you to know where patient information lives, protect it with reasonable safeguards, and keep records that prove it. Your IT provider can run the technical side, but the compliance program is still yours.

HIPAA is long, but the part that touches your IT is easier to follow than its reputation suggests. It does not hand you a shopping list of products. It asks you to understand your own risks, put sensible protections in place, and write down what you did.

This guide covers the IT side of HIPAA for owners and administrators. It is general information, not legal advice. For questions about your specific obligations, talk to healthcare counsel or a compliance professional.

Who HIPAA applies to

HIPAA applies to two groups. Covered entities are health plans, healthcare clearinghouses, and healthcare providers that send health information electronically for things like billing. That includes most nursing homes, home health agencies, clinics and dental offices.

Business associates are the vendors that handle protected health information (PHI) on behalf of a covered entity. Billing companies, EHR vendors, cloud hosts and IT providers usually fall into this group. Size does not excuse you. A two-provider clinic has the same basic duties as a hospital, scaled to what is reasonable for its size.

The three kinds of safeguards

The Security Rule covers PHI in electronic form. It groups its requirements into three kinds of safeguards.

Administrative safeguards

These are the management decisions: naming someone responsible for security, doing a risk analysis, training staff, deciding who gets access to what, and planning for emergencies. Most of HIPAA security work lives here, and most of it is paperwork backed by real practice.

Physical safeguards

These cover the building and the equipment. Who can walk up to a workstation, where the server sits, how screens are positioned, and what happens to an old computer or copier hard drive when you get rid of it.

Technical safeguards

These are the controls inside your systems: a unique login for each person, automatic logoff, audit logs that record who looked at what, encryption, and protection for data sent over a network.

Risk analysis comes first

The risk analysis is the foundation of the Security Rule. It is a written review of where your electronic PHI is stored and sent, what could go wrong with it, how likely and how serious each problem is, and what you are doing about it.

It is not a one-time form. You are expected to revisit it as things change, such as a new EHR, a new building, or a move to cloud email. A risk analysis that stops at a checklist of yes and no answers usually falls short. A good one names your actual systems and ends with a plan that someone owns.

Business Associate Agreements

Before a vendor handles PHI for you, you need a signed Business Associate Agreement (BAA). The BAA commits the vendor to protecting that information and to telling you if something goes wrong.

Think broadly about who qualifies: your IT provider, email and file storage service, backup vendor, e-fax service, shredding company and billing service. A common surprise is a free or consumer-grade tool that staff started using on their own. If the vendor will not sign a BAA, PHI should not go into that tool.

If something goes wrong

HIPAA has a Breach Notification Rule. In general terms, when unsecured PHI is seen or taken by someone who should not have it, you must assess what happened and, unless you can show a low probability that the information was compromised, notify the affected people and the U.S. Department of Health and Human Services. Larger breaches bring extra steps. Your state may add its own rules.

The deadlines and details depend on the size and facts of the incident, so confirm them with counsel as soon as you suspect a problem. From an IT standpoint, two things help most: properly encrypted devices, because a lost laptop that was encrypted is a very different event from one that was not, and logs that let you say what was and was not accessed.

What an auditor or investigator asks for

Whether the request comes from a federal investigator, a state surveyor, a business partner or your insurer, it tends to cover the same ground.

Common gaps, and where an IT provider helps

The gaps we see most often are ordinary ones. Shared logins at a nurse station. Accounts still active for people who left months ago. No multi-factor authentication on email. Laptops with no encryption. Backups that have never been test restored. A risk analysis that is years old or missing.

An IT provider can take on the technical safeguards: unique accounts, multi-factor authentication, encryption, patching, monitored endpoint protection, backups, and the reports that show those are in place. A good one will also help with the technical parts of your risk analysis and sign a BAA.

What stays with you: naming a security officer, approving policies, training your people, deciding who should have access, managing your vendors, and making the call on breach notification with your counsel. No IT provider can make an organization HIPAA compliant by itself, and you should be wary of any vendor that promises to.

Common questions

Does HIPAA require encryption? The Security Rule expects you to address encryption and to document your decision. In practice, encrypting laptops, phones and anything that leaves the building is the sensible choice, and it can change how a lost device is treated. Ask your counsel how the current rule applies to you.

Is our EHR vendor responsible for HIPAA? Only for its own piece. The vendor protects the system it hosts. You are still responsible for who has logins, the computers and network used to reach it, your email, your paper and everything else outside the EHR.

How often do we need a risk analysis? The rule calls for it to be kept current rather than naming a fixed schedule. Many organizations review it yearly and again after a major change such as a new system, a new location or a security incident.

Will UnityCare sign a BAA? Yes. UnityCare Technologies signs a Business Associate Agreement before we work with systems that store or transmit PHI.

Need help with the IT side of HIPAA?

We are based in Edmond, Oklahoma and support healthcare organizations across Oklahoma, Texas and Kansas, on-site and remote. We handle the technical safeguards, sign a BAA, and give you records you can hand to an auditor.

Related reading

Contact UnityCare Technologies

Call or text: 405-285-3845

New customers: start@unitycareit.com

Existing customers: support@unitycareit.com

Service area: based in Edmond, Oklahoma, serving Oklahoma, Texas and Kansas

Hours: Mon–Fri 8 AM–5 PM CT; 24/7 after-hours support