临床文档与报销之间日益扩大的脱节
The Growing Disconnect Between Clinical Documentation and Reimbursement
Droidal 首席执行官 Inger Sivanthi
多年来,我审阅过的大多数文档问题,实际上从来都不是真正的文档问题,而是后来以拒付、CDI 工作量超支以及悄然流失的收入形式显现出来的工作流问题。
这就是行业一直回避的真相。我们不断购买工具来解决一个与工具无关的问题。临床文档与报销之间的差距并不是因为技术失效而扩大,而是因为在任何技术介入之前,我们一直忽视了系统之间存在多么严重的不匹配。
这是结构性问题,而不是编码问题
下面是一个令人不适的事实,我会直接说明:临床文档与报销之间日益扩大的脱节,主要不是技术故障,而是许多组织仍未完全正视的结构性问题。
许多组织认为,问题出在编码绩效、EHR限制或医生培训上。这些都是症状,而不是原因。真正的问题在于,临床团队是为了连续性的医疗照护而记录文档,而支付方则依据特异性、医疗必要性和政策一致性进行裁定。这是两个不同的系统,也有两套不同的激励机制。
领导层往往更愿意相信,解决方案是更智能的工具、新的供应商或更好的培训。但除非组织首先接受这样一个事实:工作流本身从未被设计为支持报销,否则这些措施都无法弥合这一差距,这正是脱节持续扩大的原因。
数据让情况更加清晰
数据已经清楚地讲述了这一情况。2024 年,初次理赔拒付率达到 11.8%,高于几年前的 10.2%。一项发表于 2026 年的同行评审健康信息学研究发现,近 47% 的保险理赔拒付直接与文档问题有关,而不是与资格或提交错误有关。
这不仅仅是一个账单问题,而是一个源文档问题。
反复出现的缺口很容易列举:
缺少支付方处理理赔所要求的临床特异性
医疗必要性表述薄弱,给审核人员留下拒付或下调编码的空间诊断推理不完整,迫使编码员进行解读,而不是确认病历对下一位医疗服务提供者而言,已经足够清楚地讲述了临床故事。但它没有很好地讲述报销故事。而报销正是维持组织运转的关键。
为什么大多数组织采取了错误的解决方式
我曾看到组织投入数百万美元试图解决这一问题,但许多组织仍然选择那些更能提升速度、而不是更能改善一致性的干预措施。
环境式 AI 让记录撰写得更快,但更快并不等于更一致。如果工作流仍然产生含糊或不完整的临床语言,那么工具只是在加速同一个问题。
CDI 团队也能提供帮助,但作用有限。回顾性查询可以改善病历,但到那时就诊已经结束,医生回答问题时依靠的是记忆,而不是当时的情境。这是纠正,而不是预防。
编码自动化可以减少人工工作量,但它无法创造从未被记录的特异性。如果源文档内容单薄,自动化只会更高效地处理这种单薄内容。
结果是可以预料的:各部门觉得自己正在改善工作流中的某个环节,而整个组织却仍在持续流失收入。
真正的一致性是什么样的做得好的组织不再把文档视为一项独立的行政任务,而是将其视为医疗服务交付的一部分。
领导层围绕实际决策点构建工作流,而不仅仅是围绕组织架构。这意味着在医疗服务提供点提供对支付方敏感的提示,建立尽早要求特异性的文档结构,并让 CDI 团队以运营合作伙伴的方式工作,而不是充当事后审核人员。
AI 应处理可重复的工作:
发现缺失的文档要素标记可能的支付方标准从临床医生的叙述中自动填充结构化字段人类应处理判断:
确认诊断具有临床支持处理支付方的模糊要求决定如何处理例外情况当这种分工明确后,员工就不再把文档视为额外负担,而会开始将其视为工作自然推进方式的一部分。此时,报销才能在不为临床医生制造更多摩擦的情况下得到改善。
领导者应提出的问题
领导层不应问:“文档工具的表现如何?”更重要的问题是,工作本身是否经过结构化设计,使文档能够在记录创建之时就支持报销。
这个问题会改变对话方向。它将重点从供应商选择转向工作流设计,将问题从软件性能转向运营问责,并迫使领导层审视临床意图与支付方期望之间的差距,而真正的问题正存在于这里。
技术已经准备就绪。环境式智能、自然语言处理和 AI 辅助编码已经能够开展有用的工作。但能力并不等同于影响。如果工作流不匹配,即使是最好的工具也只能提供有限帮助。
接下来会怎样
最令我担忧的是,许多组织仍然认为这是一个文档优化问题,而实际上它是一个上游的报销设计问题。只要临床文档依据一种逻辑创建,而报销依据另一种逻辑进行评判,拒付、返工和收入流失就会继续固化在流程之中。
因此,我不认为这是一篇关于工具是否准备就绪的文章,而是关于组织是否准备好围绕这些工具重新设计工作。只有当卫生系统不再把文档视为下游的清理工作,而是将其视为连接医疗服务交付与支付的运营桥梁时,临床文档与报销之间的差距才会开始缩小。
关于 Inger Sivanthi Inger Sivanthi是Droidal的首席执行官。Droidal 是一家 AI 医疗服务提供商,专注于收入周期和运营自动化。凭借在大型语言模型和应用 AI 方面的深厚专业知识,他通过部署智能 AI 代理,帮助医疗组织实现了超过 2.5 亿美元的成本节约。他的工作强调负责任且符合伦理的 AI 采用,以大规模改善医疗和财务成果。
Inger Sivanthi, CEO of Droidal
Most documentation problems I have reviewed over the years were never really about documentation itself. They were workflow problems that showed up later as denials, CDI overruns, and revenue that quietly disappeared.
That is the honest truth the industry keeps avoiding. We keep buying tools to fix a problem that is not about tools. The gap between clinical documentation and reimbursement is not growing because technology is failing. It is growing because we keep ignoring how misaligned our systems are before any technology enters the picture.
This Is Structural, Not a Coding Problem
Here is the uncomfortable truth I will state directly: the growing disconnect between clinical documentation and reimbursement is not primarily a technology failure. It is a structural problem that many organizations still have not fully confronted.
Many organizations assume the problem lives in coding performance, EHR limitations, or physician training. Those are all symptoms, not causes. The real problem is that clinical teams document for care continuity while payers adjudicate for specificity, medical necessity, and policy alignment. Those are two different systems with two different incentives.
Leadership often prefers to believe the fix is a smarter tool, a new vendor, or better training. None of those will close the gap unless organizations first accept that the workflow itself was never designed to support reimbursement, which is why the disconnect continues to grow.
The Numbers Make It Clearer
The numbers are already telling the story clearly. Initial claim denial rates hit 11.8% in 2024, up from 10.2% just a few years earlier. A 2026 peer-reviewed health informatics study found that nearly 47% of insurance claim denials were tied directly to documentation issues, not eligibility or filing errors.
That is not just a billing problem. It is a source-documentation problem.
The recurring gaps are simple to name:
Missing clinical specificity that payers require to process a claim
Weak medical necessity language that gives reviewers room to deny or downcode Incomplete diagnostic reasoning that forces coders to interpret instead of confirm The chart tells the clinical story well enough for the next provider. It tells the reimbursement story poorly. And reimbursement is what keeps the organization running.
Why Most Organizations Fix This the Wrong Way
I have watched organizations spend millions trying to fix this, and many still choose interventions that improve speed more than they improve alignment.
Ambient AI makes notes faster, but faster is not the same as aligned. If the workflow still produces vague or incomplete clinical language, the tool simply accelerates the same problem.
CDI teams help too, but only to a point. A retrospective query can improve a chart, but by then the encounter is already over and the physician is answering from memory, not context. That is correction, not prevention.
Coding automation reduces manual effort, but it cannot create specificity that was never documented. If the source note is thin, automation only processes thinness more efficiently.
The result is predictable: departments feel like they are improving their part of the workflow while the organization continues to leak revenue.
What Real Alignment Looks Like
The organizations that do this well stop treating documentation as a separate administrative task. They treat it as part of care delivery.
Leadership builds workflow around actual decision points, not just the org chart. That means payer-sensitive prompts at the point of care, documentation structures that ask for specificity early, and CDI teams that work like operational partners instead of after-the-fact reviewers.
AI should handle repeatable work:
Surfacing missing documentation elements
Flagging likely payer criteria Auto-populating structured fields from clinician narrative Humans should handle judgment:
Confirming the diagnosis is clinically supported
Navigating payer ambiguity Deciding how to handle exceptions When that division is clear, staff stop seeing documentation as an extra burden and start seeing it as part of how the work naturally moves. That is when reimbursement improves without creating more friction for clinicians.
The Question Leaders Should Be Asking
Leadership should not be asking, “Is the documentation tool performing?” The more important question is whether the work itself is structured so that documentation supports reimbursement at the point where the record is created.
That question changes the conversation. It shifts the focus from vendor selection to workflow design. It moves the issue from software performance to operational accountability. And it forces leadership to look at the gap between clinical intent and payer expectation, which is where the real problem lives.
The technology is ready. Ambient intelligence, natural language processing, and AI-assisted coding are already capable of doing useful work. But capability is not the same as impact. If the workflow is misaligned, even the best tools will only help a little.
Where This Goes Next
What concerns me most is that many organizations still think this is a documentation optimization issue when it is really a reimbursement design issue upstream. As long as clinical documentation is created in one system of logic and reimbursement is judged in another, denials, rework, and revenue leakage will remain built into the process.
That is why I do not see this as a story about whether the tools are ready. I see it as a story about whether organizations are ready to redesign the work around them. The gap between clinical documentation and reimbursement will start to close only when health systems stop treating documentation as a downstream cleanup exercise and start treating it as an operational bridge between care delivery and payment.
About Inger Sivanthi Inger Sivanthi is the Chief Executive Officer of Droidal, an AI healthcare services provider focused on revenue cycle and operational automation. With deep expertise in large language models and applied AI, he has helped healthcare organizations achieve more than $250 million in cost savings through the deployment of intelligent AI agents. His work emphasizes responsible and ethical AI adoption to improve healthcare and financial outcomes at scale.
Reader Interactions