HL7 PTR_PCF (Patient Pathway Response, Problem-Oriented) | Integration Soup HL7 Reference Guide

HL7 PTR_PCF Patient Pathway Response (Problem-Oriented)

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

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

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

You will mostly see this when maintaining older patient-care query interfaces. The message is useful, but it lives in the older QRD-based query world.

A small PTR PCF example

MSH|^~\&|CAREPATH|CITYHOSP|EHR|CITYHOSP|20260723152500||PTR^PCF^PTR_PCF|PTR00001|P|2.5.1 MSA|AA|QRYPCE001 QAK|QRYPCE001|OK|PCF^Problem-oriented pathway response^L|1|1|0 QRD|20260723152400|R|I|QRYPCE001|||1^RD|123456^^^CITYHOSP^MR|PTH^Problem-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|DIABCARE^Diabetes care pathway^L|PTH-20260723-020|20260723144000|ACTIVE^Active^L ROL|1|UC|EDU^Diabetes educator^L|55667^Moana^Leah PRB|UC|20260723152500|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|UC|20260723152500|A1CBELOW8^A1c below 8 percent^L|GOL-20260723-020|EOC-773|1|20260723144000|20261023000000

What workflow it represents

A requester asks for pathway information, and the maintaining system returns the pathway plus its problem-oriented context. Receivers use this to show why the pathway exists, which problems are attached, and which goals or observations are being tracked under the same plan.

Problem-oriented does not mean problem-only. The response can still include linked goals, observations, orders, roles, comments, and variances.

How to read the structure

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

Each PATIENT group starts with required PID and optional visit detail through PV1 and PV2.

The required repeating PATHWAY group starts with PTH. Optional pathway roles use ROL. Nested problem detail starts with PRB and can carry observations, goals, orders, comments, and variances with OBX, GOL, ORC, NTE, and VAR.

Implementation traps

Do not collapse PTH and PRB lifecycle statuses into one field. A pathway can remain active while a problem is updated, corrected, resolved, or reprioritized.

Make the response limit explicit. If a query asks for pathway detail and the response contains only one of several matching pathways, the receiver needs to know whether that is complete or paged.

Keep PTR_PCF distinct from PPT_PCL. The trigger and message type look similar, but one is problem-oriented and the other is goal-oriented.

Reference notes

HL7 patient-care references identify PTR_PCF as the patient pathway problem-oriented response for event PCF. HL7 terminology also marks PTR as a deprecated/backward-compatible patient pathway response message type.