HIPAA and AI Phone Agents: What a Medical Practice Must Check

A medical practice can use an AI phone agent under HIPAA, but only after five checks: a signed business associate agreement with every vendor that stores call data, control over what lands in transcripts, a written retention period, a recording notice that meets California's consent rule, and access limited to the minimum the call needs. This guide walks through each one.

Why does HIPAA apply to an AI phone agent at all?

Patients rarely call just to ask about parking. They call to book a follow-up, ask about lab results, refill a prescription or reschedule a procedure. The moment a caller gives a name and a reason for the visit, the call contains protected health information (PHI). An AI agent that answers, transcribes, summarizes or books that call is handling PHI on the practice's behalf.

That puts the agent squarely inside the HIPAA Privacy, Security and Breach Notification Rules. The rules do not ban the technology. They set conditions on who may handle the information, how it is protected and what happens when something goes wrong. A practice that meets those conditions can answer every call around the clock; one that skips them carries the risk alone.

This article covers the vendor contract, the data the agent creates, and the consent and access questions. It is general guidance as of October 2026, not legal advice, so confirm the specifics with your attorney or compliance officer.

Is the AI vendor a business associate?

Business associate: a person or company, other than the practice's own workforce, that creates, receives, maintains or transmits protected health information while performing a function or service for a covered entity. A business associate must sign a business associate agreement and is directly liable for parts of the HIPAA Rules.

For an AI phone agent the answer is almost always yes. The agent creates recordings and transcripts, writes appointment details into the practice management system, and often stores call summaries for staff to review. Each of those is creating or maintaining PHI.

The HHS guidance on cloud computing is direct on two points practices often get wrong. First, a cloud provider that stores PHI is a business associate even when it holds only encrypted data and has no decryption key. Second, the so-called conduit exception, which covers carriers such as the postal service, is limited to transmission-only services with transient storage. A provider that keeps recordings or transcripts is not a conduit.

That distinction matters when you map your phone stack. The carrier delivering the call may be a conduit. The AI platform, the transcription engine, the cloud phone system storing voicemail, and any analytics tool reading call logs probably are not.

What should the business associate agreement cover?

A BAA is not a formality to file away. HHS publishes sample business associate agreement provisions that show what the contract has to commit the vendor to. For an AI phone agent, read the vendor's BAA against these points.

1. Permitted uses. The vendor may use or disclose PHI only as the agreement allows or the law requires. Look closely at any clause letting the vendor use call content to train or improve its models.
2. Safeguards. The vendor must protect electronic PHI under the Security Rule, not just promise "industry standard security".
3. Incident and breach reporting. The vendor must report uses outside the agreement, security incidents and breaches. Ask for a specific reporting timeframe in writing.
4. Subcontractors. If the AI vendor relies on a separate speech-to-text or language model provider, those subcontractors must agree to the same restrictions. Ask for the list.
5. Patient rights. The vendor must help the practice respond to patient requests for access, amendment and an accounting of disclosures.
6. Termination. When the contract ends, the vendor returns or destroys the PHI and keeps no copies, unless retention is specifically justified.

If a vendor will not sign a BAA, or offers one only on an enterprise plan, that answers the question for patient-facing calls.

What happens to PHI in recordings and transcripts?

An AI agent produces more patient data than a human receptionist does. A person answering the phone remembers the call and types a few fields. An AI agent can keep the audio, a full transcript, a summary, the structured fields it extracted and logs of every step. Each copy is PHI, and each copy lives somewhere.

Before go-live, ask the vendor where each of these is stored, who on their side can see it, and whether you can switch any of them off. Many practices find they need the structured booking and a short summary, not hours of stored audio.

The table below compares how three common call-handling setups treat patient information.

Question	Voicemail on a cloud phone system	Live answering service	AI phone agent
Captures PHI	Messages, often transcribed	Staff notes and messages	Audio, transcript, summary, booking data
Business associate	Yes, if it stores voicemail	Yes	Yes, plus any AI subcontractors
Main data risk	Unreviewed messages piling up	Notes in a third-party system	Many copies across several systems
Access control	Mailbox permissions	Vendor staff	Integration permissions and admin roles
Retention control	Mailbox settings	Vendor policy	Per data type, if the vendor allows it
After-hours coverage	Records only	Depends on staffing	Answers and books around the clock

None of these options is automatically compliant or automatically risky. The AI column simply has more data types to account for, which is why the mapping work comes before the contract is signed.

How long should call data be kept?

HIPAA requires that Security Rule policies and related documentation be kept six years from creation or from when they were last in effect. That rule covers your policies, risk analysis and similar records. It does not set a single retention period for call audio.

Whether a call transcript or summary must be kept longer depends on whether it becomes part of the patient's medical record and on California's own record retention rules. That is a question for your attorney and your EHR policy, not for the AI vendor's default setting.

What the practice can do is decide in writing. Set a retention period for each data type (audio, transcript, summary, logs), confirm the vendor's platform can enforce it automatically, and make sure deleted means deleted across backups within a stated window.

Do patients have to be told the call is recorded?

California's Penal Code section 632 makes it a crime to record a confidential communication without the consent of all parties, and a call about someone's health is about as confidential as calls get. An AI agent that records or transcribes a patient call therefore needs a clear notice at the start, before capture begins.

A short, plain notice works best: who is answering, that the call may be recorded and transcribed, and how to reach a person. Our free call recording notice generator drafts that wording for a California business. Have your attorney approve the final script.

The notice is also a good moment to be honest that the caller is speaking with an AI agent. Patients tend to accept automation when it is disclosed and they can reach a person easily.

What should the AI agent be allowed to see?

The HIPAA minimum necessary standard asks covered entities to limit use and disclosure of PHI to what a purpose requires, and to define which roles need which categories of information. Disclosures to a provider for treatment are an exception, but a scheduling agent is not treating anyone.

Treat the AI agent as a workforce role with its own permission set:

1. List the call types the agent will handle: new appointments, reschedules, directions and hours, prescription refill requests, billing questions.
2. For each call type, list the fields it truly needs, such as name, date of birth, callback number and available slots.
3. Grant the integration read and write access to those fields only, not the full chart.
4. Route anything clinical, such as symptoms, results and medication questions, to a person, with a warm transfer during hours and a callback task after hours.
5. Review the agent's access whenever you add a new call type.

This limits the damage of any mistake, and it keeps the agent in the work it does well: answering promptly, booking accurately and handing off cleanly.

What should a practice check before going live?

Pull the steps above into one pre-launch review, owned by a named person:

1. Map every system that will touch call data, including subcontractors.
2. Sign a BAA with each vendor that stores or processes that data.
3. Update your risk analysis to include the AI agent and its integrations.
4. Set and configure retention for each data type.
5. Approve the recording and AI disclosure script.
6. Limit the agent's integration permissions by call type.
7. Test with staff calls, then a small share of live calls, and review transcripts before full launch.

Folding these checks into a written AI policy for a small business keeps them alive after launch, when new staff and new call types arrive.

Key takeaways

• An AI phone agent handling patient calls processes PHI, so HIPAA applies.
• Any vendor that stores recordings or transcripts is a business associate, even with encrypted data; only transmission-only carriers fit the conduit exception.
• Read the BAA for model training, subcontractors, breach reporting and data return.
• Decide retention for audio, transcripts, summaries and logs separately, in writing.
• California requires all-party consent to record confidential calls, so announce recording first.
• Give the agent only the fields each call type needs, and route clinical questions to people.

How Telxpress helps

Telxpress helps Orange County clinics, specialty practices and dental offices plan and deploy patient-call automation with the compliance questions answered first. We map your phone and practice management systems, review vendor terms with your compliance lead, and configure our AI voice agent, Donya, with scoped permissions, a disclosed recording notice and handoffs to your front desk. See our healthcare industry page for the systems we install, or book an AI advisory consultation to review your current call flow.