RCM Insights: Admin
Objective. Understand how Admin and role scope shape what an answer can see, so a figure is read in light of the asking user's scope rather than as a complete, universal result.
Admin governs who can see what - the role-scoping that controls which data an answer draws on. It answers 'is this answer complete for the person asking', with the discipline that an answer's completeness depends on the asking user's role scope.
See it in the demo
What this screen answers
Admin answers the governance and scope question: who can ask what, and which data does a given role's answers draw on? In an RCM provider serving many clients, role-scoping is what keeps one client's data out of another's answers. A Sales person uses it to show that governance is built in, not bolted on; a CSM uses it to validate the account's roles and scopes so that users get complete answers for their remit and no more.
The task
Review how roles map to data scope for the account - which clients, payers and areas each role can see. When an answer looks surprisingly low or incomplete, check whether the asking user's role scope explains it before assuming the data is wrong. The task is review role-to-scope mapping, then read answers in light of the asker's scope - at that level, without inventing specific admin-control names, and escalating advanced setup to a specialist.
How to read it
The classic misread is treating any answer as a complete, universal result regardless of who asked. What an answer can see is role-scoped - a figure returned under a limited role may legitimately differ from the same question asked under a broader one, because they draw on different data. So read a figure in light of the asking user's scope, and when two users get different answers, check their roles before suspecting a data error. Admin governs scope and access; it does not change what a metric means - that is the Metrics view's job.
Honest limits
This screen proves role-scoped access and governance on seeded data. It does not prove the customer's actual role model, client-data segregation or entitlement. Confirm the live role-scoping, data segregation and access model with product before relying on it for a customer - this is governance and is customer-specific and entitlement-dependent. Advanced configuration is a specialist escalation, not a demo claim.
Interpretation check
An answer's completeness depends on the asking user's role scope - a figure under a limited role can legitimately differ from the same question under a broader one. Read a number in light of the asker's scope; Admin governs access and scope, not what a metric means.
Practical task
On the demo Admin screen, map two roles to the data scope they can see and write a short note on how the same RCM question could return different figures under those two roles - with a line stating that this is a scope difference, not a data error, and that live role-scoping must be confirmed with product.
Self-check
Two users ask the same question and get different numbers. Before suspecting a bug, what do you check?
Their role scopes - each answer draws on the data that user's role can see, so different scopes can legitimately produce different figures.
Why is role-scoping especially important for a multi-client RCM provider?
It keeps one client's data out of another client's answers - governance that protects confidentiality and keeps answers correct for each user's remit.
An answer looks surprisingly incomplete. Is the data necessarily wrong?
No - the asking user's role scope may exclude part of the relevant data. Check the scope before concluding the data or metric is faulty.
What does Admin govern, and what does it not?
It governs who can see what - access and data scope. It does not change what a metric means; that is set by the metric definition in the Metrics view. Advanced setup is a specialist escalation.
Verified vs demo. Screen is live in the demo at /#/admin; role-scoped access and governance are demo-shown on seeded data, and exact controls, role logic and figures are SME-validation-pending. Live role-scoping, client-data segregation and entitlement are production-dependent - confirm with product; advanced setup is a specialist escalation.