Overview
Loop 2300 is the claim-information loop within X12 837 Professional (P) and Institutional (I) claim transactions. Each 837 submission can contain multiple Loop 2300 occurrences — one per claim — with each Loop 2300 holding the attributes of a single claim. Service-line detail sits in Loop 2400 inside each Loop 2300 occurrence.
The structure nests within higher-level loops. Loop 2000A (Billing Provider) contains Loop 2000B (Subscriber) contains Loop 2000C (Patient, when different from subscriber) contains Loop 2300 (Claim) contains Loop 2400 (Service Line). The hierarchical structure allows a single 837 transaction to carry claims from one billing provider for multiple subscribers/patients efficiently.
Loop 2300 contains the CLM segment — the claim-identifying segment with attributes including claim submitter's identifier (claim number), total charges, place of service, claim frequency (original, replacement, void), and provider signature-on-file indicator. Additional segments within Loop 2300 carry dates (admission, discharge, accident), diagnoses (HI segment with ICD-10-CM codes), prior-authorization references, claim notes, patient account number, and many other claim-level attributes.
The diagnoses segment (HI) within Loop 2300 is particularly important because the service lines in Loop 2400 reference diagnoses by pointer rather than repeating the ICD-10-CM code. Loop 2300 might list diagnoses E11.9, I10, Z23; Loop 2400 service lines reference these as diagnosis pointers 1, 2, 3. This indirect reference structure is efficient but requires careful coordination between claim-level diagnoses and service-line pointers.
For providers and billers, Loop 2300 is where most operational data lives. Claim-level information drives payer adjudication decisions — place-of-service affects facility-fee application, claim frequency affects duplicate-claim logic, prior-authorization references affect PA validation. Errors in Loop 2300 data are common causes of claim rejection at payers.
For RCM engineering teams building 837 generators or consumers, Loop 2300 is the core structural unit requiring careful attention. Modern EDI tooling abstracts Loop 2300 population behind user-friendly interfaces, but understanding the underlying structure is essential for debugging rejections and optimizing submissions.
Loop 2300 (Claim Information) in 837 is one of the compliance areas where documentation discipline determines audit outcomes more than policy sophistication. Practices that invest in clean Loop 2300 (Claim Information) in 837 records, consistent 837 file workflows, and auditable edi transaction evidence come out of OIG, RAC, and MAC audits with materially smaller recoupment exposure than practices with equivalent policies but weaker paper trails.
From a board-reporting standpoint, Loop 2300 (Claim Information) in 837 belongs in the compliance committee's quarterly dashboard. The reporting line should include volume, exception rate, and any open remediation action; reviewers tie Loop 2300 (Claim Information) in 837 metrics to the broader compliance program KPIs so an emerging Loop 2300 (Claim Information) in 837 risk surfaces before it becomes a formal finding. Pairing the Loop 2300 (Claim Information) in 837 trend with 837 file gives the committee a single view of whether the control environment is strengthening or drifting.
Industry benchmark
Every 837P and 837I claim is carried in a Loop 2300 occurrence. Claim-count limit per 837 transaction varies by payer and clearinghouse agreement; typical batch limits are 5,000–10,000 claims per transaction.
Worked example
An 837P submission contains 3 Loop 2300 occurrences for 3 claims from a billing provider to a single payer. Each Loop 2300 holds a CLM segment with claim number, total charge, place of service 11 (office), claim frequency 1 (original), and HI segments listing relevant ICD-10-CM diagnoses. Each Loop 2300 contains Loop 2400 occurrences with service-line CPT codes and diagnosis-pointer references.
Frequently asked questions — Loop 2300 (Claim Information) in 837
Is Loop 2300 the claim itself?
Yes — Loop 2300 represents one claim within an 837 transaction. Multiple Loop 2300 occurrences represent multiple claims. Service lines within each claim are carried in Loop 2400 nested inside Loop 2300.
What's the difference between Loop 2300 and Loop 2400?
Loop 2300 is claim-level (one per claim, containing claim-wide attributes). Loop 2400 is service-line-level (one per service line within a claim). Service lines reference claim-level diagnoses via pointers.
How do diagnoses work in Loop 2300?
The HI segment within Loop 2300 lists all diagnoses for the claim (up to 12 in 837P 5010). Service lines in Loop 2400 reference these diagnoses by pointer (1–12) rather than repeating the codes.
Disclaimer
This glossary entry is operational reference for revenue-cycle and medical-billing professionals. It is not legal, clinical, or contractual advice. Industry benchmarks cite named public sources where available; always verify against the current guidance from the authority body before relying on a number in a contract, policy, or compliance filing.