HIPAA and AI Voice Agents: What Healthcare Practices Need to Know

Clinic front desks are some of the busiest phone lines anywhere: appointment bookings, reschedules, refill requests, directions, insurance questions — often all at once, while patients are standing at the counter. An AI voice agent can take a lot of that load. But healthcare comes with an extra question: what about HIPAA?

Here's what healthcare practices in the US need to understand before putting AI on the phones.

First: there's no such thing as a "HIPAA certified" AI

You'll see vendors describe themselves as a "HIPAA compliant AI voice agent." It's worth knowing that there's no official government certification for HIPAA compliance. Compliance depends on how a system is built, configured, contracted, and operated in your practice — not just on the underlying technology.

So the better question isn't "is this tool HIPAA compliant?" It's "can this be deployed in a way that supports our HIPAA obligations — and will the vendor sign the paperwork to back that up?"

When HIPAA applies to your voice agent

If your practice is a covered entity and the voice agent creates, receives, stores, or transmits protected health information (PHI) on your behalf — patient names tied to appointments, reasons for visits, medication details, insurance info — then HIPAA's rules apply to how that data is handled. In practice, almost any scheduling or reminder agent for a clinic touches PHI.

The essentials

1. Business Associate Agreements (BAAs)

Any vendor that handles PHI on your behalf is generally a business associate and needs a signed BAA. That includes the company building and running your voice agent — and, through them, the relevant sub-processors in the chain (telephony, speech, language model, and hosting providers that touch PHI). Ask directly: who touches the data, and is there a BAA covering each step?

2. Minimum necessary

The agent should only collect and access the information it actually needs to do its job. A booking agent needs a name, date of birth, and a preferred time. It probably doesn't need the full medical history.

3. Access controls and audit logs

Only authorised people should be able to access call recordings, transcripts, and patient data — and there should be a record of who accessed what, and when.

4. Encryption

PHI should be encrypted in transit and at rest. That covers call audio, transcripts, and any data passed to your EHR or scheduling system.

5. Retention and deletion

Decide how long recordings and transcripts are kept, and make sure they're deleted when they're no longer needed, in line with your policies.

Design choices that reduce risk

• Verify identity before sharing anything specific about a patient's appointment or care.
• Keep clinical questions out of the agent's scope — route them to staff.
• Send urgent or emergency situations to a human (or emergency services guidance) immediately.
• Avoid reading sensitive details aloud unless the caller has been verified.
• Disclose clearly that the caller is speaking with an AI assistant.

The safest healthcare voice agents are deliberately narrow: they're excellent at scheduling and reminders, and they know exactly when to hand the call to a person.

What about EHR integration?

Connecting the agent to your EHR or practice management system is what turns it from a message-taker into something that can actually book appointments. It's also where a lot of the data handling happens, so integration should be scoped with security in mind: least-privilege access, only the fields the agent needs, and logging of every action.

Questions to ask any vendor

• Will you sign a BAA? Which sub-processors handle PHI, and are they covered?
• Where is call data stored, and for how long?
• Who on your team can access recordings and transcripts?
• How is data encrypted in transit and at rest?
• How does the agent handle clinical, urgent, or sensitive calls?

For every healthcare engagement, we build data handling and disclosure into the project scope from day one. If you run a practice and want to explore it, we're happy to walk through how it would work with your specific systems.