Skip to main content

Inside a claim: every section of the detail page

A tour of the claim detail page — the header identifiers, the money strip, all five tabs, the activity timeline and tasks, and the CMS-1500 view.

Written by Nanda Guntupalli

Open any row on the Claims page and you get the claim's full story on one screen. This article walks through every section, top to bottom.

A claim's detail page: header, money strip, tabs, and the Tasks rail

The header

The top of the page identifies the claim and who's holding the ball:

  • Patient — name, MRN, age, and sex, with a View patient link to their record.

  • Owner — whose move is next: Needs your attention, Taiga working on it, or No action needed — plus when the claim last changed.

  • Why is this claim stuck? — appears when the claim is in a state that needs explaining (denied, rejected, waiting on your team, and so on). Click it for a plain-English note on what's happening and whether you need to act.

  • View CMS-1500 — opens the claim as a filled-in CMS-1500 form (the standard paper claim format) in a new tab. Useful for audits, records requests, or just seeing exactly what a payer sees.

Below that, the identifier row: date of service, claim ID, PCN (patient control number), patient external ID (the ID from your EHR), patient DOB, billing type, and billable status. Each ID has a copy button — when you email support about a claim, copy the claim ID from here instead of typing patient details.

The money strip

Five numbers summarize the claim's finances at a glance:

  • Billed — what was charged.

  • Allowed — what the payer's adjudication allows.

  • Payments — what has been collected so far, from all sources.

  • Balance — what's still outstanding.

  • Responsible party — who owes that balance next: the payer, the patient, or no one (resolved).

The tabs

Claim properties

Everything the claim was built from, in expandable sections: patient demographics, primary and secondary insurance (payer, plan, member ID, group), non-insurance payers, the rendering provider (NPI and taxonomy), service facility, billing provider, the care team (referring and supervising providers), and additional submission details like referral or prior-authorization numbers and accident information.

If something here is wrong — an outdated member ID, the wrong rendering provider — that's often the root cause of a rejection or denial. Email [email protected] with the claim ID and what needs to change.

Dx, Service lines & Remits

The clinical and payment substance of the claim:

  • Diagnoses — the ICD-10 codes submitted.

  • Place of Service — where the care happened.

  • Service Lines — each CPT/HCPCS code with its modifiers, quantity, and billed and allowed amounts.

  • Remits — remittance advice from payers as payments post, and the adjustments they carry.

  • Insurance Payments — the payer payments applied to this claim.

The Dx, Service lines & Remits tab

Until a payer responds, the remit and payment sections read "No remits received yet" — that's normal for a claim in flight.

Write offs & Patient payments

Adjustments written off the claim and payments collected from the patient, as they post.

Other claims

The patient's other claims, so you can check history without leaving the page — handy for spotting a pattern like every visit from one provider denying the same way.

Documentation

Documentation attached to the claim.

Activity and Tasks

The right-hand rail is the claim's paper trail:

  • Activity — a timeline of everything that has happened: the visit completing, status changes, submissions, and payer responses, each timestamped. Once a claim has gone out, a Submission card sits at the top: the payer it went to (with payer ID and whether they're primary or secondary), a Submitted → Clearinghouse → Payer progress row, and the submission date and clearinghouse — so you can confirm the claim actually went out and whether the payer has it.

  • Tasks — the billing work items on the claim, including finished ones. Each task shows its context and what action is required, and whether it blocks claim submission. Tasks marked for your team also surface on the Queues page.

Together they answer the two questions that come up most: what happened to this claim, and what is it waiting on right now?

Did this answer your question?