Texas Nursing Facility Medicaid: Reconcile Admission Transactions, LTCMI and Claims

Texas nursing facility receivables can stall before a claim reaches adjudication. A resident transaction may be rejected, an assessment record may not cover the service interval, or a claim may be routed as though it were still an original submission. The billing lead needs a dependency map that identifies which record is wrong and who can fix it.

The current HHSC nursing facility FAQ distinguishes transaction, assessment and claim responsibilities. The Form 3619 instructions explain its Medicare skilled coinsurance transaction scope and electronic submission requirements. Its historical identifier examples should not be used as current claim-format guidance.

Separate the state record from the claim

The NF remains responsible for timely 3618 and 3619 transactions in the LTC Online Portal and its MDS/LTCMI work. The 3619 instructions describe a 72-hour transaction deadline and payer-source transitions. Managed-care service coordination has a separate notice process; a transaction acknowledgement does not establish that notice occurred.

For STAR+PLUS unit-rate services, HHSC describes authorization through the 3618 and MDS process, while add-on services may have separate authorization requirements. TexMedConnect can route original NF claims to the responsible managed-care organization. The FAQ specifically directs providers not to submit corrections or adjustments to that state routing portal.

Follow one fictional stay

Assume the following operational events for a Medicaid applicant or recipient. Clinical necessity, eligibility and coverage have to be established separately; the table does not make those determinations.

The facility should not repeatedly resend the same claim while the state date conflict remains. Nor should it alter a clinically supported assessment date just to make a claim clear. The missing output is an accepted and accurate state interval, with evidence of what changed.

Quantify the unresolved interval

Suppose the September 20–30 unit-rate interval contains 11 otherwise eligible days at an invented $200 per diem. The $2,200 claim balance belongs in an exception category tied to the rejected transaction and unconfirmed assessment status. It is not yet proof of a payer underpayment.

After the state records are resolved, assume the payer adjudicates only nine supported days for $1,800. The remaining $400 now has a narrower question: did the corrected state interval include the two omitted days, did the claim contain them, and did the payer apply a separate reason for excluding them? Attach those specific records to the inquiry.

Keep the original claim identifier and payer acknowledgement. If a corrected claim is required, record its relationship to the original so an additional $2,200 receivable is not created. If only a status inquiry is appropriate, the action should not generate another claim at all.

Close each dependency with evidence

The final transaction map contains resident identifier, event type, actual event date, submission time, response status, accepted interval, assessment identifier, payer, claim identifier and final disposition. Protected information belongs in the organization’s controlled workflow, not an unsecured shared troubleshooting document.

An internal “submitted” status is insufficient. For a transaction, closure means the state response supports the intended interval. For a claim, closure means the payer’s adjudication and payment or further dispute route are known. Those are different events and may occur on different dates.

In a platform evaluation, introduce the rejected payer-transition record and ask staff to locate the affected $2,200 without opening unrelated claims. Then require the system to preserve the accepted correction and prevent duplicate receivable creation. This tests the full operational dependency, rather than a generic claim-submission screen.