← Knowledge library

Executive analytics

Read the Revenue Cycle dashboard without confusing revenue and cash

Use financial totals, readiness and the episode worklist to direct operational attention.

Current source · source reviewed · 6 min read

Before you begin

1. Start with the displayed measures

Review Gross charges, Claims generated, Payments posted and Open denials. These describe different stages of financial work; do not treat them as interchangeable revenue or bank totals.

The illustrated figures are seeded operational examples. Payments posted does not itself prove bank credit; use the advice and cash ledgers for that distinction.

Forty seeded synthetic revenue scenarios show claims, posted-payment figures and open denials with readiness blockers; posted amounts do not establish bank cash.
Read the populated synthetic revenue dashboard · 2026-10-18. Current audited MANSOQ application in an isolated local synthetic training environment. Forty seeded synthetic revenue scenarios show claims, posted-payment figures and open denials with readiness blockers; posted amounts do not establish bank cash.

2. Inspect throughput and queue counts

Read Ready to claim, NPHIES queued and the Front/Middle/Back Office stage cards. A growing queue calls for an owner and drill-down into its cause.

3. Open the Episode worklist

Inspect patient/account, stage, readiness, revenue and exception columns. Select an episode to read the actual blockers and financial evidence behind a summarized readiness percentage.

The seeded E40 episode has legacy actions and unresolved canonical prerequisites; verify member coverage, charging and readiness before claim construction.
Inspect episode prerequisites before building a claim · 2026-10-18. Current audited MANSOQ application in an isolated local synthetic training environment. The seeded E40 episode has legacy actions and unresolved canonical prerequisites; verify member coverage, charging and readiness before claim construction.
The synthetic E40 claim has distinct encounter and claim identities, no local invoice, unstated ledger columns and missing terminology release evidence.
Separate claim, encounter, invoice and coding facts · 2026-10-18. Current audited MANSOQ application in an isolated local synthetic training environment. The synthetic E40 claim has distinct encounter and claim identities, no local invoice, unstated ledger columns and missing terminology release evidence.

4. Separate decisions from recovery

Use denial aging, suspense, certificate expiry and external acceptance indicators alongside totals. Prioritize unresolved operational conditions rather than assuming a higher claim total means more cash.

Drill-down is essential

The dashboard source renders default zeros when data has not loaded. Confirm data availability and period before interpreting a zero as verified business performance.

Targets need a basis

The reporting engine does not hard-code a national clean-claim, first-pass or cost-to-collect benchmark. Use a recorded local target with its cohort, denominator and sample limits.

What the current screenshots demonstrate

These are current captures from an isolated Polyclinic training environment, using explicitly fictional insurance, response, authorization, remittance and policy fixtures. They demonstrate the displayed controls and scoped observations only. They do not establish live payer connectivity, a genuine insurer approval, regulatory qualification, production tax filing, a complete role/facility matrix or a cleared financial estimate.

Troubleshooting

The headline and an episode appear inconsistent

Compare facility scope, refresh state, period, stage and source records. Verify actual cash through the canonical settlement ledger before escalating a payment discrepancy.

Source evidence

References are pinned to the private MANSOQ source repository. Repository access is required to open these links.