Offered workflow scope is confirmed in implementation. Public examples are fictional; specific integrations and production data handling are evaluated separately.
How the workflow works
01
Separate verified facts from estimates
Keep the payer source, check date, service scope, known benefit information, and unresolved questions visible. Eligibility and authorization do not guarantee payment.
02
Review the patient-facing explanation
An authorized person checks the financial policy and applicable requirements. Use understandable language and identify who can resolve a disputed or uncertain amount.
03
Reconcile the final responsibility
Check adjudication, contracts, posted payments, adjustments, and applicable protections before sending a balance. Keep corrections and patient questions as owned follow-up.
The evidence stays with the case
Separate verified facts from estimates
Keep the payer source, check date, service scope, known benefit information, and unresolved questions visible. Eligibility and authorization do not guarantee payment.
Example Coverage summary: Evidence: Verified fact / estimate / open question; Next action: Named owner review · Demo data
Review the patient-facing explanation
An authorized person checks the financial policy and applicable requirements. Use understandable language and identify who can resolve a disputed or uncertain amount.
Example Explanation review: Evidence: Source / assumptions / contact owner; Next action: Named owner review · Demo data
Reconcile the final responsibility
Check adjudication, contracts, posted payments, adjustments, and applicable protections before sending a balance. Keep corrections and patient questions as owned follow-up.
Example Billing handoff: Evidence: Reviewed balance / supporting basis / next action; Next action: Named owner review · Demo data
Inspect a fictional workflow
Try the workflow · fictional demo case
An estimate includes an unresolved benefit question
Fictional coverage summary: eligibility is current, but a service-level benefit remains uncertain before a patient-facing explanation.
Select a check to reveal the finding and next action. Nothing is sent to a payer.
0 of 3 checks reviewed. A named person still approves the next action.
This fictional example illustrates an offered Marsa workflow. We do not connect this public example to a payer or present it as a customer result. We measure demo starts and completions using fixed labels; no input text is collected.
Explore the offered workflows with fictional examples. These public walkthroughs prepare example outputs locally; they do not access records, connect to a payer, or submit anything.
Authorization and concurrent review
✓Authorization requirement checks and payer routing
✓Packet preparation and evidence checks
✓Initiation, attachments, and submission after approval
✓Status follow-up and additional-information responses
✓Renewals, concurrent review, and unit reconciliation
Fictional case · no patient information
A fictional IOP renewal has an amendment, a quantity question, and one missing supporting item.
Your implementation scope confirms the required payer workflows, systems, integrations, and operating responsibilities. A named human approves payer submissions.
A named authorized human approves payer-facing work. Qualified people retain clinical, coding, financial, contractual, and privacy decisions. No payer submission happens automatically.
Can I send patient information for the evaluation?
No. Use demo-safe, de-identified worksheet facts. Do not send charts, denial letters, or patient identities.
See the workflow on a demo case
Twenty minutes, your payer questions, and a visible human-review checkpoint.