The ERQ segment is used to issue queries where the desired response is formatted as an event replay response message. This enables the querying application to request detailed event data from an application that supports this feature, such that it may no longer be necessary for it to capture and store all event information at the time of the original trigger event.
SEQ |
LEN |
DT |
OPT |
RP/# |
TBL# |
ITEM# |
ELEMENT NAME |
1 |
32 |
ST |
O |
00696 |
Query Tag |
||
2 |
60 |
CE |
R |
00706 |
Event Identifier |
||
3 |
256 |
QIP |
O |
Y |
00705 |
Input Parameter List |
2.24.21.0 ERQ field definitions
Definition: This field may be valued by the initiating system to identify the query, and may be used to match response messages to the originating query. If it is valued, the responding system is required to echo it back as the first field in the query acknowledgment segment (QAK). This field differs from MSA-2-message control ID in that its value remains constant for each message (i.e., all continuation messages) associated with the query, whereas MSA-2- message control ID may vary with each continuation message, since it is associated with each individual message, not the query as a whole.
Components: <identifier (ID)> ^ <text (ST)> ^ <name of coding system (ST)>^<alternate identifier (ID)> ^ <alternate text (ST)> ^ <name of alternate coding system (ST)>
Definition: This field contains the HL7 event identifier corresponding to the original trigger event. Its contents dictate the format of the response message. Hence, a value of "A04" in this field indicates a request for the data associated with the "register a patient" trigger event. The ERP response message returns the contents of the "register a patient" message defined in Chapter 3. If more than one match is found, the ERP returns repeating groups of the segments defined by the "A04" message.
Components: <field name (ST)> ^ <value1 (ST) & value2 (ST) & value3 (ST...>
Definition: This field contains the list of parameter names and values to be passed to the responding system, in the form "<field name> ^ <value1 & value2 & value3 ...>." A single valued parameter contains only a single subcomponent in the second component: thus no subcomponent delimiters are needed (e.g., <field name> ^ <value>). A simple list of values (i.e., a one-dimensional array) may be passed instead of a single value by separating each value with the subcomponent delimiter: "<field name> ^ <value1&value2 &...>" Refer to Section 2.24.16.4, "EQL query statement (ST) 00710 for field naming conventions.
For example, , a value of "@00122^123-45-6789" could be combined with the A04 event identifier to request patient registration data for the patient with the social security number 123-45-6789.