A recent roundup in Healthcare IT Today asked revenue cycle leaders a direct question: which parts of your operations still require a human and cannot be handed off to AI? Five leaders answered. Their responses converged on the same territory: complex denials, billing disputes, compliance gray areas and any interaction where a patient is scared, confused or emotionally activated.
Dawn Crump at MRO, Krista Bowman at Further, Cindy Otero at Naples Comprehensive Health, Michelle Durbin at Altera Digital Health and Anurag Mehta at Omega Healthcare each drew the same boundary. Not "AI or human?" but "AI for which workflows and human for which ones?" That is the same boundary every health system operations leader needs to draw for language access.
1. Why the RCM Framework Maps Directly to Medical Interpretation
The five RCM contributors did not argue against AI.
They argued for precision about where AI belongs and where it does not.
1.1 Upstream AI, downstream human judgment
Dawn Crump, Vice President of Revenue Integrity Solutions at MRO, put it directly: "While AI can automate upstream processes like registration, coding, and CDI, errors or gaps in those stages can still lead to denials that demand critical thinking and contextual understanding to resolve." The downstream human is not a fallback. They are a designed part of the system.
Medical interpretation follows the same structure. AI handles appointment confirmation, prescription instructions, administrative intake and post-discharge follow-up for stable patients efficiently. Predictable vocabulary. Bounded clinical context. Low emotional stakes.
1.2 Empathy and trust cannot be automated
Krista Bowman, Managing Director at Further, put the empathy argument in operational terms: "Money is inherently emotional... so people don't want to talk to an AI chatbot when they have financial questions." The customer service side of RCM stays with employees because human connection is the product.
Language access changes that dynamic in an important way. When interpretation is properly embedded in the workflow, it empowers the provider or staff member to lead the financial conversation directly, in the patient's language, with precision.
AI is not the party having the financial discussion.
It is the tool that interprets, accurately and in real time, what the provider says. The conversation stays human.
1.3 Compliance and accountability require human ownership
Cindy Otero, Senior Director of Revenue Cycle at Naples Comprehensive Health, named a category that gets missed in AI adoption conversations: "Managing industry regulations and compliance standards within revenue workflows will also always require human oversight and engagement."
In language access, that human ownership is not an add-on. It is foundational. Section 1557 of the Affordable Care Act explicitly requires human oversight in AI-assisted medical interpretation, making human-in-the-loop not a best practice but a regulatory baseline. The compliance layer is built into the architecture of responsible AI interpretation from the start. What Cindy Otero describes as a gap in RCM is, in language access, already a design requirement.
2. How to Assess Where Your Organization Actually Stands
Before a health system can design an AI-human interpretation model, it needs an honest read of its current state. Language access programs fall into three operational tiers.
2.1 Tier 1: reactive
Interpretation is deployed when a gap is flagged, typically by a clinician mid-encounter. No scheduled interpretation at intake. No structured coverage across touchpoints. Staff improvise. Wait times are unpredictable. Cost is unpredictable (mostly billed per minute).
2.2 Tier 2: task-based
Interpretation is scheduled for flagged encounters, usually in-person visits identified at scheduling or registration.
Coverage is inconsistent across telehealth, phone triage and discharge.
AI may be in use for specific workflows but without a governing framework for which encounters qualify.
2.3 Tier 3: infrastructure-based
Interpretation is embedded from first patient contact across every touchpoint: scheduling, telehealth, in-person encounters, discharge and follow-up. Encounter type drives modality selection. Documentation is consistent. The organization can report on interpretation utilization the same way it reports on other clinical services.
Where does your organization sit? The three tiers are a diagnostic as much as a framework. A health system that has begun thinking about language access as infrastructure, covering the patient across scheduling, phone, telehealth, in-person encounters and discharge, is already moving toward Tier 3. That shift in thinking is what drives the move, not the technology. Vendors that offer a suite of products covering the full patient journey, like No Barrier, make Tier 3 operationally achievable without building a patchwork of point solutions.
3. What the Cost Conversation Actually Looks Like
The cost structure in language access is well understood by anyone who has managed it.
3.1 The visible costs
Per-minute phone interpretation is expensive at volume.
In-house interpreters are expensive to staff and impossible to scale across a multi-site network.
AI interpretation looks attractive on a cost-per-encounter basis, particularly for high-frequency interactions.
3.2 The invisible costs
The cost comparison that matters most is not AI versus phone interpretation. It is AI-plus-human-for-complex-encounters versus the current workaround model.
When a clinician uses a bilingual medical assistant informally, the cost is invisible but real: the MA's time is pulled from their primary role and the health system carries the compliance exposure without knowing it.
3.2 The subscription shift
Flat monthly pricing removes the per-minute dynamic that creates background pressure on how long a provider spends with an LEP patient. When every minute on the line has a dollar attached, that pressure is real even when it is never explicitly discussed. Removing it changes provider behavior in ways that do not show up in a cost-per-encounter comparison. It converts language access from a variable cost that grows with patient volume into a predictable operational line item.
4. Which Encounters Require a Human
Michelle Durbin, Director of Solution Management at Altera Digital Health, named the principle directly: "AI does a great job prioritizing work and suggesting next steps but experienced teams are still critical when it comes to interpreting gray areas, handling payer nuance and supporting patients through challenging financial situations."
In RCM, the gray area is financial complexity.
In language access, it is clinical and emotional complexity.
4.1 AI-suited encounters
Appointment reminders, prescription instructions, administrative intake, low and complex encounters, post-discharge follow-up and telehealth. These share the same characteristics as the upstream RCM workflows where AI performs well: predictable vocabulary, bounded context and recoverable errors.
4.2 Human-indicated encounters
Informed consent, goals of care, sensitive diagnosis delivery, end-of-life conversations and any encounter where the patient's emotional state is elevated. On Care Culture Talks, Dr. Aurelio Muzaurieta, an ER physician who is deployed in fast-moving clinical environments, was direct about where AI reaches its ceiling: the encounters where stakes are highest are exactly where human presence matters most. The gray area in language access is not payer nuance. It is a patient receiving a diagnosis they did not expect, in a language that is not their own.
The classification does not require a complex algorithm. It requires a policy decision made in advance, documented in the workflow and trained into the front-desk and clinical team before go-live.
5. Why Adoption Is the Harder Problem
Anurag Mehta, Founder and CEO at Omega Healthcare, identified the root cause of most AI deployment failures in RCM: "The difference between AI that delivers meaningful improvement and AI that introduces new risks comes down to how intelligence is designed into workflows and how it is shaped by expertise."
That is not a technology observation. It is an operations observation.
5.1 The deployment conversation
When we work with health systems on deployment, the conversation rarely starts with the technology. It starts with what triggers interpretation at the front desk, how patients experience phone interpretation, how telehealth encounters are covered end to end and what the clinical team does when a provider or patient needs a different level of support. Getting those answers right is what determines whether the organization has built language access as infrastructure or simply added a new tool to an existing workaround.
5.2 The training model
Adoption at No Barrier follows a structured model: training before go-live, recorded training materials for onboarding new staff, champion identification within the clinical team and custom support materials built around the organization's existing workflows. Medical organizations that invest in that training layer alongside the rollout consistently show stronger adoption and usage. Reach out to understand how we support your team.
6. What to Do With This
The Healthcare IT Today RCM conversation and the language access operational reality point at the same principle: AI handles volume well when the task is bounded and the stakes of a single error are recoverable. Human judgment is required when the task is emotionally activated, contextually complex or where an error has consequences that are difficult to reverse.
6.1 Assess your tier
If your organization is at Tier 1, the priority is coverage breadth before coverage optimization. Get interpretation embedded at every touchpoint before refining which touchpoints use which modality.
6.2 Classify your encounters before go-live
The classification does not need to be exhaustive. It needs to be clear enough that front-desk and clinical staff can apply it without a decision tree in front of them.
6.3 Measure what matters
- Utilization rate by encounter type.
- Documentation completeness.
- Patient satisfaction scores segmented by preferred language.
- Staff satisfaction
These are the metrics that tell you whether the program is working, not the cost-per-encounter calculation that drove the initial procurement.
No Barrier covers 295+ language access options and is built to support that full operational model, from scheduling through discharge. Reach out to understand the breakdown we offer.
.svg){kind=small}