Key takeaways
- Most small practices are best served by a managed service provider or a hybrid with one trusted internal coordinator.
- Outsourcing IT does not outsource HIPAA responsibility; you still need a BAA, a breach process and documentation.
- Small practices often run less common EHRs, so ask any IT provider for experience with your exact systems.
- Put response times, security tasks, user changes and vendor coordination in writing.
What IT support actually covers
In a small medical office, IT support is less about servers and more about keeping the front desk, exam rooms and billing running every hour you are open. The work falls into a few groups: keeping devices and networks working, protecting patient data, managing who has access to what, coordinating with software vendors when something breaks, and planning for replacements and outages. When any of that is nobody's job, it becomes the practice manager's job by default, usually at the worst moment.
- Help desk: login problems, printers, scanners, phones, workstation issues.
- Security: patching, antivirus or endpoint protection, email filtering, multifactor authentication, backups.
- Access: setting up new staff, removing leavers on their last day, reviewing permissions.
- Vendor coordination: working with the EHR, phone and internet providers during outages.
- Planning: device replacement, network upgrades, new locations, budgeting.
Three ways to staff it
| Model | Best for | Strengths | Weaknesses |
|---|---|---|---|
| In-house IT staff | Larger groups or several locations | Knows your setup; on site; fast for small fixes | One person cannot cover security, nights and vacations; hard to hire |
| Managed service provider (MSP) | Most practices with one to ten providers | A team, monitoring, security tools, predictable contract | Less on-site presence; quality varies; must learn your workflows |
| Hybrid | Practices with a tech-capable manager or staff member | Internal coordinator plus MSP depth | Needs clear split of duties to avoid gaps |
| Break-fix only | Very small offices with few systems | Pay only when something breaks | No monitoring or prevention; slow when it matters |
For most small practices the realistic choice is between an MSP and a hybrid. A single in-house IT employee rarely has the range to cover help desk, security, networking and vendor management, and no one covers them when they are out. Break-fix arrangements are cheap until a ransomware incident or a failed server shows that nobody was watching.
Your EHR shapes the choice
Small practices tend to run a wider mix of software than large systems. Only 32% of physicians in solo practice used an EHR from one of the five market-leading developers in 2024, compared with 90% of those in practices with more than 50 physicians[1]. An IT provider that supports many large-system clients may never have seen your EHR, your PM or your imaging software.
Source: Office of the National Coordinator for Health IT (ASTP/ONC), HHS, 2024[1]
Show the data
| Item | Value |
|---|---|
| Solo practice | 32% |
| More than 50 physicians | 90% |
Ask every candidate which EHR and PM systems their current clients use, and ask for a reference on yours. A provider who knows your EHR's update schedule, hardware requirements and support process will solve problems faster and will know when to call the vendor instead of guessing.
Responsibility does not move with the contract
Hiring an IT provider moves the work, not the legal responsibility. An MSP that can access systems holding protected health information is a business associate, and a covered entity may allow that only with satisfactory assurance, in a business associate agreement, that the vendor will safeguard it[2]. You remain the covered entity. If a breach happens, your practice notifies patients.
The deadlines are fixed. Notifications to affected individuals must be made without unreasonable delay and no later than 60 calendar days after discovery[3]. Breaches affecting fewer than 500 individuals must be logged and reported to HHS no later than 60 days after the end of each calendar year[4]. Penalties scale with culpability: the inflation-adjusted civil money penalty runs from $145 minimum per violation in the lowest tier up to a $2,190,294 calendar-year cap per identical provision[5]. Your IT provider should help you meet these obligations, and the contract should say how.
What a good MSP contract covers
- Response times by severity, including what counts as urgent when the front desk cannot check patients in.
- Hours of coverage, and what happens at 7:30 am before clinic opens.
- Security tasks included: patching schedule, endpoint protection, email filtering, multifactor authentication, backup monitoring and restore testing.
- User changes: new staff set up before their first day; leavers removed on their last day.
- Vendor coordination: the MSP calls the EHR, phone and internet vendors on your behalf.
- Incident support: who leads, who calls whom, and how evidence is preserved.
- Documentation: a current list of devices, accounts, licenses and network settings that belongs to you.
- A signed business associate agreement and a clear exit clause with handover of all documentation.
Example clause to ask for: 'Provider will remove all system access for departing staff within four business hours of notice and confirm removal in writing.' Leavers who keep access are one of the most common and preventable risks in small offices.
How to decide
- Count what you support: users, devices, locations, systems with patient data. More than a handful of each points to an MSP or hybrid.
- Look at who handles IT today. If it is the practice manager in spare moments, name that time and decide whether to keep it.
- Decide what must happen on site, such as printers, network closets and new workstations, and what can be remote.
- Check your security basics: backups tested, multifactor authentication on email and remote access, a current device list. Gaps point to buying a security-focused service.
- Compare predictable monthly support with unpredictable emergency bills over the past two years.
Questions to ask an IT provider
Healthcare experience
How many medical or dental practices do you support, and which EHRs do they run? Can we speak to one?
Security services
Which security tools and tasks are included, and how do you show us they are working each month?
Backup and restore
How often do you test restoring our data, and how long would a full restore take?
Response
What is your response time when the front desk cannot log in at opening? Who answers the phone?
Incidents
What do you do in the first hour of a suspected breach or ransomware attack?
Agreements
Will you sign our business associate agreement, and do your subcontractors sign one with you?
Exit
If we leave, what documentation and access do we get back, and how quickly?
A hybrid that works
Example: a fictional four-provider dermatology practice named its office manager as the internal IT coordinator, with two protected hours a week. The coordinator owns the device list, approves new accounts and leavers, and is the single contact for the MSP. The MSP handles monitoring, patching, backups, help desk and vendor calls. Each month they meet for 30 minutes to review open tickets, failed backups and upcoming renewals. Neither side assumes the other is doing something that is not written down.
The first 30 days with a new provider
The start of an IT relationship sets its quality. A good provider spends the first month learning your office, not just installing monitoring software. Expect an on-site visit, a walk through each workstation and the network closet, and a written list of what they found.
- Week 1: collect admin passwords, vendor contacts and contracts; install monitoring; confirm the BAA is signed.
- Week 2: produce a device and account inventory; flag unsupported systems, shared logins and former staff accounts.
- Week 3: test a backup restore and document how long it took; check multifactor authentication on email and remote access.
- Week 4: deliver a short risk list ranked by urgency, with a plan and a cost for each item, and agree the monthly review rhythm.
If a provider cannot produce the inventory and a restore test within a month, that is useful information about how the next emergency will go. Ask for both in writing and keep them with your HIPAA documentation.
Warning signs your IT support is not working
- Nobody can tell you when backups were last restored successfully.
- Former staff accounts are still active weeks after they left.
- The same problem is reported every week and closed as fixed.
- Staff use personal devices or email to get around a broken tool.
- There is no current list of devices, accounts or licenses.
- The provider cannot say what happens during an internet outage.
Any two of these are a reason to review the contract. If you change providers, insist on a written handover of passwords, documentation and admin access before the old contract ends, and change all administrative passwords on the day the new provider takes over.
Frequently asked questions
Does a small medical office need a managed IT provider?
Not always, but most practices with more than a few users benefit from one, because a single person cannot cover help desk, security, backups and vendor coordination reliably. A hybrid with an internal coordinator is common.
Does an IT provider need a business associate agreement?
Yes, if it can access systems that hold protected health information. Sign the agreement before giving it access, and confirm its subcontractors are covered too.
If our MSP causes a breach, who notifies patients?
Your practice, as the covered entity, remains responsible for notification. The contract should require the MSP to report incidents to you quickly and support your investigation.
What should we check every month?
Backup success and a periodic restore test, patch status, accounts for anyone who left, open tickets and upcoming license or contract renewals.
References
Office of the National Coordinator for Health IT (ASTP/ONC), HHS (2024). Office-based Physician Electronic Health Record Adoption, 2008-2024 (ONC Data Brief) (opens in a new tab) ↑
Legal Information Institute, Cornell Law School (current). 45 CFR § 164.502 - Uses and disclosures of protected health information: General rules (opens in a new tab) ↑
Legal Information Institute, Cornell Law School (current). 45 CFR § 164.404 - Notification to individuals (opens in a new tab) ↑
Legal Information Institute, Cornell Law School (current). 45 CFR § 164.408 - Notification to the Secretary (opens in a new tab) ↑
Legal Information Institute, Cornell Law School (current). 45 CFR § 102.3 - Penalty adjustment and table (opens in a new tab) ↑