We’re migrating to Dragon Medical One in February, and I’m building a shared orthopedic terminology set to standardize AO/OTA fracture language and implant descriptors across our pool. If you’ve done this, what combo of tools — TextExpander snippets, Dragon custom vocab, or Epic SmartPhrases — gave you the best accuracy on items like tibial plateau ORIF, Broström repair, and SLAP lesions while keeping the QA workflow clean?
We got the best accuracy in DMO by loading a custom vocab with spoken/written pairs for AO/OTA codes and key procedures — e.g., spoken “brostrom repair” → written “Broström repair” and “tibial plateau orif” → “tibial plateau ORIF” — then letting Epic SmartPhrases handle boilerplate. Caveat: disable Dragon’s auto-format for numbers or it’ll mangle AO/OTA strings like 41-B3.1.
Building on @david_m59: push a curated procedures/eponyms list through Nuance Management Center with simple spoken forms and keep the written forms exact, including “Broström.” Use Epic SmartPhrases for the templated bits (laterality, implants) and reserve TextExpander for brand/size strings with a semicolon trigger to avoid collisions. We did this two weeks before a DMO go‑live and it stabilized accuracy; just disable TE in the Hyperspace dictation box or it fights Dragon.
One trick that helped me was prefixing spoken forms with a short, unique trigger (like a secret handshake), so saying “ortho ankle scope” forces the exact capitalization/diacritics and avoids false positives. I pair that with TextExpander fill-ins for implant details and keep DMO vocab for single eponyms (agree with @MayaJobs on simple spoken forms), but small caveat: staff have to learn the trigger; want my CSV template for bulk import via Nuance Management Center?