Clinic receptionist answering a VoIP phone call

No VoIP phone system is HIPAA compliant on its own. Compliance comes from how the service is built, what your provider agrees to in writing, and how you configure and use it. If your practice or company handles patient information over a VoIP line, you need a signed Business Associate Agreement (BAA) where one applies, technical safeguards on the system, and documented risk management. This guide covers each piece, including call recording, voicemail and the state consent rules that Ohio and Michigan owners ask about most.

Mavericks Office Solutions
Make Business Calls More Secure
Mavericks provides voice communication solutions alongside cybersecurity and managed IT services for businesses handling sensitive information.

Explore IT and voice solutions

TL;DR

  • HIPAA does not certify phone products. A VoIP system is compliant only when the provider’s contract and your configuration meet the Security Rule.
  • VoIP that carries electronic protected health information (ePHI) falls under the Security Rule. Voicemail, recordings and transcripts are in scope too.
  • A provider that creates, receives, maintains or transmits PHI for you is a business associate and must sign a BAA.
  • Call recording raises two separate questions: HIPAA safeguards for the stored audio, and state consent law. Ohio and Michigan differ.
  • Compliance is shared: the provider supplies the tools, and you set them up, train staff and document everything.

Table of Contents

Are VoIP phones HIPAA compliant?

VoIP can be used by covered entities, but the technology itself carries no compliance label. The Department of Health and Human Services (HHS) says covered health care providers may use audio-only and other telehealth technologies when they comply with the applicable HIPAA Rules. When a covered entity uses VoIP or another electronic technology to transmit ePHI, the Security Rule applies to that transmission.

That is why marketing claims such as “HIPAA certified phones” should not drive your decision. What matters is whether the service lets you meet each safeguard, and whether the vendor will accept its share of responsibility in a contract.

Who is covered? HIPAA applies to covered entities (most health care providers, health plans and clearinghouses) and to their business associates. If you run a dental office, a behavioral health practice, a billing company or an IT firm that supports clinics, your phone traffic may well include PHI: appointment details, diagnoses, insurance questions, test results left on voicemail.

Are VoIP phones HIPAA compliant?

When HIPAA applies to phone calls and when it may not

Not every phone call triggers the same rules. HHS draws a useful line:

  • Audio-only over a traditional landline. HHS says this is outside the Security Rule because the information transmitted is not electronic. The Privacy Rule’s reasonable safeguards still apply, such as speaking where others cannot overhear.
  • VoIP or other electronic transmission. The Security Rule applies because the call travels as data over a network.
  • Recorded or transcribed sessions and stored audio messages. HHS names these as technologies that need Security Rule consideration when covered entities use them.

Two practical points follow. First, most businesses that moved to cloud phones are now on VoIP whether they think about it or not, so assume the Security Rule applies. Second, even if some calls are voice-only, the voicemail box, the call log, the recording archive and the voicemail-to-email feature are stored electronic data.

HHS also notes that a patient’s choice of phone system does not bind the patient to HIPAA, and a covered entity is not responsible for privacy or security after the information reaches the patient’s phone or device. Your responsibility covers your side of the call.

The Business Associate Agreement

A BAA is the contract that makes your VoIP provider answer for the PHI it touches. HHS says a business associate relationship exists when a vendor creates, receives, maintains or transmits PHI on your behalf. A VoIP or unified communications provider that hosts your voicemail, stores recordings or runs your cloud PBX typically falls into that category.

There is a narrow exception. HHS says no BAA is needed for a telecommunications provider that acts only as a conduit, with transient access, no routine access to PHI, and no creating, receiving or maintaining of PHI. A hosted phone platform that stores messages and recordings is usually not in that position.

What a BAA must contain

Per HHS, a BAA must describe the permitted and required uses and disclosures of PHI, prohibit unauthorized ones, and require the business associate to meet applicable Privacy Rule obligations. The Security Rule side adds more. According to HHS’s Security Rule summary, the contract must:

  • document satisfactory assurances from the business associate;
  • require compliance with the Security Rule;
  • bind relevant subcontractors to comparable obligations;
  • require reporting of security incidents and breaches as applicable.

Read the BAA with a short checklist: Does it cover voicemail, recordings and transcripts, or only “voice traffic”? Does it name who hosts the data and who the subcontractors are? What are the breach-notice timelines? What happens to stored data when you leave? A BAA you have not read is not much protection.

Safeguards a HIPAA-ready phone system needs

The Security Rule is risk-based. HHS’s summary of the rule describes administrative, physical and technical safeguards governed by risk analysis and risk management. Under 45 CFR 164.306, covered entities and business associates must protect the confidentiality, integrity and availability of ePHI, guard against reasonably anticipated threats and impermissible uses, and ensure workforce compliance.

HIPAA safeguards and ePHI protection objectives

The rule also lets you scale safeguards to your size and risk. But “addressable” does not mean optional. Under the same section, you must assess whether an addressable safeguard is reasonable and appropriate, implement it or an equivalent alternative when it is, and document your decision.

Technical safeguards

45 CFR 164.312 sets the technical requirements that map directly onto a phone system:

Safeguard What it means for VoIP
Access control and unique user ID Every user has their own login to the softphone, admin portal and voicemail. No shared admin accounts.
Emergency access procedure A documented way to reach ePHI, such as recordings or voicemail, during an emergency.
Audit controls Logs showing who listened to, downloaded or deleted recordings and changed settings.
Integrity protections Controls that keep ePHI from being altered or destroyed improperly.
Person or entity authentication Strong sign-in, ideally with multi-factor authentication for admins and anyone who can reach recordings.
Transmission security Encryption for calls and messages in transit, plus protection against interception.

Strong authentication deserves attention because phone admin portals are a common way into an organization. For a closer look at how security keys and multi-factor login map to HIPAA’s administrative expectations, see this guide on HIPAA and MFA requirements.

Physical safeguards

45 CFR 164.310 covers facility access, workstation use and security, and device and media controls. For phones, that means desk phones and softphone laptops are part of your inventory. Required disposal and media re-use procedures apply when you retire a handset, a mobile device or a server that held ePHI.

Network and configuration basics

HIPAA does not hand you a VoIP configuration template, so a general security baseline helps. Our VoIP security checklist for small businesses walks through seven steps aligned with DHS and NIST guidance, including securing admin access, segmenting voice traffic and keeping firmware current. Reliability belongs in the plan too, since ePHI availability is one of the three things HIPAA asks you to protect. See our guide to VoIP failover during an outage.

Call recording, voicemail and transcripts

Recording is where most HIPAA phone questions land, and it involves two different bodies of law.

HIPAA: protect the stored audio

A recording of a patient call that includes PHI is ePHI once stored. HHS says your risk analysis and risk management must address, for recorded or transcribed sessions and stored audio messages, interception risk, encryption capability, unauthorized access to stored ePHI, authentication, and automatic session termination or device locking.

In practice, set these controls:

  1. Decide whether you need to record at all. If the purpose is quality or training, limit it to the lines where it is needed.
  2. Restrict who can play back or export recordings, and log every access.
  3. Confirm recordings and voicemail are encrypted in storage, not only in transit.
  4. Turn off voicemail-to-email or transcription features, or route them to secured mailboxes, unless your risk analysis supports them. Plain email is a common leak path.
  5. Set a retention and deletion schedule, and write it down.
  6. Make sure the BAA covers wherever the recordings live.

HIPAA does not itself say whether you must tell callers you are recording. State wiretap laws do, and they vary. Check these with your attorney, because your callers may be in other states.

  • Ohio: a one-party consent state under Ohio Rev. Code 2933.52(B)(4). A participant in a call can generally record it, though the exception does not cover recording made for a criminal or tortious purpose.
  • Michigan: the eavesdropping statute prohibits recording private conversations without consent of all parties by someone who is not a party to them, and courts disagree on whether a participant may record alone. Because of that uncertainty, the safer course is to get everyone’s consent.

The simplest workable habit for either state: play a short recording notice at the start of calls and have staff say it when they place calls. It protects you when a caller is in an all-party consent state and it builds patient trust. Mention in your notice of privacy practices how you handle recorded calls where it applies.

So is a voice recording a HIPAA violation? Not by itself. A violation arises when the recording is stored, accessed or shared without the required safeguards, or without a permitted purpose.

Is Google Voice or a consumer phone app HIPAA compliant?

The same test applies to any product, including free or consumer tools: does the vendor act as a business associate, will it sign a BAA covering the service you use, and can you configure it to meet the safeguards above? If the answer to the BAA question is no, do not use that service for calls, texts or voicemail containing PHI. The same goes for a VPN: a VPN may help with transmission security, but it is one control, not a compliance status.

Your shared responsibility

The National Consortium of Telehealth Resource Centers stresses that the provider supplies capabilities and contractual assurances, while the healthcare organization must configure, use, train, monitor and document the system. Its recommended steps match what auditors expect to see:

  1. Run an initial risk assessment and repeat it regularly.
  2. Select a VoIP solution that can meet your needs and validate its security settings.
  3. Use authentication and encrypted network communications.
  4. Encrypt stored data.
  5. Train staff on what they may say and store over the phone.
  6. Document policies and activity.

If you are building a broader program, our 90-day HIPAA compliance IT plan shows where the phone system fits among risk analysis, access control and incident response. A written incident response plan matters here, since your BAA will require reporting of security incidents.

Questions to ask any VoIP provider

Use this list in a sales call or contract review:

  • Will you sign a BAA that covers voice, voicemail, recordings, transcripts and faxes?
  • Where is data stored, and who are your subcontractors?
  • Are calls encrypted in transit, and are recordings and voicemail encrypted at rest?
  • Can I enforce multi-factor authentication and unique logins for every user?
  • Can I pull audit logs on recordings and admin changes?
  • How do I export or delete data when the contract ends?
  • How does 911 location work for remote and multi-site staff? Our E911 guide for VoIP explains what to confirm.
  • Who answers when something breaks, and how fast?

If you still send faxes with patient records, include them in the review. Our guide to fax over VoIP covers how to run it.

Our perspective

Most of the HIPAA phone problems we see are not exotic. They are a shared admin password on the phone portal, voicemail-to-email going to an unsecured inbox, or recordings nobody has looked at in three years. The phone system gets treated as separate from IT, so no one owns its risk.

We think that is the wrong way to run it. Voice, security, Microsoft 365, cloud hosting and the help desk touch the same patient data, and a gap in one becomes a gap in all of them. That is why we operate as an outsourced IT department: one team looks at the phone system, the network, the logins and the backups together, and the risk analysis reflects how your office really works.

Support matters in a compliance setting, too. When a user is locked out or a device goes missing, you want someone who answers quickly and knows your environment. Our help desk is local and USA-based, with an average response under 12 minutes, and we do not route calls offshore.

If you are a small practice or a business serving health care clients in Ohio or Michigan, start with the risk analysis, then choose the phone system that fits it. Not the other way around.

Jeffrey

How Mavericks can help

Mavericks Office Solutions runs your technology as an outsourced IT department: managed IT support, cybersecurity, cloud hosting, Microsoft 365 and business phone service, supported by a local help desk. If you want your voice system reviewed alongside the rest of your environment, start with our UCaaS and VoIP service and our cybersecurity services.

Mavericks Office Solutions

For a wider view, see our managed IT services or contact our team to talk through your phone setup.

FAQ

Are phones HIPAA compliant?

No phone is compliant by design, because HIPAA does not certify products. A system becomes compliant in use when it meets the Security Rule safeguards, your risk analysis supports it, and a BAA is in place where the provider handles PHI. Traditional landline audio-only calls sit outside the Security Rule, but the Privacy Rule’s reasonable safeguards still apply.

Do I need a BAA with my VoIP provider?

Yes, if the provider creates, receives, maintains or transmits PHI for you, which is typical for hosted phone services with voicemail and recording. HHS excepts a telecommunications carrier acting purely as a conduit with only transient access. Ask your provider in writing which category it falls into.

Is call recording a HIPAA violation?

No. Recording is allowed when you protect the stored audio as ePHI, limit access, log it and cover it in your BAA and risk analysis. Separately, state law governs consent: Ohio is a one-party consent state, while Michigan’s law is less settled, so getting all parties’ consent is the safer path.

Can voicemail contain PHI?

Yes. HHS lists messaging services that store audio messages as technologies needing Security Rule consideration. Secure the voicemail box with unique credentials, encrypt stored messages, and control voicemail-to-email forwarding.

Sources