MLLP Adapter Best Practices

Note the following MLLP Adapter best practices.

• If you plan to receive data from a number of hospital systems, there are several ways to identify the hospital sending the data:
  • Create and design integrations in different projects for each hospital system, then view the Observe tab in the project to see runtime data coming from that hospital system.
  • Enable payload tracing. MLLP messages typically contain identifying information that maps to the context issuing the message (such as the hospital). This is part of the payload. However, this payload is only available when payload tracing is enabled.
• If you have many hospitals sending data, there are notification mechanisms that you can design to handle errors.
  • Use scope logic and add notifications to integrations to trigger and send emails in case of failure with a fault handler. MLLP requires an explicit acknowledgment to receive messages. Errors are handled, but there are scenarios such as a network failure where if the acknowledgment is not received by the MLLP client, it stops sending messages and Oracle Integration is not notified.