Monitoring the Healthcare: HL7 to HL7 pattern

The flows generated by this pattern are monitored by the Healthcare Operational Monitoring view in Message Broker Explorer (MBX). The monitoring view displays TCP/IP statistics published by the message flows. The TCP/IP statistics are not sufficient by themselves and so they are augmented by information stored in user-defined properties in the message flows. This topic explains what these user-defined properties are called and the information they contain.

If you are using the HL7 nodes outside of the pattern to create custom integrations, then you can integrate your message flows with the monitoring view by configuring the same user-defined properties. Your message flows must also follow the same naming convention as the pattern. Sender flow names must end with Sender , for example ADTSender.msgflow . Receiver flow names must end with Receiver , for example ADTReceiver.msgflow .

User-defined properties

This pattern always has a single Receiver flow and one or more destinations. The source application identifier and facility are therefore fixed for all destinations. The destination identifier and facility will vary depending on which destination message flow you inspect.

Property name
Identifier1
Identifier2
Identifier3
Identifier4
TCPIPNode
SourceIdentifier
SourceFacility
DestinationIdentifier
DestinationFacility
QueuePrefix
Back to the Healthcare: HL7 to HL7 pattern specification