The Demo site for our new HL7 Version 2+ (plus) Standard
visit the hl7 website

Draft Website - For Review Purposes Only

QIP - query input parameter list

HL7 Component Table - QIP - query input parameter list
Seq# Description Data Type Usage Vocabulary Length C.LEN Flags
QIP
1 Segment Field Name ST R
[6..12]    
2 Values ST R
199

Components: <Segment Field Name (ST)> & <Values (ST)>

Definition: This data type contains a segment field name and the list of values to be passed to the query processor.

Example:

|@PID.5.1^EVANS|

QIP-1: Segment Field Name (ST)

Definition: This component contains the segment field name.

Naming conventions:

Segment field names are designated by the “@” symbol concatenated with the HL7 segment ID followed by the sequence number for the field separated by a period. See sections 2.5.2, "Segments and segment groups" and 2.5.3.1, "Position (sequence within the segment)" for a definition of segment ID and sequence number. If the field is divided into components, the designation may be suffixed with ".nn", to identify a particular component (a suffix of “.3” indicates the third component of the field); otherwise, the whole field is assumed. If the field is further divided into subcomponents, the designation is suffixed with “.nn.mm", which identifies the component and subcomponent requested by relative position.

Site-specific segment field names may be used. In this case, the site-specific segment ID (if the field is not being added to an existing HL7 segment) and the sequence number must be defined so that they do not conflict with existing HL7 segment IDs and field sequence numbers.

Values for this field are defined in the function-specific chapters of this specification.

Note: If the “@” is being used as one of the delimiter characters defined in MSH-2-encoding characters, it must be “escaped.” See Section 2.7.1, "Formatting Codes".


QIP-2: Values (ST)

Definition: This component contains the field value or values in the form "value1& value2 & value3..."

A single-valued parameter contains only a single subcomponent in the second component, thus no subcomponent delimiters are needed (e.g., <segment 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 (e.g., <segment field name> ^ <value1 & value2 &...>).