Seq# | Description | Data Type | Usage | Vocabulary | Length | C.LEN | Flags |
---|---|---|---|---|---|---|---|
QSC | |||||||
1 | Segment Field Name | ST | R | ||||
2 | Relational Operator | ID | O | [2..2] | |||
3 | Value | ST | O | 199 | |||
4 | Relational Conjunction | ID | O | [3..3] |
Components: <Segment Field Name (ST)> & <Relational Operator (ID)> & <Value (ST)> & <Relational Conjunction (ID)>
Example:
|@PID.5.1^EQ^EVANS|
Definition: The name of the field that is participating as a qualifier (usually the "key"). Refer to Section 2.A.59.1, “Segment Field Name (ST),” for segment field name conventions.
Definition: Refer to HL7 Table 0209 - Relational Operator for valid values.
Definition: The value to which the field will be compared.
Definition: Refer to HL7 Table 0210 - Relational Conjunction for valid values. The relational conjunction is defined as follows: If more than one comparison is to be made to select qualifying rows, a conjunction relates this repetition of the field to the next.
When applied to strings, the relational operators LT, GT, LE, and GE imply an alphabetic comparison.
A "generic" comparison selects a record for inclusion in the response when the beginning of the designated field matches the select string.
Where a repeating field is specified as an operand, a match on any instance of that field qualifies the row for inclusion in the response message.
AND takes precedence over OR. More sophisticated precedence rules require that the query be expressed as an embedded query language message or a stored procedure query message (see Chapter 5, "Query").