Do you sign Business Associate Agreements (BAAs) with our medical practice?
Yes — that's standard practice for every medical client we sign. The HIPAA Security Rule requires any service provider with access to Protected Health Information (PHI) to execute a written BAA with the covered entity. Many generic MSPs refuse because the BAA puts them on the hook for breach liability. We sign because doing IT for healthcare without one is doing it wrong — both for HIPAA compliance and for our own E&O posture.
Have you worked with HIPAA-covered medical practices before?
Yes. We support a range of Arkansas healthcare clients — solo physician offices, multi-provider clinics, dental practices, mental-health practices, and specialty groups. We build the IT and security side around HIPAA from the start: documented access controls, encrypted email and storage, MFA on every account with PHI access, logged file activity, off-site encrypted backups, and the technical safeguards the HIPAA Security Rule actually names. We're not the auditor of record — we're the team that gets the technical environment ready for one.
What EMR/EHR systems have you supported?
On the IT and security side: Epic, Athena Health, eClinicalWorks, NextGen, AdvancedMD, Practice Fusion, Dentrix, Eaglesoft, and a handful of others. We don't replace your EMR vendor's implementation team — we work alongside them on the IT plumbing: network and bandwidth sizing, firewall rules, MFA enrollment, single sign-on, certificate management, off-site backup integration, endpoint security, and the documentation HIPAA risk assessments expect to see for any system processing PHI.
How do you handle PHI in backups and email?
Backups: encrypted in transit and at rest, stored off-site with documented retention that meets HIPAA's 6-year minimum for records of compliance activities. Email: TLS in transit, advanced threat protection on inbound (the #1 attack vector for healthcare), encrypted-email enforcement for outbound messages containing PHI, and email retention policies that align with your record-keeping obligations. Every configuration is documented so it shows up on your risk assessment without scrambling.
What's your role if we have a breach or suspected breach?
We're the technical first-responders. On suspected breach: contain the scope (isolate affected systems, preserve forensic evidence, change credentials), identify what PHI was accessed and by whom, document the timeline, and provide the technical record your privacy officer and outside legal counsel need to determine whether it's a HIPAA-reportable breach. We don't make the breach-notification call — that's your privacy officer and attorney — but we make sure they have what they need to make it correctly within HHS's 60-day window.
Can you help us prepare for an HHS OCR inquiry or annual HIPAA risk assessment?
Yes, on the IT and security side. We produce the documentation an OCR investigator or HIPAA risk assessor expects from your technical environment: access control inventories, audit logs, encryption status, BAA register, incident log, training records, backup-and-recovery proof, and the configuration evidence behind your administrative, physical, and technical safeguards. We work alongside your compliance officer or outside HIPAA consultant — they make the legal and policy calls; we keep the technical evidence current and accessible.
Do you provide HIPAA awareness training for our staff?
Yes. Annual HIPAA awareness training is a HIPAA Security Rule requirement (45 CFR §164.308(a)(5)). We deliver it through monthly micro-training modules and quarterly phishing simulations specifically built around healthcare scenarios — fake EMR password reset emails, fake billing-portal logins, fake patient-record request scams. Each module is short, the training records are documented (so they're available for a risk assessment), and the phishing-simulation reports show measurable improvement in your team's detection rate over time.
How are you different from a healthcare-IT consultancy?
Most healthcare-IT consultancies deliver a written report and an invoice, then leave you to find someone who'll actually implement the controls. Most generic MSPs configure controls without understanding why HIPAA requires a particular configuration. We do both — the gap assessment AND the implementation AND the ongoing operational work — so your documentation, your controls, and the institutional knowledge stay in one place. Plus we're locally based in Arkansas with same-day on-site response across 10 counties, not a national consultancy billing $300+/hour out of a different time zone.