Rekey Desk / Workflows / Claim status follow-up keying
Claim status workflow
Claim status follow-up: payer responses read, AR notes keyed
A batch of 277 responses lands and the AR queue is already behind. Your biller reads each one, opens the portal, types a note, then reopens three systems to act (r/healthIT post, captured 2026-09-24). The claim waits in the queue, and you count the days yourself.
Rekey Desk maps this loop step by step, writes the rule for every status field, and builds the keying into your AR work queue. The Rekey Map, the Field Rulebook, the Keying Build and the Exception Queue cover it end to end.
Request a sample run See a sample run
Last updated . Rekey Desk is run by Mike Rodgers from Denver and works remotely with operators across the United States.
What the response carries
A 277 response says a claim was received, rejected or pending, and it names the reason. The payer portal says the same thing in the payer's own words. Today a person reads both and retypes the result.
Teams polling 277 responses need rules for which statuses stay automated and which go to a person, and staff should not have to reopen three systems to act (r/healthIT post, captured 2026-09-24).
- Status and reason code go into the AR work queue note.
- Payer claim reference goes into the tracker, character for character.
- The next action follows the rulebook, not the biller's memory.
Which statuses stay automated
The Field Rulebook decides it in writing: a status with a clear reason code and a known next step is keyed into the note. Anything that needs judgment goes to a named person with the page attached.
That line is the point of the build. Your team writes it once and every batch follows it.
| Field | Read from | Keyed into | Rule |
|---|---|---|---|
| Status and reason code | Payer response | AR work queue note | Status text copied with the date received |
| Claim reference number | Payer response | Claim tracker | Character for character, spaces included |
| Portal status screen | Payer portal | AR work queue note | Screen text copied with the portal date |
| Next action | Field Rulebook | Queue assignment | Assigned by reason code to a named person |
The Rekey Map on this loop
The map counts each place a person types what the response already says: the note, the tracker, the follow-up date. Minutes and hand-offs are counted per step.
That count is what you compare against the build price, and if the loop is thinner than it feels, the teardown readout will say so.
Where people stay in
Your biller still works the queue, calls payers where calls are needed and decides what to refile. No payer submissions or appeals happen on your behalf.
Bring a week of responses to a teardown and get the Rekey Map, the Field Rulebook and a fixed build quote.
What correct looks like
The checks behind this page
- Check: every step in the Rekey Map names the response it reads from and the AR screen it types into.
- Check: every field in the Field Rulebook has a source, a target, a format rule and a named decider.
- Check: the Keying Build keys a held-back sample your staff already keyed, and every mismatch is listed.
- Check: every exception carries a reason code and the source page, and nothing is guessed.
Named owner of mistakes: Mike Rodgers. Every field your staff mark wrong is counted in the Monthly Accuracy Report, the rule behind it is fixed, and the affected records are checked again before the next batch.
Start here
Workflow Teardown, $2,500 fixed
Readout 10 business days after your de-identified sample set arrives. The $2,500 is credited in full against the Keying Build if you sign within 30 days of the readout. If the map shows the workflow is not worth automating, the readout says so, and you keep the map and the rulebook.
The Keying Build is a fixed price quoted after the teardown, and Run and Check is a monthly price quoted with it.
What your people still own
- Your biller works the queue and decides what to refile.
- Your team calls payers and handles appeals.
- Your named people decide every exception in the queue.
- You own the Field Rulebook, the exception log and the build configuration.
FAQ
Questions about this page
- What does the Workflow Teardown cost?
- It is $2,500 fixed, credited against the build if you sign within 30 days. The readout arrives 10 business days after your de-identified sample set, with a sample run on 25 documents you can compare.
- Do you replace our clearinghouse or billing system?
- No, the build keys into the AR work queue and trackers you already use, and replacing them is out of scope. The screens stay yours; only the typing changes.
- Which statuses go to a person?
- Any status the Field Rulebook marks as needing judgment goes to a named person with the page attached. Reason codes with a known next step are keyed into the note.
- Who owns a keying mistake?
- Mike Rodgers is the named owner. Every field your staff mark wrong is counted, the rule behind it is fixed, and affected records are re-checked before the next batch.
Request a sample run
Tell us the workflow that eats the most typing
One short form. We reply by email with what we need for the sample run. No patient data in this form, please.
- Workflow Teardown: $2,500 fixed
- Readout 10 business days after your de-identified samples arrive
- Credited in full against the build if you sign within 30 days