The QPD segment defines the parameters of the query.
HL7 Attribute Table - QPD - Query Parameter Definition
| Base Framework | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Seq# | Data Element | Description | Flags | Implement | Cardinality | Length | C.LEN | Vocabulary | Data Type | |
 QPD | ||||||||||
  | 1 | 01375 | Message Query Name | SHOULD | [1..1] | QueryName (CD) | CWE Coded with Exceptions | |||
 | 2 | 00696 | Query Tag | C Condition defined for this element = Truncation not allowed! | MAY | [0..1] | 32 | ST String Data | ||
 | 3 | 01435 | User Parameters (in successive fields) | = Truncation not allowed! | MAY | [0..1] | 256 | varies variable data type | ||
The root for the expression is on the segment.
| Seq. | Referenced Elements | Introduction | Invariant | Comment |
|---|---|---|---|---|
| 1 | ? |
| Seq# | Data Element | Description | Flags | Implement | Cardinality | Length | C.LEN | Vocabulary | Data Type | |
|---|---|---|---|---|---|---|---|---|---|---|
| QPD | ||||||||||
| 1 | 01375 | Message Query Name | SHALL | [1..1] | QueryName (CD) | CWE Coded with Exceptions | |||
| 2 | 00696 | Query Tag | C Condition defined for this element = Truncation not allowed! | MAY | [0..1] | 32 | ST String Data | ||
| 3 | 01435 | User Parameters (in successive fields) | = Truncation not allowed! | MAY | [0..1] | 256 | varies variable data type | ||
| Base Framework | Base Standard Profile | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Seq# | Data Element | Description | Flags | Implement | Cardinality | Length | C.LEN | Vocabulary | Data Type | Implement | Vocabulary | |
| QPD | ||||||||||||
| 1 | 01375 | Message Query Name | SHOULD | [1..1] | QueryName (CD) | CWE Coded with Exceptions | SHALL | ||||
| 2 | 00696 | Query Tag | C Condition defined for this element = Truncation not allowed! | MAY | [0..1] | 32 | ST String Data | MAY | |||
| 3 | 01435 | User Parameters (in successive fields) | = Truncation not allowed! | MAY | [0..1] | 256 | varies variable data type | MAY | |||
| Base Framework | Base Standard Profile | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Seq# | Data Element | Description | Flags | Optionality | Repetition | Length | C.LEN | Table | Data Type | Optionality | Table | |
| QPD |
||||||||||||
|
1 | 01375 | Message Query Name | O | (0471) | CWE Coded with Exceptions |
R | |||||
|
2 | 00696 | Query Tag | C Condition defined for this element |
O | 32= | ST String Data |
|||||
|
3 | 01435 | User Parameters (in successive fields) | O | 256= | varies variable data type |
||||||
| Seq# | Data Element | Description | Optionality | Repetition | Length | C.LEN | Table | Data Type | |
|---|---|---|---|---|---|---|---|---|---|
| QPD |
|||||||||
|
1 | 01375 | Message Query Name | R | (0471) | CWE Coded with Exceptions |
|||
|
2 | 00696 | Query Tag | C | 32= | ST String Data |
|||
|
3 | 01435 | User Parameters (in successive fields) | O | 256= | varies variable data type |
|||
Definition: This field contains the name of the query. These names are assigned by the function-specific chapters of this specification. It is one to one with the Query Profile for this query name, and it is in fact an identifier for that Query Profile. Site-specific query names begin with the letter "Z." Refer to User defined table 0471 - Query name in Chapter 2C, Code Tables, for suggested values.
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 this field is valued, the responding system is required to echo it back as the first field in the query acknowledgement 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.
Implementation considerations: It is not necessary to value this field in implementations where the only return message on the socket will be the response to the query that was just sent. Conversely, in an "asynchronous" implementation where many queries, responses, and other messages may be communicated bidirectionally over the same socket, it is essential that this field be valued so that the Client knows to which query the Server is responding.
Definition: These successive parameter fields hold the values that the Client passes to the Server.
The client data is presented as a sequence of HL7 fields. Beginning at QPD-3-User parameters, the remaining fields of the QPD segment carry user parameter data. Each QPD user parameter field corresponds to one parameter defined in the Query Profile, where each name, type, optionality, and repetition of each parameter has been specified. While these parameters are understood to be usually "anded" together, the user SHALL inspect the required Query Profile to properly understand each. Except in the QSC variant, the parameter names do not need to be stated in the query; they are understood to be positional based on the Query Profile.
Each parameter field may be specified in the Query Profile to be of any single data type, including the complex QIP and QSC types. Parameter fields may also contain the sort control (SRT) field or the segment group (ID) field defined in Sections 5.5.6.6, "RCP-6 Sort-by Field (SRT) 01624," and 5.5.6.7, "RCP-7 Segment Group Inclusion (ID) 01594," below.
Parameter fields in the QPD segment appear in the same order as in the Query Profile.
The Demo site for our new HL7 Version 2+ (plus) Standard
