RCM & insurance

Record and verify all four denial remedies in separate tracks

Follow actual wide forms for correction, information response, reconsideration and claim-level appeal, with required fields, saved histories and unresolved liability made explicit.

20 min read · Source baseline f6e9f05f

Verification and applicability

Actual wide root/Clinic UI writes for all four remedies, independent database and normal API detail/replay checks

Check your installed version, permissions and local configuration.

Before you begin

These two clearly fictional claim/denial fixtures and owned two-code maps were initialized by IT. They are rehearsal records, not actual payer adjudications; both claims intentionally remain draft. No normal operator map activation/publication or external qualification was proved.
Use exact role and facility access, retained reason/provenance, qualified configuration and genuine authorized evidence in actual operation. A reason alone never establishes who owes money.

1. Find the reason and open the exact case

Open Revenue Cycle → Denials. Read reason namespace, responsible team, elapsed receipt age, allowed actions, recovery certainty and final disposition separately. Match the exact reason, then select Work it. This list shows KB-LOCAL-CORRECTION for the coding pair and KB-LOCAL-CONTESTED for the contracting pair. Both explicitly preserve financial responsibility undetermined and patient debt undecided. The denial desks above are not configured; a mapped owner role is not proof the queue governance is complete.

**Find reason, team, permitted remedy and unresolved liability · 2026-10-18**Recorded baseline screen · 1728 × 921
Capture details
Actual original wide Chrome capture; fictional local Clinic recordkeeping. Two visibly fictional ownURN cases expose different remedy pairs. Both remain open, financial responsibility undetermined and patient debt undecided. All four denial desks are currently not configured; this rehearsal does not claim completed queue governance.
**Exact reason**: Do not infer financial responsibility from a denial reason.
**Undetermined**: No patient or payer debt established.
**Contested remedy pair**: Reconsideration and appeal are distinct.
**Correction remedy pair**: Correction and information response are distinct.
**Work it**: Open the exact contested case.
**Desk not configured**: Map owner is not proof queue governance exists.

2. Read evidence, receipt clock and required payload before saving

The detail distinguishes reason, responsible team, receipt time, recovered amount and linked claim. A displayed legacy denied amount has no value-state and is labeled unstated; it is not proof of recovery, established liability or billable patient debt. No denial_response rule is configured in this fixture. The action cards separately name mechanism, track, deadline kind and claim level; missing fields keep their respective buttons disabled. Mechanism labels describe intended transaction types, while this current remedy endpoint only appends a local history entry.

**Read required correction and information fields · 2026-10-18**Recorded baseline screen · 1728 × 921
Capture details
Actual original wide Chrome capture; fictional local Clinic recordkeeping. The actual correction and information-response cards start disabled with separate required payloads. This local recordkeeping endpoint does not perform the transaction mechanisms printed on the cards.
**Correction card**: Distinct clinical/coding record.
**Information card**: Separate response payload.
**Cancellation reason**: Actual transactions need certified vocabulary separately; this exercise supplies none.
**Corrected fields**: One field per line.
**Attachment references**: References only, no file-upload validation here.
**Disabled until complete**: Complete each card’s required fields.

**Read distinct reconsideration and appeal requirements · 2026-10-18**Recorded baseline screen · 1728 × 921
Capture details
Actual original wide Chrome capture; fictional local Clinic recordkeeping. The contested case exposes exactly reconsideration and appeal, with distinct payloads and the explicit unpublished claim-item-sequence extension guard. Both are claim-level local history records; no actual payer rejection or qualified reviewer is represented.
**Reconsideration**: Contested lines, justification and references.
**Appeal**: Justification, references and reviewer challenge.
**Line linkage blocked**: Do not invent an unpublished extension.
**Contested lines**: Content references do not change claim-level wire scope.
**Reviewer challenge**: Requires truthful supported facts in real use.
**Incomplete appeal disabled**: Each payload must be complete.

3. Record a correction in the clinical/coding track

On the correction case enter cancellation reason code, corrected fields one per line and rationale. The photographed input is explicitly fictional local practice. KB-LOCAL-CORRECTION is an owned rehearsal reason, not certified external cancellation vocabulary. Choose Correct a malformed or wrong submission once. Scroll to Remedy history and verify correction appears under Clinical and coding corrections. This normal UI write saved the full payload, actor and timestamp; it did not cancel the original, build a fresh claim, change money or contact a payer. Actual cancellation/fresh submission need separately validated source rules, certified vocabulary and supported transport.

**Complete the fictional correction record · 2026-10-18**Recorded baseline screen · 1728 × 921
Capture details
Actual original wide Chrome capture; fictional local Clinic recordkeeping. Actual UI payload uses an explicitly fictional reason, one corrected local display field and a rationale denying external action. Choosing the button records local history only; it does not cancel or build a fresh claim.
**Fictional reason**: This owned reason is not certified cancellation vocabulary.
**Corrected fields**: One named local field per line.
**Rationale**: Explain what was wrong and retain boundaries.
**Record correction**: Normal button appends local history; no transaction sent.
**Clinical coding track**: Not a financial concession.

**Verify correction in the clinical/coding history · 2026-10-18**Recorded baseline screen · 1728 × 921
Capture details
Actual original wide Chrome capture; fictional local Clinic recordkeeping. The saved correction appears under Clinical and coding corrections (1), separately from contested adjudications (0) and financial concessions (0). Independent stored-record inspection verifies the exact correction payload and actor/time; draft claim and unsent status remain.
**Clinical/coding count1**: Local correction saved.
**Correction timestamp**: Read exact action and local time.
**Contested count0**: No contested entry on this case.
**Financial concessions0**: No money was conceded.

4. Record an information response as its own entry

Enter requested items one per line, attachment references one per line and the narrative, then choose Answer an information request with additional evidence. This example references the actual retained owned rehearsal document and states no genuine payer request or clinical evidence exists. The free-text references are not an attachment upload, ownership check or evidence-content validation. Scroll to history and verify both correction and information response remain as distinct clinical/coding entries with their timestamps; contested and concession counts remain0.

**Complete requested items, references and narrative · 2026-10-18**Recorded baseline screen · 1728 × 921
Capture details
Actual original wide Chrome capture; fictional local Clinic recordkeeping. Actual separate information-response form contains one fictional requested item, one owned source reference and a narrative that no actual payer request or clinical evidence exists. References are free text here; saving does not upload or validate an attachment or transmit a communication.
**Requested items**: One item per line.
**Attachment references**: Retain actual authorized evidence in real use; this is an owned rehearsal note.
**Narrative**: Written explanation accompanies the references.
**Record information response**: Local history only.
**Clinical coding track**: Keep apart from reconsideration/appeal.

**Verify both clinical/coding records remain separate · 2026-10-18**Recorded baseline screen · 1728 × 921
Capture details
Actual original wide Chrome capture; fictional local Clinic recordkeeping. Actual history now shows correction and information response as two separate clinical/coding entries, with contested and financial concession counts still0. The normal response toast says recorded; independent DB verifies retained content, actor and timestamp.
**Clinical/coding count2**: Both entries persist.
**Original correction retained**: No overwrite.
**Information response retained**: Separate timestamped record.
**Concessions0**: No financial movement.
**Recorded toast**: Corroborated by independent record readback.

5. Open the contracting case and record reconsideration

Return to All denials and Work it on KB-LOCAL-CONTESTED. Supply existing contested line references one per line, justification and attachment references. Choose Ask the payer to reconsider a contested adjudication once. Although the payload names lines, the mechanism is claim-level. The observed action created one local Contested adjudications entry; it did not transmit a message, modify a line adjudication or request a real monetary concession. Verify the retained action and timestamp before proceeding.

**Record a fictional claim-level reconsideration · 2026-10-18**Recorded baseline screen · 1728 × 921
Capture details
Actual original wide Chrome capture; fictional local Clinic recordkeeping. Actual UI names one existing fictional line, an explicit no-adjudication justification and owned source reference. The card is claim-level; line references identify contested content and do not establish a published line-level appeal extension.
**Existing fictional line**: Use retained matching identity.
**Justification**: No actual adjudication or concession asserted.
**Source reference**: Owned rehearsal source, not payer evidence.
**Record reconsideration**: Appends local contested history only.
**Claim-level**: No external communication executed.

**Verify reconsideration in contested history · 2026-10-18**Recorded baseline screen · 1728 × 921
Capture details
Actual original wide Chrome capture; fictional local Clinic recordkeeping. Actual history shows one reconsideration in Contested adjudications, with clinical/coding and financial concessions0. Independent stored record proves the exact payload and actor/time; there is no external adjudication, recovery or transmission.
**Contested count1**: Distinct reporting track.
**Reconsideration retained**: Timestamped local record.
**Clinical/coding0**: No correction merged into this track.
**Concessions0**: No monetary outcome.

6. Record a distinct claim-level appeal with truthful reviewer context

Complete appeal justification, attachment references and reviewer challenge. The example truthfully asserts no actual payer reviewer or qualification/specialty dispute. Choose Appeal the adjudication once and verify a second contested entry labeled appeal appears beside reconsideration. The current form requires reviewer_challenge; if a real case has no established challenge, obtain the proper supported handling rather than inventing an allegation. The screen explicitly blocks unpublished claim-item-sequence linkage; this exercise does not enable a line-level appeal. No real legal filing or payer communication occurred.

**Complete claim-level appeal without false reviewer assertions · 2026-10-18**Recorded baseline screen · 1728 × 921
Capture details
Actual original wide Chrome capture; fictional local Clinic recordkeeping. Actual appeal payload explicitly labels a fictional claim-level history exercise; reviewer challenge states no actual payer reviewer, qualification or specialty mismatch is asserted. The unpublished line linkage guard remains visible and no external authority is fabricated.
**Justification**: Explain exact basis with truthful retained evidence in real operation.
**References**: The sandbox uses its owned rehearsal note.
**Reviewer challenge**: No real reviewer assertion in this fixture.
**Record appeal**: Local history only.
**Unpublished line linkage**: Keep claim-level; do not invent extension.

**Verify reconsideration and appeal without financial concession · 2026-10-18**Recorded baseline screen · 1728 × 921
Capture details
Actual original wide Chrome capture; fictional local Clinic recordkeeping. Actual contested history retains reconsideration and appeal as two distinct timestamped entries. Independent database readback confirms both payloads and actor/time; claims remain drafts with submitted_at NULL and no new exchange or financial concession.
**Contested count2**: Two separate remedies saved.
**Reconsideration retained**: No overwrite.
**Appeal retained**: Separate exact action.
**Concessions0**: No recovery or financial write.

7. Read results by track and verify the saved record

Clinical/coding corrections, contested adjudications and financial concessions are separate histories. Independent stored-record inspection confirmed all four exact payloads, actor and timestamp. Both linked claims still have draft status, submitted_at NULL, no payer reference and unchanged fictional totals. Financial responsibility stays undetermined. The sole case exchange is an automatic local eligibility validation_failed fixture record with sent/received NULL; no new exchange followed these remedy records. No patient debt, recovery, payer acknowledgement or external submission is established.

Source evidence

References are pinned to the private MANSOQ source repository. Repository access is required to open these links.