Medical Copilot Is Live Inside eClinicalWorks
Medical Copilot is now live inside eClinicalWorks. If your practice runs on eCW, your physicians can launch our Clinical Documentation and Coding Intelligence directly from the Progress Note, without ever leaving the chart. No new system to log into, no copy and paste, no workflow change.
Think of it as a scribe and a coder sitting next to every physician, on every encounter. You trigger the application from the Progress Note, and in around ten seconds it runs everything in parallel and gets the encounter ready to finalize.
What happens when you launch it from the Progress Note
It starts from the full picture. Medical Copilot reads the notes, the lab results, the orders, and the services, whatever is already sitting in the chart. Because it starts from the complete record, nothing gets missed just because it was buried in the EHR.
When something is missing, it asks. If the documentation cannot support the most accurate code, it asks the questions needed to close the gap before the claim goes out, not months later in an audit or a denial. Each query is a compliant clarification with the answer options ready to click. If no gaps are found, no query is raised.
Your answers are written back to the chart. Responses to queries are written back into the eClinicalWorks Progress Note, so the documentation stays consistent and ready for any insurance audit. Confirmed diagnoses and codes are written back as well. The chart, the documentation, and the claim always tell the same story.
What that looks like on real encounters
Closing a specificity gap. An office follow-up for a patient with type 2 diabetes and chronic kidney disease arrives with two diagnoses, both unspecified. Medical Copilot spots the gap: the CKD stage is never stated, and the stage is required for the best ICD-10 code. So it asks exactly one question: what stage is this patient's chronic kidney disease? The physician picks the stage, the answer is written back into the note, the diagnosis becomes specific, and the claim now reflects the most accurate code.
Connecting the dots already in the chart. A routine heart failure follow-up is coded as unspecified heart failure, yet the echo in the chart shows an ejection fraction of 25 percent. The note never says whether the failure is systolic, diastolic, or combined, so Medical Copilot connects those findings and asks the one question that settles it.
Knowing when not to ask. On a similar heart failure follow-up where the physician has already stated the type, no query comes up at all. Medical Copilot goes straight to the correct code, I50.22, chronic systolic congestive heart failure, with the plain-language justification, the guideline it applied, and the HCC risk mapping attached as evidence.
Coding what the guideline requires. A sleep medicine note carries a single code, insomnia unspecified, but the physician documented chronic insomnia related to chronic low-back pain. That relationship changes the coding. Medical Copilot replaces the unspecified code with insomnia due to a medical condition and, because the guideline requires it, adds the low-back pain as its own diagnosis. Two documented conditions, both on the claim, no query needed.
Beyond diagnoses, Medical Copilot suggests the CPT and HCPCS service codes tied to their source text and supporting diagnosis, checks bundling rules and MUE quantities, and suggests a supported Evaluation and Management level with the medical-decision-making drivers behind it. The levels are consistent and defensible: no undercoding out of caution, no overcoding risk. When a same-day procedure is involved, it checks whether the visit truly bills separately before adding modifier 25, and when the chart shows no evidence for a separate visit, it knows not to code one.
Three ways in, one engine
Everything above runs the same no matter how the encounter comes in.
- From the Progress Note. The physician clicks the app shortcut inside eClinicalWorks and Medical Copilot runs right there in the chart. This is live today.
- By voice. The physician talks, Medical Copilot captures the encounter, and the conversation drops straight into the same engine. Clinicians stay hands-free and the documentation is complete with a full Progress Note.
- Through the backend worklist. Once encounters are completed, Medical Copilot pulls them regularly from the EHR into a ready queue. Physicians can review between patients or at the end of the day, and the results write back to the chart. The worklist also serves coding teams who monitor and confirm codes on behalf of physicians: they confirm the clear cases themselves and refer only the queries to the doctors.
Why this matters for eClinicalWorks practices
The care has already been delivered. Medical Copilot makes sure the documentation, the diagnosis, and the codes prove it. For a practice on eCW, that means less documentation burden for physicians, fewer denials and resubmissions for the billing team, specificity and HCC capture that hold up under audit, and clean claims paid right the first time.
Integration with athenahealth is coming soon, and the same reviewer-controlled workflow will apply there as well.
Getting started
Getting started is easy. Because Medical Copilot launches inside eClinicalWorks, there is no migration project: we can have your practice fully onboarded in one day.
To see it on your own encounters, inside your own eClinicalWorks environment, book a demo.
eClinicalWorks® is a registered trademark of eClinicalWorks, LLC. athenahealth® is a registered trademark of athenahealth, Inc. Clinical examples are illustrative and are not real patient encounters.