HIPAA
Not legal advice. This page describes legal and regulatory frameworks in general terms. Jurisdiction changes the answer, and the same voice deployment can be lawful in one market and unlawful in another. Take advice on your specific circumstances.
In one sentence
HIPAA is the United States law governing the privacy and security of health information, and any voice AI vendor that handles patient information on behalf of a healthcare provider becomes a business associate directly bound by it.
Not to be confused with SOC 2, or PCI DSS.
Definition
HIPAA is the US law that governs how health information is kept private and secure.
A voice agent taking patient details for a clinic sits squarely inside it, and the vendor behind that agent carries contractual liability of its own.
The Health Insurance Portability and Accountability Act regulates protected health information through three rules: Privacy, Security and Breach Notification. They bind covered entities and the business associates working on their behalf, and the obligations reach further down the supply chain than most vendors expect.
Who is covered
- Covered entities. Health plans, healthcare clearinghouses, and healthcare providers who transmit health information electronically.
- Business associates. Vendors that create, receive, maintain or transmit protected health information for a covered entity. A voice AI vendor serving a clinic is one.
- Subcontractors of business associates are bound too, which pulls the speech recognition, language model and speech synthesis providers in the pipeline into scope. Each has to be contractually covered.
The Business Associate Agreement
- A BAA has to be in place before any protected health information is handled. It is not optional and it is not a formality.
- It imposes specific obligations: safeguards, breach reporting, flow-down to subcontractors, and return or destruction of the information when the contract ends.
- Many general-purpose model providers offer BAAs on some tiers or configurations and not on others. That is a real architectural constraint on a voice pipeline, because a provider that will not sign cannot sit in the path.
What counts as protected health information in a voice conversation
- The audio itself, where it concerns an identifiable person's health, treatment or payment.
- The transcript.
- Appointment details, which reveal that somebody is a patient of a particular provider and by implication of a particular specialty.
- Even an appointment reminder implies a treatment relationship, which is why outbound healthcare voice needs care.
The Security Rule requirements that shape the architecture
- Access controls, audit controls, integrity controls and transmission security.
- Encryption is addressable rather than strictly mandated, though in practice sending protected health information unencrypted is indefensible.
- Audit logging of access is a specific requirement, so the dashboard showing transcripts needs access logging of its own.
The minimum necessary principle runs underneath all of it: use and disclose only what the purpose requires. A voice agent that retains full recordings where a structured summary would do has a minimum necessary problem, and retention decisions get tested against that standard rather than against convenience.
Common misconception
That HIPAA prohibits AI in healthcare. It does not. It requires the right agreements, safeguards and controls. The practical obstacle is pipeline composition rather than prohibition: every component that touches protected health information has to be contractually covered, and not every model provider will sign.
Why it matters commercially
Healthcare is one of the strongest use cases for voice agents, given the appointment volume and the dependence on the phone, and HIPAA is the gate in front of it. A vendor that can execute a BAA and demonstrate a covered pipeline can sell into the sector. A vendor that cannot is excluded regardless of product quality.
In voice specifically
Speech leaves two artifacts where text leaves one. The recording and the transcript are both protected health information, and the recording is the harder of the two to search, redact and destroy on request. A text conversation leaves a log. A voice conversation leaves a log and an audio file of somebody describing a symptom in their own voice.
Where AsqVox fits
The Orb is not positioned for handling protected health information today. It is covered here because healthcare inquiries are a common reason a business puts voice on its website, and because any owner in the sector will ask. The honest answer from any vendor is two things: whether a BAA is available, and whether every sub-processor behind the product is covered by it.
Visual
Every component in the path needs a signature
HIPAA does not ban AI. It requires every link in the chain to be covered.
Statistics
Every figure carries its source and year. Vendor numbers are labelled as vendor numbers, and where no reliable figure exists this page says so rather than borrowing one.
HIPAA regulates protected health information through three rules: the Privacy Rule, the Security Rule and the Breach Notification Rule.
Three rulesindustry rangeHIPAA Privacy, Security and Breach Notification Rules, 2026 - A statutory fact rather than a measurement. Cite the rule, not a vendor summary of it, and check the current text before relying on any detail.
Business associates and their subcontractors are directly subject to HIPAA obligations, and a Business Associate Agreement is required before protected health information may be handled.
BAA required firstindustry rangeHIPAA Privacy and Security Rules, 2026 - The flow-down to subcontractors is the clause voice pipelines fail on, because the speech recognition, model and synthesis providers behind the product are subcontractors in exactly this sense.
The Security Rule specifies administrative, physical and technical safeguards, including access controls, audit controls, integrity controls and transmission security.
Four technical controlsindustry rangeHIPAA Security Rule, 2026 - Audit controls are the requirement most often missed in a voice product, because the transcript dashboard is built as an internal tool and internal tools rarely ship with access logging.
The minimum necessary standard limits use and disclosure of protected health information to what the purpose requires.
Minimum necessaryindustry rangeHIPAA Privacy Rule, 2026 - This is the standard a retention policy gets measured against. Keeping everything because storage is cheap is the failure it describes.
No reliable published statistic exists for HIPAA enforcement specific to AI voice agents. The deployment base is young and enforcement precedent in this narrow area is thin.
-no reliable figureAnyone quoting an enforcement rate for AI voice is extrapolating from general HIPAA enforcement. Treat the absence as the finding rather than as reassurance.
BAA availability across model providers moves with product tiers and announcements, so any published list of which providers will sign ages quickly.
-no reliable figureCheck current provider documentation rather than a page like this one. It is the fact in this entry most likely to be out of date by the time you read it, which is why no provider is named.
A call handled by a person costs roughly USD 7 to USD 12, against roughly USD 0.40 for one handled by an agent.
USD 7 to 12 vs USD 0.40industry rangeWidely cited industry range, 2025 - Not an audited figure, and it varies with geography and call complexity. It is the cost pressure behind healthcare interest in voice, not evidence about compliance.
Examples
In practice
A clinic deploys a voice agent for appointment booking. An architecture review finds one component processing transcripts without a Business Associate Agreement: a sentiment analysis service, added later as an enhancement. It is removed from the protected health information path and replaced with an alternative that will sign. The clinical product did not change. The compliance chain did.
The everyday version
HIPAA is the American law about keeping patient information private. It does not stop you using AI. What it means is that every company handling that information has to sign an agreement taking responsibility, including the ones you never think about because they sit inside your supplier's product. One missing signature and the whole arrangement is a problem.
Usage
Who says it
- US healthcare compliance officers and privacy counsel, who use the term precisely.
- Healthcare IT procurement, for whom it is an absolute gating requirement.
- Vendors selling into US healthcare, who have to be fluent in it or will not be considered.
Where it turns up
- Usually in the same clause as BAA execution, the sub-processor list and its coverage, encryption in transit and at rest, audit logging, retention and destruction, breach notification timelines, and minimum necessary justification.
- The sub-processor coverage question is where most voice vendors fail, because their pipeline includes providers that will not sign.
Common misuse
- Claiming HIPAA compliance as a property of a product. Compliance belongs to a deployment and its agreements, not to software in the abstract.
- Assuming a BAA with the primary vendor covers the pipeline behind it. Flow-down to subcontractors has to be verified.
- Treating appointment data as non-clinical. It reveals a treatment relationship.
Questions people ask
Is AI HIPAA compliant?
Compliance is a property of a deployment and its agreements, not of software in the abstract. HIPAA does not prohibit AI in healthcare. It requires a Business Associate Agreement, appropriate safeguards and access controls, and every component that touches protected health information to be contractually covered. The practical obstacle is pipeline composition: some model providers sign BAAs only on certain tiers, and a provider that will not sign cannot sit in the path.
Does a voice AI vendor need a Business Associate Agreement?
Yes, before it handles any protected health information for a covered entity. A vendor that creates, receives, maintains or transmits that information on behalf of a healthcare provider is a business associate. The agreement imposes safeguards, breach reporting, flow-down to subcontractors, and return or destruction of the information when the contract ends.
What counts as protected health information in a voice call?
The audio itself, where it concerns the health, treatment or payment of an identifiable person. The transcript. The appointment details, which reveal that somebody is a patient of a particular provider and by implication of a particular specialty. Even an appointment reminder implies a treatment relationship, which is why outbound healthcare voice needs care.
Does a BAA with my voice vendor cover the whole pipeline?
Not automatically. Subcontractors of a business associate are bound as well, so the speech recognition, language model and speech synthesis providers behind the product are in scope and have to be covered by flow-down. Sub-processor coverage is where most voice vendors fail an RFP, because their pipeline includes providers that will not sign.
Last reviewed 30 July 2026. Written and reviewed by Dhruv Dholakia, founder of AsqVox.