RCM Insights: Saved
Objective. Reuse a saved question while remembering its scope and filters are frozen, so a re-run answers the saved question and not a slightly different one you have in mind today.
Saved is where useful questions and analyses are kept for reuse rather than re-derived each time. It answers 'which analyses are worth running again', with the discipline that a saved question carries its own frozen scope even as the data refreshes.
See it in the demo
What this screen answers
Saved answers the reuse question: of all the questions users have asked, which are worth keeping and re-running for real decisions, rather than one-off novelty queries? A Sales person uses it to show that value compounds - good questions become standing analyses; a CSM uses it to curate the handful of genuinely useful saved analyses an account relies on and to teach users which to re-run and when.
The task
Browse the saved questions, pick one that maps to a current decision, and re-run it. Before trusting the result, confirm the saved scope and filters still match the question you actually have today, and check the evidence and freshness as you would for a new answer. The task is select, re-run, confirm the scope still fits, inspect evidence - at that level, without inventing save or edit-control names.
How to read it
The classic misread is assuming a saved question answers whatever you have in mind now. A saved question re-runs with its saved scope and filters frozen - the data refreshes, but the scope does not. So a re-run answers the saved question on current data, which may be subtly different from the slightly changed question in your head today. Read the saved scope before trusting the re-run, and if your question has shifted, adjust the scope rather than reading the old one as if it fits. Reuse is powerful only when the saved scope still matches the decision.
Honest limits
This screen proves saved, re-runnable analyses on seeded data. It does not prove the saved scope matches a customer's live question today, nor that the underlying data is fresh. Confirm sources, freshness and that the saved scope still fits the decision with product and the customer before relying on a re-run. A saved analysis is a head start, not a standing guarantee.
Interpretation check
A saved question re-runs with its scope and filters frozen - the data refreshes but the scope does not. A re-run answers the saved question, which may differ from the slightly changed question you have today; read the saved scope before trusting it.
Practical task
On the demo Saved screen, pick one saved analysis, re-run it, and write a short note: the saved scope and filters, whether they still fit a current decision, and one adjustment you would make if the question had shifted - plus a line confirming you checked freshness.
Self-check
A user re-runs a saved 'top denial payers' question for this month's review. What must they check?
That the saved scope and filters still match the question they actually have today, and that the data is fresh. The scope is frozen even though the data refreshes.
Why is Saved more than a convenience?
It makes value compound - good, decision-linked questions become standing analyses reused for real decisions rather than re-derived, which is the healthy adoption pattern versus one-off novelty queries.
A re-run gives an odd result. Before assuming the data changed, what is one likely cause?
The saved scope no longer fits the current question - the frozen filters may exclude or include something the user now cares about. Read the scope before concluding the data moved.
What should a CSM confirm before an account relies on a saved analysis?
The sources and freshness, and that the saved scope still matches the decision - confirmed with product and the customer - so a re-run stays defensible.
Verified vs demo. Screen is live in the demo at /#/saved; saved, re-runnable analyses are demo-shown on seeded data, and exact controls, save logic and figures are SME-validation-pending. Live sources, freshness and whether a saved scope fits are production-dependent - confirm with product.