The SPR segment is used to issue queries using stored procedure calls. Refer to the functional chapters for the lists of HL7-defined stored procedure names, input parameters and output tables.
SEQ |
LEN |
DT |
OPT |
RP/# |
TBL# |
ITEM# |
ELEMENT NAME |
1 |
32 |
ST |
O |
00696 |
Query Tag |
||
2 |
1 |
ID |
R |
0106 |
00697 |
Query/ Response Format Code |
|
3 |
60 |
CE |
R |
00704 |
Stored Procedure Name |
||
4 |
256 |
QIP |
O |
Y |
00705 |
Input Parameter List |
2.24.20.0 SPR 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.
Definition: This field refers to HL7 table 0106 - Query/response format code for valid values.
Table 0106 - Query/response format code
Value |
Description |
D |
Response is in display format |
R |
Response is in record-oriented format |
T |
Response is in tabular format |
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 name of the stored procedure that is to be executed. Values for this field are defined in the function-specific chapters of this specification; site-specific stored procedure names begin with the letter "Z."
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 stored procedure, 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.