MANSOQ Security & governance
Assign RCM permissions by responsibility
Separate master-data editing, publication, claims, bank cash and treasury confirmation.
Current source · source reviewed · 6 min read
Before you begin
- Organization/facility role administration access.
- A documented responsibility and approval model.
1. Identify each team’s work
Distinguish configuration readers, editors, import operators, publishers, claim handlers, cash managers, bank confirmers and insured-visit preparers.
2. Assign facility-scoped rights
The RCM authorization handler checks rights in the facility organization. Give access only for the facility and actions required by the person’s role.
3. Keep clinical rights distinct
Claim management is explicitly a financial right, not a clinical right. A doctor or nurse role alone should not be assumed to authorize claims, refunds or bank changes.
4. Test maker-checker pairs
Ensure another appropriately authorized person can approve tariffs, refunds and bank-detail changes. A user holding multiple roles still cannot approve their own protected change.
5. Review effective access
Verify actual deployed role assignments and customizations rather than assuming the source’s default role list is the facility’s current assignment.
Current source defaults
Configuration read defaults include facility admin, admin, administrator and billing. Editing/import/publication default to facility admin/admin; claim/cash/bank confirmation also include billing. Prepare Insured Visit defaults to facility admin/admin. Deployments may customize these assignments.
Permission does not establish evidence
An authorized person must still supply required source, dates, distinct approval and external readiness proof. A role grant cannot waive an activation gate.
Troubleshooting
A staff member can view but cannot act
Identify the specific permission and facility scope. Have the responsible administrator assign the documented role after reviewing the business responsibility.
Source evidence
References are pinned to the private MANSOQ source repository. Repository access is required to open these links.