HL7 v2.5.1 Specificationsv2.5.1

to moveEnter to openTry PID-5, ADT, 0004

QAK segment

The QAK segment contains information sent with responses to a query. Although the QAK segment is required in the responses to the enhanced queries (see section 5.10.4), it may appear as an optional segment placed after the (optional) ERR segment in any query response (message) to any original mode query. 5.5.2.0 QAK field definitions 5.5.2.1 QAK-1 Query Tag (ST) 00696 Definition: This field may be valued by the initiating system to identify the query, and may be used to

The shape of one line

segmentQAK|QAK-1Query Tag|QAK-2Query Response Status|QAK-3Message Query Name|QAK-4Hit Count|QAK-5This payload|QAK-6Hits remaining

required in some cases optional

Count the pipes to find a field, and count the empty ones too: an empty field still holds its place. Leave out the separator before QAK-2 and its value arrives as QAK-1, so the receiver stores Query Response Status as Query Tag.

This page carries the QAK field table as published and nothing beyond it. The field notes, vendor behaviour, FHIR mapping and parsing guidance that thePID page has are still to be written for QAK.

Every field

SEQLENDTOPTRP/#TBL#ITEM#Element nameCardinality
QAK-132STC00696Query Tag0..1
QAK-22IDO020800708Query Response Status0..1
250CEO047101375Message Query Name0..1

QAK-3 is a CE, which holds 6 components separated by carets.

SEQLENDTOPTTBL#Component name
CE.120STOIdentifier
CE.2199STOText
CE.320IDO0396Name of Coding System
CE.420STOAlternate Identifier
CE.5199STOAlternate Text
CE.620IDO0396Name of Alternate Coding System
QAK-410NMO01434Hit Count0..1
QAK-510NMO01622This payload0..1
QAK-610NMO01623Hits remaining0..1

Message types carrying QAK

QAK appears in 27 message structures, belonging to 12 message types.