visit the hl7 website The Demo site for our new HL7 Version 2+ (plus) Standard

27.6.1 Application Management (99.1.13)

28 .Application Management (14)

14

Chapter Co-Chair and Editor

Anthony JulianMayo Clinic

Chapter Co-Chair

Nick Radov

United Healthcare

Chapter Co-Chair

Sandra StuartKaiser Permanente

Chapter Co-Chair

Dave ShaverCorepoint Health

Sponsoring Work Group:

Infrastructure and Messaging

List Server:

inm@lists.hl7.org

28.1 Chapter 14 Contents (14.1)

28.2 Introduction (14.2)

The information in this chapter was relocated from Appendix C as of v2.4 of the standard. It had previously been entitled Network Management, and has been renamed to more accurately describe the purpose of the messages described herein. This chapter does not specify a protocol for managing networks, á la TCP/IP SNMP. Rather, its messages provide a means to manage HL7-supporting applications over a network.

Because this chapter was originally named "Network Management," the messages and segments have labels beginning with the letter "N." These labels are retained for backward compatibility.

As a technical chapter, this information is now normative with respect to the HL7 standard. It is anticipated that additional messages and message content will be added to this chapter in the near future.

28.3 Trigger Events and Message Definitions (14.3)

28.3.1 NMQ - Application Management Query Message (Event N01) (14.3.1)

NOTE: The MFQ//MFR transaction was retained for backward compatibility as of v2.5 and has been withdrawn as of V2.7. See conformance based queries as defined in Chapter 5.

28.3.1.1 Acknowledgement Choreography (14.3.1.0)

None - Refer to Chapter 5 for generic query choreography.

28.3.2 NMD - Application Management Data Message (Event N02) (14.3.2)

The N02 event signifies when an unsolicited update (UU) Application Management Data message (NMD) is created by on application to transmit application management information to other applications. In this case, the initiating application sends an NMD message as an unsolicited update (UU) containing application management information to a receiving application, which responds with a generic acknowledgement message (ACK).

For example, an application going down for backups (or starting up again after backups) might issue such a message to one or more other applications. An application switching to another CPU or file-server may also need to use this transaction to notify other systems.

Segment Cardinality Implement Status
NMD^N02^NMD_N02
MSH

Message Header

[1..1] SHALL
SFT

Software Segment

 
CLOCK_AND_STATS_WITH_NOTES [1..*] SHALL
CLOCK [0..1]  
NCK

System Clock

[1..1] SHALL
NTE

Notes and Comments

 
APP_STATS [0..1]  
NST

Application control level statistics

[1..1] SHALL
NTE

Notes and Comments

 
APP_STATUS [0..1]  
NSC

Application Status Change

[1..1] SHALL
NTE

Notes and Comments

 

 

NMD_N02

MSH-15 MSH-16 Immediate ACK Application Ack
We need some ER7 examples...
We need some XML examples...

Acknowledgement Choreography

NMD^N02^NMD_N02

Note: Because this message pair does not have an application acknowledgement, the value in MSH-16 does not affect the choreography

ACK^N02^ACK: Generic Acknowledgement

Acknowledgement Choreography

ACK^N02^ACK