Closing the Gaps: Building One Connected Revenue Cycle

One patient, one account, one Revenue Cycle—and no unresolved work without a clear owner.

By Vanessa Couch-Laguana, Head of RCM, LunaBill

Healthcare organizations often describe the Revenue Cycle in terms of the front end and the back end.

The front end schedules and registers the patient, verifies coverage, secures authorizations, prepares estimates, and discusses financial responsibility. The back end submits claims, follows up with payers, manages denials, resolves balances, and communicates with patients after care.

Those distinctions may help organize departments, but they can also create silos.

A patient does not experience the Revenue Cycle as a collection of separate departments. The patient experiences one organization. Likewise, an account does not stop being connected to Patient Access when the patient leaves the registration desk. It continues through clinical care, documentation, utilization management, charge capture, coding, billing, follow-up, denial management, and patient collections.

After nearly three decades in Revenue Cycle operations, I have learned that the greatest delays often occur not within a department, but between departments—especially when work is incomplete, ownership is unclear, or one team does not know what the next team needs.

Closing those gaps requires more than stronger communication between Patient Access and Patient Financial Services. It requires the entire Revenue Cycle, including the clinical and operational departments that support it, to work as one connected system.

The Revenue Cycle begins before the front desk

Patient Access does not begin when a patient arrives for care. It begins with scheduling, preregistration, and financial clearance.

For prescheduled services, especially surgical and procedural cases, organizations should complete as much work as possible before the patient arrives. Depending on the organization’s structure, that work may be managed by scheduling, Patient Access, a centralized preregistration team, or a dedicated financial-clearance unit.

Regardless of the department name, the responsibilities should be clear.

A complete financial-clearance process may include:

Confirming patient demographic and insurance information
Verifying eligibility and benefits
Determining referral and authorization requirements
Obtaining the required authorization
Confirming that the scheduled service matches the authorized service
Reviewing medical-necessity or order requirements
Preparing an estimate of the patient’s expected responsibility
Conducting appropriate patient outreach
Collecting amounts due when appropriate
Screening for financial assistance
Screening for available coverage options, including Medicaid or Medicare when appropriate
Escalating services that have not been financially cleared

The organization should also define exactly what “financially cleared” means. If one department considers an account cleared after eligibility is verified, while another expects authorization, an estimate, patient contact, and documentation to be completed, the account may move forward with important work still unresolved.

The Healthcare Financial Management Association’s patient financial communication guidance recommends beginning discussions as early as possible, maintaining continuity from preregistration through the encounter, verifying insurance information, and connecting patients with estimates, payment options, or financial assistance when appropriate. That continuity can prevent patients from being asked the same questions repeatedly and can give them clearer information before care is delivered.

Responsibility does not end when the patient leaves the desk

Registration should be completed as thoroughly as possible, but responsibility does not end when the patient is no longer standing at the registration desk.

When information remains incomplete, the account needs:

A clearly identified owner
A documented description of what is missing
A required next action
A completion timeframe
An escalation path
A record of previous attempts and outcomes

Without those elements, an incomplete account can become “out of sight, out of mind.” It may sit untouched until billing discovers the problem or a payer rejects or denies the claim.

By then, the organization may be trying to locate coverage information, obtain documentation, correct an authorization, or contact a patient weeks after the encounter. Staff must reconstruct what happened, patients may have difficulty remembering the details, and payer deadlines may already be approaching.

Every unresolved account should have an owner. I think of this as a no-orphan-account standard: no account should remain in the Revenue Cycle without a named owner, a next action, and a due date.

Prescheduled and emergency services need different workflows

Organizations should not apply the same financial-clearance workflow to every patient encounter.

For prescheduled services, there is often time to verify coverage, obtain authorization, review benefits, prepare an estimate, screen for assistance, and contact the patient before the date of service. The workflow should use that time intentionally.

Emergency care is different.

Emergency care cannot always wait for financial clearance, but financial-clearance responsibility does not disappear. The organization still needs a defined process for obtaining missing information, verifying coverage, addressing authorization or notification requirements, screening for assistance, and documenting what remains unresolved.

Most importantly, those activities cannot interfere with emergency care. The Emergency Medical Treatment and Labor Act prohibits hospitals from delaying an appropriate medical screening examination or stabilizing treatment to ask about payment or insurance. CMS: Know Your Rights—EMTALA

The emergency workflow should therefore define:

What information may be collected at arrival without delaying care
When registration and financial discussions may appropriately occur
Who follows up when information cannot be obtained during the encounter
Who submits required admission notifications
Who reviews failed or rejected notifications
How unresolved coverage and authorization issues are escalated
How patients are connected with financial assistance after stabilization or discharge

The objective is not to abandon the financial process. It is to complete it at the appropriate time without placing care at risk.

Standardize the work for unresolved accounts

When staff cannot obtain required information, the next step should not depend entirely on individual judgment.

Organizations should establish a standard unresolved-account process that defines:

How many outreach attempts are required
When those attempts should occur
Which communication methods may be used
What information employees should request
What information should be provided to the patient
Where attempts and outcomes must be documented
When the account should be escalated
Who receives the escalation
How quickly the receiving person must respond
When financial-assistance or coverage screening should begin

Patient conversations should also be supported by consistent, patient-friendly scripts. Employees need language that explains why information is being requested, what the patient may owe, where the estimate came from, and what assistance may be available.

For tax-exempt hospital facilities, federal requirements under Section 501(r) include maintaining and publicizing a written financial-assistance policy that explains eligibility and how patients may apply. The requirements also reinforce that financial-assistance processes must be implemented consistently, not simply documented in a policy. IRS: Financial Assistance and Emergency Medical Care Policies under Section 501(r)(4)

Financial assistance should not be treated as the last option after repeated collection attempts. When a patient may qualify, screening should begin as early as practical.

Moving an account is not the same as completing a handoff

An account can be moved from one workqueue to another without responsibility truly being transferred.

A complete handoff should tell the receiving department:

What has already been completed
What remains unresolved
What attempts have been made
What supporting documentation is available
What deadline or financial risk applies
What action is expected next
Who previously owned the work
Who owns it now
When further escalation is required

The receiving department must also have the access, information, capacity, and authority needed to act.

Ownership should remain with the sending department until the receiving department has the information, access, and authority needed to accept responsibility for the next action.

This is what makes the handoff closed-loop. The work is not considered transferred merely because someone routed the account. The receiving team must be able to see the history, understand the outstanding issue, and accept responsibility for the next action.

Leaders should apply this principle throughout the Revenue Cycle, not only between Patient Access and Patient Financial Services.

Clinical documentation, coding, and charge capture are part of the same cycle

An account may be fully registered and financially cleared but still remain unbillable.

Clinical documentation may be incomplete. An order may not support the service performed. A coding query may be awaiting a response. Charges may be missing. The documented level of care may not align with the claim. A medical-necessity concern may remain unresolved.

These are not separate clinical or coding problems. They are Revenue Cycle issues with clinical, compliance, financial, and patient consequences.

CMS notes that incomplete or insufficient medical records can result in payment denials when the documentation does not support the services performed, medical necessity, or the level of care billed. CMS: Complying with Medical Record Documentation Requirements

That is why a complete Revenue Cycle review should include:

Clinical documentation completion
Unsigned or incomplete orders
Medical-necessity issues
Utilization-management delays
Coding backlogs
Unanswered coding or clinical-documentation queries
Charge-capture delays
Late or missing charges
Claims held for documentation or coding
Services that do not match the authorization
Accounts that cannot meet the organization’s “ready to bill” definition

Just as “financially cleared” should have a consistent definition, “ready to bill” should mean the same thing to clinical departments, coding, billing, and leadership.

Feedback should lead to correction

Patient Financial Services should provide account-specific feedback when a correction is needed. It should also identify recurring trends that may indicate a larger problem.

However, sending the same report every month is not improvement.

Feedback should result in an action plan when the data shows a pattern. That action plan should identify:

The issue and its financial or operational impact
The root cause
The department or role responsible for correction
The actions that will be taken
The accountable owner
The completion deadline
The measure that will show whether the correction worked
The escalation path if the action is not completed

An action plan should not be closed simply because training occurred or a meeting was held. It should close only after the related KPI, aging, accuracy, or denial trend demonstrates sustained improvement.

Organizations should not wait until the next monthly meeting to address a high-risk account, a high-dollar claim, or an issue approaching a timely-filing deadline. Account-specific feedback must occur quickly enough for the organization to protect its ability to bill and collect.

A practical review cadence may include:

Immediate escalation for high-risk, high-dollar, patient-sensitive, or deadline-driven accounts
Biweekly cross-functional review of recurring trends, stalled accounts, missed handoffs, and departments not meeting key performance indicators
Monthly senior-leadership reporting on performance, root causes, unresolved barriers, corrective actions, and accountability

Senior leaders should receive at least a monthly report so they understand what is being discussed, where accounts are repeatedly becoming stalled, which performance gaps are continuing, and whether action plans are progressing.

Every senior-leadership report should answer six questions: Where is work becoming stalled? How many accounts and dollars are affected? What is the effect on patients or care delivery? What is the root cause? Who owns the corrective action? By what date should improvement be visible?

The process owner or designated operational leader should be responsible for identifying the owner of each corrective action, confirming that the person has the authority and resources to act, and documenting the due date and expected result. Reporting becomes valuable when it leads to a decision, an accountable next step, and confirmation that the correction produced a measurable result.

Review the entire Revenue Cycle scorecard

A cross-functional review should not focus only on front-end errors or back-end results.

It should include representatives from the functions affecting the account, such as:

Scheduling and preregistration
Registration
Eligibility and financial clearance
Authorization and utilization management
Clinical operations
Clinical documentation improvement
Coding
Charge capture
Billing and claims
Insurance follow-up
Denial and appeal management
Patient Financial Services
Financial counseling and assistance
Information technology
Managed care or payer relations, when appropriate

The team should review each area’s KPIs and goals, but it should also examine how performance in one area affects the next.

The scorecard should distinguish leading indicators from lagging outcomes. Preregistration completion, authorization turnaround, documentation timeliness, coding-query aging, and charge lag can reveal a problem before it becomes a denial or aged receivable. Denials, cash, write-offs, and patient complaints show the eventual result. Leaders need both views to intervene early and confirm whether the intervention worked.

A useful monthly report may include:

Preregistration completion
Financial-clearance completion
Eligibility and authorization denials
Authorization turnaround time
Point-of-service collections
Estimates completed before service
Financial-assistance screening
Missing or unsigned clinical documentation
Outstanding coding and documentation queries
Coding turnaround time and backlog
Charge lag and late charges
Medical-necessity and order issues
Clean-claim rate
Claim-edit volume and aging
Days from service to initial bill
Billing delays caused by missing information
Back-end rework
Denial volume, value, and root cause
Appeal turnaround and success
Accounts approaching timely-filing limits
High-risk or high-dollar stalled accounts
Patient billing calls and complaints
Open and overdue corrective-action plans

These measures should not be reviewed in isolation. A department may meet its volume goal while sending incomplete work to the next team. Coding may appear current while unanswered documentation queries remain outside its queue. Registration volume may be strong while eligibility denials rise. Billing productivity may look acceptable while clinical documentation holds continue to age.

Completion volume alone does not prove that the Revenue Cycle is moving effectively.

Measure time at every handoff

Organizations commonly measure final outcomes such as total days in accounts receivable, denial rates, or cash collections. Those measures are important, but they do not always show where the delay began.

Leaders should also measure how long accounts spend:

Waiting for patient information
Awaiting authorization
Pending clinical documentation
Waiting for an order or medical-necessity review
In a coding queue
Awaiting a query response
Held for late or missing charges
In claim edits
Awaiting payer follow-up
Pending an appeal
Waiting for a departmental escalation
Assigned to an action plan that has not been completed

Time-at-handoff measures help leaders locate the actual bottleneck. They can reveal that a billing delay attributed to Patient Financial Services began several weeks earlier in documentation, coding, or authorization.

They can also show whether a workflow change solved the problem or simply moved the backlog to another department.

Accountability should be specific without becoming punitive

The purpose of cross-functional reporting is not to create a list of “repeat offenders.” It is to distinguish among different types of problems so the organization can respond appropriately.

Recurring issues may result from:

An unclear workflow
Inadequate staffing or capacity
Competing responsibilities
Insufficient training
Missing system access
Poor system design
An ineffective handoff
A payer requirement
A clinical-documentation delay
A coding or charge-capture problem
An individual performance concern

Those causes require different responses.

If the workflow is unclear, redesign it. If the employee lacks access, correct the access. If staffing is insufficient, address capacity and prioritization. If training is incomplete, provide education and validation. If the payer is creating the barrier, involve managed care or payer relations.

When expectations, workflow, training, access, and workload have all been addressed and the same responsibility continues to be missed, leadership may need to manage an individual performance issue. That is different from assuming every recurring error is an employee problem.

Senior-leadership reporting should therefore identify recurring error sources, repeated performance gaps, and areas where accounts consistently become stalled. That language keeps attention on the work while still preserving accountability.

Include the patient’s experience in the review

The Revenue Cycle is not functioning well if internal KPIs improve while patients remain confused.

Leaders should examine whether patients are:

Being asked for the same information repeatedly
Receiving estimates early enough to make informed decisions
Getting consistent explanations of their responsibility
Being contacted by multiple departments about the same issue
Learning about financial assistance early enough to use it
Receiving delayed or inaccurate bills
Waiting for care because an authorization or documentation issue was not escalated
Calling because the organization’s internal handoffs were incomplete

A connected Revenue Cycle should reduce repeated contacts, improve the clarity of financial conversations, identify assistance earlier, and give patients confidence that the organization understands their account.

Three actions leaders can take now

1. Map the complete workflow and define ownership at every handoff

Follow the account from scheduling through final resolution. Define “financially cleared,” “ready to bill,” and “complete” at each stage. Require every unresolved account to have an owner, next action, due date, and escalation path.

2. Establish shared KPIs and a biweekly cross-functional review

Include Patient Access, clinical operations, utilization management, documentation, coding, charge capture, billing, follow-up, denials, and Patient Financial Services. Review both departmental performance and the time accounts spend waiting between departments.

3. Require corrective-action plans and monthly senior-leadership oversight

Recurring performance gaps should have a documented root cause, accountable owner, correction deadline, and success measure. Senior leaders should see which actions are complete, which are overdue, where barriers remain, and where additional authority or resources are required.

One patient, one account, one Revenue Cycle

The strongest Revenue Cycle organizations do not allow departmental boundaries to become stopping points.

They understand that an eligibility issue affects billing, a documentation delay affects coding, a coding backlog affects claims, a claim delay affects cash, and an inaccurate bill affects the patient’s trust in the entire organization.

Every department must own its work, but it must also understand the work that comes before and after it.

That requires clear definitions, closed-loop handoffs, shared measures, timely feedback, practical escalation, and leadership accountability.

The principle is straightforward:

One patient, one account, one Revenue Cycle—and no unresolved work without a clear owner.