The denominator comes from completed professional activity

I would agree on one provider group, specialty, and service period before expanding the review. For an ambulatory workflow, the source might be a completed encounter and its documentation. For inpatient professional charging, the source might be chargeable notes or another agreed service record. A scheduled appointment alone is not sufficient evidence that a professional service occurred.

The professional billing and clinical owners need to define which events are expected to produce charges. Canceled visits, nonbillable contacts, duplicate notes, and services provided outside the organization's billing responsibility need explicit treatment. One provider can document several times during an encounter without creating a separate billable service for every note.

For note-based charging, I would examine the note author and relevant cosigning information with the clinical and billing teams. I would not infer chargeability from the logged-in user or department alone. The rule needs to reflect the service and the organization's approved charging responsibilities.

The data request should connect the service to its outcome

I would request completed encounters or qualifying notes, provider attribution, departments, service dates, charge transactions, corrections, and the charging method expected for each population. I would ask for encounter status changes and documentation timing so we can distinguish an omission from a service that has not yet reached the agreed charging point.

For Epic, I would review the relevant note-chargeability or encounter selection rules, charge capture workflow, Charge Router configuration where used, and PB charge review rules. A CER extract is helpful only when it includes the applicable context and the build that calls each rule. I would retain the relationship between the source event, charge session, and PB transaction.

I would ask the reviewers to assign a reason to each unmatched service. Examples include no charge generated, incomplete documentation, charge awaiting review, legitimate exclusion, or reconciliation mismatch. These distinctions create an action list rather than an inflated estimate of missing revenue.

The handoff can fail before charge review begins

I would walk through the normal workflow with a provider or department representative and the application team. The key question is which action is supposed to initiate charging and how the organization confirms that action occurred. A signed note, closed encounter, or selected service does not have the same charging effect in every local build.

Then I would trace an affected example through the actual configuration. If the event never qualified for charging, I would inspect the selection criteria. If a charge exists upstream, I would investigate processing or review. If the charge posted elsewhere, I would resolve the matching or attribution problem before suggesting new charge entry.

Revenue Guardian Notes or encounter-based review may be useful when the local workflow supports them. I would validate the expected note-to-charge combinations with coding and clinical owners. These controls should identify exceptions that warrant investigation, while the underlying charging workflow remains responsible for generating appropriate charges.

A sustainable control needs clear resolution reasons

I would give the department a reconciled exception list and a defined action for each type of finding. The list should show the source event, expected charge outcome, elapsed time, and next responsible team. Reviewers need a way to document why an event is legitimately excluded and prevent the same event from returning indefinitely.

Acceptance testing would include a completed billable encounter, a canceled visit, a corrected note, a nonbillable service, a late charge, and a service that produces several appropriate charge lines. I would also test a provider or department boundary so the rule does not quietly expand to services the organization should not bill.

For confirmed gaps, the recovery process should verify documentation and applicable billing requirements before adding charges. I would reconcile additions and reversals to the original exception population and confirm whether the correction still needs coding or billing review. Closing the exception is not the same as submitting a clean claim.

The financial claim needs to follow the corrected service

I would measure the percentage of qualifying completed services without their expected charge outcome after the agreed processing interval. The denominator should exclude legitimate nonbillable events, and the report should show exclusions separately. A high exception rate caused by poor matching should not be presented as a revenue loss rate.

I would track charge lag, repeat omissions by workflow, confirmed defects per reviewed exception, and the time needed to resolve them. A control that catches more defects but consumes disproportionate reviewer effort may need better criteria or a correction to the source workflow.

For financial benefit, I would follow corrected services to incremental collectible reimbursement and subsequent payment where feasible. Added charge dollars are an inventory measure, not collections. The completed review should show both whether the service population is more complete and whether the prevention action reduces the next month's missing-charge work.