HIPAA IT support helps a medical office put the technical safeguards of the HIPAA Security Rule in place and keep a written record that they work. In practice, that means knowing where patient information lives, controlling who can open it, encrypting and backing it up, and writing it all down. Your practice stays responsible for HIPAA, and a good IT company handles the technical side and explains it in plain English.
Does the HIPAA Security Rule apply to a small medical office?
Usually, yes. According to HHS, the Security Rule covers health plans, clearinghouses and any health care provider that transmits health information electronically in connection with certain standard transactions, such as billing insurance. It protects electronic protected health information, or ePHI: patient information kept in or sent through computers, servers, email, backups and other electronic systems. It does not apply to paper records or spoken information (HHS summary of the Security Rule).
Small offices are not held to a different rulebook, but the rule is built to scale. HHS says it asks each office to choose measures that fit its size, technology, costs and risks. If you’re not sure your office counts as a covered entity, ask your attorney or professional association.
One note on timing: HHS proposed changes to the Security Rule in January 2025 (HHS Security Rule page). This guide covers the rule that HHS describes as currently in effect. If the final rule changes anything, we’ll update this page.
What are the three kinds of HIPAA safeguards?
The Security Rule groups its requirements into administrative, physical and technical safeguards. Here is each one, in office terms (HHS summary):
| Safeguard | What HHS lists | What it looks like in a medical office |
|---|---|---|
| Administrative | Risk analysis and risk management, a named security official, workforce training, incident procedures, a contingency plan, periodic evaluation | A written risk analysis, one person in charge of security, staff who know what a phishing email looks like, a plan for when the system goes down |
| Physical | Facility access, workstation use and security, device and media controls | Front-desk screens that aren’t visible from the waiting room, locked server closets, a plan for wiping or destroying old computers and drives |
| Technical | Access control, audit controls, integrity, authentication, transmission security | Unique logins, multi-factor sign-in, activity logs, protection against changes to records, secure email and remote access |
HIPAA IT support is mostly about the technical row and the backup and documentation pieces of the administrative row. The rest depends on your own policies and your people.
What is a security risk analysis, and how often do you need one?
A risk analysis is the first step, and it is required. HHS describes it as an accurate and thorough assessment of the potential risks and vulnerabilities to the confidentiality, integrity and availability of the ePHI you hold (HHS risk analysis guidance).
Three things from that guidance are worth knowing:
- There is no one required method. HHS says the rule doesn’t prescribe a specific methodology, and the right approach depends on the size and complexity of your office.
- There is no fixed schedule. HHS says the rule doesn’t specify how often to do one. It says the process should be ongoing, and that some organizations review annually or as needed.
- Certain changes should trigger a fresh look. HHS gives examples: a security incident, a change in ownership, turnover in key staff, or adopting new technology.
Whatever method you use, write it down. HHS says the risk analysis must be documented, though it doesn’t require a specific format, and the Security Rule summary says to keep required documentation for six years from when it was created or last in effect.
HHS and the Office of the National Coordinator for Health IT also offer a Security Risk Assessment Tool for small and medium-sized practices, which you can find on the HHS Security Rule page. It’s a good place to start this week if you’ve never done one.
Your IT company can’t do the analysis for you, because the practice owns it. What IT can do is give you accurate answers about your systems: what computers, servers and accounts you have, where data is stored, how it’s backed up and who can get in.
What does “addressable” mean in the Security Rule?
It does not mean optional. Some parts of the Security Rule are “required,” and others are “addressable.” HHS explains that for an addressable item, you decide whether it’s reasonable and appropriate for your office. If it is, you adopt it. If it isn’t, you document why and adopt an equivalent measure when that’s reasonable (HHS summary).
HHS says your risk analysis should inform decisions like whether and how to use encryption. So the honest answer to “do we have to encrypt our laptops?” is: your risk analysis should answer it, and if you decide not to, you need a written reason and a substitute. Turning encryption on is usually simpler than writing down why you didn’t.
What should HIPAA IT support cover day to day?
Here is what a medical office should expect from the technical side of its IT, and what BizTechPro does for the offices we support:
- A current list of what you have. Computers, servers, printers, phones, EHR connections and who uses each one. You can’t protect what isn’t on the list.
- Unique logins and multi-factor sign-in. Every person gets their own account, and a stolen password alone isn’t enough to get in. Email is the first place to turn it on.
- Encrypted devices and automatic screen locks. A laptop left on a counter shouldn’t show patient information to whoever walks by.
- Updates and monitoring. Windows and your other software stay patched, and 24/7 monitoring flags problems with your computers and network so they get looked at. That’s monitoring only, not a staffed help desk.
- Backups that get tested. HHS’s contingency plan standard covers backing up ePHI, restoring lost data and continuing critical operations in an emergency. A backup that’s never been restored is a guess, so we test by restoring files.
- Staff training. Training for everyone who touches patient information is an administrative requirement, and phishing training is a practical way to meet it.
- Records you can show. Written documentation of what’s protected and how, kept current as your office changes.
- Help with your EHR vendor. When the EHR slows down or a workstation won’t connect, we work directly with the vendor so your staff can stay with patients.
All of this helps you meet HIPAA Security Rule requirements, but it doesn’t replace your own policies, or someone in your office taking responsibility for security.
What happens when something stops working on a Monday morning?
Imagine the front desk of a Hackensack practice can’t open the day’s schedule because a server failed overnight. This is what the contingency plan is for. The plan says what gets restored first, where the backup lives, who makes the calls, and how the office keeps seeing patients in the meantime. If you’ve never tested it, that Monday is a bad time to find out.
When you need a person, you call one. Our help desk is staffed Monday to Friday, 8am to 6pm. Most support happens remotely, with site visits, when needed, for things like replacing a network switch or setting up a new workstation. Our 24/7 monitoring runs around the clock, but it’s monitoring, so for help from a person, use the help desk hours.
How do you tell good HIPAA IT support from a risky setup?
Ask your current provider, or any provider you’re considering, these questions:
- Can you show me a list of every computer, server and account that touches patient information? If nobody has one, the risk analysis has nothing solid to stand on.
- How is access controlled? Look for unique logins, multi-factor sign-in on email and remote access, and a process for removing access when someone leaves.
- Are our devices encrypted, and can you show me? A good provider can report on it instead of saying “yes.”
- When did you last restore a backup as a test? If the answer is “never,” ask for a test.
- Who answers when we call, and during what hours? Get the help desk hours in writing and know what happens after hours.
- Which vendors handle our patient information, and what HIPAA terms apply to each? For cloud tools like Microsoft 365, see our guide to Microsoft 365 support for Bergen County medical practices. For anything else, check with BizTechPro about what applies to your practice.
Be careful with any company that says it will make HIPAA “go away.” The responsibility stays with your practice, and good IT support makes it easier to carry.
Where does this fit with everything else we do for medical offices?
This guide is about the HIPAA side of IT. For the bigger picture of what we do for healthcare offices, see our page on IT for medical practices. For defenses against ransomware and phishing, see our cybersecurity services and our post on cybersecurity for medical practices in Bergen County. If you’re still comparing providers, our checklist for choosing an IT company in Bergen County covers questions that apply to any office.
BizTechPro has been based in Pearl River, NY since 2008 and supports offices across Bergen County, including Hackensack, Paramus, Ridgewood, Teaneck and Fort Lee. For the wider picture of how we support offices across the county, see our managed IT services in Bergen County page.
Frequently asked questions
What is HIPAA IT support for a medical office?
HIPAA IT support is IT help focused on the technical safeguards the HIPAA Security Rule describes, such as access controls, encryption, backups and activity logs. It also includes keeping records of what’s in place. Your practice remains responsible for HIPAA, and the IT company handles the technical side.
Who is responsible for HIPAA, our practice or our IT company?
Your practice is. HHS says regulated entities, which include covered medical practices, must put reasonable and appropriate administrative, physical and technical safeguards in place for ePHI. An IT company can set up and document the technical safeguards, but it can’t take the responsibility off the practice.
How often does a medical office need a security risk analysis?
HHS says the Security Rule doesn’t set a specific schedule, but the risk analysis should be an ongoing process. Some organizations review it annually or when something changes, such as a security incident, new technology, or turnover in key staff. Whatever you choose, document it.
Does our medical office have to encrypt its computers?
Encryption is an “addressable” item in the Security Rule, which does not mean optional. You decide, based on your risk analysis, whether it’s reasonable and appropriate. If it is, you adopt it, and if it isn’t, you document why and use an equivalent measure.
What does HIPAA say about backups?
The Security Rule’s contingency plan standard requires plans for backing up ePHI, restoring lost data and continuing critical operations in an emergency. It’s worth testing the plan by restoring files, so you know it works before you need it.
Do you offer a help desk and site visits for medical offices in Bergen County?
Yes. Our help desk is staffed Monday to Friday, 8am to 6pm, and most support happens remotely, with site visits, when needed. We also offer 24/7 monitoring of your computers and network, which is monitoring only, not a staffed help desk.
Talk to us about HIPAA IT support
If you’d like to know where your medical office stands, call BizTechPro at (845) 747-5803. Bring your last risk analysis if you have one, and if you don’t, that’s a good place to start.
