Reference·CL1 Segment·CL101
X12 837I Reference

X12 837I CL101 (Admission Type Code): Format, Values, and Testing Notes

Jul 27, 2026 · 4 min read
CL102 →

Two claims can describe the exact same procedure with the exact same charges, and still get treated completely differently by a payer's adjudication logic depending on a single digit in CL101 — because admission type is one of the first signals a payer's system reads when deciding how urgently a stay needed to happen.

Quick answer

CL101 is the first component of the CL1 segment in an X12 837I claim — a single code that tells the payer whether the admission was an emergency, urgent, elective, newborn, or trauma case.

Valid code values

1
Emergency — immediate admission required to protect life or health
2
Urgent — prompt admission needed but not immediately life-threatening
3
Elective — scheduled in advance, not urgent
4
Newborn — admission at birth — usually paired with a specific source code
5
Trauma — admission to a designated trauma center

Example

Synthetic example Generated by Synthibase
CL1*1*1*01

The first component, 1, marks this synthetic stay as an emergency admission. Synthetic claim data.

Where this trips people up

Test fixtures that default every claim to CL101 = 3 (elective) because it's the least likely to trigger extra scrutiny end up under-testing the exact scenarios — emergency and trauma admissions — that carry the most payer-side edit logic around authorization requirements. If your suite never generates a 1 or a 5, it's never actually exercised the medical-necessity checks those codes are designed to trigger.

X12 837I CL1 Segment Guide: Fields, Format, and Testing Gotchas
How to Test 837I Institutional Claims: A Complete Guide
How to Reduce Claim Denials Through Better Pre-Submission Testing
Generate every admission type automatically
Synthibase generates synthetic 837I claims covering emergency, urgent, elective, newborn, and trauma admissions — no PHI, full coverage of your edit logic.
Start free trial →
This page is written independently by Synthibase for testing and informational purposes. It is not an official publication of HL7 International or X12/Washington Publishing Company, and is not a substitute for reviewing the official standard or your trading partner's companion guide. See our Terms of Service for full legal terms.