domains / families / data / digital-health-clinical-asr-build

digital-health-clinical-asr-build

separate

Stage 2 of the Clinical ASR Flywheel. Use when curating clinical terms, tagging IPA, and synthesizing a NeMo manifest. NOT for scoring (use /digital-health-clinical-asr-eval).

When to use

• Curate a clinical-specialty term list, generate eval audio for it through Magpie TTS with a two-tier IPA pipeline, and write a NeMo-format manifest tagged with the clinical-extension fields (`term`, `entity_category`, `ipa_source`, `voice_…
• "Build a clinical ASR benchmark"
• "Curate drug names / procedure names for ASR eval"
• "Generate eval audio for medical terms"
• "Create a NeMo manifest from clinical terms"
• "Add oncology / cardiology / ortho terms to my benchmark"
• "Audition the TTS pronunciation for these drug names"
• "Make me a cycle-N manifest"

When not to use

• **English-only by default.** Magpie's en-US phoneme inventory is what the two-tier IPA pipeline validates against. Other locales need a different upstream phoneme set + override CSV format.
• **Six fixed entity categories.** Extending `entity_category` is a deliberate methodology change, not a one-off tweak — KER breakdowns, leaderboard sections, and downstream finetune scripts all key off the vocabulary.
• **Tiny first cycles.** Below ~20 terms, the by-`ipa_source` leaderboard split won't have enough rows in each bucket to be statistically meaningful. Build a meaningful cycle even if it costs a session.
• **Magpie NVCF rate-limits.** ~5–10% drops on large jobs; budget a re-run pass.

Skill page

Source