Healthcare revenue integrity gets attention when something has already gone wrong: a payer audit, a run of denials for one department, or a chargemaster line that has billed the wrong code for a year. By then the fix is expensive, because money has to be found, refunded or rebilled.
This guide treats revenue integrity as an engineering and operations problem. It covers what the function owns, how the chargemaster and charge capture fail, which audits to run, what the overpayment rule requires once a problem is found, and the data a hospital or group needs to run the program without spreadsheets passed around by email.
What is healthcare revenue integrity?
Building revenue integrity tooling?
Agnotic builds charge reconciliation, chargemaster workflows and audit worklists for hospitals and medical groups.
Healthcare revenue integrity is the work of making sure every charge a provider bills is captured, coded, priced and documented correctly before the claim leaves. It sits between clinical departments, the chargemaster, coding and compliance, and it aims for accurate payment: no missed charges, no unsupported ones, and an audit trail that explains each line.
Accuracy runs in both directions. A revenue integrity team that only hunts for missed charges becomes a revenue enhancement project, and one that only looks for overbilling becomes a compliance function with no budget. The useful version does both and treats every finding as a process defect to fix at the source.
How does revenue integrity differ from billing and coding?
Billing and coding produce claims; revenue integrity checks that the system producing them is sound. Coders assign codes to individual encounters, while revenue integrity asks why a whole category of encounters keeps needing correction.
- Patient access: Owns registration, eligibility and authorizations. Revenue integrity cares when wrong financial class data drives wrong pricing.
- Health information management and coding: Owns code assignment from documentation. Revenue integrity reviews coding patterns, not single charts.
- Patient financial services: Owns claim submission, follow-up and posting. Revenue integrity uses its denial data to find upstream causes.
- Revenue integrity: Owns the chargemaster, charge capture rules, charge reconciliation and the audit plan, and coordinates fixes with clinical departments.
- Compliance: Owns policy, investigations and reporting. Revenue integrity feeds it findings and evidence.
Reporting lines vary. Some hospitals put revenue integrity under the revenue cycle leader and others under compliance. What matters for software is that the function needs read access to clinical orders, charges, claims and remittances, which usually live in different systems.
What does a chargemaster need to stay accurate?
A chargemaster, or charge description master (CDM), needs an owner, a change process and version history. Every billable item a hospital provides has a line, and each line is reused thousands of times, so one wrong field repeats on every claim that touches it.
- Charge code and description: The internal identifier and a description clinicians and auditors both understand.
- Revenue code: The UB-04 revenue code that groups the line on institutional claims.
- CPT or HCPCS code and modifiers: Present where the payer expects a procedure code, blank or hard-coded only by deliberate decision.
- Price: The gross charge, set by pricing policy rather than by whoever created the line.
- Department and cost center: Where the charge originates and where its cost sits.
- Effective and inactive dates: So a retired code stops billing on the right date and old claims can still be rebilled correctly.
The CDM is also public now. Under 45 CFR 180.50, a hospital must publish a machine-readable file of its standard charges, including gross charges, discounted cash prices and payer-specific negotiated charges, with the codes used for billing such as CPT, HCPCS, DRG, NDC and revenue center codes, and must update it at least once a year.
The same section requires, from January 1, 2026, an attestation in the file that the information is true, accurate and complete, along with the name of a senior official designated to oversee that encoding. A chargemaster error is therefore no longer only a billing problem: it can show up in a file regulators and the public read.
Where does charge capture break down?
Charge capture breaks down where clinical work and billing are linked by a manual step or a fragile interface. Most missed or duplicate charges trace back to a handful of repeat patterns.
- Orders without charge triggers: A procedure is documented but its order type was never mapped to a CDM line, so nothing drops.
- Supplies and implants: Items used in the operating room or cath lab are not scanned, or are scanned against the wrong case.
- Time-based services: Infusion, observation and anesthesia charges depend on start and stop times that are missing or out of order.
- Interface errors: Charges from ancillary systems such as lab, pharmacy or radiology fail at the interface and sit in an error queue nobody watches.
- Late charges: Charges posted after the claim has gone out require a corrected claim, or are written off.
- Duplicates: A charge is posted by the department and again by a nurse or coder trying to be helpful.
The control for all of these is reconciliation: comparing what clinical systems say happened with what billing says was charged, by department and day. A daily report showing scheduled cases with no charges, or charges with no matching order, catches most problems while the encounter is still open.
Which audits should a revenue integrity program run?
A revenue integrity program should run audits chosen from a risk assessment, not a fixed calendar of the same reviews every year. The HHS Office of Inspector General's General Compliance Program Guidance, published in November 2023, recommends a compliance risk assessment at least annually and an audit schedule built from the risks it identifies.
The same guidance says claims reviews and audits should include a review of medical necessity by an appropriately credentialed clinician, because Medicare pays only for items and services that are reasonable and necessary. An audit that only checks codes against documentation can pass a claim that should never have been billed.
- CDM review: Lines with missing or deleted codes, revenue code mismatches, prices outside policy and lines unused for a year.
- Charge reconciliation audit: A sample of encounters traced from order to charge to claim line.
- Coding accuracy: A sample of coded encounters reviewed by a second coder, with error rates tracked by coder and service line.
- Medical necessity: Clinician review of high-risk services, such as those with frequent payer denials.
- Denial root cause: Denials grouped by cause code and department, with the upstream fix recorded.
- Price transparency file: The published file checked against the live CDM and payer contracts.
Each audit needs a written sample method, a finding format and an owner for each fix. Without the last item, the same finding returns in the next cycle.
What happens when an audit finds an overpayment?
When an audit finds a Medicare overpayment, the clock starts. Under 42 CFR 401.305, a provider must report and return an identified overpayment by the later of 60 days after identification or the date a related cost report is due.
The regulation suspends that deadline while the provider runs a timely, good-faith investigation into related overpayments from the same cause, for up to 180 days after the first overpayment was identified. It also sets a six-year lookback: an overpayment identified within six years of receipt must be reported and returned.
Three things follow for systems. The program needs a dated record of when each potential overpayment was first identified, a way to pull every claim affected by the same root cause across six years, and a record of the refund or claim adjustment. If the audit used statistical sampling and extrapolation, the regulation requires describing that method in the report, so the sampling plan has to be saved with the finding.
What data does a revenue integrity team need?
A revenue integrity team needs orders, charges, claims and remittances joined at the encounter and line level, refreshed daily. Most teams start with exports into spreadsheets, which works for one audit and fails as a program.
- Charge lag: Days from service to charge posting, by department, with outliers flagged.
- Order-to-charge match: Orders and documented procedures with no charge, and charges with no order.
- CDM history: Every change to every line, with who changed it, why and when it took effect.
- Rules engine: Department-specific checks, such as an infusion charge requiring start and stop times, run before the claim is built.
- Worklists: Findings routed to the department that can fix them, with due dates and status.
- Denial feed: Claim adjustment reason codes from the 835 remittance linked back to charge lines.
The build order that tends to work is reconciliation first, then the CDM change workflow, then worklists, and only then dashboards. Dashboards built before the joins are trusted get ignored the first time a department disputes a number.
How do you know the program is working?
You know a revenue integrity program is working when the same findings stop coming back. Totals recovered are easy to report but reward finding problems rather than preventing them, so pair them with measures of recurrence and speed.
- Repeat findings: The share of audit findings in a cycle that match a cause already found in an earlier cycle.
- Time to fix: Days from a finding to the change in the CDM, rule or workflow that prevents it.
- Charge lag trend: Whether late charges fall for departments that received fixes.
- Corrected claims: Volume of corrected or late-charge claims, by cause.
- Underpayments and refunds together: Both directions reported side by side, so the program is not judged on recoveries alone.
Set baselines from your own data before the first fixes go in. Industry benchmarks rarely match a hospital's service mix, and a target nobody can trace to local numbers gets argued away in the first review meeting.
How Agnotic can help
Agnotic Technologies builds revenue integrity tooling for hospitals and medical groups: charge reconciliation between clinical systems and billing, chargemaster change workflows with version history, rules that stop incomplete charges before the claim is built, and audit worklists that track each finding to a fix.
Agnotic also builds the data layer underneath, joining orders, charges, claims and 835 remittances so audits, overpayment lookbacks and price transparency checks draw on the same trusted records.
Turn audit findings into fixed processes
See how we build RCM software, or read more revenue cycle articles from our engineers.
Related reading on Agnotic
Go further with revenue cycle management, EMR coding, coding automation and payer contract management.
