Building a HIPAA-Compliant Healthcare Voice AI Agent
February 15, 2025 · 2 min read · Ortavox Team
A practical guide to deploying AI voice agents for healthcare use cases: appointment scheduling, patient reminders, and triage. Covers HIPAA requirements, PHI handling, BAA agreements, and architecture best practices.
AI voice agents are transforming healthcare operations. From appointment scheduling and medication reminders to post-discharge follow-ups and insurance pre-authorization calls, the use cases are compelling — and the stakes are high. A misconfigured voice agent that mishandles Protected Health Information (PHI) can result in HIPAA civil penalties that, after the January 2026 inflation adjustment, range from $145 to $73,011 per violation depending on the culpability tier, with annual caps of up to $2,190,294.
What makes a voice AI agent HIPAA-compliant?
- All audio and transcripts encrypted in transit using TLS 1.3 or higher
- PHI at rest encrypted using AES-256
- Automatic transcript deletion after configurable retention period (30–90 days)
- Audit logging of every access to call data with immutable timestamps
- Business Associate Agreement (BAA) with all vendors handling PHI
- No PHI in URL parameters, log files, or error messages
Business Associate Agreements (BAA)
Any vendor that handles PHI on your behalf must sign a BAA. For a voice AI pipeline, this includes your voice AI platform, your LLM provider, your STT provider, your TTS provider, and your telephony provider.
Not all LLM providers offer HIPAA BAAs, and the ones that do attach conditions. As of November 2026: OpenAI offers a BAA for API customers on request, limited to eligible endpoints and typically paired with zero data retention; Anthropic offers a BAA for the Claude API and its HIPAA-ready plans; Groq publishes a Customer Business Associate Addendum for GroqCloud (effective October 15, 2025) that excludes beta services. Check each provider's current terms before sending PHI.
Example: appointment reminder agent
{
"system_prompt": "You are an appointment reminder assistant. Confirm patient identity before discussing any health information. Never discuss diagnoses, medications, or test results.",
"hipaa_settings": {
"verify_identity_before_phi": true,
"allowed_phi_fields": ["appointment_date", "appointment_time", "provider_name"],
"blocked_phi_fields": ["diagnosis", "medications", "test_results"]
}
}Getting a HIPAA BAA with Ortavox
Ortavox Enterprise includes a HIPAA Business Associate Agreement and data residency options in US, EU and APAC regions, with on-premise deployment available for workloads where no audio may leave your network. On every plan, audio and transcript data is encrypted in transit (TLS 1.3) and at rest (AES-256), and call recordings are deleted after 30 days by default or can be disabled entirely. Contact enterprise sales to begin the BAA process.
Sources
- The HIPAA Journal — What are the Penalties for HIPAA Violations? — https://www.hipaajournal.com/what-are-the-penalties-for-hipaa-violations-7096/
- OpenAI Help Center — How can I get a Business Associate Agreement (BAA) with OpenAI? — https://help.openai.com/en/articles/8660679-how-can-i-get-a-business-associate-agreement-baa-with-openai
- Anthropic — Business Associate Agreements (BAA) for commercial customers — https://support.claude.com/en/articles/8114513-business-associate-agreements-baa-for-commercial-customers
- Groq — Customer Business Associate Addendum — https://console.groq.com/docs/legal/customer-business-associate-addendum
- Ortavox — How it works (security and compliance) — https://ortavox.ai/how-it-works
- Ortavox — Pricing (Enterprise) — https://ortavox.ai/pricing