What 25 Health System Leaders Told Us About AI’s Path Forward

Tell us a little bit about yourself—what do you like to do outside of work?

My family and I moved to Denver last year. I have a 2-year-old daughter and a 2-month-old son, so my life revolves around whatever they need. We relocated from Arizona to be closer to family (I have a brother and sister here and they are both married with kids!). Outside of work, we try to be as active as we can. Getting out and exploring Colorado and trying to coordinate as much as we can with friends and family in the area. 

As a kid, what did you want to be when you grew up?

I grew up in a competitive environment. I am the oldest of 5 (our family consists of 2 brothers followed by 2 sisters). Our lives had always been sports and I never imagined myself doing anything outside of that. My brothers and I all played football through college while my sisters competed in cross country through school. Because of this I always imagined myself as an athlete.

Describe a day in the life of your role.

Every day is different. I support a region of account executives who, for the most part, all come from clinical backgrounds. I am on calls most of the day, ranging from sales calls across the deal cycle where I am leading and/or supporting my team, strategic leadership discussions, collaboration across internal divisions, and also packing a bag and going to meet face-to-face onsite with groups!

What made you decide to join Commure?

I spent the better part of 2 years after I finished my MBA networking to find out what was next for my career. I explored everything you could imagine. I have a PT background and wanted to move more into the business side. I met Greg Martinez, who had really just started to get the clinical motion going here at Athelas-Commure, and it was really a quick no-brainer. I couldn't afford not to take the risk after seeing where the company was, where it's going, and the people involved. I had to be a part of it. 

How would you describe the Commure company culture?

It’s about the people. We have such a strong foundation in leadership. We understand the opportunity we have here to push this industry forward, we align on “why” we are doing what we are doing, and we have built so much trust together.

What advice would you give someone on their first day at Commure?

Keep moving. Ask all the questions because there is never enough time to learn it all. Lean on your leaders.

Interested in a career building the next generation of healthcare technology powered by AI? We are always looking for talented people across our departments.

Explore Career Opportunities

The reasons obstetricians chose medicine have little to do with the administrative demands that now dominate the clinical day. Documentation, coding, regulatory training, and the accumulating obligations of the electronic record have steadily encroached on the time clinicians can devote to their patients.

At Ob Hospitalist Group (OBHG), where more than 2,000 clinicians deliver vital women’s health services across the country, this growing imbalance has become increasingly difficult to sustain. That’s why OBHG’s adoption of Commure’s Autonomous Coding marks a decisive shift to restoring time, precision, and focus they need at the point of care. And for clinicians like Dr. Jana Thor, an OB/GYN hospitalist with OBHG, the impact has been both immediate and profound.

“Anything That Gives Us Time Back for Patient Care Is an Asset”

Like many physicians, Dr. Thor approached artificial intelligence in healthcare with hesitation.

“I was skeptical about AI in the clinical setting at first,” she admits. “But Autonomous Coding has been eye-opening. It doesn’t replace physicians or what we do. With the shortage we’re facing as clinicians, anything that saves us time so we can focus on patient care is an asset.”

For years, her coding workflow reflected the same frustrations expressed by clinicians across every specialty: manually entering patient identifiers; searching repeatedly for codes already documented; clicking through fields to supply information already contained elsewhere in the chart; and duplicating work that felt both inefficient and inescapable.

“My old workflow was painful,” she recalls. “Before you could even get to the coding, you had to manually enter the medical record number, date of birth, patient name. Even when your note was detailed and included diagnoses codes, you still had to hunt them down again.”

A Streamlined, Documentation-First Workflow

Commure’s Autonomous Coding fundamentally reshapes that experience. The system interprets clinical documentation (including CPT codes, ICD-10 diagnoses, and modifiers) and uses proprietary AI to autonomously generate the appropriate charge in seconds. What once required extensive manual entry and cross-checking now happens as a natural extension of the physician’s documentation workflow.

“Autonomous Coding has taken all of that and put it into a streamlined process,” Dr. Thor says. “It saves time. It saves clicks. It eliminates duplicate work. I don’t ever see going backwards. It’s a game changer for our workflow and practice.”

Her experience reflects OBHG’s broader results. Within months of launching Commure’s technology at pilot sites, the organization saw:

• 85%+ of charges coded using AI

• An 83% reduction in clinician time spent entering charges

• Improved accuracy through identification of codes clinicians may have missed manually

For frontline physicians, the value is felt moments regained and cognitive load reduced.

A Future Built on Clinician Time and Clinical Excellence

The accelerating demands of modern medicine are not easily reversed. But with the right infrastructure, they can be rebalanced. OBHG’s deployment of Autonomous Coding demonstrates what is possible when technology is shaped around clinicians rather than the other way around. The result is elevated accuracy, efficiency, and the centrality of patient care.

Autonomous Coding is a critical link in a larger, end-to-end revenue cycle workflow that’s part of the patient journey. Paired with Commure Engage and Ambient AI at the front end and supported by the back-end intelligence of Commure RCM, it forms a unified chain from clinical conversation to coded, optimized claim. This cohesion is what transforms isolated gains in efficiency into system-level improvement for patients, clinicians, and operations.

Learn more about the Commure’s partnership with Ob Hospitalist Group.

Clinicians didn’t get into medicine to do clerical work, but all too often are occupied by the painful realities of data entry and coding. Commure Autonomous Coding is an AI-powered solution to get clinicians out of the business of coding. It saves clinicians and coders valuable time by automatically generating medical codes from clinical documentation (including CPT codes, ICD-10 diagnoses, and modifiers). 

When integrated with the Commure Ambient AI documentation platform, autonomous coding creates an end-to-end experience that transforms how healthcare providers document encounters, submit claims, and optimize revenue capture.​​ Learn more in the video below.

Autonomous Coding: A New Way to Manage Medical Billing‍

Autonomous Coding represents a fundamental shift from traditional coding practices—breaking the cycle of 'familiar coding' and surfacing secondary diagnoses and specificities often overlooked in manual practice.

How Commure Autonomous Coding Works

Autonomous Coding leverages machine learning and natural language processing to analyze clinical documentation and automatically assigns CPT codes, ICD-10 diagnoses, and without manual intervention. It performs these tasks in seconds, compared with the one-day to six-week cycle common to manual coding submissions and approvals.

Commure’s Autonomous Coding engine leverages multi-layered analysis to ensure accuracy and that every billable aspect of a patient encounter is captured:

• Diagnosis coding: Extracts conditions with specificity that meet MEAT (Monitor, Evaluate, Assess, Treat) criteria from clinical documents.
• Procedure and service coding:  Identifies services provided during the visit and follows CPT, AMA, and CMS guidelines to generate codes.

Commure Autonomous Coding stands apart through its reasoning engine, which clearly explains every code it assigns. After codes are generated, providers can review the complete rationale—including medical decision-making logic, risk levels, time calculations, and direct references to supporting clinical documentation. This transparency helps providers understand, validate, and trust automated coding decisions while staying compliant with regulations.

Validating and Continuously Improving the Model 

What distinguishes Commure Autonomous Coding is its strict validation and continuous improvement model, which ensures that the model performs well based on client-specific data. This process includes:

• Benchmark Dataset: Before implementation, the Commure team reviews historical billing records to create gold standards”for every type of charge. This ensures that when a charge is generated for a real patient, it is based on the most accurate coding methodology.‍
• Continuous Testing: Commure conducts validation testing of suggested codes against historical coding data from large health systems. Across almost every customer tested, coding auditors have noticed patterns where the AI model selected more appropriate codes than what human coders had originally assigned.‍
• Customized Billing Rules: The solution includes health system and network-specific rules and can layer on payor-specific guidelines as they are updated.‍
• Quarterly and Annual Updates: Coding Guidelines are reviewed annually and quarterly as released, with the option for ad-hoc updates as needed. This ongoing maintenance keeps coding accurate and compliant as requirements change.

Optimizing Autonomous Coding Deployments with Forward Deployed Engineering

Building an effective autonomous coding workflow demands multidisciplinary expertise and strong integrations across multiple systems. Commure’s approach brings together clinical insight, technical depth, and coding proficiency. A typical Commure Autonomous Coding implementation includes:

• Clinical Expertise: A medical doctor serving as Clinical AI Strategy Lead oversees process strategy and ensures clinical alignment, bridging the gap between AI capabilities and real-world clinical workflows.​
• Engineering Leadership: An experienced engineer will lead architecture and development, supported by specialists in E/M automation, ICD-10 logic, product functionality, and quality assurance.
• Coding Proficiency: Certified medical coders (CPC, CPC-I, CBCS) ensure the system adheres to the latest coding guidelines and regulatory requirements.​
• Implementation Support: Implementation specialists facilitate smooth deployment and integration with existing systems and offer round the clock support for critical IT issues.

How Autonomous Coding Fits within the End-to-End Journey

Autonomous Coding serves as a pivotal connector within a comprehensive, end-to-end revenue cycle ecosystem that mirrors the full patient experience. When used alongside Commure Ambient AI and its Clinical Documentation Integrity module (aka CareCues) at the point of care, and reinforced by the downstream intelligence built into Commure RCM, it creates a continuous thread from the clinical encounter through to a fully coded, comprehensive claim. This seamless alignment elevates individual efficiency gains into broader, enterprise-wide improvements for patients, clinicians, and operational teams.

A Transformative Technology for Healthcare

Autonomous Coding signifies a crucial turning point in healthcare revenue cycle management, offering exceptional improvements in speed, accuracy, scalability, and cost-effectiveness. 

For physicians, this technology reduces administrative loads, allowing more focus on patient care. For coding professionals, it eliminates routine tasks and frees them up for complex, high-value work that utilizes their skills. For revenue cycle managers, it speeds up cash flow, enhances accuracy, and provides scalability without proportional staffing increases. 

As the technology evolves and expands, autonomous coding will become a key element of healthcare revenue cycle operations. Interested? Reach out to learn more about Commure Autonomous Coding.

You likely had several options — why did you choose Commure?

Kavan Zommers, VP of Launch Operations (BS Industrial Engineering): Prior to Commure, I spent several years in Technology Consulting at Deloitte and ZS, as well as running Ops at a seed-stage startup. After those experiences, I was on the hunt for a company solving a messy, un-sexy problem. Something with large scope and high impact. Addressing the inefficiencies that reside within U.S. Healthcare today provided me with just that. I saw a team of incredibly hard working individuals willing to do whatever it took to understand the problem that plagues every single healthcare practice and health system across the US. No job was too small for a single person in the company and no one’s voice was ignored. Having an opportunity to build and operationalize from the ground up with this mentality was not something I could pass on.

Bulat Bikmullin, Software Engineer (BS Computer Science): I’ve been working in healthcare and wanted to continue applying my skills in a fast-growing company that is meaningfully improving the industry. I was impressed by how ambitious Commure’s goals are in transforming healthcare. The company is taking on a broad, complex set of problems, and anyone joining can find an area they’re passionate about.

Pei-Hsin Wang, Director of Growth Operations (BS Mechanical Engineering): Before joining Commure, I worked in both large corporations and mid-size companies across several industries. What drew me to Commure was the challenge the team was taking on in healthcare. The industry is incredibly complex, and many workflows are still highly manual. The opportunity to apply technology to meaningfully improve these processes—and to support a growing population’s healthcare needs—really resonated with me. I was also excited by the culture of ownership at Commure. The ability to independently lead projects and make end-to-end impact aligned perfectly with the environment I thrive in. 

Ali Zaheeruddin, Senior Director of Operations (BS Computer Engineering & MBA): I’ve worked with companies of all sizes across different industries and at various stages of growth. Large organizations typically have strong product-market fit, which is what fueled their success—but with that comes layers of process and red tape that make decision-making slow. Smaller companies move quickly and give people room to take on diverse challenges, but they often haven’t yet found product-market fit. What stands out to me about Commure is that it sits in the sweet spot: a product in high demand, serving an industry ripe for a technological overhaul, and despite its growth, it still operates with the agility and mindset of a smaller company.
‍

How did Purdue prepare you for working at Commure?

Kavan: Purdue gave me the building blocks for solving incredibly unstructured problems and marrying business with technology. As an Industrial Engineering major, much of my world revolved around systems and processes, similar to how my role on Launch focuses on translating current state operations of a practice or health system to the future state on Commure’s platform.

Bulat: Studying at Purdue taught me perseverance and the importance of digging deep to understand problems thoroughly—whether it’s a theoretical challenge in class or a real engineering issue at work.

Pei-Hsin: Purdue taught me the critical thinking skills needed to approach ambiguous, open-ended problems—something that’s essential at Commure. I remember an innovation class that emphasized deeply understanding the problem before jumping to a solution, a mindset I use often here. My coursework also required juggling multiple projects at once, which prepared me well for our fast-paced environment. Being able to prioritize effectively has helped me stay focused on the most meaningful problems.

Ali: Every year taught me something new—not just academically, but personally. Beyond critical thinking, problem-solving, and the fundamentals of engineering, my time at Purdue started with learning how to be more independent. By the time I graduated, I had come to appreciate how essential collaboration with peers and partners is to achieving meaningful goals.

How have you grown?

Kavan: Commure has given me the opportunity to prove myself as a high-functioning individual contributor, team lead, and now VP of Launch Operations. Every week I face new challenges and new fires, but if there is one thing that my time at Commure has taught me it’s that there is only one right path to resolution: attack the problem and minimize time from information to decision. Act quickly, don’t get distracted by other fires, put things in motion, and keep moving.

Bulat: I joined just three months ago, but I’ve already significantly expanded my understanding of Commure’s tech stack and improved my ability to move quickly and iterate effectively.

Pei-Hsin: Commure has helped me become comfortable operating in white space. Instead of following an existing framework, I’ve learned to create one from scratch and iterate quickly. As the company grows, new challenges continue to emerge, so the work never feels repetitive. I’ve also grown more confident in leading initiatives independently and driving clarity in ambiguous situations.

Ali: At work, you’re never dealing with just one problem—you’re juggling many as you work toward your goals. The real skill lies in identifying the core issues, cutting through the noise, and prioritizing the actions that truly move you toward success.  This is an incredible skill I feel I have learned.
‍

What is something you are really proud of accomplishing?

Kavan: Over the last 2+ years I have been part of the core team building out our product offering for Federally Qualified Health Centers. 1 in 10 Americans receives care at an FQHC, and yet the software powering these practices has yet to fully solve the intricacies of their operations. As we continue to grow our FQHC offering, we are supporting millions of visits across 8+ states, driving clarity into doctor <> patient interactions, financial statements, and much more.

Bulat: I’m especially proud of working on the self-pay project, which redesigned how patient responsibility is applied. The new system is far more accurate and easier for operations teams to manage.

Pei-Hsin: One of the accomplishments I’m most proud of is building out our team, including establishing a new operations team in India. I was initially nervous about spinning up a net-new function, but within a few months the team grew into a high-performing group that now collaborates closely with our U.S. operations. It’s been incredibly rewarding to see our combined impact grow and to watch the teams come together around shared metrics and goals.

Ali: During my time here, I was asked to help build out the queuing model for our Assist product. We had made a few attempts earlier in the year that didn’t gain traction, but now we’ve reached a point where more than half of our Assist providers are successfully using the new model.
‍

What would you tell another Purdue student considering Commure today?

Kavan: If you are looking for an opportunity to push yourself beyond any preconceived notions of where the end of the road of your talent lies, Commure is the right place for you. The work we do will force you to get down to the brass text of “how do we solve this problem” under the assumption that there is ALWAYS a way to solve it. And you will wake up every single day knowing you are solving the RIGHT problems. No question.

Bulat: Join if you want to grow quickly and apply all your skills—technical, leadership, and communication—while working on problems that genuinely matter.

Pei-Hsin: If you’re looking for a place to learn quickly, grow your technical skills, and tackle new challenges every day, Commure is a great fit. You’ll take on meaningful responsibility from day one and have plenty of opportunities to expand your impact. It’s also a tight-knit, collaborative team—you’ll build strong relationships and have a lot of fun along the way.

Ali: I’ve worked in a number of places, but if you’re looking to make a real impact on a product that truly matters to people, Commure is the place to do it.

At Commure, our default mode is heads down: building, refining, and deploying AI side-by-side with our customers. Once a year, we step back and take stock of the impact in context of the Commure Pinnacle Awards. The awards themselves aren’t the point; what matters is recognizing the people who are doing the hard, necessary work to make healthcare better.

This year, we recognized:

System Impact: The Momentum Maker‍‍

Evan Kramer has played a pivotal role in bringing AI and automation to Compassus’ nationwide nursing workforce, enhancing provider satisfaction, retention, and patient access. Compassus, an integrated home-based care provider operating across 35 states with 8,000 nurses, has seen measurable impact under his leadership.

Kramer established the company’s Operational Excellence function, which has helped to drive a 70% adoption rate for AI-driven IDG documentation, reducing documentation time by 70% for this workflow. These efficiencies have enabled Compassus to expand patient access without increasing staff, while also improving clinician satisfaction, giving nurses “their Saturday's back”.

Human Impact: The Heart of Innovation

Gary Avery has driven transformative improvements in patient access and financial health at Optimus Health Care, a Federally Qualified Health Center providing preventive, primary, behavioral and specialty care to patients of all backgrounds. By championing the shift to Commure Engage, he delivered immediate, quantifiable results: patient response rates nearly doubled, rising to an impressive 39%. His efforts boosted outstanding balance collections by 106% annually. Building on this success, Gary is now leading the Commure Agents project to further streamline patient access and scheduling, and extend his vision of more connected, compassionate healthcare.

Clinical Impact: The Digital Doctor

Dr. Kermit A. Murray began as an early adopter of Commure Ambient AI. Recognizing its impact, he took the initiative to promote the solution in a newsletter he manages for Tenet’s physicians, sharing practical tips and success stories to encourage adoption. He’s helped to champion its rollout, bringing more than 100 providers onto the platform across the Arizona Market.

His leadership has gained visibility across Tenet, leading to his appointment by the VP of Tenet Physician Resources to co-chair the systemwide Primary Care Council and aid in AI implementation. In this role, Dr. Murray collaborates with fellow CMOs to scale innovation, enhance clinical workflows, and set a new benchmark for physician-led AI transformation.

‍Power User: The “Mic Drop” Award

As a telehealth, internal medicine, and primary care physician, Dr. Hanbin Zheng has seamlessly integrated Ambient AI into his daily clinical routine, leveraging it to serve a high volume of 30-40 patients every day with precision and empathy. He is on track to complete over 8,000 scribed notes by year’s end, a remarkable testament to his consistency and commitment.

Rendr Care is the largest and most comprehensive multi-specialty medical group dedicated to serving the Chinese community in New York City. With more than 250 providers caring for approximately 166,000 primary care patients across 100+ clinic sites, Rendr plays a crucial role in delivering accessible, high-quality, and culturally attuned care throughout the city’s Chinese neighborhoods.

Celebrating Today’s Innovators, Inspiring Tomorrow’s Progress

As Deepika Bodapati shared with attendees, “The most successful products and launches come from close collaboration between our engineers and our customers. These awardees show exactly what’s possible when technology truly works for people.”

To inquire about next year’s invite-only event, reach out at nexus@commure.com.

Tell us a little bit about yourself. What do you like to do outside of work? 

I'm pretty active, I enjoy surfing, training for triathlons, and hiking. Most of my hobbies involve being outdoors in some form. In the evenings, my wife and I usually unwind with whatever show we're watching. We just finished Yellowstone and absolutely loved it.

As a kid, what did you want to be when you grew up? 

Initially, an artist, though that didn't last too long. Then I was set on becoming a doctor for quite a while. That path has changed, but my interest in healthcare never did!

Describe a day in the life of your role. 

Every day brings something different, which keeps things interesting. I typically start by organizing priorities for myself and my team, then we have a standup to discuss any issues and align on the day ahead. From there, it varies, including architecture design meetings, client calls, heads-down coding, addressing escalations, or helping teammates solve problems. There's always something new to tackle.

What made you decide to join Commure? 

I've always been drawn to healthcare. In college, I majored in Computer Science but also completed all the pre-med requirements because I was genuinely torn between the two paths. I ultimately realized I wanted to build technology for healthcare rather than practice medicine. I also knew I wanted to join a company where I could take on significant ownership and grow quickly. Commure offered exactly that combination.

How would you describe the Commure company culture? 

Passionate and driven. Everyone here genuinely cares about what we're building and the customers we serve. We move quickly and hold ourselves to a high standard, but people are energized by their work. There's a real willingness to roll up your sleeves and tackle the hard problems together.

What advice would you give someone on their first day at Commure? 

Be proactive. Ask questions when something isn't clear. Introduce yourself to people whose work you admire. Speak up if there's a particular problem you want to work on. The opportunities here are real, but you have to take initiative to seize them.

What has been your greatest accomplishment so far at Commure? 

I was on of a small team of engineers tasked with a complete rebuild of our payment infrastructure. Managing a project of that scale while supporting millions of dollars in payments wasn't something I expected to do this early in my career. It's a strong example of what's possible here when you're willing to take on challenging work.

Interested in a career building the next generation of healthcare technology powered by AI? We are always looking for talented people across our departments.

Explore Career Opportunities

“Coding that once took minutes can be reviewed in seconds, which adds up quickly across a full clinic day.”

As Commure’s Clinical Strategy Lead, Dr. Aabha Morey brings together her experience as a primary care physician in India and her work across healthcare technology to help organizations adopt AI thoughtfully and effectively.

In this edition of Commure Uncharted, she breaks down why coding remains such a burden for clinicians, how generative AI has changed the landscape, and what health systems should consider when evaluating autonomous coding tools and their ROI.

Q: Why is coding still such a persistent pain point for providers and health systems?

Clinicians are trained to care for patients, not to code. Their day is already filled with diagnosing, coordinating care, and documenting visits. Coding becomes yet another task layered on top of an overloaded workflow, and if it is not done or not captured correctly, the visit cannot be reimbursed. Because coding has never been core to medical training, it often falls through the cracks. This gap makes the process both burdensome for clinicians and well-suited for generative AI tools that can take on the administrative lift.

‍Q: Why is the industry finally ready for fully or near-fully autonomous coding after years of attempts?

The shift is largely driven by advances in generative AI. Models are improving every few months in how well they understand clinical text and even clinical images. At the same time, health systems are under increasing financial pressure from reimbursement cuts, so they are looking for tools that help them capture the revenue they have already earned. Human coding is imperfect and often leaves money on the table. With the technology now strong enough to interpret documentation with far greater depth and consistency, interest in autonomous coding has grown significantly.

There has also been a cultural shift. As generative AI has become more accessible, people can see its value firsthand in their daily lives, which makes them more open to using it in clinical settings. I also see health systems approaching adoption responsibly by focusing on accuracy and data standards. Overall, the industry is more welcoming of AI than ever before, especially in areas like coding that have been long-standing pain points.

‍Q: What kind of time savings can clinicians realistically expect, and how does that time translate back into patient care?

In a recent study with a customer using our autonomous coding solution, clinicians saved up to 83 percent of the time they previously spent coding. That is time they can redirect back to patients, their teams, or even themselves. In many cases, the savings can be even higher. What used to take three minutes to code manually now takes under thirty seconds because clinicians only need to review what the AI generated.

‍Q: How do you balance physician oversight with automation to maintain trust in the system?

Clinicians still review and sign off on every AI-proposed code. AI can make mistakes, but most issues we see stem from conflicting information within the note itself. The key is using established guardrails already familiar in coding. For example, code edits flag combinations that should not appear together. If a note triggers a code edit or reflects a higher-complexity visit, it can be routed for additional review.

Autonomous coding does not mean bypassing clinicians. Instead, it gives them a faster way to validate codes with clear rationale and citations from the note, which turns what used to be a lengthy search into a quick review.

‍Q: Do you think we will ever reach a point where clinicians no longer need to sign off on notes and the coding process becomes fully automated?

Yes, it is a matter of when, not if. Lower-complexity, highly predictable visit types already follow patterns that lend themselves well to full automation. Those cases could be coded without a human in the loop. Higher-complexity visits or notes with inconsistencies will still need clinician review. Over time, as models improve and guardrails like code edits mature, more of the routine coding work can move toward full autonomy.

‍Q: What key metrics should health systems track to assess the ROI of autonomous coding?

I usually recommend looking at three areas: revenue impact, workflow efficiency, and clinician quality of life.

For revenue, track changes in claim volume, denials, and time to submission. When we compare periods of autonomous coding to prior seasons with manual coding, we see more claims going out and fewer denials. Many organizations also recover revenue simply because claims are submitted faster.

For workflow efficiency, measure how much time and how many clicks clinicians save. Coding that once took minutes can be reviewed in seconds, which adds up quickly across a full clinic day.

And for quality of life, reduced administrative burden often shows up in lower burnout and higher satisfaction. At a recent conference, clinicians actually applauded when they heard about autonomous coding, which speaks to how much frustration coding has caused over the years.

‍Q: What are the biggest adoption barriers you see, and how can organizations overcome them?

The first barrier is documentation quality. AI-generated codes will only be as accurate as the information in the note. Ensuring strong documentation standards and consistent templates goes a long way, and using the same ambient AI vendor as your autonomous coding vendor helps because upstream data flows cleanly into the coding model.

The second barrier is data flow from the EHR. Sometimes notes, especially those created by advanced practice providers, are not sent to the coding system until an attending co-signs them. That creates missed opportunities for autonomous coding. In several implementations, the remaining gap in utilization came down to notes that simply never reached us from the EMR. Working with the EHR team to make sure the right data is transmitted reliably is essential.

‍Q: What advice would you give a health system evaluating autonomous coding tools?

Start by looking at how well the vendor performs for your specific specialty. Many companies say they can handle everything from OB to neurology to facility coding, but accuracy often breaks down in areas like unspecified codes or laterality. Make sure you understand their real performance for the cases you see every day.

It is also a positive sign if a vendor tells you they need to fine-tune the model to your data. Documentation patterns vary widely across health systems, so an out-of-the-box model will never fit perfectly. Tailoring it to your environment is essential for accuracy.

Finally, consider what else the system can support. Coding is downstream from many other steps in the clinical workflow, so working with a vendor that also provides ambient documentation or intake can give you a more connected and accurate result. A shared backend ensures that all of the visit complexity is captured and reflected in the final claim.

‍Q: What makes Commure’s autonomous coding tools stand out from other solutions on the market?

One major advantage is our forward-deployed engineering model. It is one thing to tune a model for a specialty and another to tune it for a specific health system with its own payer mix, documentation standards, and nuances. Our teams work directly with customers to tailor the model so it performs optimally and scales across departments and facilities.

Another differentiator is our shared architecture with Ambient AI. Because all of the patient conversations, pre-visit information, and historical context flow through the same system, the coding model has a far more complete clinical picture. That means it captures visit complexity, patient co-morbidities, and other details that often go uncoded with manual processes.

Together, those capabilities lead to more accurate, context-rich coding that reflects the full care delivered.

Want to learn more about autonomous coding?

See What's Possible

Nurses today juggle relentless documentation requirements on top of direct patient care. To help health systems reduce this burden, we are excited to share that Commure Ambient for Nursing can now be integrated as part of Epic’s Ambient Voice Recognition Toolbox, enabling a native, in-workflow ambient experience directly inside Epic Rover.

This integration allows nurses to document patient interactions simply by speaking during the encounter. Commure’s ambient AI securely captures the conversation, converts it into structured flowsheet and LDA suggestions, and surfaces it in Epic for nurse review and filing. The entire experience is embedded in Rover, so nurses stay in the tools they already use without extra steps or separate apps.

Bringing Commure Ambient into Epic Rover unlocks several advantages. Nurses can center more of their workflow around patient conversations instead of manual data entry. Structured fields populate faster and more consistently, supporting higher documentation quality. Because the experience lives directly inside Rover, organizations gain a unified workflow that reduces toggling, minimizes friction, and supports quicker adoption.

Ambient AI helps nurses reduce repetitive charting tasks and frees time for direct care, whether during admission assessments, rounding, or reviewing devices and lines. Instead of typing in the moment or catching up at the end of a shift, nurses can focus on clinical decision-making while Commure’s AI assists in the background.

With this Epic Toolbox integration, Commure can now deliver an integrated ambient experience in Epic Rover that supports accurate documentation and a more efficient, patient-first workflow.

Trademark Statement: Epic and Rover are registered trademarks of Epic Systems Corporation.