←Module 1
Lesson · 20 min

The Revenue Cycle and Where Money Is Lost

Follow the money through a medical practice, and learn where revenue actually leaks — usually far earlier in the process than people expect.

By the end of this lesson you can

  • Define the revenue cycle and its front-end, middle, and back-end phases
  • Explain what a clean claim is and why the first-pass rate matters
  • Interpret days in accounts receivable as a measure of practice health
  • Identify the front-end failures that cause the majority of back-end denials
📘 Reading Lesson

Lesson Notes

Read through the key concepts before you try the challenge.

Revenue cycle management

On the job

You review last quarter's numbers at Lakeside Medical Associates.

The practice billed $840,000 and collected $611,000. The gap is not one large problem. It is roughly nine hundred small ones: claims denied for eligibility, claims paid at a lower rate than expected, patient balances never collected, and a stack of claims that quietly aged past the filing deadline and can no longer be submitted at all.

Your task: Learn to see the revenue cycle as a system with measurable leak points, rather than as a pile of individual claims.

Revenue cycle management is the discipline of running that whole pipeline as a system. The important insight — and it is genuinely counter-intuitive when you start — is that most revenue is lost at the front end, but the loss only becomes visible at the back end, weeks later, when a denial arrives.

PhaseCoversTypical failure
Front endScheduling, registration, eligibility, authorization, point-of-service collectionWrong or expired insurance captured; authorization never obtained
MiddleClinical documentation, coding, charge captureA service delivered but never charged; documentation that does not support the code
Back endClaim submission, payment posting, denials, appeals, patient collectionsClaims not worked before the filing deadline; denials written off instead of appealed
The three phases

The measures that tell you the truth

A practice's billing health can be read from a handful of numbers. Learning to interpret them is what separates someone who processes claims from someone who can tell a practice manager what is actually wrong.

MetricWhat it measuresWhat good looks like
Clean claim rateShare of claims accepted on first submission with no editsCommonly targeted at 95% or better
First-pass resolution rateShare of claims paid on the first submissionHigher is better; a low rate points to front-end or coding problems
Days in A/RAverage days from service to paymentOften targeted under 40 days for a physician practice
A/R over 90 daysShare of receivables aged past 90 daysCommonly targeted under 15-20%; older debt is much harder to collect
Denial rateShare of claims deniedFrequently targeted under 5-10%
Net collection rateShare of collectible revenue actually collectedOften targeted at 95% or better
Core revenue cycle metrics
These benchmarks vary by specialty, payer mix, and who is publishing them, so treat them as orientation rather than as fixed standards. What matters more than hitting any specific number is the trend: a denial rate climbing from 6% to 11% over two quarters is a problem worth investigating regardless of what the industry average happens to be.
Worked example

Reading a denial report

Last month Lakeside submitted 1,200 claims. 138 were denied. Sorted by reason: 61 eligibility or coverage, 29 missing prior authorization, 22 missing or invalid information, 14 non-covered service, 12 coding errors. Where is the actual problem?

  1. 1

    Calculate the denial rate: 138 of 1,200 is 11.5%.

    The rate frames the size of the problem before you look at causes. At 11.5%, roughly one claim in nine is failing — well above where most practices want to be, and enough to explain a meaningful revenue gap on its own.

  2. 2

    Group the reasons by which phase of the cycle owns them.

    Eligibility, authorization, and missing information are all front-end failures. That is 112 of 138 denials — over 80% — originating before the patient was ever seen. Only 12 are coding errors.

  3. 3

    Resist the instinct to retrain the coders.

    Coding is the smallest category here, and it is where people usually look first because it is the most visible. The data says the leverage is at registration and authorization. Fixing the right 20% of the problem while ignoring the 80% is a common and expensive mistake.

  4. 4

    Convert the finding into a specific front-desk change.

    Verifying eligibility electronically at scheduling and again at check-in addresses the largest single category. A recommendation naming the step, the owner, and the expected effect is actionable; 'we should reduce denials' is not.

Result: A recommendation to add a two-point eligibility check at the front desk, targeting the 61 eligibility denials and a share of the 29 authorization denials.

Denials surface at the back end and originate at the front end. Always group denial reasons by the phase that caused them before deciding what to fix.

Check your understanding

A practice has a denial rate of 12%, and most denials cite eligibility or missing authorization. Where should improvement effort be focused?

Challenge

Apply what you've learned in this lesson.

Practice reading the numbers rather than the individual claims.

  1. A practice submits 800 claims in a month. 736 are accepted on first submission. Calculate the clean claim rate and state whether it meets a 95% target.
  2. Total A/R is $412,000, of which $94,000 is over 90 days old. Calculate the percentage over 90 days and say whether it falls inside a 15-20% target range.
  3. Denials for the month: 34 eligibility, 18 authorization, 11 duplicate claim, 9 coding, 6 non-covered. Group them by revenue cycle phase and state which phase owns the largest share.
  4. Write a three-sentence recommendation to the practice manager naming the single change you would make first, the denial categories it would affect, and how you would measure whether it worked.

Finished this lesson?

Progress is saved in this browser only. It is not a grade — official progress lives in Brightspace.