What Is a Medical Claim?
A medical claim is a structured request for payment sent to a payer. It is not a bill in the ordinary sense: it is a set of assertions — who was treated, under which coverage, by which provider, what was done, and why it was necessary — and a payer pays it only if every assertion holds up against the plan and the contract.
Updated 7 min read
On this page
Key takeaways
- A claim is a request built out of assertions — identity, coverage, provider, service, necessity. Each one can be checked independently, and any one of them failing is enough to stop payment.
- Nearly every claim travels as an 837 electronic transaction. The CMS-1500 and UB-04 are the paper forms behind the professional and institutional versions of the same data — HIPAA standardized the electronic format, and ASCA is why so little is still filed on paper.
- Which format a service belongs on is decided by who is billing and in what setting — not by preference. One hospital encounter can produce two claims on two forms.
- The claim only says what it says. A payer sees the claim and, later, the record — never the visit — so anything the claim does not carry did not happen as far as adjudication is concerned.
What a claim asserts
It helps to stop thinking of a claim as a bill. A bill says what is owed. A claim makes a case — and like any case it is built from separate claims of fact, each of which a payer can accept or reject on its own. Understanding a claim means understanding what those assertions are, because every denial category is one of them failing.
- Who was treated, and under what coverage
- The patient's identity and their plan membership, as the payer holds it — not as the practice recorded it. This assertion fails when the identifiers do not match the payer's record, or when the coverage was not active on the date of service. See eligibility verification.
- Who provided the care, and who is being paid
- Often two different parties, so the claim has to say both. The NPI is the thread the payer follows to find the provider in its own records — and if that thread does not lead somewhere recognized under the contract, the claim fails on who rendered the service before what was done is ever considered.
- What was done
- The services performed, reported as CPT codes, with modifiers where a service needs qualifying — that it was distinct from another performed the same day, that it was reduced, which side of the body. The codes are what the payer prices.
- Why it was done
- The patient's condition, reported as ICD-10 codes. This is the assertion that carries medical necessity: the diagnosis is how the claim explains why the service was appropriate for this patient, and a service whose reported reason does not support it can be refused however well it was performed.
- When, where, and how much
- The date of service, the setting the care was delivered in, the units, and the charge. The date starts the timely filing clock; the setting changes what is payable and at what rate.
The claim is all the payer sees
The formats a claim travels in
Those assertions have to be carried in a shape the payer can process, and there are two answers to that: a form and a transaction. Almost everyone learns the forms and almost everything is sent as a transaction, which is why the relationship between them is worth getting straight early.
| Format | What it carries | Maintained by |
|---|---|---|
| CMS-1500 | Professional services — the work of physicians, non-physician practitioners, and most outpatient providers. The reference layout for professional billing. | The National Uniform Claim Committee (NUCC). |
| UB-04 | Institutional services — hospital and facility care. Also called the CMS-1450. Carries data a professional claim does not, because it describes a stay rather than individual services. | The National Uniform Billing Committee (NUBC). |
| 837 | The electronic transaction that actually moves. 837P carries professional claim data, 837I institutional, 837D dental. HIPAA requires an electronic claim to use the adopted standard format; ASCA separately requires most providers to file Medicare claims electronically. Between them, this is the path nearly every claim takes. | X12, which maintains the transaction set and its implementation guides. |
The forms and the transaction are not alternatives so much as two shapes for the same information. A professional claim is a CMS-1500 conceptually and an 837P in transit — which is why a rejection can name a field that appears on no form a biller has ever filled in.
One encounter can produce two claims
Why the structure matters more than it looks
A claim is not prose. It is a structured record — fields with defined meanings, in a defined order — and that structure is what makes automated adjudication possible at all. It is also what makes claims fail in ways that feel disproportionate to the mistake.
A payer's system is not reading for sense. It is matching values against records and applying rules, so a transposed digit in a member ID is not a small error that a reasonable reader would see past — it is a value that matches nothing. The claim is returned, and the fact that everything else on it was perfect makes no difference. This is the mechanism behind an entire denial category, and it is why scrubbing exists as a step at all.
The same structure is what makes the process measurable. Because every claim asserts the same things in the same places, a payer can tell you exactly which assertion failed — and you can count how often each one does. That is what a denial reason code is, and it is why denials can be read as data about a process rather than as a run of bad luck.
What happens to a claim
Once built, a claim has a journey with more gates in it than most people expect: it is scrubbed, transmitted, acknowledged, accepted, and only then adjudicated. Each gate can return it, and each reports separately — which is why “the claim was sent” and “the payer has the claim” are different statements.
That journey is the subject of The Claim Lifecycle, and the ordered operational steps behind it are set out in The Claim Submission Process. What is worth carrying forward from here is simply that the claim is a set of assertions — because every gate ahead of it is checking one.
Common questions
Is a medical claim the same as a medical bill?
No. A claim is a structured request for payment sent to a payer, asserting who was treated, under what coverage, by whom, what was done, and why. A bill is what a patient receives, and it generally comes after the payer has adjudicated the claim and decided what it will pay — the patient's share is what is left. The claim is a case made to an insurer; the bill is a statement of what a person owes.
What is the difference between a CMS-1500 and a UB-04?
The CMS-1500 bills professional services — physicians, non-physician practitioners, most outpatient providers — and is maintained by the NUCC. The UB-04, also called the CMS-1450, bills institutional services such as hospital and facility care, and is maintained by the NUBC. Which one a service belongs on follows from who is billing and in what setting, not from preference. One hospital encounter can generate both: an institutional claim for the facility and a professional claim for the physician.
If claims are electronic, why learn the paper forms?
Because they are two shapes for the same information, and the forms are how most people first learn what a claim asserts. The CMS-1500 and UB-04 remain the reference layouts for professional and institutional billing, while the 837 transaction is what is actually transmitted in nearly every case. Knowing both is what lets you connect a rejection that names an electronic field to the concept you know from the form.
Why can a claim be denied when the care was appropriate?
Because a payer never sees the visit — it sees the claim, and if the decision is challenged, the record. Anything true about the encounter that the claim does not carry, and the record does not establish, has not happened as far as adjudication is concerned. A service can be entirely appropriate and still be refused because the reported diagnosis did not support it, the coverage was not active, or an identifier matched nothing.
Key terms in this article
Defined once, on their own pages.
Continue learning
Where to go next on claims.
The Claim Lifecycle
The gates a claim passes on the way to a payment decision, and what fails at each.
What Makes a Claim Clean
The edits a claim has to satisfy before it is worth sending at all.
The Claim Submission Process
The ordered operational steps that turn an encounter into an accepted claim.
What Is a Claim Denial?
What happens when one of the claim's assertions does not hold up.
Authoritative sources
- National Uniform Claim Committee (NUCC) (opens in a new tab)
Maintains the CMS-1500 claim form used for professional services.
- National Uniform Billing Committee (NUBC) (opens in a new tab)
Maintains the UB-04 claim form used for institutional services.
- X12 — EDI standards (opens in a new tab)
Maintains the 837 claim transaction set and its implementation guides.
- Centers for Medicare & Medicaid Services (CMS) (opens in a new tab)
Administers Medicare and Medicaid, issues NPIs through NPPES, and sets the HIPAA standard transaction requirements.