Amazon Transcribe Medical - Benchmarks & Performance - OpenTranscription

Back to Models$0.075/min

Amazon Transcribe Medical

Name: Amazon Transcribe Medical
Author: Amazon Web Services

Amazon Web Services

Batch

Medical transcription with HIPAA eligibility

Transcribe with this model Compare in playground

1 languages · benchmarked

Overall Score

42.5

#23 of 28

Word Error Rate

14.92%

Character Error Rate

9.67%

Match Error Rate

13.82%

Word Info Lost

18.41%

Avg Latency

11.4s

Benchmarks Run

Benchmark trend

last 30 runs

Word error rate

14.92%

↓ 5.9% · 30d

3 runs ago

latest

Avg latency

11.4s

↓ 0.4% · 30d

3 runs ago

latest

Cost vs. accuracy

overall WER · 28 models

Amazon Transcribe Medical

field · 27 models

lower-left is better

Performance by category

8 categories

WER

lower is better

Technical

3.2%

Medical

3.7%

General

4.7%

Legal

6.2%

Finance

6.3%

Conversational

6.9%

Noisy Environment

41.7%

Code-Switching

55.8%

Category	WER	CER	MER	WIL	Latency	Benchmarks
Code-Switching	55.76%	39.67%	55.22%	65.25%	16.1s	2
Conversational	6.85%	3.80%	6.68%	10.13%	11.1s	2
Finance	6.32%	2.95%	6.25%	10.13%	10.8s	2
General	4.70%	2.39%	4.70%	7.19%	10.9s	9
Legal	6.19%	4.53%	6.12%	7.57%	11.0s	2
Medical	3.72%	1.47%	3.72%	5.62%	11.0s	2
Noisy Environment	41.67%	28.03%	35.24%	46.94%	10.9s	4
Technical	3.20%	1.64%	3.17%	5.17%	11.1s	2

Performance by accent

5 accents

Accent	WER	Benchmarks
African	24.62%	1
Australian	6.15%	1
Indian	3.17%	1
British	0.00%	1
American	1.89%	1

Pricing

pay per second

Rate

$0.075

/min

Per-second billing. Bring your own provider key and pay your provider directly — a 5% routing fee applies (first 100 min/mo free).

Set up BYOK

Cost estimator

1 hour

$4.50

10 hours

$45

100 hours

$450

1,000 hours

$4500

Billed per second of audio processed.

API & usage

POST /api/v1/transcriptions

Model ID

aws/transcribe-medical

Get an API key

Authenticate every request with your secret API key as a Bearer token. Issue a key from your dashboard.

Quickstart

Upload your audio, create a job with this model, then poll the job or set a webhook_url to be notified when it completes.

# 1. Request a signed upload URL
curl https://opentranscription.io/api/v1/uploads \
  -H "Authorization: Bearer $OT_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "file_name": "interview.mp3", "file_size": 3456789, "mime_type": "audio/mpeg" }'
# → { "upload_url": "...", "file_path": "...", "expires_at": "..." }

# 2. Upload the audio bytes to the signed URL
curl -X PUT "$UPLOAD_URL" --upload-file interview.mp3

# 3. Create the transcription job
curl https://opentranscription.io/api/v1/transcriptions \
  -H "Authorization: Bearer $OT_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "file_path": "$FILE_PATH",
    "model": "aws/transcribe-medical",
    "language": "en",
    "diarization": true,
    "webhook_url": "https://your-app.com/webhooks/ot"
  }'
# → we POST a signed event to your webhook_url when the job finishes — no polling required

Key parameters

file_path

string

required

Storage path returned by the upload step.

model

string

required

The model to run this job on.

language

string

ISO 639-1 language code. Omit to auto-detect.

diarization

boolean

Label speakers (A, B, …) in the output.

webhook_url

string

HTTPS URL notified with the result when the job completes. Delivered events are signed (X-OT-Signature).

Response

A completed job returns the transcript in the OpenTranscription Unified Schema (OTUS).

{
  "id": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
  "status": "completed",
  "transcript": {
    "text": "Welcome to the meeting, everyone.",
    "language": "en",
    "confidence": 0.97,
    "segments": [
      {
        "id": 0,
        "start": 0,
        "end": 3.5,
        "text": "Welcome to the meeting, everyone.",
        "speaker": "A"
      }
    ],
    "words": [
      {
        "word": "Welcome",
        "start": 0,
        "end": 0.42,
        "confidence": 0.99
      }
    ]
  }
}

Webhooks — skip polling

We POST a signed event to your webhook_url when a job completes or fails; verify the X-OT-Signature (HMAC-SHA256, reject if older than 300 s) and dedupe on the event id, then fetch the full transcript via GET /api/v1/transcriptions/{id}.

# We POST a signed event to your webhook_url when a job finishes.
# Headers:
#   X-OT-Signature: t=1736937042,v1=5257a869e7eceb6c6c2c2a1b4d6e9f8c2a1b4d6e9f8c2a1b4d6e9f8c2a1b4d6e
#   X-OT-Event-Id: evt_9f8c2a1b4d6e
#   X-OT-Event-Type: transcription.completed
#
# Body (thin event — fetch the transcript with GET /transcriptions/{data.id}):
{
  "id": "evt_9f8c2a1b4d6e",
  "event": "transcription.completed",
  "created": "2025-01-15T10:30:42.000Z",
  "data": {
    "id": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
    "status": "completed",
    "error_code": null
  }
}
#
# Verify: HMAC-SHA256 over "<t>.<raw_body>" with your signing secret,
# constant-time compare against any v1, and reject if |now - t| > 300s.

Rate-limited per tier — see the X-RateLimit-* response headers.

Full API reference

Reliability

rolling 30 days

Uptime · 30d

100.00%

Error rate

0.00%

Avg latency

19.4s

Last incident

None in 30d

Similar models

from the same field

More accurate

Amazon Transcribe

Amazon Web Services

4.71% WER

$0.006/min

Compare →

Cheaper

Whisper Large V3 Turbo

Groq

— WER

$0.0007/min

Compare →

Supported Languages

English

Supported Formats

mp3wavflacm4aogg

Features

HIPAA CompliantAsync APIDiarization+2

Amazon Transcribe Medical

Benchmark trend

Cost vs. accuracy

Performance by category

Performance by accent

Pricing

API & usage

Reliability

Similar models

About Amazon Transcribe Medical