SUR: Summary product experience report
This page lists the structures and trigger events SUR defines, taken from the standard. The written commentary that theADT page carries has not been written for SUR.
Recognising SUR messages
SUR announces itself in MSH-9 like this:
SUR^P09^SUR_P09- MSH-9.1
SURmessage code: what kind of message this is - MSH-9.2
P09trigger event: what happened in the real world: summary product experience report - MSH-9.3
SUR_P09message 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
SUR takes 1 structure.
SUR_P09: Summary Product Experience Report
Sent when one thing happens: P09: Summary Product Experience Report.
You must always send: MSH, FAC, PSH, PDC, PSH, FAC, PDC, NTE, ED. Everything else is optional, or required only inside a group you chose to send.
| Segment | Name | OPT | Cardinality |
|---|---|---|---|
| MSH | R | 1..1 | |
| FACILITY | a group of 5 segments, repeated together | R | 1..* |
| FAC | R | 1..1 | |
| PRODUCT | a group of 2 segments, repeated together | R | 1..* |
| PSH | R | 1..1 | |
| PDC | R | 1..1 | |
| PSH | R | 1..1 | |
| FACILITY_DETAIL | a group of 3 segments, repeated together | R | 1..* |
| FAC | R | 1..1 | |
| PDC | R | 1..1 | |
| NTE | R | 1..1 | |
| ED | R | 1..1 |
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 3 such groups: FACILITY, PRODUCT, FACILITY_DETAIL.
Trigger events
The trigger event is the real-world thing that made the message get sent. SUR defines 1.
| Event | Name | Structure |
|---|---|---|
| P09 | Summary Product Experience Report | SUR_P09 |