PEX: Product experience message
This page lists the structures and trigger events PEX defines, taken from the standard. The written commentary that theADT page carries has not been written for PEX.
Recognising PEX messages
PEX announces itself in MSH-9 like this:
PEX^P07^PEX_P07- MSH-9.1
PEXmessage code: what kind of message this is - MSH-9.2
P07trigger event: what happened in the real world - MSH-9.3
PEX_P07message 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
PEX takes 1 structure.
PEX_P07
No trigger event in the standard names this structure.
You must always send: MSH, EVN, PID, PES, PEO, PCR. 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..* | |
| EVN | R | 1..1 | |
| PID | R | 1..1 | |
| PD1 | O | 0..1 | |
| NTE | O | 0..* | |
| VISIT | a group of 2 segments, repeated together | O | 0..1 |
| PV1in VISIT | R | 1..1 | |
| PV2in VISIT | O | 0..1 | |
| EXPERIENCE | a group of 2 segments, repeated together | R | 1..* |
| PES | R | 1..1 | |
| PEX_OBSERVATION | a group of 2 segments, repeated together | R | 1..* |
| PEO | R | 1..1 | |
| PEX_CAUSE | a group of 8 segments, repeated together | R | 1..* |
| PCR | R | 1..1 | |
| RX_ORDER | a group of 3 segments, repeated together | O | 0..1 |
| RXEin RX_ORDER | R | 1..1 | |
| TIMING_QTYin RX_ORDER | a group of 2 segments, repeated together | R | 1..* |
| TQ1in TIMING_QTY | R | 1..1 | |
| TQ2in TIMING_QTY | O | 0..* | |
| RXRin RX_ORDER | O | 0..* | |
| RX_ADMINISTRATION | a group of 2 segments, repeated together | O | 0..* |
| RXAin RX_ADMINISTRATION | R | 1..1 | |
| RXRin RX_ADMINISTRATION | O | 0..1 | |
| PRB | O | 0..* | |
| OBX | O | 0..* | |
| NTE | O | 0..* | |
| ASSOCIATED_PERSON | a group of 5 segments, repeated together | O | 0..1 |
| NK1in ASSOCIATED_PERSON | R | 1..1 | |
| ASSOCIATED_RX_ORDERin ASSOCIATED_PERSON | a group of 3 segments, repeated together | O | 0..1 |
| RXEin ASSOCIATED_RX_ORDER | R | 1..1 | |
| NK1_TIMING_QTYin ASSOCIATED_RX_ORDER | a group of 2 segments, repeated together | R | 1..* |
| TQ1in NK1_TIMING_QTY | R | 1..1 | |
| TQ2in NK1_TIMING_QTY | O | 0..* | |
| RXRin ASSOCIATED_RX_ORDER | O | 0..* | |
| ASSOCIATED_RX_ADMINin ASSOCIATED_PERSON | a group of 2 segments, repeated together | O | 0..* |
| RXAin ASSOCIATED_RX_ADMIN | R | 1..1 | |
| RXRin ASSOCIATED_RX_ADMIN | O | 0..1 | |
| PRBin ASSOCIATED_PERSON | O | 0..* | |
| OBXin ASSOCIATED_PERSON | O | 0..* | |
| STUDY | a group of 2 segments, repeated together | O | 0..* |
| CSRin STUDY | R | 1..1 | |
| CSPin STUDY | 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: VISIT, EXPERIENCE, PEX_OBSERVATION, PEX_CAUSE, RX_ORDER, TIMING_QTY, RX_ADMINISTRATION, ASSOCIATED_PERSON, ASSOCIATED_RX_ORDER, NK1_TIMING_QTY, ASSOCIATED_RX_ADMIN, STUDY.
Trigger events
The trigger event is the real-world thing that made the message get sent. PEX defines 1.
| Event | Name | Structure |
|---|---|---|
| P07 | P07 |