Do you still need IT support with a cloud EHR?
By David Freeland4 min read · 
The email that looked like your EHR company
When your clinic moved its EHR to the cloud, the server left your back office. Your EHR company took over its own servers and their security. It’s natural to feel like everything else moved with them.
Now picture a busy Monday. An email lands in the shared inbox at the front desk. It looks like it’s from your EHR company, and it says the password has to be reset today. Your front desk clicks the link and types in the login. Nothing seems wrong.
Here’s what did happen. The link opened a fake sign-in page, and the login went straight to a criminal. Now someone outside your clinic can sign in to your EHR as your front desk and open patient records. Your EHR company’s servers were never broken into. They didn’t need to be.
So it’s fair to ask: “Our EHR is in the cloud. Why do we still need IT support?” The answer comes down to what actually moved.
What moved to the cloud, and what didn’t
Think of your EHR company like the landlord of your building. The landlord keeps the building maintained and the main entrance locked. But who gets a key to your suite, and whether a back door gets left open, is up to you.
A cloud EHR works the same way. Your EHR company runs the servers that hold your patient records and keeps its software up to date. Everything on your side of the door stayed with you:
- Your devices: every computer, laptop, tablet, and phone that opens the EHR. They usually remember the logins.
- Your logins: who signs in, and whether each person has a login of their own.
- Your network and email: the Wi-Fi, the internet connection, the printers, and your clinic email.
Each of those devices is a door into your accounts. Criminals rarely need to walk into your clinic. They get in over the internet, with a stolen password or malware. And when one of those devices slows down or drops off the Wi-Fi, fixing it isn’t your EHR company’s job either.
When nobody watches those doors, problems can sit unnoticed for weeks, months, or longer. While assessing the devices of a prospective new customer, Bakerford® found an unauthorized back door into a system. It had been open for more than a year, and no one knew it was there.
Where HIPAA draws the line
HHS, the federal agency that enforces HIPAA, says a cloud company that stores patient records for your clinic is your business associate. It signs an agreement with you, and it’s directly liable for following the HIPAA rules that apply to it.
But HHS also says a cloud company isn’t responsible for failures caused only by what its customer did or didn’t do. Some protections, like sign-in checks and a separate login for each person, “may be the responsibility of the customer.”
The rest of the HIPAA Security Rule still applies to your clinic, too:
- 45 CFR § 164.310(c) says your clinic must protect every computer that can open patient records, so only the right people can use it. Under § 164.304, that includes laptops and other devices that do the same job.
- 45 CFR § 164.308(a)(1)(ii)(A) requires an accurate and thorough risk analysis. That’s a careful look at where your patient information lives and what could put it at risk. HHS says it covers all of your electronic patient information, wherever it’s kept.
- 45 CFR § 164.308(a)(1)(ii)(D) requires your clinic to look over the activity on its systems on a regular schedule, using records like audit logs and access reports.
HHS enforces these rules with small practices, too. In April 2025, a small New York neurology practice paid $25,000 to settle with HHS’s Office for Civil Rights (OCR) after ransomware locked its network. OCR found the practice had failed to do an accurate and thorough risk analysis.
The three jobs that stayed with your clinic
A cloud EHR leaves your clinic three jobs. Here’s how to cover each one:
- Lock every door: Keep every computer, tablet, and phone that opens your EHR updated and encrypted. Give each person a login of their own, with multi-factor authentication (MFA). MFA means signing in takes two proofs, like your password plus a code from your phone.
- Watch around the clock: Attackers count on nights and weekends. In the attacks its own teams handled, the security company Sophos found that 88% of ransomware was set off outside business hours. Ask your IT company who watches your devices at night and on weekends.
- Teach your team the tricks: Show your front desk what a fake login email looks like, and make it normal to stop and ask before clicking. HHS lists basic cybersecurity training and email security among its essential cybersecurity goals for healthcare. Ask your IT company how they train your staff and screen out scam emails.
Your EHR company takes care of its servers, so make sure someone is taking care of everything on your side of the door.
Last reviewed November 8, 2026.
References & statutory citations
- U.S. Department of Health and Human Services (HHS): Guidance on HIPAA & Cloud Computing (Office for Civil Rights, content last reviewed December 23, 2022). (opens in a new tab)
- U.S. Department of Health and Human Services (HHS): 45 CFR Part 164 Subpart C — Security Standards for the Protection of Electronic Protected Health Information (§§ 164.304, 164.308 and 164.310; eCFR, up to date as of October 23, 2026). (opens in a new tab)
- U.S. Department of Health and Human Services (HHS): Guidance on Risk Analysis (Office for Civil Rights, content last reviewed August 12, 2026). (opens in a new tab)
- U.S. Department of Health and Human Services (HHS): HHS Office for Civil Rights Settles HIPAA Ransomware Cybersecurity Investigation with Neurology Practice (press release, April 25, 2025). (opens in a new tab)
- Sophos: Nowhere, man: The 2026 Active Adversary Report (John Shier, Hilary Wood and Angela Gunn, February 2026; vendor research from Sophos’s own incident response cases). (opens in a new tab)
- U.S. Department of Health and Human Services (HHS): HPH Cybersecurity Performance Goals (HHS 405(d) Cyber Gateway, voluntary goals, no date shown). (opens in a new tab)