HL7 PPT_PCL (Patient Pathway Response, Goal-Oriented) | Integration Soup HL7 Reference Guide

HL7 PPT_PCL Patient Pathway Response (Goal-Oriented)

The old query response for goal-oriented patient pathway detail.

HL7 message structure PPT_PCL 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	No	No
QRD	Original-Style Query Definition	Yes	No
PPT_PCL.PATIENT	Patient group	Yes	Yes
PID	Patient Identification	Yes	No
PPT_PCL.PATIENT_VISIT	Patient Visit group	No	No
PV1	Patient Visit	Yes	No
PV2	Patient Visit - Additional Information	No	No
PPT_PCL.PATHWAY	Pathway group	Yes	Yes
PTH	Pathway	Yes	No
NTE	Notes and Comments	No	Yes
VAR	Variance	No	Yes
PPT_PCL.PATHWAY_ROLE	Pathway Role group	No	Yes
ROL	Role	Yes	No
VAR	Variance	No	Yes
PPT_PCL.GOAL	Goal group	No	Yes
GOL	Goal Detail	Yes	No
NTE	Notes and Comments	No	Yes
VAR	Variance	No	Yes
PPT_PCL.GOAL_ROLE	Goal Role group	No	Yes
ROL	Role	Yes	No
VAR	Variance	No	Yes
PPT_PCL.GOAL_OBSERVATION	Goal Observation group	No	Yes
OBX	Observation/Result	Yes	No
NTE	Notes and Comments	No	Yes
PPT_PCL.PROBLEM	Problem group	No	Yes
PRB	Problem Details	Yes	No
NTE	Notes and Comments	No	Yes
VAR	Variance	No	Yes
PPT_PCL.PROBLEM_ROLE	Problem Role group	No	Yes
ROL	Role	Yes	No
VAR	Variance	No	Yes
PPT_PCL.PROBLEM_OBSERVATION	Problem Observation group	No	Yes
OBX	Observation/Result	Yes	No
NTE	Notes and Comments	No	Yes
PPT_PCL.ORDER	Order group	No	Yes
ORC	Common Order	Yes	No
PPT_PCL.ORDER_DETAIL	Order Detail group	No	No
PPT_PCL.OBR_SUPPGRP	Obr Suppgrp group	Yes	No
NTE	Notes and Comments	No	Yes
VAR	Variance	No	Yes
PPT_PCL.ORDER_OBSERVATION	Order Observation group	No	Yes
OBX	Observation/Result	Yes	No
NTE	Notes and Comments	No	Yes
VAR	Variance	No	Yes

PPT_PCL returns patient pathway information in response to an original-style query, with the pathway organized around goals. It is the response-side cousin of PPG_PCG, which sends a goal-oriented pathway as an add/update-style event.

This message is useful to understand when supporting older care-plan repositories. It should not be the first choice for a new interface unless you have a strong compatibility reason.

A small PPT PCL example

MSH|^~\&|CAREPATH|CITYHOSP|EHR|CITYHOSP|20260723151500||PPT^PCL^PPT_PCL|PPT00001|P|2.5.1 MSA|AA|QRYPCK001 QAK|QRYPCK001|OK|PCL^Goal-oriented pathway response^L|1|1|0 QRD|20260723151400|R|I|QRYPCK001|||1^RD|123456^^^CITYHOSP^MR|PTH^Goal-oriented pathway^L|CAREPATH|T PID|1||123456^^^CITYHOSP^MR||Rivera^Maya^^^^^L||19750519|F PV1|1|O|CLINIC^2^A^CITYHOSP||||12345^Nguyen^Anita PTH|UC|HFCARE^Heart failure care pathway^L|PTH-20260723-010|20260723143000|ACTIVE^Active^L ROL|1|UC|CM^Care manager^L|44556^Stone^Ari GOL|UC|20260723151500|DAILYWEIGHT^Daily weight monitoring^L|GOL-20260723-010|EOC-772|1|20260723143000|20260801000000 OBX|1|CE|GOALSTATUS^Goal status^L||ACTIVE^Active^L||||||F PRB|UC|20260723151500|HF^Heart failure^L|PRB-20260723-010|EOC-772

What workflow it represents

A requester asks for pathway information, and the maintaining system returns the pathway plus its goal-oriented care-plan detail. The receiver may display pathway progress, refresh a care-management view, or reconcile a clinical repository.

The top-level object is the pathway. Goals are nested under it so the receiver can preserve the relationship between the standardized care pathway and the objectives being tracked for the patient.

How to read the structure

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

Each PATIENT group begins with required PID and optional visit detail in PV1/PV2.

The required repeating PATHWAY group starts with PTH. Optional pathway roles use ROL. The nested GOAL group starts with GOL and can include observations, problems, orders, comments, and variances through OBX, PRB, ORC, NTE, and VAR.

Implementation traps

Do not flatten PPT_PCL into a bag of goals unless both systems agree. The pathway instance ID in PTH is what explains why those goals belong together.

Keep response semantics separate from update semantics. PTH and GOL action codes in a response describe the returned pathway and goals; they are not automatically commands to mutate the receiver.

The local v2.5.1 data gives this structure a terse title, so spell out "goal-oriented pathway response" in interface specs and test messages.

Reference notes

HL7 patient-care references identify PPT_PCL as the patient pathway goal-oriented response for event PCL. Later HL7 material marks the original-mode query response family as backward-compatible because QRD/QRF query handling was replaced by newer query mechanisms.