TL;DR
- ·HIPAA is a shared responsibility, vendor handles the technical safeguards, you handle the administrative ones.
- ·A signed BAA is non-negotiable. If a vendor won't sign one, walk.
- ·Lani AI's conversational AI for healthcare ships the full HIPAA-grade architecture (BAA, encryption, audit logs, retention, recording disclosure) via Privacy Plus+.
The shape of the problem
AI is doing the thing it does in every other industry, drop into operations, save 30 to 50% of front-office time, recover lost revenue from missed calls. Medical practices want in. But "HIPAA compliant" is a checkbox a lot of vendors slap on their landing page without actually being able to back up, and the consequences of getting it wrong (OCR investigations, six-figure fines) are bad enough that "vaguely close to HIPAA" doesn't work.
This guide is the checklist we use internally when we sign up a medical practice on Lani AI. It's not legal advice, talk to a healthcare compliance attorney before signing anything, but it's the operational floor.
The 7 items at a glance
| Item | What to ask the vendor | Proof to request |
|---|---|---|
| Business Associate Agreement | Will you sign a BAA covering calls, texts and transcripts? | The signed agreement |
| Encryption | Is everything encrypted in transit and at rest, including the AI model's path? | Encryption documentation |
| Audit logging | Is every access to patient information logged? | The audit log for a sample call |
| Retention | Can we set how long audio and transcripts are kept? | The retention settings, shown live |
| Recording disclosure | Can we set the disclosure the caller hears? | A test call that plays it |
| Escalation | Which calls go to a person, and who decides? | The written transfer rules |
| Patient verification | What must a caller confirm before anything is shared? | A test call that fails the check |
Item 1: Business Associate Agreement (BAA)
A BAA is the contract under which a vendor agrees to handle Protected Health Information (PHI) on your behalf in compliance with HIPAA. It's the most important single document in the entire stack. If a vendor won't sign one, they cannot legally process PHI for a covered entity, full stop.

Things to check: the BAA should be signed by an authorized officer of the vendor, should explicitly cover the use case you're deploying (voice calls, SMS, email, transcripts), and should include breach notification timelines that meet HIPAA's 60-day requirement. Lani AI's BAA is available via the Privacy Plus+ add-on and is included for any medical-vertical client.
Checklist
Check the BAA before you sign
- It's signed by someone authorized to sign for the vendor
- It names every channel you'll use: calls, texts, email and transcripts
- It covers the vendor's own subcontractors, including any AI model provider
- Its breach notification terms meet HIPAA's timelines
- It says what happens to your data when the contract ends
Item 2: Encryption at rest & in transit
Voice audio, SMS bodies, email content, transcripts, and CRM-synced records all need to be encrypted both in transit (TLS 1.2+) and at rest (AES-256 typically). The right question to ask a vendor isn't "do you encrypt", they all say yes, but "show me your encryption documentation." Real vendors have it ready.
For voice specifically, also ask about the model inference path. Some voice AI vendors route audio through third-party LLM providers without BAAs in place. The end-to-end chain has to be covered, not just the storage.
Template
Questions to email a vendor's security team
Send these in writing and keep the replies with your compliance file.
1. Please send your encryption documentation for data in transit and at rest.
2. Which third parties process call audio or transcripts, and do you have a BAA with each?
3. Can you show us the audit log for a sample call?
4. How do we set retention for audio, transcripts and texts, and can we change it ourselves?
5. Where do we edit the recording disclosure callers hear?
6. What does a caller have to confirm before the AI shares anything about an appointment?
Item 3: Audit logging
Every access to PHI needs to be logged with timestamps and user identity. This includes both human accesses (your team viewing a transcript) and machine accesses (the AI reading the patient's prior history during a call). If something goes wrong, the audit log is what you and your attorney use to reconstruct what happened.
Practical test: ask the vendor to show you the audit log for a sample call. If they can't produce one in real time, they don't have it.
Item 4: Configurable retention
HIPAA itself doesn't mandate a retention period, but state laws do (often 6 to 10 years for medical records). More importantly, you don't want voice recordings sitting around forever. Lani AI lets practices configure retention per category (voice audio, transcripts, SMS, email, CRM events) with auto-deletion on the schedule you set.
Default to short retention for raw audio (90 days is usually enough) and longer retention for transcripts + structured records (per your state's rules). The vendor should support both, and you should be able to change the policy without a support ticket.
Item 5: Recording disclosure
Twelve US states are two-party-consent states for call recording: every party on the call must consent before the call can be recorded. Your AI receptionist has to deliver that disclosure within the first few seconds of the call ("This call may be recorded for quality and training purposes") and respect the caller's opt-out if they object.
Lani AI handles the disclosure automatically based on the practice's location and the caller's area code, and lets you edit the disclosure text per state. If a vendor doesn't handle this, the practice ends up responsible for the violation.
Item 6: Escalation & human transfer
AI in medical contexts shouldn't make clinical decisions. The receptionist can handle booking, payment, FAQ, hours, location, and rescheduling, but anything that touches medical advice, clinical urgency, or sensitive issues needs to escalate to a human in real time.
Incoming calls
- All sorted
The AI can handle it
- Book a new patient visit
- Reschedule Thursday's appointment
- Office hours and parking
Transfer to a person
- "Is this rash something to worry about?"
- "Can I take this with my medication?"
- A complaint about a bill
Lani AI recognizes escalation intent (symptoms questions, complaints, sensitive triggers) and warm-transfers to a designated human with full call context attached. The escalation rules are configurable per practice, your office decides what triggers transfer.
Item 7: Patient verification
When a patient calls about an existing appointment or record, the AI needs to verify their identity before disclosing any PHI. Standard verification is date of birth + last name match, but practices can configure stricter rules (last 4 of SSN, address match, etc.) for sensitive cases.
No verification, no PHI disclosure. The AI defaults to "I can't share that without verifying your identity first" if the patient can't pass the check, which is the right behavior under HIPAA.
Incoming call
Patient, 7:15 pm
Lani AI
Asks for the details your office requires first
Details match
Confirms the appointment time
Sounds clinical or urgent
Transferred to staff with the conversation attached
Details don't match
Shares nothing and says the office will follow up
How Lani AI implements all seven
The Privacy Plus+ add-on unlocks the HIPAA-grade architecture: signed BAA, encrypted audio + storage, audit logging, configurable retention, recording disclosure, escalation rules, and patient verification, all configurable per practice during the 7-day pilot. Add-on pricing is $97/month on top of the base subscription.
Medical practices using Lani AI in 2026 include med spas, dental offices, dermatology, and several MSO-style multi-location healthcare groups. The architecture clears the operational floor; the rest is configuration during onboarding.
What should a practice do before turning on AI?
Get the BAA signed before any patient call reaches the system. Then decide, in writing, what the AI may and may not do: book and reschedule, answer general questions about hours and services, and hand anything clinical to a person.
Set the retention period for recordings and transcripts to match your policy, and confirm who on your team can see them. Turn on the recording disclosure your state requires before the first live call, not after.
Step by step
Before the first live patient call
- 1
Sign the BAA
Nothing involving a real patient reaches the system before this.
- 2
Write the scope down
What it may do (book, reschedule, hours, directions) and what always goes to a person (anything clinical).
- 3
Set retention & access
Match recordings and transcripts to your policy, and name who on your team can see them.
- 4
Turn on the disclosure
Use the recording disclosure your state requires, and hear it on a test call.
- 5
Get a review
Your compliance lead or attorney signs off on the setup.
This isn't legal advice, and your compliance lead or attorney should review the setup. For the checklist from the receptionist's side, see our HIPAA-compliant AI receptionist guide.
How do you test it safely on your own line?
Start with test calls from your own staff using made-up patient details, so no real health information is involved while you check the behavior. Ask it to book, to reschedule, and to answer a clinical question it should refuse and transfer.
Then move to live calls on a narrow slice, such as after-hours calls only, and review every transcript for the first week. You're checking 3 things: did it verify the caller before sharing anything, did it stay out of clinical advice, and did the right calls reach a person.
Checklist
Read every transcript from week 1 for 3 things
- Did it verify the caller before sharing anything about an appointment?
- Did it stay out of clinical advice, even when the caller pushed?
- Did every clinical, urgent or sensitive call reach a person?

There are practice-specific guides for dental offices, chiropractors and physical therapy clinics. The Lani AI 7-day pilot is completely free, with HIPAA coverage through the Privacy Plus+ add-on. If you decide to move forward, there's a setup.
Frequently asked questions
Can a medical practice use an AI receptionist under HIPAA?
Yes, if the vendor signs a Business Associate Agreement and the setup covers encryption, audit logs, retention, recording disclosure, escalation and patient verification. Have your compliance lead or attorney review it.
Do I need a BAA with an AI receptionist vendor?
Yes, if it will handle protected health information for your practice. If a vendor won't sign one, don't route patient calls to it.
Should an AI receptionist answer medical questions?
No. It should book, reschedule and answer general questions about hours and services, and transfer anything clinical to a person on your team.
How should an AI receptionist verify a patient?
By checking details your office chooses, such as date of birth and last name, before it shares anything about an appointment. If the details don't match, it shouldn't share anything.
How do I test an AI receptionist without exposing patient data?
Have staff make test calls with made-up patient details first, then go live on a narrow slice like after-hours calls and read every transcript for the first week. Lani AI offers HIPAA-aware coverage through its Privacy Plus+ add-on.
Ready when you are
See if Lani AI is right for your business.
7-day pilot, completely free. Live by the end of this week.



