EQL segment
Embedded Query Language
The shape of one line
required optional
EQL-2 and its value arrives as EQL-1, so the receiver stores Query/Response Format Code as Query Tag.This page carries the EQL field table as published and nothing beyond it. The field notes, vendor behaviour, FHIR mapping and parsing guidance that thePID page has are still to be written for EQL.
Every field
| SEQ | LEN | DT | OPT | RP/# | TBL# | ITEM# | Element name | Cardinality |
|---|---|---|---|---|---|---|---|---|
| EQL-1 | 32 | ST | O | 00696 | Query Tag | 0..1 | ||
| EQL-2 | 1 | ID | R | 0106 | 00697 | Query/Response Format Code | 1..1 | |
| 250 | CE | R | 00709 | EQL Query Name | 1..1 | |||
| ||||||||
| EQL-4 | 4096 | ST | R | 00710 | EQL Query Statement | 1..1 | ||
Related
No message structure in v2.5.1 carries EQL, and no other segment is linked to it here. The standard defines the segment on its own.