HL7 v2.5.1 Specificationsv2.5.1

to moveEnter to openTry PID-5, ADT, 0004

SPR segment

Stored Procedure Request Definition

The shape of one line

segmentSPR|SPR-1Query Tag|SPR-2Query/Response Format…|SPR-3Stored Procedure Name|SPR-4Input Parameter List

required 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 SPR-2 and its value arrives as SPR-1, so the receiver stores Query/Response Format Code as Query Tag.

This page carries the SPR 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 SPR.

Every field

SEQLENDTOPTRP/#TBL#ITEM#Element nameCardinality
SPR-132STO00696Query Tag0..1
SPR-21IDR010600697Query/Response Format Code1..1
250CER00704Stored Procedure Name1..1

SPR-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
256QIPOY00705Input Parameter List0..*

SPR-4 is a QIP, which holds 2 components separated by carets.

SEQLENDTOPTTBL#Component name
QIP.112STRSegment Field Name
QIP.2199STRValues

No message structure in v2.5.1 carries SPR, and no other segment is linked to it here. The standard defines the segment on its own.