Marcus
Revenue Cycle CoordinatorWhat Marcus handles
Supports claim follow-up, denial analysis, A/R prioritisation, documentation and exception escalation.
What remains human-controlled
All coding, billing and write-off decisions. Any account that falls outside defined parameters, including a disputed denial, an adjustment above threshold or a payer response the worker cannot reconcile, is escalated to a named human owner rather than resolved automatically. Final sign-off on any appeal, adjustment or balance affecting patient payment remains with your team.
What Perentis evaluates
Workflow and role fit
Whether the worker matches how accounts receivable is actually managed in your organisation, including payer mix, worklist rules and escalation thresholds.
Demonstrated performance
Accuracy of denial categorisation, follow-up timeliness against ageing buckets, and behaviour on incomplete or contradictory remittance data.
Security and data handling
How PHI and financial records are accessed, transmitted, retained and logged, and whether that satisfies your own control framework.
Human oversight and exception handling
Where the worker stops, what it escalates, and whether every exception reaches a named human owner.
Integration requirements
Connections to your practice management system, clearinghouse and payer portals, and the permissions each one requires.
Auditability
Whether every action, decision and escalation leaves a reviewable record your auditors can follow.
Deployment considerations
Deployment requires integration with your existing systems of record and agreement on escalation paths before go-live. Perentis defines these conditions as part of the assessment, while implementation is completed by your team or an approved delivery partner.
Discuss whether Marcus fits your workflow.
Tell us how accounts receivable runs in your organisation today. We’ll walk through the assessment, what it found, and the conditions a deployment would need to meet.