HL7 PPV_PCA Patient Goal Response

The old patient-care query response for goal details.
HL7 message structure PPV_PCA 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

SegmentNameRequiredRepeatable
MSH
 Message Header Yes No
SFT
 Software Segment No Yes
MSA
 Message Acknowledgment Yes No
ERR
 Error No Yes
QAK
 Query Acknowledgment No No
QRD
 Original-Style Query Definition Yes No
PPV_PCA.PATIENT
 Patient group Yes Yes
PID
 Patient Identification Yes No
PPV_PCA.PATIENT_VISIT
 Patient Visit group No No
PV1
 Patient Visit Yes No
PV2
 Patient Visit - Additional Information No No
PPV_PCA.GOAL
 Goal group Yes Yes
GOL
 Goal Detail Yes No
NTE
 Notes and Comments No Yes
VAR
 Variance No Yes
PPV_PCA.GOAL_ROLE
 Goal Role group No Yes
ROL
 Role Yes No
VAR
 Variance No Yes
PPV_PCA.GOAL_PATHWAY
 Goal Pathway group No Yes
PTH
 Pathway Yes No
VAR
 Variance No Yes
PPV_PCA.GOAL_OBSERVATION
 Goal Observation group No Yes
OBX
 Observation/Result Yes No
NTE
 Notes and Comments No Yes
PPV_PCA.PROBLEM
 Problem group No Yes
PRB
 Problem Details Yes No
NTE
 Notes and Comments No Yes
VAR
 Variance No Yes
PPV_PCA.PROBLEM_ROLE
 Problem Role group No Yes
ROL
 Role Yes No
VAR
 Variance No Yes
PPV_PCA.PROBLEM_OBSERVATION
 Problem Observation group No Yes
OBX
 Observation/Result Yes No
NTE
 Notes and Comments No Yes
PPV_PCA.ORDER
 Order group No Yes
ORC
 Common Order Yes No
PPV_PCA.ORDER_DETAIL
 Order Detail group No No
PPV_PCA.ORDER_CHOICE
 Order Choice group Yes No
NTE
 Notes and Comments No Yes
VAR
 Variance No Yes
PPV_PCA.ORDER_OBSERVATION
 Order Observation group No Yes
OBX
 Observation/Result Yes No
NTE
 Notes and Comments No Yes
VAR
 Variance No Yes

PPV_PCA returns patient goal information in response to an original-style patient-care query. It is the response-side companion to goal-centered patient-care workflows such as PGL_PC6, but it is not itself a new goal event.

Use this page mostly when you are maintaining an existing QRD-based care-plan interface. For new work, the backward-compatible status of this message family is a strong hint to consider newer query/response patterns instead.

A small PPV PCA example

MSH|^~\&|CAREPLAN|CITYHOSP|EHR|CITYHOSP|20260723150500||PPV^PCA^PPV_PCA|PPV00001|P|2.5.1 MSA|AA|QRYPC9001 QAK|QRYPC9001|OK|PCA^Goal response^L|1|1|0 QRD|20260723150400|R|I|QRYPC9001|||1^RD|123456^^^CITYHOSP^MR|GOL^Goal list^L|CAREPLAN|T PID|1||123456^^^CITYHOSP^MR||Rivera^Maya^^^^^L||19750519|F PV1|1|O|CLINIC^2^A^CITYHOSP||||12345^Nguyen^Anita GOL|UC|20260723150500|MOBILITY^Improve mobility^L|GOL-20260723-002|EOC-771|1|20260723142000|20260815000000|THERAPY^Therapy goal^L PTH|UC|FALLPREV^Falls prevention pathway^L|PTH-20260723-001|20260723142000|ACTIVE^Active^L OBX|1|NM|WALKDIST^Walk distance^L||25|m^meter^UCUM|||||F PRB|UC|20260723150500|FALLRISK^Risk for falls^L|PRB-20260723-002|EOC-771

What workflow it represents

A system asks for patient goals, and the application responsible for maintaining those goals returns the matching GOL records with patient, visit, pathway, observation, problem, and order context as needed.

The receiver might update a read-only care-plan display, reconcile its local goal cache, or populate a clinical repository. It should not quietly convert the response into a new goal add event.

How to read the structure

The envelope uses MSH, optional SFT, required MSA, optional ERR, optional QAK, and required QRD.

Each PATIENT group contains required PID, optional PV1/PV2, and one or more GOAL groups.

The required GOAL group starts with GOL. Optional ROL, PTH, OBX, PRB, ORC, NTE, and VAR add goal roles, pathway context, observations, linked problems, orders, comments, and variances.

Implementation traps

Goal status and problem status are separate. A query response can show an active problem with a completed, revised, cancelled, or still-open goal.

Keep GOL goal instance IDs. If the receiver stores these rows locally, the instance ID is what lets later updates line up with the same goal rather than matching on text.

If the response is limited, do not let users assume the first message is the whole care plan. QAK hit counts and profile-specific continuation behavior need to be honored.

Reference notes

HL7 terminology identifies PPV as the patient goal response message type. In the patient-care chapter, PPV_PCA is the goal response event for the older original-mode query family, later retained only for backward compatibility.