Key takeaways
- Map exactly which patient data a phone, text or booking tool will hold before you look at features.
- A signed business associate agreement is the entry ticket, not the whole review: ask about storage, retention, training use, logs and subcontractors.
- Outbound calls with AI-generated voices count as artificial voice calls under the TCPA, so consent questions belong in the review.
- Score every answer and decide in advance which answers end the conversation.
Why communication tools need their own review
When practices look at automation to improve access, scheduling and phone calls top the list, ahead of registration and prior authorization[1]. Those are exactly the tools that sit between your patients and your staff, so they collect names, phone numbers, reasons for calling and appointment details from the first day they go live.
Patients are paying attention too. In a 2026 national poll, 77% of the public said they were concerned about the privacy of personal medical information provided to AI tools[2]. A vendor review that you can explain in plain words is part of keeping that trust, and it is the evidence you will want if a regulator ever asks why you chose the tool.
Any vendor that creates, receives, maintains or transmits patient information for you needs a business associate agreement first[3]. If you are unsure whether a vendor qualifies, start with our explainer on when you need a business associate agreement, then come back to this checklist.
Step zero: list the data before the demo
Sales demos show features. Your review should start from data. Before the first call, write down every kind of patient information the tool will touch in your workflow. For a typical phone, text or booking product the list looks like this:
- Call audio, if calls are recorded, and any voicemail the system stores.
- Transcripts and summaries generated from calls or chats.
- Text message content in both directions, including replies patients type freely.
- Booking details: visit type, provider, date, and any reason-for-visit field.
- Caller ID and call logs that link a number to a patient record.
- Notes staff add in the tool's inbox or CRM view.
- Analytics exports and reports that the vendor or your staff download.
Each item on the list becomes a question: where is it stored, who can see it, how long is it kept, and how is it deleted. If an item does not apply because the tool is designed to avoid patient-specific details, ask the vendor to confirm that design in writing and check it during the trial.
The checklist
Send these questions in writing before the second meeting and ask for written answers. Group them as below so the vendor's security and legal teams can each answer their part.
- Agreement: Will you sign a business associate agreement before we send any patient information? Whose template, and can we review it now?
- Agreement: Does it include every required element, from limits on use and disclosure to subcontractor flow-down and return or destruction of data at the end[4]?
- Agreement: How many days after discovery will you report a breach to us? The legal outer limit is 60 calendar days, so ask for something shorter[5].
- Subcontractors: Which subcontractors handle our data (hosting, telephony carrier, transcription, messaging gateway), and have they signed agreements with you?
- Data use: Is any of our data used to train or improve your products? If so, is it de-identified first, and can we opt out?
- Retention: How long do you keep recordings, transcripts and message logs by default? Can we set shorter periods?
- Deletion: What happens to our data at contract end, and will you confirm deletion in writing?
- Access: Does every user get a unique login? Is multi-factor sign-in available for staff and enforced for your own support staff?
- Logs: Can we see who viewed or exported a record? The Security Rule expects activity in systems holding electronic patient information to be recorded and examined[6].
- Encryption: Is data encrypted in transit and at rest? HIPAA lists encryption as addressable, but a vendor that cannot say yes needs a strong reason[6].
- Outbound calls and texts: Does the product place automated calls or texts? Do any use an AI-generated or prerecorded voice?
- Exit: Can we export our data in a usable format if we leave?
On outbound calling, the FCC ruled in February 2024 that calls made with AI-generated voices are artificial under the Telephone Consumer Protection Act, effective immediately[7]. Telemarketing calls of that kind need prior express written consent[8]. Ask the vendor how consent is captured and stored before you switch on any automated outreach.
Extra questions for AI phone and chat tools
AI receptionists, chat widgets and call summarizers add a layer that older phone systems did not have: a model that listens, writes and sometimes speaks. The standard checklist still applies, but these tools deserve a few more questions, because the data they create is new and easy to overlook.
- What happens when a caller starts giving symptoms or test results? Does the tool stop collecting details and hand the call to staff, or does it keep transcribing?
- Where do transcripts and call summaries live, and are they included in the retention and deletion controls, or kept separately?
- Can we review a sample of real summaries during the trial to check for wrong names, wrong dates or invented details?
- Does the tool identify itself as automated at the start of a call, and can we edit that wording?
- Which outside model provider processes the audio or text, and is that provider covered by the vendor's subcontractor agreements?
- How do staff take over a live conversation, and is that handoff logged?
The answers tell you how much patient information the tool will actually hold. A product built to answer general office questions and pass patient-specific matters to your team carries a very different risk profile from one that records and summarizes every clinical detail a caller mentions. Both can be reasonable choices, but your agreement, settings and staff training should match the one you pick.
Score the answers
A simple three-level score keeps the comparison honest when two vendors both say they are HIPAA compliant. Score each checklist question, then look at the pattern rather than the total.
| Score | What the answer looks like | What to do |
|---|---|---|
| 2 - Strong | Specific, written, matches the contract and the product settings you saw | Accept |
| 1 - Partial | Correct but vague, or available only on a higher plan or by request | Get it in writing or added to the contract |
| 0 - Weak | No answer, a marketing page instead of an answer, or a contradiction | Escalate; consider it a red line if it involves the agreement, breach reporting or data use |
Decide your red lines before the first demo. Most practices treat these as non-negotiable: no signed agreement, no answer on subcontractors, use of identifiable patient data for product training without opt-out, and no way to delete data at the end of the contract.
A script for the vendor call
Practice managers often feel awkward pushing a salesperson on legal terms. A short script helps keep the conversation on track and shows the vendor you will be checking.
Script: Before we go further, we need three things in writing. Your business associate agreement template, a list of the subcontractors that would touch our patients' information, and your default retention period for recordings, transcripts and texts. If any of those are a problem, please tell me now so we do not waste each other's time.
Follow up with the full checklist by email. If the answers come back from a sales contact rather than someone in security or compliance, ask who wrote them. Keep the email thread with the signed agreement. If an investigator ever asks why you picked the vendor, that trail is your answer.
Test the answers during the trial
Use test data only
Run the trial with fictional patients until the agreement is signed. Do not paste real names into a sandbox to see how it looks.
Check the settings you were promised
Find the retention controls, recording switch, user roles and multi-factor setting in the admin screens. If you cannot find them, the answer was partial.
Export a log
Ask for or download an access log and confirm it shows who viewed what and when.
Send a STOP
If the tool texts patients, reply STOP from a test phone and confirm the opt-out is honored and recorded.
Ask for deletion
Delete a test record and ask support to confirm it is gone from backups within the stated period.
Example: two reminder platforms, one decision
Example (fictional): A pediatric practice compares two appointment reminder platforms. Platform A signs its standard agreement within a day, lists its hosting and messaging subcontractors, keeps message logs for 90 days by default and lets the practice shorten that. Platform B says it is HIPAA compliant, sends a link to its security page instead of a template, and says message content may be used to improve its service.
On the scoring sheet Platform B gets a 0 on the agreement and on training use. Those are red lines, so the practice manager stops there, even though Platform B's booking screens looked better in the demo. She files the scored checklist with Platform A's signed agreement and sets a calendar reminder to repeat the review at renewal.
Frequently asked questions
Is a vendor's HIPAA compliance badge enough?
No. There is no official HIPAA certification for vendors. What matters is a signed business associate agreement plus clear written answers on storage, access, retention and subcontractors.
Do we need a BAA if the tool only stores appointment times and phone numbers?
Usually yes. A phone number linked to an appointment at a medical practice is patient information. Treat it as such unless the tool truly holds no identifiable details.
Who in the practice should run this review?
The practice manager or privacy officer should own it, with input from whoever manages IT. Keep the completed checklist with the contract.
How often should we repeat the review?
At least at every renewal, and any time the vendor adds a feature that changes what data it handles, such as call recording or AI summaries.
References
Medical Group Management Association (MGMA) (2026). Automatic for the people: AI moves for medical practices to boost the front office and access (opens in a new tab) ↑
KFF (2026). KFF Tracking Poll on Health Information and Trust: Use of AI For Health Information and Advice (opens in a new tab) ↑
Legal Information Institute, Cornell Law School (current). 45 CFR § 164.502 - Uses and disclosures of protected health information: General rules (opens in a new tab) ↑
Legal Information Institute, Cornell Law School (current). 45 CFR § 164.504 - Uses and disclosures: Organizational requirements (opens in a new tab) ↑
Legal Information Institute, Cornell Law School (current). 45 CFR § 164.410 - Notification by a business associate (opens in a new tab) ↑
Legal Information Institute, Cornell Law School (current). 45 CFR § 164.312 - Technical safeguards (opens in a new tab) ↑
Federal Communications Commission (2024). FCC Makes AI-Generated Voices in Robocalls Illegal (news release) (opens in a new tab) ↑
Federal Communications Commission (2024). FCC Makes AI-Generated Voices in Robocalls Illegal (news release) (opens in a new tab) ↑