Vendor setup · Transcription
AWS Transcribe Medical
AWS is coming to DirectScribe as a transcription option for practices that want the strongest compliance posture — a signed AWS BAA and a Canadian data region. It is not available at launch.
Coming soon Transcription (STT) AWS BAA · ca-central-1
Coming soon
The AWS transcription path is a planned fast-follow. This page is a preview so you can plan; the vendor is not selectable in the app yet. When it ships, this guide will carry the full step-by-step setup.
Why AWS, for maximum compliance
- A BAA you can actually sign. AWS provides a Business Associate Agreement (via AWS Artifact) that covers eligible services including Transcribe Medical.
- Canadian data region. Processing can be pinned to
ca-central-1for data-residency requirements. - A purpose-built medical model. Transcribe Medical is tuned for clinical vocabulary.
The trade-off is cost: at ~440 notes/month, AWS is materially more expensive than Deepgram or ElevenLabs — see the cost breakdown. It suits practices whose compliance requirements justify it.
What setup will involve (preview)
Create an IAM user with Transcribe Medical access
In the AWS console, create an IAM user scoped to the Transcribe Medical permissions DirectScribe needs.
Generate an access key pair
Create an access key ID and secret access key for that user. Unlike the other vendors, AWS uses a key pair plus a region rather than a single key.
Choose your region
Select
ca-central-1if you require Canadian data residency.Sign the AWS BAA
Accept the AWS BAA through AWS Artifact before sending any patient-derived audio.
Not legal advice
Availability of a BAA and eligible-service scope are AWS terms that change; confirm current details with AWS. Whether this meets your obligations under PIPEDA and your provincial health-privacy law is a decision for you and your privacy advisor. See the Compliance Centre.
Let us know if AWS support would make DirectScribe viable for your practice — it helps us prioritise.