HL7 VTQ (VTQ) | Integration Soup HL7 Reference Guide

HL7 VTQ VTQ

Query and response fields from experience.

HL7 field reference VTQ fields from HL7 v2.5.1 Show fields

These are the generated fields for the version selected at the top of the page. The document stays the same, but the reference panel follows that version.

Fields

Field	Name	Required	Repeatable	Type	Table
VTQ.1	Query Tag	No	No	ST
VTQ.2	Query/Response Format Code	Yes	No	ID	0106
VTQ.3	VT Query Name	Yes	No	CE
VTQ.4	Virtual Table Name	Yes	No	CE
VTQ.5	Selection Criteria	No	Yes	QSC

VTQ carries a virtual-table query request.

Query segments define what the sender is asking for, how the receiver should format the answer, and how a multi-message response is continued or limited.

A query is an interface contract. The tag, parameters, row definitions, sort/filter rules, and continuation pointers must match exactly or the receiver may return technically valid data that is not what the requester expected.

The v2.5.1 structures show VTQ in VQQ_Q07 - VQQ Q07. That tells you where it can appear, but the implementation guide still decides which optional fields are meaningful.

For practical interface work, read the generated field panel for datatype, required, repeatable, and table details, then use the notes below to decide what the field should mean in the receiving workflow.

VTQ-1 Query Tag OptionalO SingleS TypeST

VTQ-1 is the requester's handle for this query. Echoing it back correctly is what lets the requester match a response to the question it asked.

VTQ-2 Query/Response Format Code RequiredR SingleS TypeID Table0106

VTQ-2 tells the receiver what response style is expected. Use the values from HL7 table 0106 exactly as the profile defines them; changing the format changes how the rest of the response should be interpreted.

VTQ-3 VT Query Name RequiredR SingleS TypeCE

VTQ-3 names the query, event, stored procedure, virtual table, or profile being invoked. This is the semantic switch for the query, so both sides need to agree on the allowed names and their parameter rules.

VTQ-4 Virtual Table Name RequiredR SingleS TypeCE

VTQ-4 names the query, event, stored procedure, virtual table, or profile being invoked. This is the semantic switch for the query, so both sides need to agree on the allowed names and their parameter rules.

VTQ-5 Selection Criteria OptionalO RepeatableR TypeQSC

VTQ-5 carries the criteria or parameters that narrow the query. Keep each parameter in the expected datatype shape and avoid relying on display text that the receiver cannot evaluate.

Repeats should represent separate criteria or parameters in the order the query profile expects, not a free-form pile of search terms.

HL7^® Reference Guide