100% Offline Reference 270 / 271 (005010X279A1)

ASC X12 270 / 271 Real-Time Eligibility & Benefit Loops (005010X279A1)

Real-time 270/271 transactions power front-desk patient coverage verification across CAQH CORE HTTP/SOAP endpoints and batch roster sweeps.

Four-Tier HL Hierarchy & EB Benefit Codes

LoopHL Level Code (HL-03)Key Segments in 270 (Inquiry)Key Segments in 271 (Response)
2000A20 Information SourceNM1*PR PayerNM1*PR, PER, AAA (payer-level outage/error)
2000B21 Information ReceiverNM1*1P / FA Provider + NPINM1*1P, AAA (invalid NPI / uncontracted provider)
2000C22 SubscriberTRN, NM1*IL, DMG, DTP*291, 2110C EQ*30TRN, NM1*IL, INS, 2110C EB (Active/Inactive, Deductible, Copay, Coinsurance)
2000D23 DependentTRN, NM1*03, DMG, 2110D EQ2110D EB, HSD, MSG, 2120D Benefit Related Entity (PCP / Carve-out PBM)
// Common EB-01 Eligibility / Benefit Information Codes in Loop 2110C/2110D:
EB*1*IND*30**GOLD PPO PLAN~             <-- EB-01 = 1 (Active Coverage)
EB*C*IND*30***29*1500.00*****Y~         <-- EB-01 = C (Deductible), EB-06 = 29 (Remaining = $1,500.00), In-Network = Y
EB*B*IND*98****40.00*****Y~             <-- EB-01 = B (Co-Payment = $40.00 for Professional Office Visit 98)
EB*6*IND*30~                            <-- EB-01 = 6 (Inactive Coverage)

Frequently Asked Engineering Questions

Why does Loop 2120C/D have LS*2120 and LE*2120 wrapper segments?

In X12 271, Loop 2120 (Benefit Related Entity, such as an assigned Primary Care Physician or third-party dental/pharmacy administrator) is nested inside Loop 2110 EB using explicit LS*2120 (Loop Header) and LE*2120 (Loop Trailer) bounded loop markers to prevent parser ambiguity.

Inspect, Diff, Validate & Scrub This Payload Offline in Your JetBrains IDE

Never paste regulated healthcare PHI (837/835/271) or supply-chain payloads (850/ORDERS) into browser parsers. EdiPrism X12 EDIFACT runs 100% air-gapped inside IntelliJ IDEA, PyCharm, DataGrip, Rider, GoLand, and WebStorm with a free core tier and a 14-day [Pro] trial.

Install Free from JetBrains Marketplace → Read Air-Gap Security Architecture