Medical practice IT support is the outside team that keeps a physician or specialty practice's computers, network, logins and backups working, and handles the technical side of HIPAA security. This guide is for practice owners and office managers in Buffalo and Western New York. It covers what that support should include, where your EHR vendor's job ends and your IT company's begins, the HIPAA gaps that show up most often, and what it costs.
If you run a dental office, our dental IT support checklist covers imaging and the dental side in more detail.
For a small practice, IT support should cover:
360 Business Solutions is a managed IT and compliance company in Amherst, NY, with medical clients in Western New York. Call (716) 650-7200.
At 360, usually the vendor does. JD Sentz, COO and CTO of 360 Business Solutions, is plain about it: "We have medical clients, but we don't typically support those platforms, as they are handled through the vendor."
That split is normal, and it's worth knowing before you sign with anyone. Your EHR company fixes the software. Your IT company is responsible for everything the software runs on and everyone who logs into it: the computers, the network, the internet connection, user accounts, security and backups of the data kept in your office.
Where practices get stuck is the gray zone. The EHR is slow, and the vendor says it's your network. The network looks fine, and nobody calls the vendor back. Ask any IT provider how they handle that before you hire them, and who makes the call.
When JD first walks into a practice, here's what he finds: "almost all of the controls are lacking in many areas." These are the ones he singles out, and what the HIPAA Security Rule says about each.
The Security Rule requires audit controls that record activity in systems holding patient information, and a separate section requires practices to regularly review that activity. JD lists audit log retention first among the gaps he finds. A log that gets overwritten after a week can't answer the question "who opened this chart?" three months later.
Change management records are a running list of what was changed on your systems, when and by whom: a new firewall rule, a new user, a server update. JD lists missing change management records among the usual gaps. Without them, when something breaks after a change, nobody can say what changed.
The rule requires security incident procedures: how you identify, respond to and document a suspected incident. JD names incident response documentation as one of the usual gaps, along with tabletop testing, where the team talks through a fake incident before a real one.
JD's description: "There are no policies and procedures stating how they work and operate." The Security Rule requires policies and procedures in written form, which can be electronic, and keeping that documentation for 6 years from when it was created or last in effect, whichever is later.
A data backup plan and a disaster recovery plan are both required. Periodic testing of those plans is listed as addressable. Either way, a backup you've never restored from is a guess. JD has seen what a working one is worth: in one case from his career, ransomware hit an entire file server share, and all services were restored within 24 hours from the previous night's backup. The data created that day was lost.
Not overnight. JD's answer: "within months you can begin seeing progress." The usual order is a risk analysis first, which the Security Rule requires, then the technical fixes that carry the most risk, like multi-factor authentication, open ports and untested backups, then the written policies and the testing schedule.
One thing no IT company can do is make your practice HIPAA compliant on its own. Your policies, your training and your decisions are part of it. A good provider finds the gaps, fixes the technical ones and keeps the documentation current.
At 360, most clients pay between $100 and $200 per user per month, plus a few flat monthly costs based on what the office needs. Compliance work is the biggest factor in where a practice lands in that range. For a 10-person practice, the per-user part works out to about $1,000 to $2,000 a month. That's our range applied to one practice size, not a quote. Our managed IT pricing guide explains what moves the number.
If you'd like those answered for your own practice, our compliance and security team can walk through your setup, or see what our managed IT services include. Call (716) 650-7200.
Usually not directly. The EHR vendor supports its own software. Your IT company supports the computers, network, accounts, security and backups around it, and should work with the vendor when a problem crosses both.
In most cases, yes. A company that creates, receives, maintains or transmits patient information for you is a business associate, and an IT company that manages the computers holding your charts usually falls in that group. Ask for the agreement before you sign the service contract.
At 360, most clients pay $100 to $200 per user per month plus a few flat costs. Compliance needs move a practice up or down that range.
Progress usually shows within months. Start with a risk analysis, fix the highest-risk technical gaps first, then put written policies and regular testing in place.
Many of the same controls show up on both. Our cyber insurance checklist covers what insurers ask small firms to prove.
This post explains common IT and HIPAA security requirements for small practices. It isn't legal advice. Talk to your compliance advisor about your practice.
Free 30-Minute Technology Assessment