An EB segment reports eligibility or benefit information for a specific context. Its meaning depends on the person and hierarchy that contain it, the requested service, coverage level, time period, and the values returned by the payer.
EB example
The EB fields cover benefit status, service type, coverage level, insurance type, time period, amounts, percentages, and quantities. A response can repeat benefit statements for different services or conditions. Authorization and network indications can further qualify a statement when the transaction profile and payer return those values.
The single-benefit example uses a short statement:
That line provides one statement in its surrounding subscriber context.
LS and LE example
LS and LE mark the start and end of a named loop. In this excerpt, EB01=R reports another or additional payer, and the 2120 loop names it:
DTP example
DTP supplies a date, time, or period associated with the surrounding loop:
HSD example
HSD limits the benefit in the EB before it:
REF example
REF contains an identifier whose meaning depends on its qualifier and loop:
In a 2110C or 2110D benefit loop, the 005010X279A1 implementation guide (X279A1) defines 6P as Group Number. A route can put other data in the field, so the same qualifier can contain a different value on another payer's connection.
MSG example
MSG adds text to its surrounding benefit context:
Interpret the whole context
Read an EB with its HL, NM1, dates, identifiers, limits, and explanatory text. Payer instructions can further restrict the values and qualifiers.