HL7 RCP Response Control Parameter

HL7 field reference RCP 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

FieldNameRequiredRepeatableTypeTable
RCP.1 Query Priority No No ID 0091
RCP.2 Quantity Limited Request No No CQ 0126
RCP.3 Response Modality No No CE 0394
RCP.4 Execution and Delivery Time No No TS
RCP.5 Modify Indicator No No ID 0395
RCP.6 Sort-by Field No Yes SRT
RCP.7 Segment group inclusion No Yes ID

RCP controls how a query response should be returned, including limits, timing, and continuation behaviour.

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 RCP in QBP_Q11 - QBP - Query by parameter requesting an RSP segment pattern response, QBP_Q13 - QBP - Query by parameter requesting an RTB - tabular response, QBP_Q15 - QBP - Query by parameter requesting an RDY display response, and QBP_Q21 - QBP - Get person demographics, and 9 other message structures. 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.

RCP-1 Query Priority OptionalO SingleS TypeID Table0091

RCP-1 qualifies the query workflow rather than identifying it. This is the sort of field receivers often use for branching, filtering, or display grouping.

Use the agreed value set, starting from HL7 table 0091. A local code without an agreed coding system is a small ambiguity that becomes a mapping problem later.

RCP-2 Quantity Limited Request OptionalO SingleS TypeCQ Table0126

RCP-2 carries a measured, counted, priced, or dosed value. A number without the expected unit, currency, or companion qualifier is much easier to misread than an empty field.

The generated panel links this to HL7 table 0126; many real interfaces narrow that list further, so follow the receiver's implementation guide.

RCP-3 Response Modality OptionalO SingleS TypeCE Table0394

RCP-3 carries Response Modality for this query workflow. Populate it only when the receiver has a clear use for it, and keep the value in the datatype shape shown in the generated field panel.

The generated panel links this to HL7 table 0394; many real interfaces narrow that list further, so follow the receiver's implementation guide.

RCP-4 Execution and Delivery Time OptionalO SingleS TypeTS

RCP-4 is a timing field. Send the real source-system precision, do not pad unknown dates or times, and agree how timezone offsets are handled when time of day matters.

RCP-5 Modify Indicator OptionalO SingleS TypeID Table0395

RCP-5 tells the receiver the state of this query workflow. Status fields often drive workflow branches, so use the agreed code and do not infer a status just because another field looks complete.

The coded value should follow HL7 table 0395 or the narrower table in the local profile.

RCP-6 Sort-by Field OptionalO RepeatableR TypeSRT

RCP-6 carries Sort-by Field for this query workflow. Populate it only when the receiver has a clear use for it, and keep the value in the datatype shape shown in the generated field panel.

This field can repeat. Use repetitions for separate real-world values, not as a workaround for putting several unrelated ideas in one field.

RCP-7 Segment group inclusion OptionalO RepeatableR TypeID

RCP-7 carries Segment group inclusion for this query workflow. Populate it only when the receiver has a clear use for it, and keep the value in the datatype shape shown in the generated field panel.

This field can repeat. Use repetitions for separate real-world values, not as a workaround for putting several unrelated ideas in one field.

Related links