HL7 NMR_N01 Application Management Response
NMR_N01 is the response side of the application management query workflow. It reports clock data, application statistics, status changes, and notes back to the requester.
In practice this is monitoring traffic. A receiver may use it to confirm that an interface application is alive, its clock is sane, and its message counters or status values are within expected ranges.
A small NMR N01 example
What systems do with it
The responder receives NMQ_N01 and returns NMR_N01 with management data. MSA acknowledges the original query, and optional ERR can report problems.
Operations systems use the payload to update health dashboards, raise alerts, or reconcile message counts. Because the message can include notes, it can also carry human-readable context for maintenance windows or known degraded states.
How to read the structure
MSH identifies NMR^N01^NMR_N01. MSA links the response to the original query. Optional QRD can echo query detail. The repeating management group can include NCK, NST, and NSC, each with optional NTE notes.
Implementation traps
Do not overreact to a single counter. Statistics fields often need site-specific baselines before they are operationally meaningful.
Also normalize clocks before alerting on timing. If one application reports its own local time and another expects UTC or hospital local time, stale-data alerts can fire for the wrong reason.
Reference notes
HL7 Chapter 14 application management describes NMQ/NMR as the application management query and response pair. See the HL7 v2.5 event page for N01 and the HL7 v2.4 application management chapter.