Skip to content
← Back to News

product-launch · October 29, 2026

By Joe Jurczyk, Editor

HeyGen says its Enterprise tier now supports HIPAA-eligible workflows

HeyGen will sign business associate agreements with qualifying Enterprise customers, allowing protected health information in designated services. The company describes the service as HIPAA-eligible rather than HIPAA-compliant.

healthcare
compliance
enterprise
avatar video

HeyGen said on 29 October that its platform now supports HIPAA-eligible workflows for Enterprise customers, backed by a business associate agreement (BAA). The company's wording is HIPAA-eligible rather than HIPAA-compliant: it says it runs on HIPAA-eligible infrastructure, signs BAAs with qualified Enterprise clients, and operates a shared-responsibility model in which protected health information should be used only under an executed BAA and only within designated HIPAA-eligible services. The post lists intended uses including patient education in a patient's preferred language, discharge and post-care engagement, patient support programmes, communication from key opinion leaders to healthcare providers, and clinical trial recruitment and training, and says output can be routed through medical, legal and regulatory review workflows. It cites support for 177+ languages and dialects. The post does not name which services are designated, and says nothing about encryption, data retention or audit controls. Claims about reduced production cost, faster turnaround and lower readmission risk are stated without figures.

Why it matters for digital humans: Healthcare is one of the clearer commercial cases for avatar presenters — the same discharge instruction delivered in a patient's own language, at a cost per language no filmed clinician can match — and the absence of a BAA has been a hard stop for buyers in that sector. So this reads as a procurement unlock more than a product release. The distinction HeyGen draws is worth holding onto: HIPAA-eligible means the vendor will contract for protected health information on qualifying infrastructure, not that any particular configuration is compliant, and the covered entity still owns scope and controls. Anyone evaluating this should ask which services are designated, have the BAA reviewed before patient data goes near a prompt, and treat the cost and readmission claims as unevidenced until the vendor produces data.

Related research