Add medical scribe callouts to async quickstart, models, and evals pages#784
Open
agalyanmann wants to merge 1 commit intomainfrom
Open
Add medical scribe callouts to async quickstart, models, and evals pages#784agalyanmann wants to merge 1 commit intomainfrom
agalyanmann wants to merge 1 commit intomainfrom
Conversation
Route healthcare/medical scribe builders to the Medical Scribe Best Practices guide from the three pages they are most likely to land on: the async getting-started quickstart, the models overview (Universal-3 Pro section), and the pre-recorded evals guide. Also adds a section on domain-specific evaluation beyond WER, since medical scribe customers often evaluate based on user preference rate and readability rather than word error rate alone. Follows the same <Tip> callout pattern used for voice agent routing in PRs #782 and #783. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
<Tip>callout to the async getting-started quickstart (transcribe-an-audio-file2.mdx) routing medical/healthcare builders to the Medical Scribe Best Practices guide<Tip>callout to the models page (models.mdx) in the Universal-3 Pro section highlighting U3 Pro's medical terminology accuracy and linking to the best practices guidepre-recorded-evals.mdx) explaining that WER is not always the right primary metric — medical scribe customers often evaluate based on user preference rate and readabilityContext
A healthcare customer evaluated using the older async model (not U3 Pro) and optimized for WER rather than user preference rate / readability — the metrics that actually mattered for their clinical documentation use case. The Medical Scribe Best Practices page already exists but was not discoverable from the async getting-started flow or model selection page.
This follows the same
<Tip>callout pattern used for voice agent routing in PRs #782 and #783.Test plan
<Tip>callouts render correctly on the async getting-started page<Tip>callout renders correctly in the Universal-3 Pro section of the models page/docs/use-cases/medical-scribe-best-practicesresolve correctly🤖 Generated with Claude Code