HIPAA Meeting Transcription (2026)

The problem with cloud transcription in healthcare

Healthcare meetings — patient consultations, case conferences, clinical team discussions, insurance calls — contain Protected Health Information. When you use a cloud transcription tool, that PHI travels to and is processed on someone else's servers.

• BAA complexity. You need a Business Associate Agreement with any vendor handling PHI. This requires legal review, vendor vetting, and ongoing compliance monitoring.
• Breach exposure. Healthcare data breaches cost an average of $10.93M (IBM, 2023). Every vendor with access to PHI is a potential breach vector.
• Model training concerns. Some transcription vendors have faced questions about using customer data for AI model training. Even with opt-out, the data still resides on their infrastructure.
• Audit trails. HIPAA requires documentation of where PHI goes. Cloud transcription adds complexity to your data flow documentation.

On-device: a different compliance model

Resonant processes meeting audio on your Mac's Neural Engine. The audio never leaves the device. Transcripts are stored locally. There is no data transmission to Resonant or any third party.

This fundamentally changes the compliance conversation:

• No BAA needed. No data is shared with a business associate. There's no third party in the transaction.
• No breach vector. If data never leaves the device, it can't be breached on someone else's servers.
• Simple audit. Data stays on one device. The audit trail is: “audio was captured and processed locally on [device].”
• No model training concerns. We never have your data. There's nothing to train on.

Healthcare use cases

• Telehealth consultations. Transcribe patient calls running through your Mac without uploading audio to a cloud service.
• Clinical team meetings. Case conferences where patient details are discussed.
• Insurance and billing calls. Conversations involving patient identifiers and treatment details.
• Supervision and training. Clinical supervision sessions where patient cases are reviewed.
• Research interviews. Participant interviews where research data should remain controlled.

Important notes

• Resonant is a transcription tool, not a certified EHR or medical documentation system.
• Recording consent requirements vary by state and setting. Always follow applicable laws.
• Device security (encryption, password, physical access) remains your responsibility.
• Consult your compliance team or healthcare attorney for your specific workflow.

Related resources

• Medical dictation for Mac— clinical dictation workflows.
• Private meeting transcription— the privacy architecture in depth.
• Meeting transcription without a bot— how capture works invisibly.

Frequently asked questions