Answer the records request before it becomes a recoupment.
Chart audits, records requests, prepayment reviews, and overpayment demands each become a case with a response deadline and dollars at stake. The system builds the response packet and the questions to put to the payer in writing; your team decides what goes out.
Book a workflow demoWhat it handles
Early access · shipping with design partners- Records requests logged with received date and deadline
- Charts requested, look-back period, and stated basis captured
- Per-claim response packet index
- Cover letter and document checklist drafts
- Sampling and extrapolation questions, in writing
- Prepayment review tracking
- Overpayment demand and offset tracking
- Dispute and appeal deadline tracking
- Minimum-necessary review before anything is sent
- Named-human approval before submission
Deadlines first, then documents
A records request starts a clock the day it arrives. The case records when it was received, how many charts were requested, the look-back period the payer claims, and the basis it gave, so the response is planned against the real deadline instead of the day someone opens the envelope.
- Received date and deadline
- Charts requested
- Look-back claimed
- Stated basis for the review
Records request · AUD-0412
14 days
Put the payer’s method in writing
Before a sample becomes an extrapolated demand, ask how the claims were selected, what universe the sample represents, and which criteria reviewers will apply. Those questions go to the payer in writing, and the answers stay on the case for any later dispute.
- Sampling method requested
- Claim universe requested
- Review criteria requested
- Answers kept on the case
Questions to payer
4
Recoupments you can see coming
Prepayment reviews and overpayment demands are tracked with their dispute deadlines and offset risk, so a demand letter never turns into withheld payments on unrelated claims before anyone responds.
- Dispute deadlines
- Offset risk flagged
- Amount demanded vs. supported
- Counsel escalation for large demands
Overpayment demands
2 open
Implementation library
Research the workflow before you evaluate the product.
The guardrail
Only the minimum necessary leaves your organization, and only after a named person approves it. While this module ships to design partners, response packets are built by hand from a de-identified worksheet, never from the request letter or the charts.