Reference·CL1 Segment·CL102
X12 837I Reference

Testing X12 837I CL102: What Admission Source Code Actually Needs to Handle

Jul 27, 2026 · 4 min read
← CL101 CL103 →

A patient transferred in from another hospital and a patient who walked in off a physician referral can end up on structurally identical-looking claims — same diagnosis, same charges — but CL102 is the one field that tells the payer which of those two very different pathways actually happened.

Quick answer

CL102 is the second component of the CL1 segment in an X12 837I claim — it identifies where the patient was admitted from, such as a physician referral, a clinic referral, a transfer from another hospital, or the emergency room.

Valid code values

1
Physician Referral — admitted on a referring physician's order
2
Clinic Referral — admitted from a clinic visit
4
Transfer from a Hospital — admitted directly from another acute care facility
7
Emergency Room — admitted after presenting to the ER

Example

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

The second component, 1, marks this synthetic admission as coming from a physician referral. Synthetic claim data.

Where this trips people up

Facility-to-facility transfers (CL102 = 4) can carry different reimbursement rules than a direct admission from a physician referral, so a test suite that hardcodes CL102 = 1 across every fixture — because it's the simplest case to generate — never exercises the transfer-specific adjudication path, and that gap doesn't surface until a real transfer claim hits production and reimburses incorrectly.

X12 837I CL1 Segment Guide: Fields, Format, and Testing Gotchas
How to Test 837I Institutional Claims: A Complete Guide
How to Validate X12 EDI Files Before Payer Submission
Generate every admission source automatically
Synthibase generates synthetic 837I claims covering referrals, transfers, and ER admissions — no PHI, full coverage of your reimbursement 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.