Medical Claim: Definition, Types and Examples

A medical claim is a formal request for payment that a healthcare provider or policyholder submits to a health insurer for services that are covered under a health plan. These claims come in different types depending on who submits them, the care setting, and their processing status (clean, rejected, denied, etc.).

What is a medical claim?

A medical claim is essentially a bill that describes the healthcare services a patient received and asks an insurance company to pay all or part of the cost. It includes patient demographics, provider details, dates of service, procedure codes (CPT/HCPCS), diagnosis codes (ICD‑10), charges, and insurance information.

Claims can be submitted either by the healthcare provider (most common in in‑network settings) or by the policyholder, especially when care was received out‑of‑network or in systems where reimbursement is patient‑initiated. The insurer reviews the claim, applies the patient’s benefits, and then pays the provider directly or reimburses the patient, depending on the arrangement.

Why medical claims matter

Medical claims sit at the heart of the healthcare revenue cycle and health‑plan operations.

• For providers, claims determine whether and when they are reimbursed for services, so claim quality directly impacts cash flow and financial performance.
• For payers, claims data is used to adjudicate benefits, detect fraud, manage utilization, and drive actuarial and policy decisions.
• For patients, claim outcomes affect out‑of‑pocket costs, surprise bills, and access to benefits such as deductibles, co‑insurance, and out‑of‑network reimbursement.

Because of this, understanding types of medical claims and how they move through the system is essential for clinicians, billing teams, and health IT leaders.

Types of medical claims: key ways they are classified

Medical claims are commonly categorized along three main dimensions:

1. Who pays and how the payment flows
2. The care setting and claim form
3. The claim’s quality and processing status

1. By payment method: cashless vs reimbursement claims

From an insurance‑procedure point of view, many health systems recognize two broad claim modes.

• Cashless (direct settlement) claims
  • The provider and insurer have a network relationship.
  • The provider submits the claim directly to the insurer, and if approved, the insurer pays the hospital or clinic, often before discharge, while the patient pays only applicable cost‑sharing.
• Reimbursement claims
  • The patient pays the provider upfront, then submits a claim with bills and supporting documents to the insurer.
  • The insurer validates coverage and reimburses the patient according to the policy’s terms.

Both modes involve a medical claim, but they differ in who fronts the payment and how the cash actually moves.

2. By care setting: professional vs institutional claims

In the U.S., the industry standard is to distinguish professional and institutional claims, each with its own form and electronic transaction.

• Professional (medical) claims – CMS‑1500 / 837P
  • Used by physicians and non‑institutional providers (clinics, independent labs, therapists) for professional services, often in outpatient settings.
  • Paper form: CMS‑1500, a single‑page form with 33 boxes covering patient, insurance, diagnosis codes (Box 21), and line‑item service details (Boxes 24A–24J).
  • Electronic transaction: 837P, the EDI equivalent for professional claims.
• Institutional (facility) claims – UB‑04 / 837I
  • Used by hospitals, nursing homes, rehab centers, and other facilities for inpatient stays, outpatient hospital services, and ED visits.
  • Paper form: UB‑04 (CMS‑1450), with up to 81 “form locators” describing revenue codes, service dates, units, charges, and non‑covered amounts.
  • Electronic transaction: 837I, the institutional counterpart.

Professional and institutional claims often describe overlapping care episodes but from different billing perspectives—professional work by clinicians versus facility resources.

3. By quality and processing status: clean, rejected, and denied claims

Operationally, revenue‑cycle teams classify claims by how smoothly they pass through payers and clearinghouses.

Clean claims

A clean claim contains complete, accurate information and passes clearinghouse and payer edits without requiring correction or additional documentation.

Typical characteristics include:

• Correct patient demographics and active insurance coverage
• Accurate CPT/HCPCS and ICD‑10 codes with valid diagnosis pointers
• Required authorizations and referrals in place
• Supporting documentation that matches billed services

Clean claims are the “gold standard” because they are processed quickly and paid on first submission.

Rejected claims

A rejected claim typically fails at the clearinghouse or payer’s front‑end edits before it is fully adjudicated.

Common causes include:

• Invalid or missing patient identifiers
• Coding format errors or invalid code combinations
• Structural issues in the electronic file (e.g., field missing, badly formatted date)

Rejected claims are not yet “denied” on coverage grounds; they must be corrected and resubmitted before the payer will make a coverage decision.

Denied claims

A denied claim is one that the payer has processed and decided not to pay, in whole or in part.

Reasons include:

• Services not covered under the patient’s benefit plan
• Lack of medical necessity or mismatch with coverage policies (e.g., LCD/NCD for Medicare)
• Missing or insufficient documentation to support the level of service
• Lack of prior authorization or failure to meet procedural requirements
• Claims submitted after timely filing limits

Denials are often divided into hard denials (difficult or impossible to overturn) and soft denials (may be reversible with additional information or corrections). Both reduce revenue and require follow‑up effort.

Step‑by‑step: the medical claim lifecycle (with example)

A simplified claim lifecycle typically looks like this.

1. Pre‑registration and eligibility
   • The provider collects patient demographics, insurance information, and verifies eligibility and benefits before or at check‑in.
2. Clinical encounter and documentation
   • The clinician evaluates and treats the patient; documentation captures history, exam, assessment, and plan.
   • This clinical record becomes the basis for coding and billing.
3. Coding and charge entry
   • Certified coders or automated systems assign ICD‑10 diagnoses and CPT/HCPCS procedure codes.
   • Charges are entered using a charge description master (CDM) or practice management system.
4. Claim creation and scrubbing
   • The billing system generates a CMS‑1500 or UB‑04 (or 837P/837I) claim file populated with demographic, coverage, and coding data.
   • Claim scrubbers and edits check for missing fields, invalid codes, and payer‑specific rules; non‑compliant claims are flagged and corrected.
5. Submission via clearinghouse
   • Claims are transmitted to a clearinghouse that validates structure and basic rules, returning rejections for issues that must be fixed.
   • Clean claims are forwarded to payers for adjudication.
6. Payer adjudication
   • Payers’ adjudication systems review eligibility, coverage, coding, and policies to determine payment or denial.
   • Results are communicated via Explanation of Benefits (EOB) and Electronic Remittance Advice (ERA).
7. Payment posting and follow‑up
   • Payments and adjustments are posted, and remaining patient responsibility is billed.
   • A/R staff follow up on denied, partially paid, or no‑response claims; appeals may be filed for disputable denials.

Simple examples of medical claims

Example 1: Outpatient primary‑care visit (professional claim)

A patient visits a family physician for management of hypertension and diabetes.

• The provider documents history, exam, and plan.
• Coding staff assign, for example, ICD‑10 codes for hypertension and diabetes and a CPT code for an established patient visit.
• A CMS‑1500 is generated and submitted to the insurer as a professional claim.
• If all information is correct and coverage is active, the payer processes it as a clean claim and pays according to the fee schedule.

Example 2: Hospital inpatient stay (institutional claim)

A patient is admitted for pneumonia.

• The hospital documents the admission, daily care, diagnostics, and discharge.
• Facility coders assign principal and secondary diagnoses, procedure codes, and revenue codes.
• A UB‑04 institutional claim is created, summarizing the episode of care with form locators for revenue codes, units, and charges.
• The payer adjudicates the claim under the applicable DRG or facility payment rules and issues payment or denial notices.

Example 3: Denied claim due to medical necessity

A diagnostic test is billed with a diagnosis code that does not meet a payer’s Local Coverage Determination (LCD) for medical necessity.

• The claim is processed and denied with a CO‑50 or related remark code indicating lack of medical necessity.
• The provider may review documentation, update coding if appropriate, or submit an appeal with supporting clinical evidence.

Common reasons for claim rejections and denials

Studies and payer reports highlight recurring issues that drive rejections and denials.

Frequent root causes include:

• Eligibility and coverage issues – inactive policies, benefits not verified, or services not covered under the plan.
• Demographic errors – incorrect name, date of birth, member ID, or address.
• Coding and documentation mismatches – procedure codes that do not align with diagnoses, incorrect modifiers, or documentation that does not support billed services.
• Authorization gaps – services performed without required prior authorization or referral.
• Timely filing – claims submitted after the payer’s filing deadline, often leading to non‑reversible denials.

Improving front‑end registration, documentation quality, coding accuracy, and automated edits can significantly increase clean‑claim rates and reduce revenue leakage.

How accurate documentation and tools like s10.ai influence medical claims

High‑quality medical claims start upstream with accurate, complete clinical documentation and consistent coding. Missing history elements, undocumented diagnoses, or ambiguous narratives can cascade into coding issues, rework, and denials later in the revenue cycle.

This is one reason many organizations are adopting ambient AI medical scribes and documentation tools that capture detailed encounter information and generate structured notes ready for coding and claim creation. Public information about s10.ai describes it as an AI‑enabled medical scribe and workflow automation platform that works alongside existing EHRs, with a focus on accurate note generation, broad EHR compatibility, and security frameworks such as HIPAA and SOC2. By improving clinical documentation at the point of care, such tools aim to support more accurate coding and cleaner claims, reducing downstream rework and denial risk while preserving clinician time.