To build a Utah Medicaid ABA claim replacement and void workflow, verify fee-for-service or accountable-care responsibility and read the original claim state. Correct and resubmit a denied fee-for-service claim as the current guide directs. Use the supported replacement or void path for a paid claim, with its original transaction control number. Preserve 999 and 277CA acknowledgments, remittance, authorization, service evidence, reversal, and new payment.

Define Utah's correction episode

Idris defines one episode as the original claim or local hold plus every transmission, rejection, adjudication, remittance, payment, correction, void, replacement, dispute, appeal, recoupment, refund, and closure event tied to it. The record preserves raw artifacts and the author of each clinical, coding, billing, payer, and financial decision.

Use the current Utah Medicaid authority

Utah Medicaid's PRISM training page provides claim-status, adjustment, void, reprocess, and acknowledgment instruction. The 837P fee-for-service companion guide distinguishes correction of a denied claim from replacement or void of a paid claim. It also requires the original TCN for the replacement or void route and separates the 999 from the 277CA.

Choose the responsible Utah receiver

The official publications page is the version gate for manuals and notices. The current ASD services manual controls the ABA service and authorization evidence for its scope. Idris records whether the payer is fee for service or an accountable care organization because the state companion guide cannot establish another receiver's submission process.

Classify the claim state before acting

Idris uses the register to classify local validation hold, 999 result, 277CA result, denied claim, paid claim, original resubmission, code-7 replacement, code-8 void, wrong-provider correction, plan dispute, overpayment, or reconciled close. Staff save the artifact that proves the state and receiver. A portal label, clearinghouse message, authorization number, claim-frequency value, directory entry, or phone note proves only what that source actually reports.

Build the PRISM ABA replacement and void ledger

Capture member and receiver; provider NPI and PRISM ID; service, authorization and record; original claim and TCN; 999 and 277CA controls; remittance; denied or paid state; correction fields; replacement or void intent; reversal and new adjudication; owner; clock; and close evidence. Structured fields drive routing, aging, and reconciliation. A concise narrative records the source-record issue, permitted change, uncertainty, payer instruction, client impact, disagreement, and why the accountable reviewer selected the action.

Keep decision authority with the right role

Idris does not change clinical content to obtain payment. A qualified clinician makes any permitted late entry, addendum, or correction under the practice's documentation policy, preserving original content, authorship, dates, and reason. A qualified coding or billing reviewer maps verified evidence to the receiver's current route. Operations coordinates work without authoring a clinical judgment or payer decision.

Compare source evidence with the claim

Before release, Idris compares member and payer, provider identity, location, authorization, completed record, actual date and time, code and units, earlier claim state, requested change, reference identifier, attachments, route, and deadline. The reviewer states the expected effect on the earlier claim and payment. Unknowns remain held with a named owner and escalation path.

Preserve Utah clocks and versions

Idris stores separate clocks for original filing, correction, adjustment, appeal, authorization, response, refund, and overpayment work. Each has a named start event, due event, source, and exception evidence. The register also keeps the manual, plan, form, portal, code, fee, alert, and contact version used on the action date. Later guidance triggers review without erasing the earlier source.

Prevent a duplicate transaction

Idris searches the complete Utah episode before another transmission. The check covers clearinghouse controls, payer references, remittances, replacements, voids, disputes, appeals, refunds, recoupments, and manual workarounds. A release states whether the earlier claim should remain, reverse, replace, or await payer action. Pending reprocessing is not permission to send another claim.

Protect clients and honest records

Idris separates financial follow-up from the person's care plan. A claim hold does not silently cancel clinically appropriate care, and a coverage decision does not become a clinical recommendation. The practice follows its lawful notice, continuity, record, collection, and emergency policies. Staff do not shift a provider-correctable denial or prohibited charge to a member because correction is slow.

Work through Idris's fictional cohort

Idris locks 18 fictional episodes at a Salt Lake City clinic. Twelve initially include receiver, provider match, authorization, TCN, acknowledgment, remittance, supported action, and financial owner. One denied claim is sent as a replacement, one paid claim is resubmitted as original, one void lacks the last TCN, one wrong-provider claim tries to replace under the new provider, and two records confuse 999 acceptance with claim acceptance. Four repair. Two stay held. The example is synthetic. It tests workflow and denominator logic and establishes no coverage, authorization, claim, appeal, compliance, legal, or payment conclusion for a real practice or member.

Calculate Idris's measures

PRISM route readiness is 12 of 18, or 66.7%. Sixteen episodes reach valid action or a documented hold, or 16 of 18, or 88.9%. Report local holds, front-end rejects, adjudicated denials, paid claims, adjustments, voids, replacements, disputes, appeals, recoupments, refunds, and final payments as separate cohorts. Every failed or held episode remains in its declared denominator.

Address the central Utah failure mode

Utah's fee-for-service guide gives code 7 and code 8 specific meanings. A replacement can reverse the earlier paid claim and process corrected data, while a void removes the payment without creating a corrected service claim. Idris declares the intended financial result and verifies it on the later remittance.

Test Idris's workflow

Idris tests a denied original resubmission, paid replacement, full void, wrong-provider episode, missing TCN, 999 rejection, 277CA rejection, and accountable-care claim. Each test preserves its starting state, expected route, evidence, observed result, owner, correction, retest, and disposition. Successful transmission passes only the transmission check. Adjudication, remittance, payment, and reconciliation require their own artifacts.

Reconcile the remittance and cash

Idris links every payer decision to the remittance and each remittance to the actual deposit, debit, recoupment, refund, or accounts-receivable balance. Partial effects stay open. A new payment does not erase an unresolved earlier overpayment, and a zero-dollar remittance still needs review. Finance records claim-level allocation before closure.

Run independent acceptance

Idris gives an independent reviewer the locked cohort, official sources, original claims, source records, authorizations, payer artifacts, routes, receipts, remittances, and cash reconciliation. The reviewer reproduces one correction and one hold. A changed cohort, missing failure, unsupported route, or unexplained financial difference fails acceptance.

Maintain the PRISM ABA replacement and void ledger

Idris reviews sources monthly and after program, plan, manual, code, form, portal, contract, authorization, fee, edit, appeal, or contact changes. Each source retains owner, effective and checked dates, scope, supersession, and next review. This Utah page remains draft and noindex until the named reviewers clear it.

Related resources

Sources