Make payment differences explainable before choosing the response.
Compare supported expected reimbursement with actual adjudication, retain the contract basis, and route a reviewed inquiry, correction, or dispute without inventing a recovery guarantee.
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
Establish the applicable expectation
Identify the executed agreement, service, entity, product, setting, and effective period. Record exclusions and assumptions in the calculation.
02
Explain the actual payment difference
Review the remittance, adjustments, offsets, responsibility allocation, and ledger posting. An apparent underpayment may need a contractual, coding, or reconciliation review.
03
Route the authorized dispute or correction
The qualified owner chooses the applicable response path and timing. A named human approves the payer-facing output and verifies subsequent adjudication and payment.
The evidence stays with the case
Establish the applicable expectation
Identify the executed agreement, service, entity, product, setting, and effective period. Record exclusions and assumptions in the calculation.
Example Expected amount basis: Evidence: Contract reference / period / service scope; Next action: Named owner review · Demo data
Explain the actual payment difference
Review the remittance, adjustments, offsets, responsibility allocation, and ledger posting. An apparent underpayment may need a contractual, coding, or reconciliation review.
Example Variance case: Evidence: Supported expectation / actual decision / difference; Next action: Named owner review · Demo data
Route the authorized dispute or correction
The qualified owner chooses the applicable response path and timing. A named human approves the payer-facing output and verifies subsequent adjudication and payment.
Example Review and follow-up: Evidence: Approved calculation / response evidence / outcome check; Next action: Named owner review · Demo data
Inspect a fictional workflow
Try the workflow · fictional demo case
An apparent underpayment needs its contract basis checked
Fictional service: the expected amount differs from the remittance. The reviewer must distinguish a contract question from a posting error.
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.