PGL: Patient goal message
This page lists the structures and trigger events PGL defines, taken from the standard. The written commentary that theADT page carries has not been written for PGL.
Recognising PGL messages
PGL announces itself in MSH-9 like this:
PGL^PC6^PGL_PC6- MSH-9.1
PGLmessage code: what kind of message this is - MSH-9.2
PC6trigger event: what happened in the real world - MSH-9.3
PGL_PC6message 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
PGL takes 1 structure.
PGL_PC6
No trigger event in the standard names this structure.
You must always send: MSH, PID, GOL. 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..* | |
| 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 | |
| GOAL | a group of 8 segments, repeated together | R | 1..* |
| GOL | R | 1..1 | |
| NTE | O | 0..* | |
| VAR | O | 0..* | |
| GOAL_ROLE | a group of 2 segments, repeated together | O | 0..* |
| ROLin GOAL_ROLE | R | 1..1 | |
| VARin GOAL_ROLE | O | 0..* | |
| PATHWAY | a group of 2 segments, repeated together | O | 0..* |
| PTHin PATHWAY | R | 1..1 | |
| VARin PATHWAY | O | 0..* | |
| OBSERVATION | a group of 2 segments, repeated together | O | 0..* |
| OBXin OBSERVATION | R | 1..1 | |
| NTEin OBSERVATION | O | 0..* | |
| PROBLEM | a group of 5 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..* | |
| ORDER | 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 12 such groups: PATIENT_VISIT, GOAL, GOAL_ROLE, PATHWAY, OBSERVATION, PROBLEM, PROBLEM_ROLE, PROBLEM_OBSERVATION, ORDER, ORDER_DETAIL, CHOICE, ORDER_OBSERVATION.
Trigger events
The trigger event is the real-world thing that made the message get sent. PGL defines 1.
| Event | Name | Structure |
|---|---|---|
| PC6 | PC6 |