
HIPAA Compliant VoIP for Dental Offices: 2027 Guide
HIPAA compliant VoIP for dental offices: what to require from vendors, which features carry risk, and how to set up BAAs, encryption, and logs.
Share:
Table of contents
HIPAA compliant VoIP means an internet phone system that protects patient information on every call, voicemail, and recording. Most dental offices already run on one. Far fewer have checked how it's set up, who can play back recordings, or whether the vendor signed a business associate agreement. Those gaps matter as much as a missed call, and an AI receptionist that answers after hours adds one more vendor to vet.
This guide is the full picture for 2027. It covers what HIPAA requires, how to compare providers, which features carry risk, and how to set everything up. You'll also get the latest on the Security Rule proposal and federal enforcement.
Use the tables and checklists while you talk to vendors. They're written for owners and office managers, not IT staff.
Key terms in plain English
- VoIP: phone calls that travel over the internet instead of old copper phone lines.
- PHI: protected health information, meaning anything that links a patient to their care.
- BAA: a business associate agreement, the signed contract where a vendor promises to protect PHI.
- Encryption: scrambling data so only the right system can read it, both while it travels and while it's stored.
- Audit log: a record of who opened which voicemail, recording, or setting, and when.
- Risk analysis: your written review of where patient information could be exposed and how you reduce that risk.
- Subprocessor: another company your vendor uses, such as a transcription or hosting provider.
What Is HIPAA Compliant VoIP for a Dental Office?
HIPAA compliant VoIP is an internet phone system that a dental office has set up to protect patient information, under a signed business associate agreement. No phone system is compliant by default. The contract, the technical settings, and your team's habits all have to line up.

Three things that make a phone system compliant
1
Contract
A signed BAA from the vendor, covering recordings, voicemail, and transcripts.
2
Technology
Encryption, unique logins, role-based access, and audit logs.
3
Habits
Staff training, retention rules, and a yearly review.
What counts as patient information on a phone system?
A caller who gives their name and mentions a root canal has just shared PHI. A live conversation falls under the Privacy Rule. Once the system records it, transcribes it, or saves it as a voicemail, it becomes stored electronic data. That's where the Security Rule applies.
- Voicemails and their text transcripts
- Call recordings and AI call summaries
- Text messages and eFax documents
- Call logs that show which patient called and when
Does a small practice need to worry?
Yes. Size doesn't decide it. A dental practice that sends insurance claims electronically is a covered entity, and the ADA explains how HIPAA can apply to your practice and what to do if it does. Your phone vendor is a separate matter, covered below.
In plain English: "HIPAA compliant" isn't a label you buy. It's a signed contract, safe settings, and careful habits working together.
What Does HIPAA Require From a VoIP Provider?
HIPAA doesn't mention VoIP by name, but the Security Rule requires safeguards that apply to it: access controls, audit logs, transmission security, and a signed business associate agreement. Your vendor handles part of this and your office handles the rest.
| Requirement | What it means for your phones | Question to ask the vendor |
|---|---|---|
| Business associate agreement | The vendor signs before any patient call touches the system. | Does your BAA cover recordings, voicemail, transcripts, and subprocessors? |
| Transmission security | Calls and messages stay protected while they travel. | Which encryption protects call setup and call audio? |
| Access control | Every user has a unique login and only the access the job needs. | Can we require multi-factor logins and assign roles? |
| Audit controls | The system records who opened which voicemail or recording. | Can we export access logs on request? |
| Availability | Phones keep working during an internet or power outage. | What is your uptime commitment and failover plan? |
| Risk analysis | Your office documents phone risks and how you handle them. | Can you share security documentation for our review? |
Who is responsible for what?
Think of it as shared responsibility. The vendor secures the platform, the data centers, and the encryption. Your office controls who gets a login, how long recordings stay, and which phones can connect. Both sides can fail, and regulators look at both. The ADA's HIPAA 20 questions page explains who counts as a covered entity and how business associate agreements work.
In plain English: Ask three questions: who can listen, can you prove who did, and does the call stay protected on its way?
Do You Need a BAA With Your HIPAA Compliant VoIP Provider?
Yes. A VoIP provider that stores, records, or transcribes patient information for your practice is a business associate, and HIPAA requires a signed business associate agreement first. Without one, patient calls on that system put your practice out of compliance, even if the provider encrypts everything.
A carrier that only passes data through may fall under a narrow exception. Most cloud phone services go well beyond that because they keep voicemail and recordings. HHS's Office for Civil Rights has also said that a cloud provider holding only encrypted data is still a business associate. The ADA business associate FAQ lists when a dental practice needs one.
What should the BAA cover?
- Every type of call data, including recordings, voicemail, transcripts, and logs.
- A named list of subprocessors, such as AI, transcription, and hosting companies.
- The vendor's duty to report a breach to you, and how fast.
- What happens to your data when the contract ends.
- The features you actually use, such as texting and eFax.
What if the vendor refuses to sign?
Walk away. A vendor that won't sign can't handle patient calls for you. That applies to add-ons too, like AI call summaries, which often involve a second company.
In plain English: A BAA is a signed promise from your vendor to protect patient information the way HIPAA requires. No signature, no patient calls.
Related: Our checklist covers the red flags to look for in a vendor agreement. BAA red flags and renewal checklist →
Which VoIP Features Carry the Most HIPAA Risk?
Voicemail-to-email, call recording, AI transcripts, texting, eFax, and mobile apps carry the most risk. Each one stores or forwards patient information outside the live call. Any feature that creates a file or a message needs the same protection as a chart note.
Where patient information hides on a phone system
Voicemail-to-email
Transcripts land in staff inboxes. Use encrypted delivery or a secure portal.
Call recording
Files can name a patient and a treatment. Limit who can play them.
AI transcripts
A text copy sits with another vendor. Confirm the BAA covers it.
Texting
Patient messages need consent and secure handling.
eFax
Faxes carry records and insurance forms. Send them to a secure queue.
Mobile app
A softphone on a personal phone needs a passcode and remote wipe.
Voicemail and recordings
Staff often forward voicemail transcripts to a shared inbox. That one habit can undo good encryption. Pick a delivery method that keeps the message inside the secure system, and log who plays each file.
Texting and fax
Patients like texts. HIPAA allows them with safeguards, and our guide to texting patients under HIPAA covers consent and content. For fax, check that the incoming queue is private and that old faxes don't pile up in a shared folder.
In plain English: If a feature makes a file or a message, treat it like a patient record.
How Does Encryption Protect Dental Phone Calls?
Encryption scrambles call data so only the right systems can read it. TLS protects call setup, SRTP protects the audio as it travels, and AES-256 or similar protects voicemails and recordings in storage. Ask which standard your provider uses at each step, and get the answer in writing.
The path of a patient call, and what protects each step
1
Desk phone or app
Unique login and a passcode on mobile apps.
2
The internet
TLS for call setup, SRTP for the audio.
3
Provider platform
Access controls and audit logs for staff and vendor.
4
Stored recording
Encrypted storage, short retention, role-based playback.
What should you make of "end-to-end encryption" claims?
Ask what the phrase covers. Some vendors mean only the live audio. Others include recordings and voicemail too. The answer tells you where gaps might sit.
Under today's Security Rule, encryption is an "addressable" safeguard. You must use it or document an equivalent. HHS's 2025 proposal would make it required, so choosing a HIPAA compliant VoIP vendor that already encrypts everything saves you rework.
Don't forget your own network
- Change the default password on every desk phone and router.
- Keep router and phone firmware up to date.
- Use a business-grade firewall, not a home router.
In plain English: Encryption is a lock on the call while it travels and a lock on the file while it sits in storage.
Want phone records tied to the patient chart?
DentiVoIP, the DentalBase phone system, logs phones, texts, and fax to the patient chart. Ask any vendor, DentalBase included, for a signed BAA and the written answers in this guide.
See DentiVoIP →How Do You Compare HIPAA Compliant VoIP Providers?
Compare providers on evidence, not marketing claims: a signed BAA, named encryption standards, role-based access, exportable audit logs, and a clear subprocessor list. Ask every vendor the same questions in writing. A vague reply is a red flag.

| Question | A good answer | A red flag |
|---|---|---|
| BAA | Signed, and covers recordings, voicemail, transcripts, and texting. | "We're HIPAA ready" with no document. |
| Encryption | Named standards for call data and for stored files. | "Military-grade security" and nothing else. |
| Access | Unique logins, multi-factor sign-in, roles by job. | One shared front desk login. |
| Audit logs | Exportable, showing user, action, and time. | Call history only. |
| Subprocessors | A named list, each one under a BAA. | "Trusted partners" with no names. |
| Reliability | A written uptime commitment and a failover plan. | No outage plan. |
| Exit | Data export and deletion on request. | Recordings locked in the platform. |
How to run the comparison
- Send the same question list to three vendors.
- Ask for the BAA draft early, before pricing talks go far.
- Request the security documentation and read the subprocessor list.
- Test call quality and failover during a trial.
For pricing, features, and links to Dentrix, Open Dental, or Eaglesoft, see our guide to dental office phone systems. This guide stays on the compliance side.
In plain English: Put the same questions to every vendor in writing so the answers are easy to compare.
What Changed in HIPAA for 2026, and What Is Coming in 2027?
The current Security Rule still applies unchanged. HHS proposed a major update in January 2025, but as of this writing in November 2026, no final rule has been published. Federal planning documents point to July 2027 for final action, so prepare now without waiting.
Key dates in the Security Rule story
1
October 2024
OCR launches its Risk Analysis Initiative, focused on missing or weak security risk analyses.
2
January 6, 2025
HHS publishes its proposed Security Rule update. It isn't final.
3
October 8, 2026
OCR announces a $140,000 settlement with Shen Smiles, a Pennsylvania dental practice.
4
July 2027
Federal planning target for final action. It's not a compliance deadline.
What the proposal would change
If HHS finalizes it as proposed, the rule would drop the "addressable" label for key safeguards. The proposal also points to required encryption, multi-factor sign-in, an annual compliance audit, faster system restoration after an incident, and tighter oversight of business associates. It could change before it's final, or be withdrawn.
What OCR enforces right now
OCR's Risk Analysis Initiative keeps finding the same gap: no current, thorough risk analysis. The Shen Smiles case was about patient record access, not phones. Still, it shows that dental practices of any size get investigated. As of October 9, 2026, The HIPAA Journal reported that OCR had collected $3,170,250 in penalties from 2026 enforcement.
Your phone system belongs in that analysis. Our dental HIPAA compliance checklist shows where it fits with the rest of your practice.
In plain English: Nothing new is required yet. Encryption, unique logins, and logs are already the safe path, so setting them up now means less rework later.
Why Does Phone Reliability Belong in a HIPAA Decision?
HIPAA's Security Rule protects availability as well as privacy, so a phone system that drops calls is both a compliance problem and a revenue problem. A secure system that can't ring doesn't serve patients. Reliability and after-hours coverage belong on your vendor checklist.
What unanswered calls look like
38%
of new patient calls go unanswered during business hours, according to ADA Practice Transitions.
27%
of patient call volume arrives after hours, according to Dental Economics.
80%
of callers who reach voicemail don't leave a message, according to Forbes.
Each figure is a patient who already decided to contact you.
Each lost call also wastes the money spent to earn it. WordStream puts the average cost to acquire a new dental patient at $150-$300 through digital channels, and Dental Economics puts the average lifetime value of a general dentist's patient at $12,000-$15,000. Dental Economics breaks down the revenue impact of missed calls in more detail, and our piece on dental VoIP reliability covers the technical causes of dropped calls.
Where does an AI receptionist fit?
Dental Economics reports that 73% of dental practices plan to adopt AI tools by 2027. DentiVoice, the DentalBase AI receptionist, answers around the clock and books into your schedule. It handles patient information, so it needs the same BAA and review as any phone vendor. See our HIPAA checklist for AI receptionists and the guide to a HIPAA compliant answering service.
In plain English: A phone system that's private but down still costs you patients. Check both.
Cover the calls your team can't reach
Read how dental offices handle the phone in 2026, from front desk coverage to after-hours options.
Read the phone guide →How Do You Set Up HIPAA Compliant VoIP Step by Step?
Start with a phone risk inventory, then choose a vendor, sign the BAA, configure users and retention, train the team, and test failover. Document each step as you go. The paperwork is part of compliance, not an extra.

Before you sign
- Map every place patient information touches your phones: desk phones, apps, voicemail, recordings, fax, and texts.
- Add the phone system to your written risk analysis.
- Get the BAA, the security documentation, and the subprocessor list.
While you set it up
- Create unique logins with multi-factor sign-in and job-based roles.
- Set retention for recordings and voicemail, and switch off features you don't use.
- Secure mobile apps with passcodes and remote wipe.
After go-live
- Train the front desk on what to say and not say in voicemail greetings and call-backs.
- Test failover and run a mock request for a recording.
- Review logs, users, and the vendor list once a year.
A yearly review is easier to keep than a one-time project. ADA News ran a piece on why the end of the calendar year is a good time to review HIPAA compliance.
In plain English: Write down who can access what, and check the list once a year.
What Mistakes Make a Dental VoIP System Non-Compliant?
The most common mistakes are no BAA, shared logins, unencrypted voicemail emails, and personal phones with no security. Each one is easy to fix once you spot it. A short review of your settings usually finds them.
- One shared front desk login for everyone.
- Voicemail transcripts sent to open inboxes.
- Recordings kept forever with no retention rule.
- AI or texting add-ons that sit outside the BAA.
- Staff using personal phones or free calling apps.
- A phone system left out of the risk analysis.
What about recording consent?
A HIPAA compliant VoIP system can record calls, because HIPAA doesn't ban recording. State law decides who has to agree, and some states require every person on the call to consent. A short recorded notice at the start of the call is a common safeguard. Check your state with an attorney.
In plain English: Most problems are habits, not hackers: shared passwords and open inboxes.
What Should You Do First?
Start with the BAA. Ask your current provider this week for a signed agreement, the security documentation, and the list of subprocessors. Every other step in this guide builds on that one document.
Then add the phone system to your risk analysis and fix the settings from the mistakes list. HIPAA compliant VoIP is a project you can finish in small steps.
This guide is general education, not legal advice. Confirm details with your compliance advisor or attorney.
See how your phones and patient calls fit together
Book a free demo to walk through call handling, phone records, and the vendor questions in this guide with the DentalBase team.
Book a Free Demo →Explore more guides and tools for dental practice growth.
Browse Resources →Sources & References
Frequently Asked Questions
VoIP can be HIPAA compliant, but it isn't by default. The vendor must sign a business associate agreement and support encryption, unique logins, and audit logs. Your office then configures users, retention, and devices correctly and documents the setup in its risk analysis.
Yes. HIPAA doesn't ban recording, but recordings are stored patient information that need encryption, limited access, and a retention rule. State law decides whether everyone on the call must consent, so add a recorded notice and confirm your state's rules with an attorney.
Only with safeguards. The calling app needs a signed BAA, and the phone needs a passcode, updates, and a way to wipe it if lost. Free consumer calling apps usually don't offer a BAA, so don't use them for patient calls.
HIPAA sets six years for compliance documentation, such as policies and risk analyses, but it doesn't set one retention period for recordings. State record laws and your own policy decide. Keep only what you need, and delete the rest on a schedule.
Your BAA should require the provider to report the breach to you quickly. Your practice then assesses whether patient notification is required, and HIPAA generally requires notice without unreasonable delay and within 60 days of discovery. Check the BAA's reporting timeline before you sign.
Yes, if it handles patient calls or information. An AI receptionist creates recordings, transcripts, or summaries, so the vendor and any subprocessors it uses need to be covered by a signed BAA. Add the tool to your risk analysis like any other phone vendor.
Was this article helpful?
Written by
DentalBase Team
Expert dental industry content from the DentalBase team. We provide insights on practice management, marketing, compliance, and growth strategies for dental professionals.

