FAQs about IT services for healthcare practices
Are you a HIPAA-compliant IT provider? Do you sign a BAA?
Yes. We sign a Business Associate Agreement with every healthcare client before we touch a system that handles PHI, and we operate as a covered Business Associate ourselves. The BAA is the legal floor. The actual work is the controls underneath it: encryption, access management, audit logging, breach response readiness, vendor management, and the documentation a Security Risk Analysis will ask for.
We had a lost laptop. Was it a breach? Do we have to report?
It depends on whether the laptop was fully encrypted with a recognized standard at the moment it was lost. If it was, HIPAA treats the data as unreadable and unusable, and no reporting is generally required. If it was not, you are inside the 60-day breach notification clock for individuals (or 60 days from year-end for breaches under 500 people if you choose annual reporting). Either way, we run the forensic checklist, document what was on the device, and produce the artifact you need for OCR if it gets asked for.
Our EHR vendor handles security. Why do we still need an MSP?
The EHR vendor handles the security of the EHR application and the data it stores. They do not handle the laptops, the workstations at the front desk, the back-office printer that scans charts, the wifi network the practice runs on, the email system the staff uses, or the backups of anything outside the EHR. That entire surface area is the practice's responsibility, and it is most of the actual HIPAA risk surface. That is where an MSP fits.
We are a small practice (3 providers). Is full HIPAA compliance really required?
Yes. HIPAA does not have a small-practice exemption. The Security Rule applies the same way to a three-provider practice as to a hospital, and the OCR fines on small practices have not been theoretical. What does scale with practice size is the level of effort: a three-provider practice does not need a CISO, but it does need a Security Risk Analysis, a written set of policies and procedures, encryption everywhere, MFA everywhere, training, and a documented incident response posture.
We do telehealth. What changes for the IT side?
Telehealth widens your environment by every endpoint that connects to it: home laptops, personal phones, vendor platforms, and the network paths between them. The IT side is endpoint hygiene on whatever devices providers use, MFA on the telehealth platform, a BAA with the platform vendor, encrypted recordings (or no recordings if your policy says so), and a documented patient-consent workflow that captures the right disclosures. The HIPAA enforcement discretion that covered casual telehealth tools during the public health emergency is gone; the standard rules apply now.