The flows generated by the Healthcare: HL7 to HL7 pattern are monitored by web-based monitoring. The monitoring view displays TCP/IP statistics published by the message flows. These statistics are augmented by information that is 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.
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 | Value | Examples |
|---|---|---|
| Identifier1 | The pattern instance name | ADT |
| Identifier2 | A literal string depending whether this is a Receiver or Sender message flow | Source or Destination |
| Identifier3 | The source or destination application HL7 identifier depending whether this is a Receiver or Sender message flow | Patient Registration |
| Identifier4 | The source or destination application HL7 facility depending whether this is a Receiver or Sender message flow | West City Hospital |
| TCPIPNode | The node name and TCP/IP address for the HL7 node used by the message flow | HL7 In/localhost:1111 or HL7 Out/localhost:2222 |
| SourceIdentifier | The source application HL7 identifier | Patient Registration |
| SourceFacility | The source application HL7 facility | West City Hospital |
| DestinationIdentifier | The destination application HL7 identifier | Pharmacy |
| DestinationFacility | The destination application HL7 facility | Another City Hospital |
| QueuePrefix | The queue prefix for this message flow or blank - a blank queue prefix means that the pattern instance name is used as the queue prefix | ADTQ |