The most effective revenue cycle strategy starts with patients, not paperwork. Dragon Copilot augments clinician care, helps capture the full patient story, and supports accurate reimbursement as a byproduct of good clinical documentation.
This blog is co-authored by Josh Waldo, Product Manager, Joeri Van der Vloet, Principal Research Manager, and Koen Mertens, Senior Research Manager.
Many health systems treat revenue cycle performance solely as a downstream problem. Clinicians complete documentation, teams send notes to coders, queries follow, and everyone works backward to recover what was missed. In some cases, recovery isn’t even possible in this model. With the rise and pervasiveness of AI, there is an opportunity to rethink the model by improving documentation quality and comprehensiveness at the point of care. In this new model, reimbursement accuracy can be captured before the opportunity has been lost.
In this blog post, we walk through three powerful approaches we use in Dragon Copilot to support revenue cycle management (RCM):
- Embed revenue cycle intelligence directly into the clinical workflow, delivering built-in guidance as documentation is created—while the patient is still in the room—to ensure critical details are captured.
- Deliver that intelligence directly into existing EHR workflows wherever possible.
- Extend RCM capabilities through an open ecosystem, enabling specialized partners to bring their coding expertise directly into the same workflow.
Clinicians document using Dragon Copilot while revenue relevant insights surface in context before notes ever move downstream. The result is better reimbursement accuracy, fewer back and forth exchanges, and less rework for clinicians and revenue cycle teams.
The problem, the opportunity, and the shape of a workflow solution
Most revenue cycle friction traces back to incomplete or imprecise documentation. Missing specificity, unclear assessments, and undocumented work create queries, denials, delays, and rework. The opportunity is to move RCM support upstream to the point where documentation is being created, with help that is context aware, transparent, and clinician controlled.
Solutions must analyze the patient, context and resulting documentation as they are created and surface opportunities related to:
- Diagnosis specificity and diagnostic comprehensiveness
- HCC capture and recapture opportunities
- Evaluation and management (E/M) level considerations
- Completeness of documentation relative to established criteria, like MEAT (monitor, evaluate, assess, treat)
- Prior authorization guidelines
- Complete capture of CC’s/MCC’s and other inpatient guidance
The shape of the solution must also provide assistance that shows up inside the documentation flow. It should feel like a light touch and not a separate destination or a stream of alerts. The design goal is to minimize distraction, avoid overwhelming notifications, and make every suggestion easy to review with clear evidence. Further, the nudges need to be actionable. With the click of a button, a clinician should be able to accept/reject the insight and have the appropriate actions then ensue, such as updating documentation automatically.
Small improvements may look modest in a single note, but they compound across clinicians and visits when applied consistently. If we can help clinicians capture the full clinical picture once, downstream processes inherit better inputs without asking clinicians to do a second pass.
Recognizing the scope of RCM opportunities in both ambulatory and inpatient, we are taking a three-pronged approach to help healthcare organizations enable the broadest and deepest set of coding skills into their Dragon Copilot workflows.
Built-in suggestions
Dragon Copilot already provides built-in capabilities that support RCM by improving the note itself, and we are continuing to expand them. We start by capturing all the minute details of what happened during the encounter and helping clinicians turn that into clear and comprehensive documentation. The goal is accurate and complete capture of the work performed and the patient complexity.
Dragon Copilot also supports on-demand billing code support. For each documented diagnosis, we can suggest relevant ICD-10 code options with supporting evidence so clinicians can quickly validate what is being proposed. We can also generate a coding summary report for each note to support downstream review.
Next, Dragon Copilot includes built‑in, proactive diagnosis specificity suggestions designed to support clinicians in selecting the most accurate and specific diagnoses at the point of documentation. As clinical notes are created, Dragon Copilot analyzes the documented clinical context and identifies opportunities where a diagnosis may be underspecified or incomplete.
When applicable, Dragon Copilot surfaces suggestions to refine a diagnosis (for example, laterality, acuity, severity, underlying cause, or associated conditions). For risk‑adjusted conditions, it helps clinicians identify diagnoses that may impact Hierarchical Condition Categories (HCCs), while emphasizing the need for complete, clinically appropriate, and defensible documentation.
All suggestions are advisory and designed to fit naturally into the clinician’s workflow. Clinicians remain fully in control, able to review, accept, modify, or ignore suggestions based on their clinical judgment. It does not add diagnoses automatically and does not replace clinical decision‑making. Its goal is to reduce missed specificity, support accurate clinical representation of patient complexity, and help ensure documentation aligns with coding and compliance expectations.
At a user experience level, we want this to be simple and predictable as outlined in this workflow:
- The clinician documents using Dragon Copilot’s suite of documentation tools.
- Once the note is drafted, a set of relevant suggestions to refine a diagnosis is surfaced discreetly in workflow
- Each opportunity includes the why, the evidence, and a suggested improvement.
- The clinician can accept, ignore, or defer, and stays in control at every step.
- The note is improved before it reaches coding, reducing the need for back-and-forth exchanges later.
Done well, this approach improves documentation quality without changing clinical practice. It reduces avoidable queries, supports more consistent coding outcomes, and helps revenue cycle teams spend less time on cleanup.
Looking ahead, these built-in proactive capabilities will be extended into additional high value areas such as E/M level considerations and completeness expectations such as MEAT (monitor, evaluate, assess, treat).
Integrated EHR context and workflow
Deep EHR connectivity is a force multiplier because it provides context and continuity. With the right backend integrations, Dragon Copilot can leverage chart data to understand the patient history, current problems, and the broader clinical picture that surrounds the encounter.
For example, this can include access to relevant prior notes, the problem list, medications, allergies, labs, imaging results, and structured diagnoses already documented in the chart.
This context helps us enrich the completeness and accuracy of notes before anything is presented to the clinician.
Connecting directly to EHR workflows also matters. When insights and supporting evidence can be presented in the same places clinicians already review the chart, reconcile problems, place orders, and finalize documentation, we reduce context switching and increase the likelihood that improvements happen at the right moment.
We are already building these powerful workflows with some of the most widely used EHRs in the world and are bringing the ability to get diagnosis specificity directly in workflow as one example.
This is also where we can align RCM support with clinical actions. Suggestions should appear when they are most useful, such as while the diagnoses are reviewed and the note finalized.
This strategy is also about trust and safety. Clinicians should be able to see where a suggestion comes from, what it is based on, and why it matters, without leaving their workflow.
Partner extensions
RCM is complex and it looks different across organizations, service lines, and care settings. No single approach fits every health system and covers all the targeted needs. An ecosystem approach allows specialized partners to bring their expertise into the same workflow. With an open ecosystem, any partner can integrate coding into workflow in a self-service and standardized fashion, opening coding at scale and giving health systems the widest range of options to choose from.
We see some of the most developed expertise and exciting innovations coming from our partners. Dragon Copilot now serves as a consistent channel into the workflow, so our partners can deliver value without having to reinvent access to encounter context, user experience patterns, and distribution inside the EHR.
Examples of what partner extensions can enable include:
- Specialty specific documentation guidance that reflects local policy and payer mix.
- HCC program support that includes organization specific rules for capture and recapture.
- Prior authorization support that highlights requirements earlier, when care decisions are being made.
- CC’s/MCC’s identification to accurately capture O/E ratios
The goal is to let health systems choose what to enable, where to enable it, and for whom, while keeping the clinician experience consistent and limiting disruption.
Patient-first is the best revenue cycle strategy
The most effective revenue cycle strategy starts with patients, not paperwork. Dragon Copilot augments clinician care, helps capture the full patient story, and supports accurate reimbursement as a byproduct of good clinical documentation.
When technology fades into the background and supports clinicians without interrupting care, everyone benefits: clinicians reclaim time, revenue cycle teams see fewer issues, and health systems are reimbursed accurately for the care they provide.
Microsoft