HL7 RSP_K25 (Personnel Information Response) | Integration Soup HL7 Reference Guide

HL7 RSP_K25 Personnel Information Response

The staff directory answers with people, roles, and credentials.

HL7 message structure RSP_K25 groups and segments from HL7 v2.5.1 Hide structure

These are the generated groups and segments for the version selected at the top of the page. The article explains the workflow, and this panel follows the chosen HL7 version.

Message Structure

Segment	Name	Required	Repeatable
MSH	Message Header	Yes	No
SFT	Software Segment	No	Yes
MSA	Message Acknowledgment	Yes	No
ERR	Error	No	Yes
QAK	Query Acknowledgment	Yes	No
QPD	Query Parameter Definition	Yes	No
RCP	Response Control Parameter	Yes	No
RSP_K25.STAFF	Staff group	Yes	Yes
STF	Staff Identification	Yes	No
PRA	Practitioner Detail	No	Yes
ORG	Practitioner Organization Unit	No	Yes
AFF	Professional Affiliation	No	Yes
LAN	Language Detail	No	Yes
EDU	Educational Detail	No	Yes
CER	Certificate Detail	No	Yes
DSC	Continuation Pointer	No	No

RSP_K25 is the response to a personnel information query. Where patient query responses return PID groups, RSP_K25 returns staff groups. It is useful when an ordering, scheduling, credentialing, or integration workflow needs current provider/staff metadata from a directory-like source.

The response starts with the usual query-response status segments and then repeats a staff group. That group can carry STF for staff identity, PRA for practitioner details, ORG for organizational placement, plus AFF, LAN, EDU, and CER where the profile needs them.

A small RSP K25 example

MSH|^~\&|STAFFDIR|CITYHOSP|EHR|CITYHOSP|20260717101503||RSP^K25^RSP_K25|RSP250001|P|2.5.1 MSA|AA|QBP250001 QAK|Q250001|OK|Q25^Personnel Information by Segment Query^HL7nnn|1 QPD|Q25^Personnel Information by Segment Query^HL7nnn|Q250001|55555^Reader^Riley RCP|I|5^RD STF|1|55555^CITYHOSP|Reader^Riley^^^^^L|A|F PRA|1|RAD^Radiology^L|MD^Medical Doctor^L ORG|1|RAD^Radiology Department^L|CITYHOSP

What systems do with it

A requester might use RSP_K25 to confirm that an ordering provider is active, populate scheduling resources, map local provider identifiers, or enrich outbound messages with credential and organization details. The response is especially useful when the staff directory, EHR, and ancillary systems do not share a single provider master.

QAK still controls the query outcome. The staff group is the result payload. If multiple staff records return, the requester needs a deterministic matching rule or a human review step.

How to read the structure

MSA acknowledges the original query message, QAK reports query status, and QPD echoes the question. RCP can be echoed to show the response limits that were applied. The required repeating STAFF group carries the actual personnel data.

STF is the anchor segment for the person. PRA, ORG, AFF, LAN, EDU, and CER add professional, organizational, language, education, and certification detail. Many production interfaces only populate a subset, so profile the fields that receivers actually use.

Implementation traps

Do not let an old cached response make authorization decisions by itself. Personnel status, privileges, and credentialing can change, and different systems may update at different speeds.

Also avoid mapping provider names as keys. Names are display data. Use stable identifiers with assigning authorities wherever the staff directory provides them.

Reference notes

HL7 v2.5.1 query listings pair Q25 personnel queries with K25 personnel responses and show the staff-oriented response group. See the public query chapter mirror at VICO HL7 v2.5.1 queries.