HIPAA and AI voice agents in patient access: a call-level checklist

This checklist is for teams running AI voice agents on scheduling, billing and balance calls, and for the engineers who build them. Federal rules usually set a call's outcome, not its words, so each item says which part is law and which is your standard operating procedure (SOP) choosing how to comply.

What should every patient-access call be checked for?

Twelve things: nine that federal rules require (some only of certain providers), one that HHS guidance recommends and two your SOP chooses, each with the evidence that shows it on the call.

When an uninsured or self-pay patient books, or asks what something will cost, the No Surprises Act rules require the provider to tell her out loud, in her language, that a good faith estimate is available (45 CFR 149.610(b)(1)). A provider that takes federal financial assistance must offer a caller with limited English a free qualified interpreter when one is needed (45 CFR 92.201) and take relay calls (92.202, applying 28 CFR 35.161). The rule doesn't say whether an AI agent speaking Spanish counts, so a safe SOP rule transfers to an interpreter or bilingual staff before any financial assistance or estimate notice.

Rows that span calls need the patient record and dial log; see our guide to auditing AI voice agent calls against your SOP.

What does HIPAA require before the agent discloses PHI?

Two things: the caller's identity and authority verified when either isn't known, and no more PHI moving than the call needs. Protected health information (PHI) is individually identifiable health information held by a covered entity or its business associate, and under 45 CFR 160.103 it includes information about payment for a person's care. A patient's balance is PHI. So is the fact that she has an appointment.

45 CFR 164.514(h) requires a covered entity to verify the identity and authority of a person requesting PHI when either isn't already known. It names no method and no number of identifiers; two, such as date of birth and ZIP code, is an SOP choice. What it fixes is the order, so a grader checks timestamps, not the agent's word: the verification match must come before the first account detail.

On outbound calls, the duty in 164.530(c) to limit incidental disclosures is best met by asking for the patient by name and giving no reason for the call until she's verified.

The minimum necessary standard in 164.502(b) doesn't limit what a verified patient hears about herself, but it covers uses, disclosures and requests, including what reaches the voice vendor: a scheduling agent whose lookup returns diagnosis codes and claim history puts all of it in the transcript and everywhere the transcript goes.

Can the agent discuss a bill with a spouse or adult child?

Yes, within limits, and HIPAA allows more than many SOPs do. 45 CFR 164.510(b) lets a provider share PHI with family, close friends or anyone the patient identifies, limited to what's relevant to their involvement in her care or its payment: on her agreement or lack of objection if she's on the line and able to decide, or in professional judgment about her best interest if she isn't. HHS's guide for providers gives the billing case: a hospital may discuss a patient's bill with her adult son.

"Professional judgment" is the part an AI agent can't supply, and these disclosures are exempt from the verification rule. A defensible SOP draws the agent's rule narrower than the law: discuss the account with someone else only when the patient agrees on the call or has named that person as an authorized contact, and otherwise take a message or transfer to staff.

Minors need their own rule. A parent is usually a minor's personal representative, treated as the patient (164.502(g)), except for care the minor could lawfully consent to alone, where state law, or failing that the provider's judgment, decides what the parent may learn (164.502(g)(3)). An itemized balance can reveal exactly that care, so a safer SOP rule for a patient under 18 is no itemized detail and a transfer to staff unless the record clears the parent.

What can go on a voicemail, and what if the patient asks you to call elsewhere?

Little more than the provider's name and number and a request to call back, and a reasonable request to be reached another way is one a provider must honor. HHS FAQ 198 covers both. Voicemail isn't prohibited, so the rest is SOP: no diagnosis, procedure, condition-revealing department or balance. Test beep detection too, or the agent reads its live script, balance included, to the mailbox. Collection agencies follow Regulation F's stricter limited-content message; see FDCPA and Regulation F rules for AI collection calls.

Under 45 CFR 164.522(b), a provider must accommodate reasonable requests to be contacted by other means or at other locations, and may not require an explanation as a condition. It may require the request in writing and, when appropriate, ask how payment will be handled. On the call, the agent saves "don't call this number" with a tool call that succeeds, or explains how to submit it in writing. Only the dial log proves later calls respected it.

Who needs a business associate agreement, and how long should transcripts live?

Every business associate needs one. A business associate is a person or company that creates, receives, maintains or transmits PHI on a covered entity's behalf, including its subcontractors that do the same (45 CFR 160.103). For a hosted voice agent that means the platform, its speech, language model and voice providers, and whoever later receives transcripts, such as QA. Receiving PHI to process it is enough, so a vendor that keeps nothing still needs a BAA; HHS's cloud computing guidance limits the "conduit" exception to transmission. The provider signs with the platform, and the platform with its subprocessors (164.502(e)(1)); ask to see those agreements. Loops, for example, signs a BAA with its NDA and DPA before it receives any access.

HIPAA sets no retention period for transcripts; HHS says state law generally governs medical record retention (FAQ 580). The often-quoted six years is for HIPAA documentation such as policies (164.316(b)(2), 164.530(j)). A kept billing-call recording or transcript can be part of the designated record set, which includes a provider's billing records (164.501), so the patient's right of access applies while it exists (164.524).

Platforms differ: Retell offers per-agent retention from one day to two years, and Vapi's HIPAA mode keeps recordings and logs unless you bring your own storage. With zero retention nothing is left to backfill, so an auditor must receive each call as it ends, under its own BAA.

Which TCPA rules apply to patient calls made with an AI voice?

The FCC's February 2024 ruling (FCC 24-17) treats AI-generated voices as "artificial" voices under the Telephone Consumer Protection Act (TCPA), so outbound AI calls follow 47 CFR 64.1200. Every one must state the caller's registered business name at the start and a callback number during or after the call ((b)(1), (2); FCC 24-17, paragraph 9).

Consent for billing calls usually rests on the number the patient gave with the account. The FCC's 2008 ACA International ruling (FCC 07-232, paragraphs 9 and 10) treats a number provided in the transaction that created a debt as consent to calls about that debt, by the creditor or a collector calling for it, and the Eleventh Circuit applied it to a number on hospital admission forms (Mais v. Gulf Coast Collection Bureau, 2014). The FCC's 2015 healthcare clarification (FCC 15-72, paragraph 141) is narrower than often quoted: footnote 473 ties its "healthcare calls" to HIPAA's definition of health care, which describes care, not payment. Since McLaughlin Chiropractic v. McKesson (2025), district courts read the statute for themselves, so treat both as persuasive, not settled. A patient can revoke by any reasonable means, including on the call, honored within ten business days (64.1200(a)(10)). More in TCPA consent for AI voice calls after the FCC's 2024 ruling.

What do state medical debt laws change on a billing call?

They change what the agent may say about credit reporting and how it sizes a plan, above a federal floor for tax-exempt hospitals. At least 30 days before a first extraordinary collection action, such as credit reporting or selling the debt, the hospital must send a written notice with a plain language summary of its financial assistance policy and make a reasonable effort to tell the patient about it orally, and most such actions must wait 120 days after the first post-discharge bill (26 CFR 1.501(r)-6(c)(3), (c)(4)). An AI billing call can supply the oral part only.

Colorado's HB23-1126 keeps medical debt off consumer reports and bars a collection agency from falsely saying it will appear on one or affect a credit score (C.R.S. 5-16-107(1)(r), set to repeal July 1, 2028). For patients who qualify for Hospital Discounted Care, a plan can't take more than 4% of monthly household income on the hospital's bill or 2% on each licensed professional's separate bill (6% on one combined bill), and the bill is paid in full after 36 months of payments (C.R.S. 25.5-3-503(1)(b), (c)). An agent that sizes a plan from the balance alone can break that. New York's S4907A (2023) bars providers from reporting medical debt to credit bureaus.

The reporting bans carry a question mark. In July 2025 a federal court in Texas vacated the CFPB's medical debt rule and wrote that a state ban on reports with coded medical information would be preempted (Cornerstone Credit Union League v. CFPB). In October 2025 the CFPB issued an interpretive rule reading the Fair Credit Reporting Act to preempt state laws on what consumer reports contain, medical debt included, and on what furnishers report, while stating it has no binding effect (90 FR 48710). In November 2025 ACA International sued to block HB23-1126 as preempted (ACA International v. Fulford, D. Colo.); it was undecided when we checked the docket in September 2026. The SOP rule that holds up either way: the agent never raises credit reporting on a medical bill.

What does a graded patient-access call look like?

Like this, with each verdict tied to a timestamp or a tool result.

Agent: Hi, this is Ava, an automated assistant calling for Birchwood Community Hospital, on a recorded line. May I speak with Maria Chen?

Patient: Speaking.

1.1 met · registered name, automated assistant and recording stated by 00:05; no reason given before verification

Agent: Thanks, Maria. To protect your privacy, what are your date of birth and ZIP code?

Patient: October 18, 1983, and 60614.

1.2 met · verify_patient returned a match at 00:19, before any account detail

Agent: There's a balance of $412.50 from your visit on August 12. Would you like to pay that today with the card on file?

2.1 met · $412.50 matches get_balance at 00:21

2.3 missed · payment requested at 00:24 with no mention of financial assistance

Patient: Not today. And please stop calling this number, my husband answers it. Use my cell, three one two, five five five, zero one [inaudible].

3.2 needs review · new number partly inaudible at 00:41; a person should confirm what was saved

Agent: Of course. I've updated how we'll contact you.

3.3 missed · log_contact_preference returned an error at 00:44; the agent confirmed the change anyway

Agent: If you have questions, our billing office is at 312-555-0148.

1.3 met · callback number stated at 00:49, before the call ended

3.4 not checked · no calls to the old number after ten business days; needs the dial log

A listen-through would pass most of this call. Rule 2.3 is an SOP rule that, at a tax-exempt hospital, also carries the 501(r) oral notice. Rule 3.3 sounds compliant; only the tool-call record shows the preference was never saved, so the next call goes to the number the patient refused. "Stop calling this number" also revokes TCPA consent, so rule 3.4 stays not checked until the dial log arrives.

This is general information, not legal advice; confirm with counsel how these rules apply in your states.

Turn the table into numbered SOP rules with named evidence, mark which need the patient record or dial log, and grade a month of calls. Loops grades every call against rules your compliance lead approves, quotes the line behind each verdict, checks that tool calls succeeded, and signs a BAA before access (security details). A free 30-day audit delivers its first report within 72 hours of rule approval; if your platform keeps no transcripts, it grades new calls from the day you connect.