To build a TennCare ABA claim correction and MCO appeal workflow, identify the member's managed-care company and the claim's present state before choosing an action. Preserve the original claim, payer reference, remittance, service and authorization evidence, corrected submission, reconsideration, appeal, complaint, independent-review record, and payment result. A correction fixes supported claim data under the current payer route. A dispute challenges a payer decision through the applicable MCO route.

Define Tennessee's correction episode

Hana 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 TennCare authority

TennCare's claims and appeals page routes a provider who disagrees with a claim outcome to the applicable managed-care organization for reconsideration or appeal. It describes a later provider-complaint route through TennCare Oversight. Hana treats those as separate stages rather than sending the same packet everywhere at once.

Choose the responsible Tennessee receiver

The MCO page identifies the health-plan layer, while the current provider-manual library preserves current and historical manual versions. Tennessee's independent-review page applies to eligible claims disputes with covered managed-care companies and has its own filing conditions. Hana records the MCO, product, first denial date, plan steps, and eligibility evidence before using it.

Classify the claim state before acting

Hana uses the register to classify local hold, clearinghouse reject, MCO front-end reject, paid claim, adjudicated denial, corrected claim, reconsideration, provider complaint, independent review, recoupment dispute, refund, 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 TennCare MCO claim-correction and appeal register

Capture member and MCO; product; billing and rendering identities; service, authorization and record; original claim and payer reference; received date; remittance; correction reason; plan route; reconsideration and appeal results; complaint or independent-review eligibility; financial effect; owner; clock; and closure 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

Hana 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, Hana 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 Tennessee clocks and versions

Hana 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

Hana searches the complete Tennessee 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

Hana 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 Hana's fictional cohort

Hana locks 21 fictional episodes at a Nashville practice. Fourteen initially show the MCO, original reference, service evidence, authorization, remittance, action, receipt, and financial owner. One claim went to the wrong MCO, one correction lacks a changed field, one denial was resent without reconsideration, one complaint skipped the plan route, one independent-review clock lacks its first-denial date, and two paid claims lack reconciliation. Five repair. Two remain 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 Hana's measures

TennCare episode readiness is 14 of 21, or 66.7%. Nineteen episodes reach a supported action or accountable hold, or 19 of 21, or 90.5%. 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 Tennessee failure mode

A corrected claim and a claim-payment dispute answer different questions. Repeatedly resubmitting an unchanged denial can create duplicates without preserving review rights. Hana states whether the practice is fixing claim data, contesting adjudication, reporting an unresolved plan process, or requesting independent review before any release.

Test Hana's workflow

Hana tests a wrong-MCO claim, front-end rejection, paid-claim data error, adjudicated denial, reconsideration, provider complaint, independent-review screen, and recoupment notice. 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

Hana 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

Hana 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 TennCare MCO claim-correction and appeal register

Hana 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 Tennessee page remains draft and noindex until the named reviewers clear it.

Related resources

Sources