HL7 PPT Messages: Patient Pathway (Goal-Oriented)

HL7 PPT messages communicate a goal-oriented care pathway for a patient. A PPT message is the authoritative record of a structured care pathway organized around the goals the patient is expected to reach: it identifies the pathway, lists the goals that compose it, and attaches the problems each goal addresses, the orders placed to help achieve each goal, and the observations that measure progress toward each goal. The PPT message is sent from the system that authors and maintains the care pathway to systems that need to know the pathway in motion. This page explains what a PPT message represents, the trigger event that carries it, every segment the message can contain and what each one holds, and how a PPT pathway relates to FHIR. Sample content is constructed for illustration with fictional identifiers.

What a PPT message represents

A PPT message — PPT stands for Patient Pathway, Goal-Oriented — communicates a care pathway whose organizing principle is the patient's goals. Where a PPP message conveys a care pathway organized by clinical problems, a PPT message conveys a pathway organized by goals: the PTH segment is the pathway container, and the GOL segment is the unit of structure within it. Each goal in the pathway carries its own action, target date, lifecycle status, and instance identifier, and each goal can be linked to the problems it addresses (via PRB), the orders placed to support it (via ORC and OBR), and the observations that measure progress (via OBX).

The sender is the system that authors and maintains care pathways — typically a care-plan management system, a disease-management application, or an EHR clinical documentation module — and the receiver is any application that needs the pathway to coordinate care, such as a case-management tool, a care-coordination platform, a quality-reporting system, or an integration engine fanning the pathway out to downstream subscribers. A single PPT message can carry one or more PATHWAY groups, each opening with a PTH segment and containing one or more GOAL sub-groups, so a complete goal-oriented pathway — with all its goals, linked problems, orders, and observations — is delivered in a single transmission.

When a PPT message is sent

A PPT message is sent when a goal-oriented care pathway is established, updated, or otherwise communicated to other systems. Common scenarios include: a care-plan system publishing a newly established chronic disease pathway whose milestones are framed as patient goals, a disease-management application updating the lifecycle status of an in-flight pathway as goals are achieved or abandoned, or an EHR communicating a goal-oriented oncology or rehabilitation pathway to a care-coordination platform. Each message carries one or more PATHWAY groups, so multiple pathways for the same patient can be communicated together when appropriate.

Trigger event

The PPT message type carries a single trigger event:

• PPT^PCL – Patient pathway (goal-oriented) goal-centric communication.

Because PPT has one trigger event, the receiver's handling turns on the action code in PTH-1 and the lifecycle status in PTH-5 at the pathway level, and on the action code and lifecycle status carried in each GOL within the GOAL sub-groups, rather than on the trigger code in MSH-9 alone.

Integration topology

The diagram shows the pathway-authoring system publishing a goal-oriented pathway through the integration engine to downstream subscribers.

{{diagram: care-plan system → PPT^PCL → integration engine → case-management, care-coordination, quality-reporting}}

Typical senders: care-plan management system, disease-management application, EHR clinical documentation module, or any application that authors and maintains goal-oriented care pathways.

Typical receivers: case-management tool, care-coordination platform, quality-reporting system, clinical analytics, or integration engine fanning the pathway out to downstream subscribers.

Direction: unsolicited notification. The pathway-authoring system sends PPT whenever a goal-oriented pathway is established or its state changes; no prior query is required.

Segments in a PPT message

The PPT_PCL message is structured in layers. A required MSH and PID form the outer shell. A repeating PATHWAY group then opens with a required PTH — the pathway container — followed by optional notes, variance, and role segments at the pathway level, then a repeating GOAL sub-group that organizes the body of the message. Each GOAL sub-group opens with GOL and can attach problems (PRB), orders (ORC and OBR), and observations (OBX), each with their own notes, variance, and role segments. Cardinality follows HL7 notation: [X] optional, {X} repeating, [{X}] optional and repeating; a bare code is required. Each segment code links to its canonical field-by-field reference.

[ ] = optional, { } = repeating

The PATHWAY group repeats once per pathway, and the GOAL sub-group within it repeats once per goal in the pathway, so a single PPT message can carry the full structure of a goal-oriented care pathway — all goals, linked problems, supporting orders, and progress observations — in one transmission. The canonical segment pages carry the full field-by-field detail.

Sample PPT message

Note. Constructed for illustration. Patient identifiers, pathway identifiers, goal identifiers, dates, and names are fictional.

MSH|^~&|CAREPLAN|MERCYGEN|CASEMGMT|MERCYGEN|20260604093512||PPT^PCL^PPT_PCL|MSG00071|P|2.5.1
PID|1||MR98765^^^MERCYGEN^MR||SMITH^MARY^A||19650315|F
PTH|AD|HTN-CTRL^Hypertension Control Pathway^L|PATH-2026-0017|20260601083000|active^Active^L
NTE|1||Goal-oriented pathway established following hypertension review on 2026-06-01.
ROL|1|AD|PWOWN^Pathway Owner^HL70443|PROV01^CHEN^ALICE^^^^MD
GOL|AD|20260601083000|00001^Reduce systolic blood pressure to <130 mmHg^L|GOAL-2026-0042|||||active^Active^L|20260901
NTE|1||Goal set as primary milestone in the hypertension control pathway.
ROL|1|AD|GOWN^Goal Owner^HL70443|PROV01^CHEN^ALICE^^^^MD
PRB|AD|20260601083000|I10^Essential hypertension^I10|PRB-2026-0031
ORC|NW|ORD-2026-0099||||||20260601083000
OBR|1|ORD-2026-0099||55284-4^Blood pressure systolic^LN
OBX|1|NM|55284-4^Blood pressure systolic^LN||158|mm[Hg]|<130||||F|||20260601

What this sample shows

The PPT^PCL in MSH-9 marks a goal-oriented patient pathway communication. The PID identifies the patient — medical record number MR98765, Mary A. Smith. The PTH opens the PATHWAY group: PTH-1 action code AD adds a new pathway; PTH-2 carries the coded pathway type (HTN-CTRL — Hypertension Control Pathway); PTH-3 assigns the unique pathway instance ID PATH-2026-0017; PTH-4 records the established datetime as 1 June 2026; and PTH-5 sets the lifecycle status to active. The pathway-level NTE and ROL attach a clinical note and identify the pathway owner. The GOL opens the GOAL sub-group: GOL-3 carries the coded goal (reduce systolic blood pressure to below 130 mmHg); GOL-4 is the unique goal instance ID GOAL-2026-0042; GOL-10 sets the lifecycle status to active; and GOL-12 sets the target date to 1 September 2026. The PRB links the goal to essential hypertension (I10); the ORC and OBR link an order to capture systolic blood pressure; and the OBX carries the baseline reading of 158 mmHg associated with the goal.

Working with PPT messages

PTH is the pathway container, GOL is the organizing unit

A PPT pathway is identified and bounded by PTH — PTH-3 is the stable pathway instance identifier and PTH-5 is the pathway lifecycle status — and is composed of goals carried by GOL within repeating GOAL sub-groups. This is the distinguishing feature of PPT relative to PPP: in a problem-oriented pathway, the PRB segment organizes the sub-groups; in a goal-oriented pathway, GOL organizes them. Read PTH-3 and PTH-5 first to anchor the pathway, then walk the GOAL sub-groups in order.

Use PTH-3 and GOL-4 to reconcile against existing records

When a PPT message updates a pathway already known to the receiver, the pathway instance ID in PTH-3 is the stable identifier that lets the receiver match the incoming pathway to an existing record, and the goal instance ID in GOL-4 lets each contained goal be matched to an existing goal record. Reconcile on these identifiers rather than on position within the message — the sender may reorder goals between transmissions, and a goal absent from a full pathway update should be treated as no longer part of the pathway rather than silently retained.

Map lifecycle statuses before processing

Both PTH-5 (pathway lifecycle status) and GOL-10 (goal lifecycle status) are coded values whose vocabularies vary across sending systems. Map each to the corresponding state in the receiver's care-plan model before processing — for example, normalize the sender's active, in-progress, current, and equivalents to a single canonical state — rather than comparing raw strings at the point of use.

Orders and observations attach under the goal, not the pathway

In a goal-oriented PPT, supporting orders (via ORC and OBR) and observations (via OBX) attach inside the GOAL sub-group, not directly under the PATHWAY group. The semantic is that each order is placed to help achieve a specific goal and each observation measures progress toward a specific goal. Preserve this attachment when forwarding the pathway downstream: dropping orders or observations up to the pathway level loses the goal association that motivates them.

Vendor variance. The PROBLEM, OBSERVATION, and ORDER sub-groups within each GOAL sub-group are all optional, and their presence varies widely by sender. Some care-plan systems send PTH with GOL only and no sub-groups; others always attach the addressed problem via PRB and the baseline observation via OBX. Confirm a partner's field and sub-group usage against their interface specification rather than assuming the base standard.

FHIR equivalent

A goal-oriented care pathway corresponds to the FHIR CarePlan resource, with the goals linked via CarePlan.goal to individual Goal resources, the patient as a Patient resource, and, for a messaging exchange, a MessageHeader at the head of a Bundle. A PPT message — a pathway with its goals, addressed problems, supporting orders, and progress observations — conceptually maps to a FHIR Bundle containing one CarePlan, one Goal per GOL segment, Condition resources for any linked PRB, ServiceRequest resources for any linked ORC/OBR, and Observation resources for any OBX.

There is, however, no published mapping to lean on. The HL7 v2-to-FHIR Implementation Guide provides no message map for PPT_PCL and no ConceptMap for the PTH segment — the patient-care message family (PPP, PPT, PGL, PPG) is not covered by the current IG. A FHIR CarePlan with linked Goal resources produced from a PPT message is therefore mapped manually, taking the pathway code and lifecycle status from PTH, the goal code, lifecycle status, target date, and subject reference from each GOL, and deriving linked Condition, ServiceRequest, and Observation resources from any PRB, ORC/OBR, and OBX segments present.

Common pitfalls

Pitfall. Treating PPT as a problem-oriented pathway. The PPP and PPT messages share the same outer shape but differ in their organizing principle: PPP organizes sub-groups under PRB; PPT organizes them under GOL. A parser that walks PPT looking for PRB at the top of each sub-group misses every goal in the pathway.

Pitfall. Discarding the pathway instance ID in PTH-3 or the goal instance ID in GOL-4. Without stable identifiers for the pathway and its goals, updates cannot be matched to the correct existing records during reconciliation; duplicate or orphaned pathway and goal entries result.

Pitfall. Re-parenting orders and observations to the pathway level. In a goal-oriented PPT, each order and observation is attached to a specific goal; flattening them up to the pathway level loses the goal association and breaks downstream consumers that rely on knowing which goal each order is intended to advance.

How Vorro handles PPT messages

Vorro receives PPT^PCL messages from care-plan and disease-management systems, anchors each pathway on the instance identifier in PTH-3, and reads the pathway lifecycle status from PTH-5 before walking the GOAL sub-groups in order. Vorro reconciles each contained goal on the instance identifier in GOL-4, normalizes both PTH-5 and GOL-10 to a canonical lifecycle vocabulary before forwarding, and preserves the attachment of linked problems via PRB, supporting orders via ORC and OBR, and progress observations via OBX under the correct goal rather than flattening them to the pathway level. Where a FHIR destination is configured, Vorro maps each pathway to a FHIR CarePlan with linked Goal, Condition, ServiceRequest, and Observation resources and delivers the result as a Bundle — composed manually, since the v2-to-FHIR Implementation Guide publishes no map for this message — and surfaces structural inconsistencies (a PATHWAY group with no GOAL sub-groups, or an ORDER attached at the pathway level) as integration alerts rather than silently passing them through.

Related messages

• PPP — the patient pathway (problem-oriented) message that conveys the same pathway concept organized by problems rather than by goals.
• PGL — the patient goal message that unsolicitedly adds, updates, or deletes individual goals outside the structure of a pathway.
• PPG — the patient pathway (goal-oriented) message used in the patient-goal query/response pattern alongside PPT in the patient-care message family.

Sources

• HL7 v2-to-FHIR IG — message maps index — confirms no message map for PPT_PCL
• HL7 v2-to-FHIR IG — segment maps index — confirms no ConceptMap for PTH
• HL7 Messaging Standard Version 2.5.1 product brief