What Is Revenue Cycle Management in Healthcare? Follow One Claim From Visit to Payment

A patient arrives for an outpatient diagnostic test. The hospital performs the test, the clinician documents it, and the patient goes home. The visit is over, but the work of getting paid started before the patient arrived. It continues until the hospital reconciles the insurer's payment and resolves any remaining balance.

Revenue cycle management (RCM) is how healthcare organizations manage the financial and administrative work tied to delivering care. It includes verifying coverage, obtaining prior authorization when required, documenting and coding services, submitting claims, posting payments, and following up on denials or unpaid balances.

Following one claim shows where these tasks intersect and how a small gap at one handoff can create rework for several teams.

One diagnostic claim, from scheduling to payment

In this fictional example, a hospital performs and bills for an outpatient diagnostic test. The patient's health plan requires prior authorization for this service. The dollar amounts illustrate how payment and adjustments are recorded.

1. Patient access verifies coverage

Before the appointment, the patient access team confirms the patient's insurance details, checks whether coverage is active, and reviews the benefits for the planned service. The team also checks whether this plan requires authorization for the test at the scheduled location.

The handoff: Patient access sends the order and relevant plan details to the authorization team.

2. The authorization team secures approval

The authorization team gathers the required clinical documentation, submits the request, and records the approval and its reference number. The hospital performs the test as scheduled. The payer will still evaluate the submitted claim before deciding how much to pay.

The handoff: The approval record needs to be available to the billing team preparing the claim.

3. The clinical and coding teams document what happened

The clinical team records the service performed and the information supporting the order. The coding team reviews the record, assigns the applicable diagnosis and procedure codes, and confirms that the charges reflect the documented service.

The handoff: Coding passes the completed record to billing so the team can assemble and review the claim.

4. Billing catches a gap before submission

During claim review, the billing team sees that the authorization reference is missing from the claim record. The approval exists, but it was stored separately and never linked to the encounter. Billing asks the authorization team to confirm that the approval matches the service, date, and location. The team links the record and completes the claim before sending it to the payer.

This is where a targeted review can save work. The reviewer has a specific issue to resolve, knows who owns the source information, and can act before the payer receives the claim.

5. The payer processes the claim

The payer reviews the claim and sends a remittance advice explaining its payment and adjustments. The payment posting team uses that information to reconcile the account. The table below shows how the hospital records this claim. For more on how remittance advice works, see the CMS guide to payment and remittance advice.

6. Patient financial services resolves the balance

The hospital posts the $320 payer payment and the $200 contractual adjustment. Patient financial services issues a statement for the $80 patient responsibility. In this example, the patient pays that amount, and the account closes.

If the payer had denied the claim, the follow-up team would review the reason on the remittance advice and determine whether the next step was a correction, additional documentation, or an appeal. For example, if billing had not caught the missing authorization reference, the payer could have denied the claim for lack of authorization even though an approval existed. The team would then have to locate the approval, correct and resubmit the claim or file an appeal, and wait longer for payment. That finding can also help the hospital identify where to improve the upstream workflow.

RCM stages and metrics to track

Most organizations group revenue cycle work into three stages. The front end covers scheduling, registration, eligibility verification, and prior authorization (steps 1 and 2 above). The mid-cycle covers clinical documentation, charge capture, and coding (step 3). The back end covers claim submission, payment posting, denial management, and patient billing (steps 4 through 6).

To see where revenue is delayed or lost, teams commonly track a few core metrics: clean claim rate (the share of claims accepted on first submission), denial rate, days in accounts receivable (how long it takes to collect payment), and net collection rate (the share of collectible revenue actually collected).

What hospital, diagnostic, and life sciences leaders can learn from one claim

Hospital leaders can look for recurring failures at the handoffs between patient access, clinical teams, coding, and billing. If authorization references regularly go missing, review how approvals are recorded and transferred before adding more manual claim checks.

Diagnostic company and laboratory leaders can use the same approach to examine the order-to-payment workflow. Look at whether the ordering provider supplies the required information, whether payer requirements are checked for the specific test, and whether the organization responsible for billing receives what it needs.

Life sciences leaders working with diagnostic or provider partners can use the same workflow to pinpoint where patient access to a test breaks down. Are orders delayed because documentation is incomplete? Are tests performed but claims held for review? Each problem sits at a different stage of the cycle and calls for a different fix.

Where AI can support revenue cycle management

AI is most useful when it targets a specific, recurring failure point rather than the whole revenue cycle at once. In the example above, an AI-assisted pre-submission review could compare the claim against authorization records, flag the missing reference, and route it to the authorization team before the claim reaches the payer. Similar checks can compare assigned codes against clinical documentation, confirm payer requirements for a specific test, and estimate expected reimbursement before submission.

To get started, choose one recurring problem your team can measure, such as claims held for missing authorization references. Track how often the issue occurs, how long it takes to resolve, and how many flagged claims are corrected before submission.

OptraHEALTH's Revenue Intelligence solution supports pre-submission denial risk review, prior authorization, coding review, and reimbursement estimation. A product discussion can focus on the workflow where your team sees the most rework and the information reviewers need to act.