Why a discharged episode can remain unbilled
A discharge date is one milestone. Coding completion, charge evidence and bill release may follow in separate systems with different owners. A useful daily review starts with a source-verified episode alias, the setting, four milestone dates, the current blocker and a named next action. Avoid patient identifiers in an exported worklist.
Define the event before counting delays
Choose the eligible discharge population and reporting cutoff. Keep the same calendar-day convention for every row. If a date is missing or out of sequence, treat that as a source review item. A pending code or charge should remain visibly pending instead of being represented as an implied claim or dollar recovery.
Work the exception
- Confirm the discharge and downstream milestone dates in their source systems.
- Describe one blocker in plain language and identify the accountable role.
- Assign the next internal action and due date; revisit open rows in a consistent cadence.
- Close only after the source evidence and bill-release state are confirmed.
Compare unresolved counts and elapsed days across like periods after checking the underlying population. The worklist supports operational review; it does not decide coding, payer deadlines, or billing compliance.
See the Hospital Discharge-to-Bill Excel Control and actual fictional workbook preview. For a separate ambulatory count gap, view the Physician Encounter-to-Charge Control.