Insights for clinical leaders, physicians, nurses, and care teams focused on improving care delivery, reducing administrative burden, and enhancing the clinical experience.
Cem's Journey of Uncapped Growth and Opportunity at Commure
Commure Team
|
August 14, 2026
When Cem Torun started on what would become Commure's Ambient AI product, he spent the first 4 months tasked with figuring out whether the idea was worth building at all. There were no users and no team, just Cem and a rough concept that Tanay, Commure's CEO, and Hersh, its CBO, had pointed him toward before stepping back to let him run with it.
Four years later, he's the VP of Engineering for Ambient AI and leads a team of more than 40.
When he first moved to the Bay Area after college, he skipped the apartment search and lived on a retired pharmacist's boat in the Redwood City harbor for 2 weeks, commuting to the office by Uber and turning up most mornings covered in mosquito bites. The owner had spent years in pharma, so their evening conversations about the industry ended up teaching Cem a fair amount about the field he'd just joined.
His route into healthcare took a few turns along the way. As a kid, he wanted to be a YouTuber, talking his teachers into letting him turn writing assignments into short films instead of essays. His parents wanted a doctor in the family, so he spent his first 2 years of college in pre-med, building on the time he'd spent volunteering at a palliative oncology center in high school.
That volunteer work showed him how many problems healthcare had, but fixing them one patient at a time felt too small for the scale he wanted, so he taught himself to code and figured out he could build technology for medicine instead of practicing it.
Being able to work on the first iteration of Commure’s Ambient AI kept rewarding his willingness to take on new problems and think outside of the box. After 4 months of iterating, he had proven the idea was worth pursuing and was told to build a team around it. When that team grew to 6 engineers and still had no product manager, he covered the role himself until the company hired one. He did the same with design, building it to a solid standard until a full-time designer came on board.
Cem had his biggest test at Commure with the first major Ambient AI enterprise deal. Getting a large health system live was a big implementation, so Cem flew out and worked alongside the team in person for 4 to 6 weeks straight to make sure everything was specifically tailored for their unique workflows.
When Cem talks about why he's stayed 4 years, he says it's uncommon for someone early in their career to be handed stakes this high, and he's watched Commure choose to grow its own leaders instead of bringing in a 20-year veteran every time a hard problem surfaces.
He tells candidates their impact won't be capped by title or tenure, and that no one waits around for an assignment. If you see a problem worth solving, you go solve it. He's honest about the trade-off too, that people who measure their work in weeks tend to miss the results, while those who stay on a hard problem for a couple of years see what that kind of focus produces.
He points to his work on Ambient AI as the clearest example of this. The product supports some of the country's leading oncology and drug-discovery organizations, so the code his team writes reaches cancer research and patient care directly. He admits he undervalued that impact early on, since it was his first full-time job and he assumed most companies operated at those high stakes.
Cem now runs his own team on the same logic, giving people work that sits a little past what they've done before and puts enough structure around it so no one falls too far. As they show they can move quickly, he hands them more.
That approach is how a solo, 4-month experiment turned into a 40-person engineering org in less than 3 years, and how the person who started it went from proving out an idea by himself to leading the team that scaled it.
The same drive holds outside the office, where Cem is training for his first triathlon. He took it on because he wanted something genuinely hard, then talked 6 friends into doing it with him. He booked the race in Berlin because a domestic one sounded boring.
Nine months ago he couldn't swim, and the first time he got in a pool he couldn't make it a single length without stopping for air, which he says made him feel like a kid again. Since then he's learned to swim, bought his first real road bike, and picked up enough about gear sets, shifters, and fixing a flat to give a TED talk on it.
It's the same move he's made his whole career, going after the thing he doesn't know how to do yet and working at it to make it happen.
Interested in a career building the next generation of healthcare technology powered by AI? We are always looking for talented people across our departments.
Most of what drives denials is knowable and fixable, from the front-desk data that starts a claim to the coding and documentation behind it, which is why a structured denial management program pays for itself.
What is denial management?
Denial management is the systematic process of identifying denied claims, finding out why a payer refused them, correcting and resubmitting or appealing them, and fixing the upstream problems so the same denials stop recurring. Done well, it protects cash flow and surfaces the process gaps that cost an organization revenue.
A rejection and a denial aren't the same thing, and the distinction changes how you work each one. A rejection happens before the payer fully processes a claim, usually because of missing or malformed data, so you can correct and resubmit it quickly. A denial happens after the payer adjudicates the claim and decides it won't pay, which means you either correct and resubmit or file a formal appeal.
In medical billing, denial management runs alongside eligibility, coding, and collections, and it depends on all of them, since a claim denied for a coding error or a missing authorization started going wrong long before it reached the payer.
Regulators are responding to the pressure. Under the CMS Interoperability and Prior Authorization Final Rule, impacted payers must, as of January 2026, decide urgent prior authorizations within 72 hours and standard ones within 7 calendar days, give a specific reason for each denial, and publicly report their prior authorization metrics. Those rules should add transparency over time, though the denial volume providers face today is still climbing.
What causes claim denials?
Most denials trace back to a short list of recurring causes across the front end, coding, and documentation. In KFF's analysis of marketplace claims, the single most common reason was an unhelpful "other" category, followed by administrative reasons and excluded services, with lack of prior authorization or referral at 9% and only 6% tied to medical necessity.
In day-to-day billing, the causes that show up most often are:
Eligibility and registration errors, where coverage is inactive or the patient's information is wrong on the date of service.
Missing or incorrect data, from a misspelled name to a transposed member ID.
Missing prior authorization, when a service that needed advance approval didn't get it.
Coding errors, including wrong CPT, ICD-10, or modifier choices, and duplicate claims. Getting this right is where AI medical coding is increasingly earning its keep.
Medical necessity, when the documentation doesn't support the service billed, which ties denial rates directly to clinical documentation improvement.
Timely filing, when a claim lands after the payer's submission window and becomes almost impossible to recover.
Non-covered services and coordination-of-benefits issues, common when a patient carries more than one plan.
Denials also fall into categories that shape how you work them. Soft denials are temporary and can be corrected and resubmitted, while hard denials require a formal appeal or turn into written-off revenue. Administrative denials come from process errors like eligibility or missing data, and clinical denials question medical necessity or coding and need clinical evidence to overturn.
The denial management process, step by step
The denial management process is a repeatable cycle that starts when a payer refuses a claim and ends only when the claim is resolved and the reason behind it is fixed. It breaks into five stages:
Identify and log the denial. Pull every denial from remittance advice, explanation-of-benefits statements, and your payer work queues, and log it right away so nothing slips past the timely-filing deadline.
Categorize the denial. Sort each one by reason code, payer, dollar value, and age, which turns a pile of individual problems into patterns you can act on.
Investigate the root cause. Read the Claim Adjustment Reason Codes and Remittance Advice Remark Codes to understand what actually went wrong, rather than what the denial appears to say on the surface.
Correct and resubmit, or appeal. Fix and resend the claim when it's a correctable error, or build a formal appeal when the payer got it wrong, knowing an appeal can run several rounds of review before it resolves.
Prevent the next one. Feed what you learned back upstream so the same denial stops recurring, which is the stage that compounds over time.
Because about 70% of denials are ultimately overturned once providers pursue them, prioritizing by dollar value, claim age, and likelihood of success is how a team recovers the most revenue with the staff it has.
How to prevent denials
The most effective denial management programs stop denials before submission by tightening the front end, documentation, and coding. Prevention is really about revenue integrity: making sure what's documented, coded, and billed matches the care delivered.
A few practices move the needle most:
Verify eligibility and benefits at registration, so coverage problems surface before the visit rather than after the claim.
Handle prior authorization proactively, tracking which services need it and securing approval early.
Strengthen documentation and coding, since accurate notes and codes are what hold up under payer review. Autonomous coding helps here by generating codes with supporting rationale straight from the documentation.
Capture charges completely, because missed or late charges never surface as denials and become permanent losses, which is why charge capture belongs in any prevention plan.
Track denial trends with analytics, so a spike from one payer or one service line gets caught early.
Build cross-department accountability, matching each denial type to the team that can prevent it, from front desk to coding to billing.
Platforms like Commure Pro pull coding, charge capture, and documentation into one layer so these controls run on every encounter instead of depending on someone remembering to check.
Metrics that matter in denial management
A handful of KPIs tell you whether your denial management is working. The core four are your denial rate (the share of claims denied), your appeal overturn rate (how often you win the denials you fight), your days to resolution (how long a denial takes to clear), and your write-off rate (the revenue you give up).
There's no universal target, but recent MGMA benchmarking put the aggregate first-pass denial rate near 8%, and many organizations run well above that. Two other numbers frame the opportunity: denials get overturned roughly 70% of the time when pursued, and each one costs about $57.23 to work, so a lower denial rate and a higher first-pass yield translate directly into recovered margin.
How AI is changing denial management
AI is shifting denial management from an after-the-fact cleanup job toward prevention, flagging at-risk claims before they're submitted, and automating the appeals and resubmissions that used to consume staff hours. The same models can categorize denials by reason code, group similar claims for bulk resubmission, and draft appeals with the supporting documentation attached.
That's the approach behind Commure's AI work on denials, which pairs accurate coding and charge reconciliation on the front end with automated denial categorization and resubmission on the back end. One New York health system cut its timely-filing denials by 53% and raised monthly charges by 20% (from $7.5M to $9.4M) after deploying automated charge note reconciliation, detailed in the NYC health system case study.
Denials are one piece of a broader move toward healthcare automation across the revenue cycle, where prevention on every claim beats recovery on the ones that slip through.
Turning denial management into prevention
Denial management works best as part of a connected revenue cycle, where clean documentation, accurate coding, and complete charge capture combine into a claim that's right the first time. That's what revenue cycle management built on AI is meant to deliver.
See how Commure RCM turns denial management from a recovery scramble into a prevention system.
What is the difference between a claim denial and a claim rejection?
A claim rejection happens before the payer processes the claim, usually because of missing or invalid data, so you can correct and resubmit it quickly. A denial happens after the payer adjudicates the claim and refuses to pay, which means you either fix and resubmit it or file a formal appeal. Rejections clear faster; denials take more work.
In medical billing, denial management is the workflow billing teams use to catch, correct, appeal, and prevent denied claims. It covers reading payer reason codes, resubmitting fixable errors, appealing wrongful denials before filing deadlines close, and feeding root causes back to registration, coding, and documentation so the same denials stop recurring.
What are denial management services?
Denial management services are the people, software, or outsourced partners that handle denied claims for a provider. They range from in-house billing teams to third-party RCM vendors and AI-driven tools that flag at-risk claims before submission, categorize denials by reason code, and automate resubmissions and appeals to recover revenue faster.
What is the difference between denial management and revenue cycle management?
Denial management is one part of revenue cycle management, which covers the full financial path of a claim from registration and eligibility through coding, billing, and payment posting. Denial management focuses specifically on the claims a payer refuses, resolving them and preventing the next ones, so it only works as well as the revenue cycle around it.
If you've spent any time in home health care operations, you already know the math: the agency that responds first wins the patient. It doesn't matter how good your clinical team is or how strong your outcomes are, if you're still processing referrals through fax queues and manual spreadsheets, you're losing business to the agency that picked up faster.
Referral intake is the front door to your entire business, and right now, for most agencies, that front door is held together with fax paper. 75% of home health organizations still rely on fax as their primary referral channel. Home health industry estimates 10 minutes per referral, scaling to five to eight hours of administrative time weekly at 30-50 referrals per week. Despite that investment, only 50% of referrals convert on average
Payers, hospitals, and discharge teams aren't waiting around. They're sending the same referral to a dozen agencies simultaneously, and they're moving on quickly. When your intake team is manually keying demographics, chasing payer verification, and managing status updates across phone calls and portals, you're leaving revenue on the table.
The administrative burden doesn't just cost agencies with missed referrals. It costs staff. The volume of manual, repetitive work in referral intake is one of the leading drivers of burnout and turnover on intake teams, a problem that compounds itself as agencies struggle to backfill.
Introducing Commure Orchestrator for Home Health
Commure Orchestrator is an AI-native referral management platform that automates the entire intake workflow, from the moment a referral arrives to the moment a patient is admitted. No manual handoffs, dropped follow-ups, or data entry.
The platform operates across five automated steps:
Ingest. Referrals are captured from every source the moment they arrive (fax, portal, EHR, email) and pulled into a single unified system. Your team stops chasing down incoming referrals across channels and starts working them.
Extract. AI automatically structures every referral: patient demographics, clinical notes, payer information, diagnosis codes. The data is clean, complete, and ready to act on, without anyone retyping it.
Validate. Every business rule your agency runs, including service area, acuity, and payer eligibility, executes automatically before anyone touches the referral. Manual checklist work disappears.
Coordinate. One queue for every team. Communication is centralized so there are no emails, spreadsheets, or dropped handoffs between intake, clinical, and scheduling staff.
Close. Accepted referrals write directly back into the EHR. The audit loop closes automatically. Zero manual data entry at the back end.
The result is faster response times, higher acceptance rates, and a meaningful reduction in the administrative load your team carries every day.
One Workflow. Impact Across the Organization.
The effects of a faster, more automated intake process compound across the business:
Revenue: Reduce missed referrals with higher acceptance rates.
Operations: Increase staff throughput without adding headcount.
Patient experience: Reduce time-to-care by matching patients to available capacity faster.
Compliance: Maintain audit-ready, real-time visibility across your entire referral pipeline.
Commure Orchestrator integrates with AI Call Center Agents and digital patient intake, so automation doesn't stop at intake approval. Once a referral is accepted, patients can be scheduled immediately, and pre-visit intake can be completed via SMS or email before the first visit, connecting the full referral-to-visit handoff without gaps.
Orchestrator is already processing hundreds of thousands of tasks fully autonomously across home health, ambulatory, and specialty care settings.
Ready to See It in Action?
If your intake team is still managing referrals manually, we'd like to show you what a fully automated workflow looks like in practice.
For the third year running, more than 60 executives from organizations like MEDITECH, HCA Healthcare, Willis Knighton Health, Lifepoint Health, WellNow Urgent Care, Summit Behavioral Healthcare, and Nathan Littauer Hospital gathered at Commure Nexus for a full day of sessions, roundtables, and candid conversations. The discussions spanned the front door to final payment, and every point of administrative friction in between.
Commure CEO Tanay Tandon opened the day by highlighting a core thesis at Commure: Healthcare has a work tax problem. Providers spend 15-30 minutes before every visit manually building the clinical picture they need, and another 15-30 minutes after on clinical documentation, for every patient. Layer on the back-end: every prior auth chased, every claim resubmitted, every administrative hour spent on billing complexity instead of care. That friction carries a price.
At the industry level, it adds up to an estimated $1 trillion in administrative costs annually, with providers absorbing a 10-15% cost to transact. The rest of the modern economy runs at roughly 3%. That gap is a structural failure, and that was the center of conversation among healthcare leaders who gathered at Commure Nexus in Boston.
A Tribute to Jim Merlin
This year's Nexus opened with a keynote called “Never Stop Inventing” alongside MEDITECH, and we want to honor the man who made that conversation what it was. Jim Merlin, 40-year veteran of MEDITECH and one of the most respected voices in health IT, passed away shortly after Nexus. Jim brought the kind of earned conviction to this work that only comes from decades in the field. We are grateful he was with us in Boston, and we hold his memory with tremendous respect.
Jim shared the story of how MEDITECH pioneered the health IT category and modern day EHR, how they continue to help lead the industry. That spirit of innovation set the stage for the conversations that followed.
Jim Merlin, Chief Business Development Officer, MEDITECH
Keynote: Never Stop Inventing: The Builders That Rewrote Healthcare, Twice
From Missed Calls to Admitted Patients: How Summit Behavioral Health Transformed Its Call Center
Every missed call is a missed patient. Across healthcare, front-desk capacity constraints, including hold times, after-hours gaps, and overwhelmed staff, mean that patients who can't get through often don't try again. In behavioral health, where that first call may be the hardest one a patient ever makes, the stakes are even higher.
Commure COO Deepika Bodapati opened with a live demo of Commure's AI call center agent, which offers 24/7 coverage, intelligent call routing, scheduling, and intake, handled without staff involvement. Then Caleb Rich, SVP of Patient Acquisition and Admissions for Summit Behavioral Health, walked through how the organization is transforming their call center experience with an AI agent.
Summit BHC is one of the fastest-growing behavioral health networks in the country, with 38 facilities nationwide, serving a highly diverse patient population across its nationwide network of psychiatric hospitals and addiction treatment centers. The administrative burden at the front door, including missed calls, delayed intake, lost admissions, is acute. With Commure's AI agent, Bella, live across their network, Summit achieved more inquiries handled and higher admissions conversion within the first three months of deployment. That's more people getting into treatment when they need it most, not lost in a queue.
Caleb Rich, SVP of Patient Acquisition and Admissions, Summit Behavioral Healthcare
After the Note: Where Ambient AI Goes Next
Documentation is both a burnout problem and revenue problem. If it isn't documented, it didn't happen; not for the patient record, and not for the claim. Leaders from Lifepoint Health, Willis Knighton Health, and WellNow Urgent Care shared ground-level perspectives on deploying AI-powered clinical documentation across their organizations.
The session pushed further than ambient clinical documentation. The real value lives in what comes before and after the note: pre-visit summaries, pre-charting, real-time patient record queries, charge-note reconciliation.
The compounding advantage belongs to health systems that connect the note to the full clinical and financial workflow, not those who stopped at transcription. Documentation feeds coding. Coding feeds claims. Claims feed intelligence that improves the next encounter. That loop, running continuously on one data model, is where the structural advantage builds.
Sam Ascher, SVP & GM of Commure Ambient AI; Martin Christensen, WellNow Urgent Care; Mark Galea, CIO, Willis Knighton Health; Ryan Mackey, MD, CMIO, Lifepoint Health
All In on AI: Building an End-to-End Platform Strategy Across the Patient Journey
Point solutions address individual moments of friction. A platform closes the loop. That was the argument at the center of the day's final panel, featuring two health systems at different points on the same path.
Ross Rigdon, COO at Raleigh Orthopaedic Clinic, brought the RCM story to life, unearthing the “work tax” with back end revenue cycle workflows. Raleigh Orthopaedic has built one of the most comprehensive full-platform Commure Athelas deployments in the ambulatory space, handing off the complete revenue cycle to an AI-native platform and capturing gains across charge acuity, denial rates, and time-to-payment. The bet was strategic: when documentation, coding, and claims run on a shared data model and continuously learn from one another, every encounter makes the next one more accurate and more efficient.
James Wellman, VP & CIO at Nathan Littauer Hospital, laid out their own roadmap to full-platform, making the case that integrated AI infrastructure across the patient journey isn't a long-term aspiration. It's a decision health systems are making right now. Nathan Littauer's strategy spans four interconnected pillars: ambient clinical documentation, AI call center agents, Patient360 real-time chart querying, and full-cycle revenue cycle management. The vision is a connected set of rails: one intelligent data model, running from the patient's first call to final payment, where each layer of the platform makes every other layer smarter.
James Wellman, VP & CIO, Nathan Littauer Hospital
Patrick Winter, SVP of Commercial Operations, Commure; Ross Rigdon, Chief Operations Officer, Raleigh Orthopaedic Clinic
Compounding Intelligence: The Commure Platform Future
Tanay opened the day with a clear goal: reduce the cost to transact in healthcare. Max Krueger, Head of Forward Deployed Engineering, closed it with a look at what comes next.
The platform already spans the full revenue cycle (front, mid, and back) on one intelligent data model. The roadmap compounds what's working: documentation feeds coding, coding informs charge reconciliation, claims data trains denial prevention upstream, and voice agents capture information at the front door that flows cleanly through every step that follows.
The destination: health organizations paid in 1-2 days, not 30+. Near real-time settlements. Staff focused on care, not chasing payments. A financial foundation stable enough to grow from.
That future requires infrastructure, not a collection of tools: the same kind of shared rails that made credit card networks transformative. Health systems that build on this platform accumulate a data and intelligence advantage that point-solution buyers simply can't close.
Max Krueger, Head of Forward Deployed Engineering, Commure
The Work Tax Has a Fix
The name Nexus has always meant something to us: a point where things converge. This year, what converged was a shared conviction that the work tax crushing American healthcare is not an immovable structural reality but a solvable engineering problem. And the health systems in that room are proving it, one deployment at a time.
We are grateful to Jim Merlin for helping open this conversation with the wisdom of someone who has seen what it actually takes to change how medicine is practiced. His voice will stay with this work.
Before we built Patient360, my team and I spent weeks shadowing providers across hospitals and ambulatory clinics. The pattern was hard to miss: providers were spending 10 to 20 minutes prepping for a patient they'd see for 5 or 10 minutes.
And that prep time wasn't spent thinking about the patient. It was clicking through the EHR, pulling up labs and imaging one screen at a time, and calling around to track down documents that never made it into the chart.
Tens of thousands of providers now use it to walk into visits already caught up; this post is about what they've taught us so far.
The medical note was only half the problem
Commure Ambient AI solved clinical documentation. Providers stopped working on documentation at 10 pm and are now finishing their notes within a few minutes.
But when we asked providers where their remaining time was going, they pointed to everything that happens before the visit. Documentation had gotten faster while prep was still as slow as it had always been.
Providers didn't go to medical school to click through 20 screens collecting information. They went to make judgments and care for patients. Our job at Commure is to synthesize everything and hand it to them so they can do exactly that.
So we started building beyond the note. Patient360 is a complete clinical picture of the patient, assembled continuously from EHR data: labs, imaging, medications, allergies, signed notes, and past appointments.
That picture powers two things providers touch every day. The first is an AI pre-visit summary that gets a provider current on a patient in about 60 seconds, tailored to their specialty. The second is an AI assistant that answers natural-language questions about the chart, like "any abnormal labs since the last visit?"
Specialty tailoring was a day-one decision. A cardiologist and an orthopedic surgeon need different labs, different baselines, and different acronyms, so a generic summary gets you 60% of the way, which still leaves the provider digging through the EHR to close the gap. With insights from specialists working in the field every day, we created specialty-specific summaries for cardiology, orthopedics, oncology, OBGYN, and more.
"Patient360 gave me exactly what I needed to prep for the visit — the right level of patient-centered information, surfaced at the right time. The reminders on incomplete tests were especially valuable. We've been extremely pleased with the pre-visit summary." — Kansas Heart
What providers have taught us so far
The most common feedback in our early rollouts was a request for more. Providers who had the summary and assistant before the visit asked if they could have access to the tools during and after the visit as well.
The second lesson was how dramatically prep timing shifts once the work is done for you. One clinical practice told us they used to prep charts a full week ahead because the process took so long. Now their providers review the summary 2 minutes before walking in.
"Patient360 has been extremely helpful. Yesterday, with a busy clinic schedule and an eval about to start, I used it to quickly get the key context for the visit. It gave me exactly the information I needed and saved me several minutes of going into the chart to find the information." — Athens Orthopedics
The third surprised me. Some care teams included Patient360 as part of their daily huddle, pulling it up so everyone's current on a patient in seconds before discussing the case. We built it for individual prep, and providers turned it into a collaboration tool.
And the fourth is my favorite. Providers who had been hesitant about recording visits at all loved Patient360 once they saw what it gave them in return.
"Seeing providers who are typically slower to adopt new technology quickly embrace Commure, and specifically Patient360, has been a huge win. They're using it daily to prepare for visits faster and review patient information more efficiently. Now we want to see it rolled out across the entire site." — Mountainlands Community Health Center
Trust is everything
Every enterprise conversation I have starts with some version of the same question: how do I know the data is correct and safe?
It's the right question. A summary that's wrong, or that omits something like a prior heart attack, can be nearly as harmful as the EHR chaos it replaced. Trust in healthcare AI has to be earned in the product itself, so we built it with trust as the leading factor from the start.
Every insight in Patient360 links back to its source in the chart. If a provider wants to verify where a statement came from, the citation is one click away.
And when the chart conflicts with itself (which happens constantly when different providers document different things), instead of picking a winner, we surface the conflict on the summary so the clinician can make the call with full information.
What providers consistently asked us
Across these first rollouts, providers and health system leaders kept pressing us on the same three questions. They're the right ones to ask of any tool in this space.
Can I trust the data? They asked how we handle conflicting information, whether every insight is cited to its source, and how we think about what's missing, since an absent heart attack is nearly as dangerous as an invented one.
Does it fit the workflow I already have? The worst outcome is a tool providers have to learn. Patient360 was built alongside clinicians from the first design review, and our bar is zero-second training: you open it, and you're ready.
Where Patient360 goes next
Patient360 started as the picture a provider sees before the visit. It's becoming the insights layer underneath the whole encounter.
Pre-charting is next: Patient360 context will flow directly into the medical note, so relevant history, labs, and the HPI foundation are already in place before the provider enters the room and starts documenting the encounter. We're also ingesting the documents and detailed medical history that live as PDFs in the chart, like scanned imaging results and referral packets, so nothing gets left out of the picture.
After that comes in-visit intelligence: care suggestions that surface in real time as the conversation unfolds, always as options the provider can accept or dismiss, never decisions made on their behalf.
Our goal is the same one we started with. Providers should spend their training and judgment on patients, and Patient360 exists to clear away everything standing in between.
If your team is still prepping charts a week in advance, come see what a 2-minute prep workflow actually looks like. Email us at solutions@commure.com or book a demo via the button below.
Healthcare automation has already saved the US health system hundreds of billions of dollars. Electronic transactions and automation helped the industry avoid an estimated $258 billion in administrative costs in 2024, with roughly $21 billion a year still available from work that stays manual or partly manual, according to the 2025 CAQH Index.
The strain behind those figures shows up on every clinical schedule. Physicians reported a 57.8-hour workweek in 2024, and 7.3 hours of it went to administrative tasks like prior authorization, insurance forms, and meetings, per the American Medical Association.
For health systems looking to cut administrative costs and give staff time back, the real question is what to automate, in what order, and how to do it without adding risk.
What is healthcare automation?
Healthcare automation is the use of technology to complete healthcare tasks with little or no manual effort, across operational, financial, and clinical work. It covers everything from insurance eligibility checks and claims processing to clinical documentation and patient reminders.
Most people first meet it in its narrow form, robotic process automation (RPA) in healthcare, where software handles repetitive, rule-based steps such as data entry or eligibility verification. The broader term is intelligent automation, which combines RPA with artificial intelligence so systems can read unstructured documents, interpret context, and make complex decisions.
Health care automation works best when it runs across a whole process rather than one isolated step, so a patient's information moves from intake through documentation, coding, billing, and follow-up without being re-keyed at each stage.
The main types of healthcare automation
Healthcare automation spans a few distinct technologies, and knowing the difference helps you match the right tool to the right job.
Robotic process automation (RPA). Software bots follow fixed rules to handle high-volume, repetitive tasks like eligibility checks, claim status lookups, and moving data between systems. It's fast and reliable for work that never changes.
AI and machine learning. These models find patterns in data, so they can predict likely claim denials, prioritize worklists, or surface a possible diagnosis for clinician review. They get better as they see more examples.
Intelligent automation. This pairs RPA with AI so a single workflow can read a faxed referral, pull the relevant clinical details, and route the case, handling the messy inputs that rule-based bots alone can't.
Ambient AI. Ambient AI listens during a visit and drafts the clinical note in real time, which is why teams often ask how ambient AI and AI scribes differ. It takes documentation off the clinician's plate entirely.
Agentic AI. The newest layer, agentic AI, can plan and carry out multi-step tasks on its own, check its work against policy, and pull in a human when a case needs judgment.
You don't have to pick just one. Most decisions here land with the people accountable for operations, revenue, and IT, so whether you're a COO weighing throughput, a revenue cycle or finance leader watching cost per claim, or a CMIO protecting clinician time, the goal is the same. A mature program uses all of these types, matched to the risk and complexity of each task.
Where healthcare automation works across health systems
Healthcare automation can be applied across the entire care and revenue journey, not only the billing office. Health systems get the most from it when their automation connects these areas, so information flows from one to the next instead of stopping at department lines.
Patient access and intake. Automated scheduling, reminders, and digital intake reduce no-shows and cut front-desk phone volume, while eligibility checks confirm coverage before the visit. This is the front end of patient engagement, where modern patient communication software handles two-way conversations: reminders, replies, scheduling, and follow-up in one place. Yale New Haven Health used automated pre-visit outreach to cut no-shows and same-day cancellations by 54% in its breast imaging program.
Clinical documentation. Ambient AI drafts notes during the encounter, and dictation feeds structured data back into downstream systems, so clinicians spend less of the visit typing.
Patient communication and coordination. Healthcare AI agents handle inbound calls, answer routine questions, and manage follow-up, freeing staff for work that needs a human.
Back office. Supply chain ordering, compliance reporting, and security monitoring all run more accurately when automated systems handle the routine checks.
The core benefit of healthcare automation is time returned to people, which then shows up as lower costs, fewer errors, and a better experience for patients and staff.
When automation absorbs data entry, paperwork, and documentation, clinical teams spend more of the day on care and administrative teams move to higher-value work. At North East Medical Services, clinicians started heading home 1 to 2 hours earlier each day after adopting ambient AI.
Costs also drop and revenue holds. Fewer manual touches mean fewer coding and billing errors, faster payment, and less rework, which is how one New York City health system raised revenue cycle performance by 20%.
Patients notice too. Faster scheduling, quicker responses, and fewer forms make the experience smoother, and automated follow-up keeps people engaged between visits.
Automation also scales in a way that hiring can't. A system absorbs higher patient volumes without adding headcount for every task, and automated access controls and audit trails support compliance along the way.
What to automate first
Start where the burden is heaviest, and the payoff is fastest to see, then expand into adjacent work. Early, visible wins build trust that carries into the next project.
Clinical documentation is the clearest first move. It's the single largest source of clinician time and burnout, and ambient AI addresses it directly by drafting the note during the visit for the clinician to review and sign, so results show up right away in reclaimed hours and less after-hours charting. Because a clinician still approves every note, the clinical risk stays low while the relief is immediate.
Prior authorization is the next obvious candidate. Physicians and their staff spend about 13 hours a week on it, completing roughly 40 requests per physician, and 40% of practices now employ people who work on nothing else, according to the AMA's 2025 survey. It's high volume, highly repetitive, and directly measurable, which is exactly the profile automation handles well.
Eligibility verification, patient intake, claim scrubbing, and appointment reminders fit the same criteria and are common early wins.
Sequence matters as much as selection. Prove the value on one workflow, measure the time and money it returns, then expand into adjacent steps. A phased rollout produces the hard numbers you need to justify each next investment.
Why healthcare automation succeeds or stalls
Automation succeeds when it fits how clinicians already work, and it stalls when it's bolted on without their input. The technology is rarely the hard part; adoption is. A few practices separate the programs that stick from the ones that stall:
Bring staff in early. Involve the clinical and administrative teams who'll use the tools before you buy, so the workflow fits their day instead of fighting it.
Aim for top-of-license work. Target the tasks that pull people away from what they trained for, and measure success by the time given back, not screens added.
Keep a human in the loop. Let automation handle the routine work and route exceptions and anything with clinical or financial weight to a person for review.
Start small and prove it. Roll out one workflow, show the time and dollars it returns, then use those numbers to justify the next phase.
Get governance right from day one. Automated systems touch protected health information, so insist on HIPAA-compliant handling, clear audit trails, and attention to model bias.
Integrate with the EHR. Tight integration keeps data accurate and stops staff from re-keying information between systems.
Healthcare automation is now core infrastructure
Healthcare automation is no longer optional: health systems and mid-sized practice groups nationwide are treating it as a core part of how they operate and compete. The organizations seeing the greatest results treat it as one connected system, starting where the work is most repetitive and the ROI is hardest to ignore. The real opportunity lies in building automation that compounds, with each layer making the next one more powerful.
See how the Commure platform brings ambient AI, revenue cycle, and patient engagement together in one place.
Frequently asked questions
What are examples of healthcare automation?
Common examples include automated appointment scheduling and reminders, insurance eligibility checks, medical coding, claims processing and denial prevention, ambient AI that drafts clinical notes, and AI agents that handle patient phone calls. More than 50% of health plans and 25% of provider organizations now use AI in administrative workflows, per the 2025 CAQH Index.
What's the difference between RPA and AI in healthcare?
RPA follows fixed rules to automate repetitive tasks like data entry and eligibility checks, and it can't adapt on its own. AI uses machine learning to interpret data, predict outcomes, and handle unstructured inputs like faxed referrals. Intelligent automation combines the two, which is what most healthcare workflows actually need.
Will healthcare automation replace healthcare jobs?
No. Healthcare automation mainly targets administrative and repetitive work rather than clinical judgment, so it shifts staff toward higher-value tasks instead of eliminating roles. Physicians spend 7.3 hours a week on administrative tasks alone, per the AMA, and automating that work lets clinical teams operate at the top of their license.
Is healthcare automation HIPAA compliant?
It can be, when built correctly. Automation tools handle protected health information, so they need HIPAA-compliant data handling, encryption, access controls, and audit trails. Compliance depends on the vendor and configuration, not the technology itself. Commure is HIPAA-compliant and built for enterprise health systems, so hold any platform you evaluate to that same standard.
How do you get started with healthcare automation?
Start with one high-volume, rule-based, low-risk workflow such as prior authorization or eligibility verification. Measure the time and money it returns, then expand into adjacent steps. A phased rollout builds staff trust and produces the hard numbers you need to justify each next investment.
Tell us a little bit about yourself—what do you like to do outside of work?
Relocating from Long Island, NY, 5 years ago with my wife and 2 daughters, ages 8 and 6, to the Raleigh-Durham, NC area - there is no shortage of fun to keep us busy down here. From hiking trails at the lake to pickleball to dance class to the swim team, we are always keeping active. My daughters are slowly becoming “foodies” too. They don’t run with the chicken nugget and tater tot crowd. They love sushi and ramen. They love “millionaire” bacon (just add a little brown sugar) and “fruity-face” pancakes. We grill year-round - my kids are carnivores! - so my rib-eye steak and cheeseburger game is on point. North Carolina is known for its BBQ - we’ve tried many of the local places and think we found our go-to spot. We have also started baking together more - the kitchen gets wrecked, but we have a blast, and the end product is always worth it. Look up the recipe for Hummingbird Cake and thank me later.
As a kid, what did you want to be when you grew up?
I thought I wanted to be a doctor - then I took Organic Chemistry in college as a Pre-Med major…that's when I learned I didn’t really want to be a doctor. Whenever my kids need a band-aid, I’m quick to tell them: “Don’t worry, Dad was pre-med for a semester. You’re in good hands.”
I wound up studying Psychology and Sociology at the University of Notre Dame (Go Irish!), with intentions to pursue a career as a Sports Psychologist - but upon graduating instead received a wonderful opportunity in the Real Estate and Construction sector back home in New York City. This role afforded me an opportunity to work on many high-profile projects - many of which were engagements with large health systems such as NYU Langone Medical Center, Memorial Sloan Kettering, and Mount Sinai. My company at the time leveraged proprietary VR/AR software to design, manufacture, and build sustainable medical care spaces - everything from hospital headwalls and footwalls with embedded medical gases to millwork for nursing stations.
Describe a day in the life of your role.
As an Account Manager, serving as the single point of contact for our partners - the role touches every phase of every product in our bundle. A typical day looks like this: execute on whatever it is your partners require. We are full-time client advocates, relationship managers, issue-resolvers, account retainers, project coordinators, revenue and data analysts, product experts, process/workflow builders, strategic consultants, and often…behavioral psychologists!
What made you decide to join Commure?
From my time in construction, I learned this: demolition is easy; building is hard. Anybody can tear down or point out faults. The real skill and true craftsmanship is reserved for the creators and builders - people who take empty space and transform it into something beautiful and useful. Good design is both form and function, in harmony - the Commure product suite nails this.
Seeing firsthand the significant impact Real Estate and Facilities projects have on patient care - and a medical practice’s ability to generate revenue - laid the groundwork for pursuing a role at Commure to tackle the healthcare problem. The United States is #1 in the world in wealth, but outside the top 30 in healthcare delivery - this needs to change.
How would you describe the Commure company culture?
This is a team sport. While we each have distinct responsibilities, we operate as one team. Our culture is defined by collaboration, accountability, and a relentless focus on client outcomes. Across the organization, we are united by a common mission: building best-in-class, AI-native products to improve provider productivity, reduce administrative burden, and allow healthcare teams to focus on what matters most - patient care.
What advice would you give someone on their first day at Commure?
Be a heat-seeking missile for pain - actively seek the gnarliest challenges and pain points that impact our customers. Prioritize building product knowledge and expertise across our bundle. Operate without fear. Dive headfirst into ambiguous challenges, and when you identify a gap - the standing order to my team - go bridge the gap. You do not need to ask permission. Brick-by-brick, drive the company forward.
What has been your greatest accomplishment so far at Commure?
We have accomplished so much in my 2+ years - improving user experience while surfacing inconsistencies in claims before they were submitted - and fixing claims we knew an insurance company would deny payment before they were submitted. The impact of this release was astonishing - automating previously time-consuming workflows while improving First Pass Rate and cash flow for partners across our portfolio.
What does "a win" look like in your role?
Earning a renewal and extending into a multi-year partnership. It shows we have built trust, delivered meaningful results, and created an experience that our partners want to continue investing in. Those outcomes only happen when all disciplines - including Sales, Launch, Account Management, Operations, Engineering, Product, and Support - are working in harmony - one team. Every renewal strengthens our business and expands our opportunity to improve healthcare for more patients and providers.
Interested in a career building the next generation of healthcare technology powered by AI? We are always looking for talented people across our departments.
A new patient in one of the 15 largest metro areas in the U.S. now waits an average of 31 days to see a physician, according to AMN Healthcare's 2025 survey, and rural patients often wait longer still (roughly 20% of Americans live in rural areas while only about 9% of physicians practice there, according to the National Rural Health Association). That wait is a symptom of a system that loses patients before the patient journey ever begins, and every day of delay is a chance for someone to switch providers, defer care, or disappear from the schedule entirely.
The patient journey is the full arc of a person's experience with a health system, from the first symptom or online search, through treatment and long-term follow-up. Health systems have mapped that journey for years, yet far fewer have fixed the gaps along the way.
This guide covers what the patient journey is, the stages every patient moves through, how to map it, and how to close the gaps that quietly cost health systems patients and revenue.
What is the patient journey?
The patient journey is the sequence of interactions a person has with a healthcare organization over time, starting well before a first appointment and continuing long after a visit ends. It covers how someone finds a provider, books and prepares for care, moves through the visit itself, and stays connected for follow-up and ongoing needs.
Much of the healthcare patient journey plays out beyond the exam room: the phone tree at scheduling, the intake form, the reminder that does or doesn't arrive, the call after a procedure when a question comes up at 9 p.m.
It helps to separate two terms that often get used interchangeably. The patient journey is what actually happens to the patient. A patient journey map is the tool you build to see that experience clearly and decide what to change.
Why the patient journey matters
Healthcare has shifted from a system patients accepted to one they shop, and people now compare providers the way they compare any other service. That shift shows up plainly in switching behavior. About 1 in 5 patients switched providers in the past year, and nearly 90% of them did so because the organization was hard to do business with, according to an Accenture survey reported by the American Hospital Association. 7 in 10 pointed to access as a deciding factor when they chose someone new.
That pattern points squarely at the friction around care: the busy phone line, the confusing bill, the message that never gets a reply. Every one of those friction points sits somewhere on the patient journey, which is why mapping it and fixing what you find has become a retention strategy in its own right.
The stages of the patient journey
Most patient journeys move through 6 stages: awareness, consideration, access, the visit, follow-up, and ongoing care. Few patients travel them in a tidy line, since people loop back, pause, or drop out along the way, but the stages give you a shared structure for pinpointing where the experience breaks down.
Awareness
Awareness starts the moment someone notices a symptom or decides they need care. Most people begin with a search engine rather than a physician referral, so the clarity of what they find shapes their first impression of your organization long before they ever call. Content that answers real questions, a findable location listing, and current reviews all work well at this stage.
Consideration
In the consideration stage, patients weigh their options against practical criteria: location, accepted insurance, reviews, and whether they can actually reach you. This is where many patients silently choose a competitor, often for reasons that have nothing to do with clinical quality. A booking page that asks for too much, a call that goes to voicemail, or a week-long callback delay can end the relationship before it begins.
Access
Access is where the journey stalls more often than not. With new-patient waits averaging a month across major metros, the organizations that win patients are the ones that make scheduling fast and answer the phone reliably.
Access is also one of the more fixable stages. One community health center that began handling inbound calls with AI call center agents saved 800 labor hours for every 10,000 calls, roughly $240,000 a year, while resolving a large share of requests without staff involvement. Widening patient access at the front door keeps patients from giving up before they arrive.
Preparation belongs to this stage too. Long paper forms and prep instructions that are easy to miss create no-shows and day-of delays, which is why modern patient intake moves the clipboard onto the patient's phone through conversational outreach. Timely, multi-touch reminders that patients can actually respond to help reduce no-shows and protect both the schedule and the revenue attached to it.
The visit
The visit is where clinical care happens and where traditional patient-satisfaction measurement concentrates, spanning check-in, the encounter, and discharge. It's also where communication gaps take root, since patients often leave without asking the questions that mattered most to them and forget a large share of what they were told once they get home. What happens over the following days depends heavily on how well the visit sets them up.
Follow-up
Follow-up is the stage health systems most often let slide, even though it's where good clinical work can come undone. A 2026 study of more than 579,000 Medicare admissions found that many high-risk patients never receive post-discharge follow-up, and those who did were significantly less likely to be readmitted within 30 days. After a procedure, patients navigate medication questions, recovery uncertainty, and handoffs between care teams, and every handoff is a point where someone can slip through the cracks.
Two strategies make a measurable difference here. Tighter transitions of care keep information from getting dropped as a patient moves between settings, and proactive outreach closes the post-surgical care gap during the window when patients are home and most likely to need answers.
Ongoing care
Ongoing care turns a single visit into a lasting relationship that supports better health. For someone managing a chronic condition, this stage can stretch across years, and it's where loyalty is either earned or lost. Steady, personalized chronic care management keeps patients engaged between appointments, surfaces problems earlier, and reduces the avoidable complications that pull people back into acute care.
Patient journey mapping
Patient journey mapping is the practice of laying out each stage, touchpoint, and emotion a patient experiences, so you can see where the journey serves them and where it fails them. The patient journey map is the visual result, a shared picture of what patients do, think, and feel as they move through your system.
Here is a very basic example of a patient journey map. The more details you can fill in, the better.
Done well, a map earns its keep in a few ways. It creates a common view of the experience across departments that rarely talk to each other, exposes the specific moments where patients get stuck, and turns vague complaints about "patient experience" into a prioritized list of fixable problems.
Types of patient journey maps
Teams generally build one of four map types depending on the question they're answering.
A current-state map shows the journey as it runs today, drawn from real patient data, and it's the right starting point for incremental improvement.
A future-state map describes the journey you want to deliver and works well for aligning teams around a new service or process.
A day-in-the-life map widens the lens to what a patient experiences outside your system, which helps you spot unmet needs you'd otherwise miss.
A service blueprint goes the other direction and adds the people, systems, and policies behind each touchpoint, so you can trace a pain point back to the process that caused it.
Most organizations start with one type and add others as the work matures.
Patient journey analytics
The strongest maps sit on data. Patient journey analytics is the practice of layering your operational and experience data onto the map: scheduling and no-show records, call-center hold times, message response rates, portal usage, and post-visit feedback. Those numbers show you where patients actually drop off rather than where you assume they do, and they let you measure whether a change at one touchpoint moved the outcome you cared about.
How to map the patient journey
Here are the steps to take to build out your patient journey map:
Define your scope and goal. A map can zoom in on a single interaction, like booking an appointment, or span an entire condition, like managing diabetes over several years. Let the problem you're trying to solve set the boundaries.
Gather data from multiple sources. Combine direct patient input from interviews, surveys, and short diary studies with the operational and experience data you already hold, like scheduling records, message response rates, and existing patient satisfaction and engagement survey scores. Interviews add depth, surveys validate patterns at scale, and the data you already collect grounds the whole map in what really happens.
Build personas. A new mother's journey looks nothing like an oncology patient's, so segment by the populations you actually serve rather than mapping a generic average patient.
Chart touchpoints and emotions. For each stage, record what the patient does, who and what they interact with, and how they feel. The emotional low points usually mark your biggest opportunities, since that's where frustration leads to a decision to leave.
Validate and act. Put the draft in front of patients and frontline staff to catch what you missed, then commit to fixing the touchpoints it exposes. A map only pays off when it drives real changes to how you operate.
Common mapping mistakes
A few mistakes hurt the value of patient journey mapping. The most common is treating the finished map as the deliverable, when the map only matters once it changes how you work. Others include mapping the journey your organization wishes patients took instead of the one they actually take, building the whole thing from internal assumptions without talking to a single patient, and mapping so broadly that no team owns any specific fix. Assigning clear ownership for each stage, and revisiting the map as your services and patients change, keeps it from going stale.
Closing the gaps
Finding the gaps is the easy part; closing them, stage by stage, is where patient experience actually improves and where retention follows.
In practice, that means answering the phone during the access stage, replacing paper intake with conversational outreach before the visit, and staying in contact through follow-up and ongoing care instead of going quiet once the encounter ends. The connected set of tools that supports patients across all of these stages is what many health system leaders now call the digital front door, and it works best as a single platform that writes back to the EHR rather than a stack of disconnected point solutions. Keeping patients informed between visits is the job of patient communication software that reads each reply and routes anything a human needs to handle to the right person.
Commure Engage is built for exactly this work, supporting front-cycle patient experience across scheduling, intake, communication, and care navigation on one platform. Yale New Haven Health used Commure Engage for pre-appointment outreach in its breast imaging program and cut no-show and same-day cancellation rates by more than half.
Map the journey your patients actually take, then close the gaps one stage at a time. See how it all comes together.
What is the difference between the patient journey and the patient experience?
The patient journey is the full sequence of steps a patient moves through, from first symptom to ongoing care. The patient experience is how they perceive and feel about those steps. The journey is the path, and the experience is the quality of each interaction along it, which is why you map the journey to improve the experience.
What are the stages of the patient journey?
The patient journey typically moves through 6 stages: awareness, when someone notices a symptom; consideration, when they weigh providers; access, when they schedule and prepare; the visit, when care happens; follow-up, after a procedure or discharge; and ongoing care, which sustains the relationship over time. Few patients travel them in a straight line.
Who is responsible for the patient journey in a health system?
No single department owns the patient journey, which is part of what makes it hard to fix. It crosses scheduling, front-desk staff, clinicians, billing, marketing, and IT, so improving it takes shared ownership rather than one team's effort. Most organizations assign an owner for each stage plus a cross-functional group to keep the full journey aligned.
How can health systems improve the patient journey?
Health systems improve the patient journey by fixing the touchpoints a journey map exposes, stage by stage. The biggest gains usually come at access: answering the phone, offering online self-scheduling, and replacing paper intake with digital outreach. A July 2025 MGMA poll found 71% of practices have less than 25% of their patients using digital tools to self-schedule, so the opportunity is wide open.
When a clinic reaches a patient by phone before a visit, only 3% miss the appointment. When the reminder lands in voicemail, that climbs to 24%. When no one picks up at all, 39% don't show. Those numbers come from a study of 250 primary care patients managing depression, published in Psychiatric Services, and they point to something most communication tools get wrong. Reaching a patient and sending a message are two different things.
For 20 years, patient communication software has mostly meant reminders. An appointment gets booked, the system fires off a text or a robocall, and the office hopes it lands.
Modern patient communication software works differently. It's two-way, omnichannel, automated, HIPAA-compliant, and EHR-integrated. Instead of sending a text and hoping the patient receives it, AI reads each patient's reply, responds in natural language, and routes anything that needs a human to the right person.
Why one-way reminders hit a wall
Reminders work, up to a point. A randomized trial published in AJMC tested three approaches: a reminder 3 days out, 1 day out, or both. Patients who got both missed 4.4% of appointments, compared with 5.8% and 5.3% for a single reminder 3 days or 1 day before.
In that same research, the highest-risk group still missed roughly 20% of visits even after two reminders. The authors concluded automated messages have to be backed by staff outreach or patient navigation to engage with those patients.
So the old model forces a hard choice. Send more reminders that high-risk patients already skip, or put staff back on the phones.
A modern patient communication platform closes that gap. Automated digital care pathways are personalized to patients' unique care journeys, and AI call center agents can handle the follow-up calls that used to eat staff hours. One FQHC saw its agents save 800 labor hours for every 10,000 calls, about $240,000 a year.
What modern patient communication software actually does
Modern platforms respond, instead of just sending. When a patient texts a question, AI reads the reply and answers in plain language, drawing on a clinician-curated knowledge base, so responses stay inside vetted clinical boundaries. Anything urgent, or anything the system shouldn't answer on its own, routes to the right care team member.
None of this requires a portal login or an app. The platform reaches patients by SMS, RCS, voice, or email, and every exchange writes back to the EHR so the care team sees it where they already work.
Routine outreach runs on its own. Appointment prep, reminders, and post-visit check-ins go out automatically, without staff sending them one by one. The result is one continuous conversation with each patient instead of a scatter of one-way pings.
How to evaluate patient communication software
When you compare platforms, four things separate one that works from one that adds cost. Here’s what to ask when comparing vendors:
Ask whether it's genuinely two-way and omnichannel. A tool that only pushes messages out is a reminder system with a new name, and it leaves you managing the same problem you started with. Confirm patients can reply on the channel they choose and get a real answer back.
Ask how it handles HIPAA. A two-way thread carries symptoms, medications, and test results, so it needs the safeguards the HHS Office for Civil Rights expects: encryption, consent capture, access controls, and audit logging, with a business associate agreement in place. Get the specifics, not a compliance logo.
Ask how deep the EHR integration goes. Read-only isn't enough. Communication should write back to the record, or your care team ends up reconciling two systems by hand.
Ask where automation stops and people start. The platform should resolve routine volume on its own and escalate complex cases to staff, so you get the efficiency without dropping the patients who need a person.
These map to the broader questions health system leaders weigh when they build a digital front door, where communication sits alongside scheduling, intake, and care navigation.
Patient communication that patients respond to
Commure Engage brings these capabilities into one platform. It reaches patients across SMS, RCS, voice, and email, runs on 500+ clinically validated care pathways, and integrates bi-directionally with the EHR. More than 80% of patient inquiries resolve automatically, and outreach capacity scales up to 6.5x without adding staff.
What is patient communication software? Patient communication software is the platform a health system uses to reach and respond to patients across channels like text, voice, and email. Modern tools are two-way and AI-powered, so patients get answers and the care team stays in the loop, with everything connected to the EHR.
How is patient communication software different from an appointment reminder tool? A reminder tool sends one-way messages: appointment times, prep instructions, and alerts. Patient communication software adds a return path. Patients reply, get answers, and their responses route to the care team and into the EHR. The reminder becomes one feature inside a two-way system.
Is patient communication software the same as a patient portal? No. A portal waits for patients to log in. Patient communication software reaches patients on the channels they already use, like text and voice, and doesn't require a separate login or app.
Is texting patients HIPAA-compliant? It can be, with the right safeguards. Standard consumer texting isn't secure enough for protected health information. A HIPAA-compliant platform adds encryption, consent capture, access controls, and audit logging. The vendor also must sign a business associate agreement.
Who should own patient communication in a health system? It usually spans operations, IT, and clinical leadership, with input from marketing on voice and messaging standards. Operations owns the workflows, IT owns the EHR integration and security, and clinical teams shape the escalation and triage logic. Naming one accountable owner early keeps the program from fragmenting.
.jpg)
