HIPAA and AI Voice Agents: The Checklist Before You Sign

Summarize with AI
Practice manager reviewing a business associate agreement at her desk in a medical group office
In this article
Lorem ipsum dolor sit amet
Vocca actually answers calls like that.

Key takeaways

  • An AI voice agent that handles patient calls is a HIPAA business associate. The vendor signs a BAA before the first real call, pilots included.
  • No product is "HIPAA certified": HHS certifies no product and recognizes no private certification as proof of compliance.
  • Five BAA clauses carry most of the risk: permitted uses, scope, subcontractors, breach notification and the end of the contract.
  • A SOC 2 or ISO 27001 certificate often belongs to the hosting provider, not to the vendor. Ask whose it is.
  • Consent to record calls is set by state law, and about a dozen states require everyone on the call to agree.
  • Send the 15 questions at the end of this article to every vendor, and ask for written answers.

An AI voice agent that answers your patient calls hears names, dates of birth, symptoms and the reason for each visit. Under HIPAA, that makes the vendor a business associate of your practice, and the contract that governs it is your responsibility.

HHS does not certify any product as "HIPAA compliant". So when a vendor calls itself a HIPAA-compliant AI receptionist, that is where your review starts. This checklist covers what to check before the first live call, and ends with 15 questions you can send to every vendor on your shortlist. It is an evaluation guide, not legal advice: your compliance officer or counsel should review the final agreement.

Is an AI voice agent a business associate under HIPAA?

Yes. HIPAA treats any vendor that creates, receives, maintains or transmits protected health information (PHI) for a covered entity as a business associate. An AI voice agent that books appointments does all four in a single call:

  • it receives PHI when it hears the caller;
  • it creates PHI when it writes the appointment into your scheduling system;
  • it maintains PHI when it keeps a recording or a transcript;
  • it transmits PHI when it sends the confirmation.

The "conduit" exception won't help here. HHS reserves it for transmission-only services, like the phone carrier that carries the call from one end to the other. It even holds that a cloud provider storing encrypted PHI it cannot read is a business associate (HHS, cloud computing guidance). An agent that understands the conversation and acts on it is far past that line. The same goes for a live answering service that takes patient messages, which is why the BAA question comes up on both sides when you compare an AI receptionist with an answering service.

So the BAA has to be signed before the first real patient call, pilot included. A pilot with real patients at a single location is still real PHI.

What the BAA must actually cover

HIPAA lists the clauses a BAA must contain (45 CFR 164.504(e)). Most of them are standard. For an AI voice agent, five carry the risk, and they deserve a slow read.

  1. The permitted uses say what the vendor may do with PHI. This is where it would reserve the right to reuse your call data, for instance to train or improve its models. If it wants that right, the clause should say so plainly and set limits. "Improving our services", with nothing after it, is not a limit.
  2. The scope should name every module you turn on: inbound calls, outbound reminders, text messages, analytics. A contract that covers one product while you use three leaves two of them outside.
  3. The subcontractors matter because an AI agent rarely works alone. Hosting, speech recognition, the language model, text messaging: each provider that handles PHI on the vendor's behalf must accept the same restrictions in its own written agreement (45 CFR 164.502(e)). Ask for the list, in writing.
  4. On breach notification, the law only sets a ceiling: without unreasonable delay, and no later than 60 calendar days after discovery (45 CFR 164.410). Many groups negotiate a shorter deadline.
  5. At the end of the contract, the vendor must return or destroy all the PHI it still holds, in any form. For a voice agent, "any form" covers recordings, transcripts, call summaries, logs and backups.
The BAA chain behind one patient call
Your practiceCovered entity
AI voice agent vendorBusiness associate: hears, books, records, confirms
Subcontractor BAAs
HostingStores recordings, transcripts, logs
Speech recognitionTurns the call audio into text
Language modelUnderstands the request
Text messagingSends confirmations and reminders

Phone carrier: outside the chain. It only carries the call, so HHS treats it as a conduit. Every other link handles PHI and needs a written BAA.

Where your patients' call data lives

One call leaves several traces:

  • the audio recording;
  • a transcript;
  • the appointment written into your EHR or scheduling software;
  • the call summary sent to your team;
  • technical logs.

For each of them, ask where it is stored, how long it is kept, and who decides when it is deleted.

HIPAA doesn't require US storage. HHS allows PHI on servers abroad under a BAA, and notes that the risk depends on the location (HHS FAQ). Many groups still write US hosting into their contracts.

The sharper question is about access from outside the United States. Can anyone reach your data from abroad, for support, billing or engineering? Plenty of vendors have international teams and still meet the requirement. What you need is a precise answer, covered by the BAA. A vague one is the warning sign.

Who can access PHI, and how

The Security Rule expects each person to see only what their job requires, and every access to leave a trace. With an AI voice agent, that applies on your side and on the vendor's.

On your side, check two things. Can you set roles per user? A scheduler doesn't need every recording. And can you see who listened to a call or opened a transcript in the access logs?

On the vendor's side, ask which employees can reach call data, when, and how that access is logged. "The whole team has access" is the answer you don't want to hear.

SOC 2, ISO 27001, HITRUST: what each one proves, and what it doesn't

A certification is evidence of good security practice. It doesn't make a vendor HIPAA compliant, and it never replaces the BAA. HHS says it does not recognize private certifications under the Security Rule (HHS FAQ), and that a business associate cannot be certified in place of a contract (HHS FAQ).

The three names you'll see most often measure different things:

  • SOC 2 is an auditor's report on security controls. A Type I report looks at how they are designed at one point in time; a Type II report tests whether they actually worked over several months.
  • ISO 27001 certifies an information security management system, within a defined scope.
  • HITRUST is a certifiable framework common in US healthcare, mapped to HIPAA.

Most buyers skip one question: whose certificate is it? Many AI vendors run on cloud providers that hold SOC 2 and ISO 27001. That covers the data centers and the infrastructure. It says nothing about the vendor's own application, its code, its access policies or its support staff. Both can be true, and both are useful. The vendor just has to tell you which is which, and show you the report, its scope and its date.

Call recording and patient consent

HIPAA doesn't forbid recording patient calls. A recording is PHI, protected like the rest. Consent is a matter of state law, and about a dozen states, California and Florida among them, require everyone on the call to agree to the recording. A group with sites in several states, or with patients calling from out of state, needs a short recording notice at the start of every call.

Two more questions belong here. How does the agent introduce itself, and do you choose the wording? And what happens when a patient says they would rather talk to a person? The right answer is a transfer to your staff, under your rules.

The 15 questions to send every vendor

Paste these into your RFP or your security questionnaire. Tick each one off once the vendor has answered it in writing, or copy the full list in one click.

#QuestionWhat a good answer looks likeRed flag
1Will you sign a BAA before any PHI is processed, including during a pilot?Yes, before the first live call. The standard BAA is available for your counsel to review"After the pilot", or "we're certified, so no BAA is needed"
2Which services does the BAA cover?Every module you activate: inbound, outbound, text messages, analyticsOne product named, while you use several
3Which subcontractors handle our PHI, and does each one have a BAA with you?A written list (hosting, speech recognition, language models, messaging), each under a BAA"We can't share that"
4Do you use our call data to train or improve AI models?No, or only on terms written into the BAA"To improve our services", with no detail
5Where are recordings, transcripts and logs stored?Named regions and named providers"In the cloud"
6How long do you keep each type of data, and who sets that period?You set it, within a stated maximum, with deletion on requestNo deletion mechanism
7Can anyone access our data from outside the United States?Which functions, from where, under which safeguards, covered by the BAANo answer, or a flat denial with no detail
8How is access to PHI controlled inside your company?Role-based, limited to what each role needs, loggedShared accounts
9Can we see who accessed a recording or a transcript?Access logs available to youNo logs
10How quickly will you notify us of a breach?A written process, within the legal 60-day ceiling, often shorter by contract"As required by law", with no process behind it
11Which certifications do you hold, and which belong to your hosting providers?A clear split between the two, with reports or attestations available on request"SOC 2 compliant", with nothing to show
12How does the agent announce recording at the start of a call?A notice you can configure, in your wordsNo notice
13What happens when a caller asks for a person or describes an emergency?Immediate transfer to your staff, under rules you defineThe agent keeps trying, or takes a message
14What does the agent write into our EHR, and with which permissions?A dedicated integration account, limited to the scheduling data it needsFull administrator credentials
15What happens to our data when the contract ends?Return or destruction, confirmed in writing, backups includedNo answer

How Vocca handles HIPAA

We work as a HIPAA business associate for our US healthcare customers, and we sign a BAA with each of them before any PHI is processed. US customer data is hosted in the United States, in a production environment kept separate from the one that serves our European customers. Our US hosting providers are bound by their own BAAs.

Patient data is encrypted in transit and at rest. Access to PHI is role-based, limited to what each role needs, and logged, and our team receives security and privacy training. Your practice manages its own users' permissions. Every subcontractor that handles PHI on our behalf is bound by a written agreement at least as protective as ours. If unsecured PHI is ever breached, we notify the practice without unreasonable delay, and no later than 60 days after discovery.

Buyers ask about two more points, so here they are plainly. Our infrastructure partners are SOC 2 and ISO 27001 certified, which means those certifications belong to the infrastructure we run on. And Vocca was founded in France: some of our support, billing and engineering work is done from France or elsewhere in the EU, which can involve access to US customer data from outside the United States. That access is covered by the BAA and by the safeguards above.

Your practice sets the retention period, within the limits of our data retention policy. We never use patient data to train AI models. The details are on our security and compliance page.

Your compliance team will want to read the agreement itself. Ask us for our BAA, or book a demo to see how our AI voice agent books appointments directly in your EHR, across every site of a multi-location group. For hospitals, our guide to hospital outpatient calls shows what an AI voice agent can handle and what stays with patient access staff.

FAQ

Is it safe to use an AI voice agent for patient calls under HIPAA?

Yes, if the vendor signs a BAA before any PHI is processed and backs it with real safeguards: encryption, access controls, audit logs and a clear list of subcontractors. HIPAA doesn't prohibit AI. It asks you to choose a business associate that protects PHI, and to put that commitment in writing.

Does an AI receptionist need to sign a BAA?

Yes. An AI receptionist that answers patient calls creates, receives, maintains and transmits PHI on your behalf, which makes the vendor a business associate. The conduit exception only covers services that carry data from one point to another, so it doesn't apply. Without a signed BAA, the vendor shouldn't handle a single real patient call, pilots included.

Does SOC 2 mean a vendor is HIPAA compliant?

No. SOC 2 is an audit report on security controls, and HHS doesn't recognize any private certification as proof of HIPAA compliance. A SOC 2 report is useful evidence, but it doesn't replace the BAA. Check whether it covers the vendor itself or only its hosting provider.

Can an AI phone agent record patient calls?

Yes. HIPAA allows recordings, which are PHI and protected as such. Consent to record depends on state law, and about a dozen states require everyone on the call to consent. A recording notice at the start of each call is the simplest way to meet the strictest rule.

Which questions should I ask an AI receptionist vendor about security?

Start with the BAA, its scope and its subcontractors. Then ask where call data is stored, how long it is kept, who can access it (including from outside the United States), how fast a breach is reported, and whose certifications you're looking at. The 15 questions in this article cover each point.

Man in a black leather jacket holding a smartphone to his ear, looking to the side with blurred modern city buildings in the background.

Less time on the phone, more time on care