PTR: Patient pathway problem-oriented response
This page lists the structures and trigger events PTR defines, taken from the standard. The written commentary that theADT page carries has not been written for PTR.
Recognising PTR messages
PTR announces itself in MSH-9 like this:
PTR^PCF^PTR_PCF- MSH-9.1
PTRmessage code: what kind of message this is - MSH-9.2
PCFtrigger event: what happened in the real world: patient pathway (problem-oriented) response - MSH-9.3
PTR_PCFmessage structure: which segments to expect, and in what order
How to use these specifications explains MSH-9 in full, with a worked example.
Message structures
PTR takes 1 structure.
PTR_PCF: Patient Pathway (Problem-Oriented) Response
Sent when one thing happens: PCF: Patient Pathway (Problem-Oriented) Response.
You must always send: MSH, MSA, QRD, PID, PTH. Everything else is optional, or required only inside a group you chose to send.
| Segment | Name | OPT | Cardinality |
|---|---|---|---|
| MSH | R | 1..1 | |
| SFT | O | 0..* | |
| MSA | R | 1..1 | |
| ERR | O | 0..* | |
| QAK | O | 0..1 | |
| QRD | R | 1..1 | |
| PATIENT | a group of 3 segments, repeated together | R | 1..* |
| PID | R | 1..1 | |
| PATIENT_VISIT | a group of 2 segments, repeated together | O | 0..1 |
| PV1in PATIENT_VISIT | R | 1..1 | |
| PV2in PATIENT_VISIT | O | 0..1 | |
| PATHWAY | a group of 5 segments, repeated together | R | 1..* |
| PTH | R | 1..1 | |
| NTE | O | 0..* | |
| VAR | O | 0..* | |
| PATHWAY_ROLE | a group of 2 segments, repeated together | O | 0..* |
| ROLin PATHWAY_ROLE | R | 1..1 | |
| VARin PATHWAY_ROLE | O | 0..* | |
| PROBLEM | a group of 7 segments, repeated together | O | 0..* |
| PRBin PROBLEM | R | 1..1 | |
| NTEin PROBLEM | O | 0..* | |
| VARin PROBLEM | O | 0..* | |
| PROBLEM_ROLEin PROBLEM | a group of 2 segments, repeated together | O | 0..* |
| ROLin PROBLEM_ROLE | R | 1..1 | |
| VARin PROBLEM_ROLE | O | 0..* | |
| PROBLEM_OBSERVATIONin PROBLEM | a group of 2 segments, repeated together | O | 0..* |
| OBXin PROBLEM_OBSERVATION | R | 1..1 | |
| NTEin PROBLEM_OBSERVATION | O | 0..* | |
| GOALin PROBLEM | a group of 5 segments, repeated together | O | 0..* |
| GOLin GOAL | R | 1..1 | |
| NTEin GOAL | O | 0..* | |
| VARin GOAL | O | 0..* | |
| GOAL_ROLEin GOAL | a group of 2 segments, repeated together | O | 0..* |
| ROLin GOAL_ROLE | R | 1..1 | |
| VARin GOAL_ROLE | O | 0..* | |
| GOAL_OBSERVATIONin GOAL | a group of 2 segments, repeated together | O | 0..* |
| OBXin GOAL_OBSERVATION | R | 1..1 | |
| NTEin GOAL_OBSERVATION | O | 0..* | |
| ORDERin PROBLEM | a group of 2 segments, repeated together | O | 0..* |
| ORCin ORDER | R | 1..1 | |
| ORDER_DETAILin ORDER | a group of 4 segments, repeated together | O | 0..1 |
| CHOICEin ORDER_DETAIL | a group of 0 segments, repeated together | R | 1..1 |
| NTEin ORDER_DETAIL | O | 0..* | |
| VARin ORDER_DETAIL | O | 0..* | |
| ORDER_OBSERVATIONin ORDER_DETAIL | a group of 3 segments, repeated together | O | 0..* |
| OBXin ORDER_OBSERVATION | R | 1..1 | |
| NTEin ORDER_OBSERVATION | O | 0..* | |
| VARin ORDER_OBSERVATION | O | 0..* |
R inside a group means required of that group. Send the group and you must include that segment; leave the group out and it never appears. This structure has 14 such groups: PATIENT, PATIENT_VISIT, PATHWAY, PATHWAY_ROLE, PROBLEM, PROBLEM_ROLE, PROBLEM_OBSERVATION, GOAL, GOAL_ROLE, GOAL_OBSERVATION, ORDER, ORDER_DETAIL, CHOICE, ORDER_OBSERVATION.
Trigger events
The trigger event is the real-world thing that made the message get sent. PTR defines 1.
| Event | Name | Structure |
|---|---|---|
| PCF | Patient Pathway (Problem-Oriented) Response | PTR_PCF |