Confirm transaction set: 837P uses implementation guide 005010X222A2 and 837I uses 005010X223A3; both share the ISA/GS/ST envelope structure but diverge in CLM and service loop segments
In CLM05 (claim service location), 837P uses a place-of-service code (2-digit CMS POS code, e.g., '11' for office, '21' for inpatient) while 837I uses facility/claim/frequency type codes (e.g., '11' for hospital inpatient, '13' for outpatient hospital) — these code sets are different and not interchangeable
837P uses SV1 segments for professional service lines: SV101 composite procedure code (qualifier + CPT/HCPCS), SV102 charge, SV103 unit/basis of measurement, SV104 units; 837I uses SV2 segments for institutional service lines with revenue codes in SV201
837I requires CLM05-1 facility type code and Bill Type Code in its own composite; it also requires UB-04 equivalent data including Condition Codes (HI*BF), Occurrence Codes (HI*BH), and Value Codes (HI*BE) in HI segments that do not appear in 837P
Both require HI segments for diagnosis codes but 837I typically includes a longer list of ICD-10 diagnoses (principal, admitting, external cause) and procedure codes (ICD-10-PCS in SV2 or HI*BP) in addition to revenue codes
Attending, operating, and other physician NPI loops (Loop 2310) are structured similarly in both but 837I requires the attending physician loop (NM1*71) while 837P requires the rendering provider loop (NM1*82)
Known gotchas
Submitting a 837P with institutional service data or vice versa will result in a 999 structural rejection or a 277CA intake rejection — ensure your claim builder selects the correct template based on the billing provider type and place of service
Revenue codes (SV201) used in 837I have no equivalent in 837P; mapping between the two for hybrid claims (e.g., critical access hospital professional billing) requires careful coordination with the payer
837I claims for inpatient stays use a single CLM with a span date range in DTP*435 rather than individual line-level dates of service as in 837P; line-level DTP segments on SV2 loops follow different qualifier rules
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp