Reference·CLM Segment·CLM05-2
X12 837P Reference

Testing X12 837P CLM05-2: What Facility Code Qualifier Actually Needs to Handle

Jul 27, 2026 · 4 min read
← CLM05-1 CLM06 →

CLM05-2 looks trivial because it only ever carries one value in a professional claim — which is exactly why teams stop validating it and never notice when a code generation bug quietly swaps in the wrong qualifier.

Quick answer

CLM05-2 is the Facility Code Qualifier, the second component of the CLM05 composite in an X12 837P claim — it tells the payer which code list the facility code in CLM05-1 was drawn from.

Valid code values

B
Place of Service Codes for Professional Claims — the standard value used in nearly every 837P submission

Example

Synthetic example Generated by Synthibase
CLM*ACCT61034*260.00***11:B:1*Y*A*Y*Y*P*

The B in the composite 11:B:1 confirms the 11 that precedes it is a CMS place-of-service code. Synthetic claim data.

Where this trips people up

Because CLM05-2 is almost always B, some hand-built test files hardcode the entire CLM05 composite as a string — so when a code refactor accidentally drops or mangles the qualifier, the mistake sails through every test that never checks the field in isolation and only surfaces as an obscure 999 syntax rejection.

X12 837P CLM Explained: Structure, Fields, and Common Mistakes
What is X12 837P? Complete Format and Field Guide
How to Validate X12 EDI Files Before Payer Submission
Stop hand-building composite elements
Synthibase assembles the entire CLM05 composite correctly every time — facility code, qualifier, and frequency code — so structural mistakes never reach your test files.
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.