HIPAA guide · Checklist
HIPAA-compliant VoIP: the 12-point checklist for practices
What a phone system has to do before it can safely handle patient calls, voicemail and recordings, and the exact question to ask any vendor on each point.
By the Stratus VoIP team · Updated
The short answer: a VoIP phone system is HIPAA compliant for your practice when the vendor signs a Business Associate Agreement covering every feature that stores patient information, everything stored (voicemail, recordings, texts, faxes, transcripts) is encrypted in transit and at rest, each person has their own login with multi-factor sign-in, every access is logged, and the system is part of your practice's risk analysis. A plain landline sits outside the HIPAA Security Rule. VoIP and cloud phone systems sit inside it (HHS).
No phone system is "HIPAA certified." HHS doesn't certify or endorse products. What you're really checking is whether a vendor will sign a BAA and give you the safeguards to meet your own obligations. Here's the checklist we use, and the question that separates a real answer from marketing.
01A signed Business Associate Agreement that names what it covers
Why it matters. A vendor that stores voicemail, call recordings, transcripts, texts or faxes for you is a business associate, not a pass-through "conduit." HHS says so directly in its audio-only telehealth guidance and its cloud computing guidance.
Ask your vendor: "Does your BAA cover voicemail, recording, texting, fax, transcription, AI and analytics on the plan I'm buying?"
02BAAs that reach the vendor's own subcontractors
Why it matters. Your vendor's hosting provider, texting carrier and transcription service touch the same data. HHS requires business associates to have their own agreements with subcontractors.
Ask your vendor: "Which subcontractors handle our data, and do you hold a BAA with each one?"
03Calls encrypted in transit
Why it matters. Transmission security is a Security Rule standard. Encryption that follows NIST guidance is what turns intercepted data into "secured" information under HHS's breach guidance.
Ask your vendor: "Do desk phones, computer apps and mobile apps encrypt signaling (TLS) and audio (SRTP)?"
04Stored data encrypted at rest
Why it matters. Voicemail, recordings and transcripts live on a server somewhere. Encrypting them per NIST SP 800-111 can keep a lost or stolen file out of breach-notification territory (HHS).
Ask your vendor: "Are voicemail, recordings, transcripts, faxes and backups encrypted at rest, and who holds the keys?"
05A unique login for every person, plus multi-factor sign-in
Why it matters. Unique user identification is a required access control. Multi-factor authentication is part of HHS's proposed 2025 Security Rule update, so plan for it now.
Ask your vendor: "Can we require MFA for every admin and user, and auto-log-off idle sessions?"
06Role-based access to recordings and analytics
Why it matters. HIPAA's minimum-necessary standard means the person answering phones doesn't automatically need to replay every recorded call.
Ask your vendor: "Can front-desk staff take calls without being able to play or download recordings?"
07Audit logs you can actually read
Why it matters. Audit controls are a Security Rule standard, and logs are how you prove a breach didn't happen.
Ask your vendor: "Can I see who played, downloaded, shared or deleted any recording or voicemail?"
08Retention and deletion you control
Why it matters. HIPAA doesn't set a retention period for recordings (state law may), but you must be able to keep what you need and delete the rest securely. HIPAA policies themselves are kept six years (HHS).
Ask your vendor: "Can we set how long recordings and voicemail are kept, and confirm when they're deleted?"
09Voicemail email and texting that don't leak details
Why it matters. A voicemail attached to an ordinary email is patient information in a new place. HHS allows messages to patients but says to limit what you disclose.
Ask your vendor: "Can voicemail emails be notification-only, without the audio attached?"
10Breach terms in writing
Why it matters. A business associate must tell you about a breach without unreasonable delay and within 60 days, and you then have your own deadlines to notify patients (HHS Breach Notification Rule).
Ask your vendor: "What notification timeline does your BAA commit to, and what details will you give us?"
11A plan for outages
Why it matters. A contingency plan (backups, disaster recovery, emergency operations) is required, and the proposed rule adds a 72-hour restoration target.
Ask your vendor: "If our internet or your data center goes down, where do calls go, and how fast do you restore?"
12The phone system in your risk analysis, and staff trained on it
Why it matters. Risk analysis is required and is a top enforcement focus for the HHS Office for Civil Rights (HHS guidance). While you're at it, check your state's call-recording consent law. That's not HIPAA, but practices often miss it.
Ask your vendor: "Will you give us the documentation we need for our risk analysis?"
What this costs if you get it wrong
HIPAA civil penalties run from $145 to more than $2.19 million per violation category per year (HHS, 2026 amounts). State attorneys general enforce HIPAA too. In 2024, an Indiana dental group agreed to pay the state $350,000 over a ransomware attack it allegedly failed to report (HIPAA Journal).
How Stratus answers the checklist
Stratus VoIP signs a BAA with every healthcare customer, and we built the platform for practices that live on the phone. In a 20-minute demo we'll go through all twelve items on your own call flow, then show you call analytics and pricing: $15 per phone a month.