Claim Status Report and Tracer Reply
This transaction set communicates the status of submitted claims or responds to inquiries about pending claims. Healthcare payers send claim status reports to healthcare providers, billing services, or clearinghouses; providers and billing entities receive these reports to track claim adjudication progress or resolve claim issues. The 926 is typically sent in response to a provider’s tracer inquiry or as a proactive update on claim processing. Key segments include the F11 (Status) segment, which reports the current state of a claim; the F14 (Line Item Reject) segment, which details specific claim line rejections when applicable; and the TRN (Trace) segment, which links the status report to an original tracer request by reference numbers.
Consider a scenario where Community Health Billing Services submits a status inquiry to MedCare Insurance about an outstanding claim. MedCare generates a 926 transaction containing multiple F11 segments—one indicating the claim is pending additional information, another showing a line item rejection due to a coding error flagged in the F14 segment, and a third reflecting partial payment approval. The TRN segment in each F11 loop references Community Health Billing Services’ original tracer number, enabling them to match the status report to their inquiry. This structured response allows Community Health Billing Services to understand exactly which claims need follow-up, which specific line items were rejected, and why, without requiring phone calls or manual reconciliation.
Claim Status Report and Tracer Reply (GC926) contains 1 table (Heading), 1 loop, and 6 segments. Sign up free or login to view every table, loop, and element in full, as well as download it in Markdown or console (text) formats.
Sign up free to see the full GC926 reference
See every segment, loop, and element across all 1 tables. Download it as a diagram or Markdown, or use the tedi CLI to access the full X12 reference from your terminal.