NMD: Application management data message
This page lists the structures and trigger events NMD defines, taken from the standard. The written commentary that theADT page carries has not been written for NMD.
Recognising NMD messages
NMD announces itself in MSH-9 like this:
NMD^N02^NMD_N02- MSH-9.1
NMDmessage code: what kind of message this is - MSH-9.2
N02trigger event: what happened in the real world: application management data message - MSH-9.3
NMD_N02message 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
NMD takes 1 structure.
NMD_N02: Application Management Data Message
Sent when one thing happens: N02: Application Management Data Message.
You must always send: MSH. 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..* | |
| CLOCK_AND_STATS_WITH_NOTES | a group of 3 segments, repeated together | R | 1..* |
| CLOCK | a group of 2 segments, repeated together | O | 0..1 |
| NCKin CLOCK | R | 1..1 | |
| NTEin CLOCK | O | 0..* | |
| APP_STATS | a group of 2 segments, repeated together | O | 0..1 |
| NSTin APP_STATS | R | 1..1 | |
| NTEin APP_STATS | O | 0..* | |
| APP_STATUS | a group of 2 segments, repeated together | O | 0..1 |
| NSCin APP_STATUS | R | 1..1 | |
| NTEin APP_STATUS | 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 4 such groups: CLOCK_AND_STATS_WITH_NOTES, CLOCK, APP_STATS, APP_STATUS.
Trigger events
The trigger event is the real-world thing that made the message get sent. NMD defines 1.
| Event | Name | Structure |
|---|---|---|
| N02 | Application Management Data Message | NMD_N02 |