HL7 PPP_PCB (Patient Pathway Message, Problem-Oriented) | Integration Soup HL7 Reference Guide

HL7 PPP_PCB Patient Pathway Message (Problem-Oriented)

A pathway update that organizes the care-plan detail around problems.

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

PPP_PCB sends a patient pathway add event, with the pathway as the top-level object and problems as the primary nested detail. It is the problem-oriented pathway companion to PPG_PCG.

Use it when a system is opening or sharing a pathway for a patient and the receiver needs the problem-centered clinical context that explains why the pathway exists.

A small PPP PCB example

MSH|^~\&|CAREPATH|CITYHOSP|REPOSITORY|CITYHOSP|20260723144000||PPP^PCB^PPP_PCB|PPP00001|P|2.5.1 PID|1||123456^^^CITYHOSP^MR||Rivera^Maya^^^^^L||19750519|F PV1|1|O|CLINIC^2^A^CITYHOSP||||12345^Nguyen^Anita PTH|AD|DIABCARE^Diabetes care pathway^L|PTH-20260723-020|20260723144000|ACTIVE^Active^L ROL|1|AD|EDU^Diabetes educator^L|55667^Moana^Leah PRB|AD|20260723144000|DM2^Type 2 diabetes mellitus^L|PRB-20260723-020|EOC-773|1|20260723090000|||CHRONIC^Chronic^L OBX|1|NM|A1C^Hemoglobin A1c^L||8.7|%^percent^UCUM|||||F GOL|AD|20260723144000|A1CBELOW8^A1c below 8 percent^L|GOL-20260723-020|EOC-773|1|20260723144000|20261023000000

What workflow it represents

A pathway has been added for the patient, and the sender is sharing the problem-oriented view of that pathway. Receivers use it to open the pathway, connect it to active problems, route work to care teams, or synchronize care-plan detail across clinical systems.

The problem is not just explanatory text. If it is represented in PRB, it should be managed as a problem record with an action code and stable problem instance identifier.

How to read the structure

The header and patient context are MSH, optional SFT, required PID, and optional PV1/PV2 visit detail.

The required repeating PATHWAY group starts with PTH. PTH identifies the pathway, the pathway instance, the action, and the lifecycle timing for that pathway.

Within each pathway, optional NTE, VAR, and ROL add comments, variances, and pathway roles. The nested PROBLEM group starts with PRB and may carry problem roles, observations, goals, and orders through ROL, OBX, GOL, and ORC.

Implementation traps

Problem-oriented does not mean problem-only. A useful PPP_PCB profile still says what to do with linked goals, observations, orders, roles, comments, and variances.

Do not mix the PTH and PRB lifecycle states. A pathway can remain active while a problem is corrected, resolved, or reprioritized.

Make the message type/trigger explicit in test data. PPG^PCG and PPP^PCB are close enough that copy-paste mistakes are easy and painful.

Reference notes

HL7 terminology identifies PPP as the patient pathway problem-oriented message. In v2.5.1 the PPP_PCB structure requires PID and one or more PTH-led PATHWAY groups, with nested PRB-led problem material and optional observations, goals, orders, roles, comments, and variances.