X12 837I CL1 Segment Guide: Fields, Format, and Testing Gotchas
Professional claims never carry this segment at all, which is exactly why it catches teams off guard the first time they stand up 837I testing off the back of an existing 837P pipeline. CL1 is where an institutional claim declares how the patient arrived, why, and how the stay ended — and a mapping engine built only against 837P has nowhere to put any of it.
CL1 (Claim Information) is an institutional-claim-only segment in an X12 837I that describes the circumstances of an inpatient or facility stay — the admission type, the admission source, and the patient discharge status at the end of the encounter.
The elements that actually matter in practice
Example
A synthetic inpatient stay: admission type 1 (emergency), admission source 1 (physician referral), patient status 01 (discharged to home). Synthetic claim data.
Where this trips people up
CL1 only shows up on the institutional side, so teams that clone their 837P test harness for 837I coverage frequently forget to populate it at all — the claim validates against basic syntax rules and gets submitted anyway, then bounces back once the payer's edits notice a facility claim with no admission or discharge information attached. The other common miss is CL103: a stale or default discharge status (like leaving it at 30, still a patient) on a claim for a stay that clearly ended gets flagged by payer front-end edits even when every other field on the claim is correct.