The Revenue Cycle: Registration to Remittance
Duration: 50 min · Level: Intermediate · Module: 7. Revenue Cycle & Coding Basics · Focus: revenue-cycle, claims, billing, A/R, denial-management
Healthcare is unusual among industries: the moment a service is delivered, the bill is not done — it is barely begun. A single visit triggers a long administrative chain that can stretch for weeks before a dollar arrives. That chain is the revenue cycle: the combined administrative and clinical process by which providers track a patient's care episode from registration all the way through final payment. When it breaks, the cost is enormous — US hospitals lose billions every year to claims that are denied, underpaid, or never collected. As a CEHRS specialist you do not run the whole cycle, but you touch it at multiple points, and the exam expects you to know its shape, its vocabulary, and where good documentation prevents money from leaking out.
The cycle, step by step
Memorize the cycle as an ordered chain, because the order is the point — each step depends on the one before it:
pre-registration → registration → charge capture → medical coding → claim submission → payment posting → denial management → accounts receivable follow-up → patient billing.
A useful memory hook is to split that chain in half. The first half (registration, charge capture, coding, submission) is about getting a clean claim out the door correctly the first time. The second half (payment posting, denial management, A/R follow-up, patient billing) is about chasing the money once the claim is in the payer's hands. The earlier in the chain a problem is caught, the cheaper it is to fix — which leads directly to the next distinction.
Front-end versus back-end: prevention beats correction
The single most testable idea in this lesson is the split between front-end and back-end work.
- Front-end revenue cycle is registration, eligibility verification, and prior authorization. Its job is to prevent denials before they happen — confirming the patient's coverage is active and the service is authorized before anyone provides care.
- Back-end revenue cycle is coding, billing, and denial management. Its job is to correct problems after the fact — reworking a claim that came back denied, appealing, resubmitting.
The exam's framing is blunt and worth internalizing: front-end prevention is far cheaper than back-end correction. A denial caught at registration costs a phone call; the same denial caught after submission costs a coder's time, a biller's time, an appeal, and delayed cash. This is exactly why a CEHRS specialist's attention to registration data quality has outsized financial value.
The three metrics you must know
Revenue cycle health is measured, and three numbers come up repeatedly. Learn each with its target:
- Days in A/R — the average number of days it takes to collect after billing. Target: under 50 days. Rising days-in-A/R means cash is getting stuck somewhere in the chase-the-money half of the cycle.
- Clean claim rate — the percentage of claims that need no correction before the payer accepts them. Target: above 95%. A low clean claim rate points to front-end and coding problems.
- Denial rate — the percentage of claims denied on first submission. Target: under 5%.
A simple way to keep them straight: clean claim rate and denial rate are roughly two sides of the same coin (claims that go through clean versus claims that bounce), while days-in-A/R measures speed rather than accuracy.
Charge capture and the payers behind the claim
Two more concepts round out the picture. Charge capture is the process of documenting every billable service that was provided so it can be billed. The principle is that EHR documentation must support every charge — and the failure modes cut both ways. Under-capture (services delivered but never billed) is straightforward revenue leakage. Over-capture (billing for more than was documented or done) is not just an error; it is a compliance risk that can rise to fraud. The defensible position is always the same: the documentation supports the charge, no more and no less.
Finally, know who is paying, because their rules differ. Medicare is the federal payer, with strict documentation requirements and comparatively lower reimbursement rates. Commercial payers — Blue Cross, Aetna, UnitedHealth and the like — negotiate their rates through contracts, so reimbursement varies by agreement. Medicaid is the joint state-federal payer covering low-income patients. The CEHRS role across all of this is consistent: ensure documentation is complete enough to support coding, process prior authorizations, keep registration data clean, and help route documentation-improvement (CDI) queries when the record does not yet support the code.
Putting it into practice
Turn the cycle into something you can reconstruct under exam pressure.
- Write the nine cycle steps in order on one line, then draw a vertical bar between "claim submission" and "payment posting" — left of the bar is get-the-claim-out-right, right of the bar is chase-the-money.
- Above the first three steps, label them front-end (prevents denials); above coding/billing/denials, label them back-end (corrects denials). Add the reminder: front-end is cheaper.
- To the side, list the three metrics with their targets: Days in A/R < 50, clean claim rate > 95%, denial rate < 5%.
- Self-test: cover the page and rebuild the chain, then explain in one sentence why a registration error is more expensive than it looks. If you can do both, you own the structural questions in Domain 5.
Key takeaways
- The revenue cycle runs in a fixed order: pre-registration → registration → charge capture → coding → claim submission → payment posting → denial management → A/R follow-up → patient billing.
- Front-end work (registration, eligibility, authorization) prevents denials; back-end work (coding, billing, denials) corrects them — and prevention is far cheaper than correction.
- Three metrics to memorize with targets: Days in A/R (< 50 days), clean claim rate (> 95%), denial rate (< 5%).
- Charge capture must be supported by EHR documentation: under-capture is lost revenue, over-capture is a compliance/fraud risk.
- Know your payers: Medicare (federal, strict rules, lower rates), commercial (contract-negotiated rates), Medicaid (joint state-federal for low-income patients).
- The CEHRS contribution is documentation completeness, authorization processing, registration data quality, and routing CDI queries.
Next: C7.2 ICD-10-CM: Structure, Guidelines & High-Yield Codes →
Part of Module 7: Revenue Cycle & Coding Basics.