- Dragon Copilot does support working with CPT and other billing codes, but the context only confirms this at the level of prompts and coding workflows, not specifically that CPT codes will be rendered inside an Assessment and Plan customizable template section. The documented examples show prompts like “Update A&P with CPT codes” and “Add ICD-10 codes to each diagnosis,” which indicates that Copilot can place codes into the note text, including Assessment and Plan, when driven by an appropriate prompt.
- The context does not document any special or required template syntax (such as a particular placeholder format) that guarantees CPT code generation in a customizable template. The guidance for customizable templates is generic: select a section (such as Assessment and Plan), edit the template text and instructions, and then let generative AI produce content that must be reviewed and edited. There is no documented reserved syntax for CPT that differs from ICD-10 or other code types.
- The context confirms that Dragon Copilot can generate and enrich codes (ICD-10, HCC, E&M, SNOMED CT, CPT, etc.) and that prompts can request codes directly (for example, “Update A&P with CPT codes,” “Add ICD-10 codes to each diagnosis”). However, it does not specify any separation between codes available in the UI note sections versus codes only available via a partner API payload. The behavior of the Dragon Data Exchange partner API payload versus what appears in the rendered note is not described in the provided material.
Given the available documentation, the only supported, documented levers are:
- Use prompts that explicitly instruct Copilot to add CPT codes into the Assessment and Plan text, such as:
- “Update A&P with CPT codes.”
- “Add ICD-10 codes to each diagnosis.”
- Use customizable templates on the Assessment and Plan section, understanding that output is generative and must be reviewed, and that behavior cannot be fully predicted.
For this scenario (CPT not appearing despite template instructions and prompts), the context does not provide additional configuration steps, template syntax, or API/UI distinctions beyond the above. Escalation to product support would be required to confirm whether this is a product limitation or an integration-specific issue with the Dragon Data Exchange partner API.
References: