# mulesoft HL7 MLLP Connector - Full Documentation --- product: HL7 MLLP Connector version: 2.2 is-latest-version: true --- # HL7 MLLP Connector 2.2 > For the full documentation index, see: https://docs.mulesoft.com/llms.txt Anypoint Connector HL7 Minimal Lower-Layer Protocol (MLLP) Connector (HL7 MLLP Connector) provides connectivity and parsing functionality for HL7 MLLP messages. For compatibility information and fixed issues, see the HL7 MLLP Connector Release Notes. ## Before You Begin To use this connector, you must be familiar with: - Anypoint Connectors - Mule runtime engine (Mule) - Elements and global elements in a Mule flow - Creating a Mule app using Anypoint Studio or Anypoint Code Builder - HL7 MLLP Connector To use HL7 MLLP Connector, you must have: - Purchased a MuleSoft license for HL7. Contact your Account Representative about purchasing a license. - Anypoint Studio or Anypoint Code Builder ## See Also - [HL7 MLLP Connector Release Notes](https://docs.mulesoft.com/release-notes/connector/hl7-mllp-connector-release-notes-mule-4) - [HL7 MLLP Connector in Anypoint Exchange](https://www.mulesoft.com/exchange/com.mulesoft.connectors/mule-hl7-mllp-connector/) --- product: HL7 MLLP Connector version: 2.2 is-latest-version: true --- # HL7 MLLP Connector 2.2 - Examples > For the full documentation index, see: https://docs.mulesoft.com/llms.txt Use these examples to read and write HL7 messages over the Minimum Lower-Layer Protocol (MLLP). ## Set Global Properties Set these global properties before using the examples: - Delimiter The standard HL7 delimiter value that separates MLLP messages. It is a hexadecimal 0x1C character also known as FS. Applications in some clinics use a different delimiter value in this field. The standard value in the HL7 MLLP connector is shown as `001C`. - Host Sets the socket host address - Port Sets the socket port For an advanced connection, complete these fields: - Reuse address Whether to reuse the configured socket or fail when trying to bind to the socket - Send TCP With No Delay Whether or not to transmit data immediately, or collect data for greater efficiency before sending - Linger How long (in milliseconds) the socket takes to correctly close so any remaining data transmits. - Keep alive Whether to close open socket connections that are unused for a long period with an unavailable connection. - Fail on unresolved host Whether the socket fails during its creation if the host (set on the endpoint) cannot be resolved. - TLS tab Configure a new TLS configuration. Its presence implies the use of SSLServerSocket instead of plain TCP. - Set the send or receive buffer size. ## Example - Read and Write Message This example workflow sequentially invokes read and write HL7 messages over MLLP: - writer-flow Sends the given message through the socket to be received by the reader-flow - reader-flow Receive a MLLP message, and log the message - The app, index, styles, app-config, rest-service, order-controller, and write-order are used to load static resources related to the user interface. ## Read and Write HL7 Messages Over MLLP ```xml ``` ## See Also - [Introduction to Anypoint Connectors](https://docs.mulesoft.com/connectors/introduction/introduction-to-anypoint-connectors) - [Salesforce Help](https://help.salesforce.com) --- product: HL7 MLLP Connector version: 2.2 is-latest-version: true --- # HL7 MLLP Connector Reference > For the full documentation index, see: https://docs.mulesoft.com/llms.txt ## MLLP Listener Configuration
NameTypeDescriptionDefault ValueRequired

Name

String

Name for this configuration. Connectors reference the configuration with this name.

x

Connection

Connection types that can be provided to this configuration.

x

Expiration Policy

Configures the minimum amount of time that a dynamic configuration instance can remain idle before Mule considers it eligible for expiration. This does not mean that the instance expires at the exact moment that it becomes eligible. Mule purges the instances when appropriate.

### MLLP Listener Connection Type
NameTypeDescriptionDefault ValueRequired

Delimiter

String

Character code that separates MLLP messages. By default, MLLP uses 001C.

x

TLS Configuration

Uses SSLServerSocket instead of plain TCPServerSocket for accepting new SSL connections.

Port

Number

Connection’s port number.

x

Host

String

Connection’s host name.

x

Reconnection

Configures a reconnection strategy to use when a connector operation fails to connect to an external server.

Send Buffer Size

Number

Size of the buffer used when sending data, in bytes. This is set on the socket.

Receive Buffer Size

Number

Size of the buffer used when receiving data, in bytes. This is set on the socket.

Client Timeout

Number

SO_TIMEOUT value on the socket, which indicates the amount of time, in milliseconds, that the socket waits in a blocking operation before it fails. A value of 0 means that the socket waits indefinitely.

0

Reuse Address

Boolean

If true, SO_REUSEADDRESS is set on the socket before binding. This helps reduce address already in use errors when a socket is reused.

true

Send TCP With No Delay

Boolean

If true, transmitted data is sent immediately instead of collected together for greater efficiency. This value defaults to true even though the socket default is false because reducing the amount of network traffic over latency is not usually a concern today.

true

Linger

Number

SO_LINGER value, in milliseconds, which indicates how long the socket takes to close so that remaining data is transmitted correctly.

Keep Alive

Boolean

If true, enables SO_KEEPALIVE behavior on open sockets. This automatically checks socket connections that are open, but unused, for long periods and closes them if the connection becomes unavailable. This is set on the socket. It is used by a server socket to control whether connections to the server are kept alive before they are recycled.

false

Fail On Unresolved Host

Boolean

Whether the socket fails during its creation if the host set on the endpoint can’t be resolved. Set this value to false to allow unresolved hosts (useful when connecting through a proxy).

true

Connection Count

Number

Number of connections accepted at one time. This value can be an integer or DataWeave expression. An empty value, negative value, or value of 0 indicates that the connector can accept an unlimited number of connections.

Server Timeout

Number

SO_TIMEOUT value when the socket is used as a server. This is the timeout that applies to the accept operation. A value of 0 (the ServerSocket default) causes the accept to wait indefinitely if no connection arrives.

Receive Backlog

Number

Maximum queue length for incoming connections.

50

## Request Configuration Configuration for requester sockets.
NameTypeDescriptionDefault ValueRequired

Name

String

Name for this configuration. Connectors reference the configuration with this name.

x

Connection

Connection types that can be provided to this configuration.

x

Expiration Policy

Configures the minimum amount of time that a dynamic configuration instance can remain idle before Mule considers it eligible for expiration. This does not mean that the instance expires at the exact moment that it becomes eligible. Mule purges the instances when appropriate.

### MLLP Requester Connection Type
NameTypeDescriptionDefault ValueRequired

Local Address Settings

Address that a socket should bind to.

TLS Configuration

Configuration for TLS, which can be used from both the client and server sides.

Port

Number

Connection’s port number.

x

Host

String

Connection’s host name.

x

Reconnection

Configures a reconnection strategy to use when a connector operation fails to connect to an external server.

Pooling Profile

Characteristics of the connection pool.

Send Buffer Size

Number

Size of the buffer used when sending data, in bytes. This is set on the socket.

Receive Buffer Size

Number

Size of the buffer used when receiving data, in bytes. This is set on the socket.

Client Timeout

Number

SO_TIMEOUT value on sockets. This indicates the amount of time, in milliseconds, that the socket waits in a blocking operation before failing. A value of 0 means waiting indefinitely.

0

Reuse Address

Boolean

If true, SO_REUSEADDRESS is set on the socket before binding. This helps reduce address already in use errors when a socket is reused.

true

Send TCP With No Delay

Boolean

If true, transmitted data is sent immediately instead of collected together for greater efficiency. This value defaults to true even though the socket default is false because reducing the amount of network traffic over latency is not usually a concern today.

true

Linger

Number

SO_LINGER value, which indicates how long, in milliseconds, the socket takes to close so that any remaining data is transmitted correctly.

Keep Alive

Boolean

If true, enables SO_KEEPALIVE behavior on open sockets. This automatically checks socket connections that are open, but unused, for long periods and closes them if the connection becomes unavailable. This is set on the socket and is used by a server socket to control whether connections to the server are kept alive before they are recycled.

false

Fail On Unresolved Host

Boolean

If true, the socket fails during its creation if the host set on the endpoint can’t be resolved. Set this value to false to allow unresolved hosts (useful when connecting through a proxy).

true

Connection Timeout

Number

Number of milliseconds to wait until an outbound connection to a remote server is successfully created. Defaults to 30 seconds.

30000

## Sources - [MLLP Listener](#mllp-listener) ### MLLP Listener `` Listens for the socket connections of the given protocol in the configured host and port. When a new connection is received, this source schedules a socket worker to handle the communication for that connection.
NameTypeDescriptionDefault ValueRequired

Configuration

String

Name of the configuration to use.

x

Output Mime Type

String

MIME type of the payload that this operation outputs.

Output Encoding

String

Encoding for the payload that this operation outputs.

Primary Node Only

Boolean

Whether this source executes only on the primary node when running in a cluster.

Streaming Strategy

Configures how Mule processes streams. Repeatable streams are the default behavior.

Redelivery Policy

Configures the redelivery policy for executing requests that generate errors. You can add a redelivery policy to any source in a flow.

Reconnection Strategy

Reconnection strategy to use.

#### Output

Type

Binary

Attributes Type

#### Associated Configurations - [MLLP Listener Configuration](#mllp-listener-config) ## Operations - [Send](#send) ### Send `` Sends the data using the client associated with the MLLP Requester connection.
NameTypeDescriptionDefault ValueRequired

Configuration

String

Name of the configuration to use.

x

Content

Binary

Data to serialize and send through the socket.

#[payload]

Reconnection Strategy

Reconnection strategy to use.

#### Associated Configurations - [Request Configuration](#request-config) #### Throws - MLLP:CONNECTIVITY - MLLP:LISTENING\_ERROR - MLLP:RETRY\_EXHAUSTED - MLLP:SECURITY - MLLP:SENDING\_ERROR - MLLP:UNKNOWN ## Object Types - [CRL File](#crl-file) - [Custom OCSP Responder](#custom-ocsp-responder) - [Expiration Policy](#ExpirationPolicy) - [Immutable Socket Attributes](#ImmutableSocketAttributes) - [Keystore](#KeyStore) - [Pooling Profile](#PoolingProfile) - [Reconnect](#reconnect) - [Reconnect Forever](#reconnect-forever) - [Reconnection](#Reconnection) - [Redelivery Policy](#RedeliveryPolicy) - [Repeatable File Store Stream](#repeatable-file-store-stream) - [Repeatable In Memory Stream](#repeatable-in-memory-stream) - [Socket Connection Settings](#SocketConnectionSettings) - [Standard Revocation Check](#standard-revocation-check) - [TLS](#Tls) - [Truststore](#TrustStore) ### CRL File Specifies the location of the certification revocation list (CRL) file.
FieldTypeDescriptionDefault ValueRequired

Path

String

Path to the CRL file.

### Custom OCSP Responder Configures a custom OCSP responder for certification revocation checks.
FieldTypeDescriptionDefault ValueRequired

Url

String

URL of the OCSP responder.

Cert Alias

String

Alias of the signing certificate for the OCSP response. If specified, the alias must be in the truststore.

### Expiration Policy Configures an expiration policy strategy.
FieldTypeDescriptionDefault ValueRequired

Max Idle Time

Number

Configures the maximum amount of time that a dynamic configuration instance can remain idle before Mule considers it eligible for expiration.

Time Unit

Enumeration, one of:

  • NANOSECONDS

  • MICROSECONDS

  • MILLISECONDS

  • SECONDS

  • MINUTES

  • HOURS

  • DAYS

Time unit for the Max Idle Time field.

### Immutable Socket Attributes
FieldTypeDescriptionDefault ValueRequired

Host Address

String

Address of the host where the requests are sent.

Host Name

String

Name of the host where the requests are sent.

Local Certificates

Array of Any

SSL local certificates. If the socket is not an SSL socket, this value is null.

Peer Certificates

Array of Any

SSL peer certificates. If the socket is not an SSL socket, this value is null.

Port

Number

Port to which the requests are sent.

### Keystore Configures the keystore for the TLS protocol. The keystore you generate contains a private key and a public certificate.
FieldTypeDescriptionDefault ValueRequired

Path

String

Path to the keystore. Mule resolves the path relative to the current classpath and file system.

Type

String

Type of keystore.

Alias

String

Alias of the key to use when the keystore contains multiple private keys. By default, Mule uses the first key in the file.

Key Password

String

Password used to protect the private key.

Password

String

Password used to protect the keystore.

Algorithm

String

Algorithm used by the keystore.

### Pooling Profile Configures the pooling profile characteristics.
FieldTypeDescriptionDefault ValueRequired

Max Active

Number

Maximum number of Mule components that are active in a session at one time. When set to a negative value, there is no limit to the number of Mule components that are active at one time. When this value is exceeded, the pool is considered exhausted.

Max Idle

Number

Maximum number of Mule components that can sit idle in the pool at any time. When set to a negative value, there is no limit.

Max Wait

Number

Number of milliseconds to wait for a pooled component to become available when the pool is exhausted and the Exhausted Action is set to WHEN_EXHAUSTED_WAIT.

Min Eviction Millis

Number

Minimum amount of time that an object can sit idle in the pool before it’s eligible for eviction. When set to a negative value, no objects are evicted from the pool due to idle time alone.

Eviction Check Interval Millis

Number

Number of milliseconds between runs of the object evictor. When set to a negative value, no object evictor is executed.

Exhausted Action

Enumeration, one of:

  • WHEN_EXHAUSTED_GROW

  • WHEN_EXHAUSTED_WAIT

  • WHEN_EXHAUSTED_FAIL

Behavior of the Mule component pool when the pool is exhausted. Possible values are:

  • WHEN_EXHAUSTED_FAIL

    Throws a NoSuchElementException.

  • WHEN_EXHAUSTED_WAIT

    Blocks by invoking Object.wait(long) until a new or idle object is available.

  • WHEN_EXHAUSTED_GROW

    Creates a new Mule instance and returns it, which makes the Max Active value ineffective.

    If Max Wait is positive, Mule blocks for at most that many milliseconds, after which it throws a NoSuchElementException. If Max Wait is a negative, Mule blocks indefinitely.

Initialization Policy

Enumeration, one of:

  • INITIALISE_NONE

  • INITIALISE_ONE

  • INITIALISE_ALL

Determines how components in a pool should be initialized. Possible values are:

  • INITIALISE_NONE

    Doesn’t load any components into the pool on startup.

  • INITIALISE_ONE

    Loads one initial component into the pool on startup.

  • INITIALISE_ALL

    Loads all components into the pool on startup.

Disabled

Boolean

If true, pooling is disabled.

### Reconnect Configures a standard reconnection strategy, which specifies how often to reconnect and how many reconnection attempts the connector source or operation can make.
FieldTypeDescriptionDefault ValueRequired

Frequency

Number

How often to reconnect, in milliseconds.

Blocking

Boolean

If false, the reconnection strategy runs in a separate, non-blocking thread.

Count

Number

How many reconnection attempts to make.

### Reconnect Forever Configures a forever reconnection strategy by which the connector source or operation attempts to reconnect at a specified frequency for as long as the Mule app runs.
FieldTypeDescriptionDefault ValueRequired

Frequency

Number

How often to reconnect, in milliseconds.

Blocking

Boolean

If false, the reconnection strategy runs in a separate, non-blocking thread.

### Reconnection Configures a reconnection strategy for an operation.
FieldTypeDescriptionDefault ValueRequired

Fails Deployment

Boolean

What to do if, when an app is deployed, a connectivity test does not pass after exhausting the associated reconnection strategy:

  • true

    Allow the deployment to fail.

  • false

    Ignore the results of the connectivity test.

Reconnection Strategy

Reconnection strategy to use.

### Redelivery Policy Configures the redelivery policy for executing requests that generate errors. You can add a redelivery policy to any source in a flow.
FieldTypeDescriptionDefault ValueRequired

Max Redelivery Count

Number

Maximum number of times that a redelivered request can be processed unsuccessfully before returning a REDELIVERY_EXHAUSTED error.

Use Secure Hash

Boolean

If true, Mule uses a secure hash algorithm to identify a redelivered message.

Message Digest Algorithm

String

Secure hashing algorithm to use if the Use Secure Hash field is true. If the payload of the message is a Java object, Mule ignores this value and returns the value that the payload’s hashCode() returned.

Id Expression

String

One or more expressions that determine when a message was redelivered. This field can be set only if the Use Secure Hash field is false.

Object Store

ObjectStore

Configures the object store that stores the redelivery counter for each message.

### Repeatable File Store Stream Configures the repeatable file-store streaming strategy by which Mule runtime keeps a portion of the stream content in memory. If the stream content is larger than the configured buffer size, Mule backs up the buffer’s content to disk and then clears the memory.
FieldTypeDescriptionDefault ValueRequired

Max In Memory Size

Number

Maximum amount of memory that the stream can use for data. If the amount of memory exceeds this value, Mule buffers the content to disk. To optimize performance:

  • Configure a larger buffer size to avoid the number of times Mule needs to write the buffer on disk. This increases performance, but it also limits the number of concurrent requests your application can process, because it requires additional memory.

  • Configure a smaller buffer size to decrease memory load at the expense of response time.

Buffer Unit

Enumeration, one of:

  • BYTE

  • KB

  • MB

  • GB

Unit for the Max In Memory Size field.

### Repeatable In Memory Stream Configures the in-memory streaming strategy by which the request fails if the data exceeds the maximum buffer size. Always run performance tests to find the optimal buffer size for your specific use case.
FieldTypeDescriptionDefault ValueRequired

Initial Buffer Size

Number

Initial amount of memory to allocate to the data stream. If the streamed data exceeds this value, the buffer expands by Buffer Size Increment, with an upper limit of the Max In Memory Size value.

Buffer Size Increment

Number

Amount by which the buffer size expands if it exceeds its initial size. Setting a value of 0 or lower specifies that the buffer can’t expand.

Max Buffer Size

Number

Maximum size of the buffer. If the buffer size exceeds this value, Mule raises a STREAM_MAXIMUM_SIZE_EXCEEDED error. A value of less than or equal to 0 means no limit.

Buffer Unit

Enumeration, one of:

  • BYTE

  • KB

  • MB

  • GB

Unit for the Initial Buffer Size, Buffer Size Increment, and Max Buffer Size fields.

### Socket Connection Settings
FieldTypeDescriptionDefault ValueRequired

Port

Number

Connection’s port number.

x

Host

String

Connection’s host name.

x

### Standard Revocation Check Configures standard revocation checks for TLS certificates.
FieldTypeDescriptionDefault ValueRequired

Only End Entities

Boolean

Which elements to verify in the certificate chain:

  • true

    Verify only the last element in the certificate chain.

  • false

    Verify all elements in the certificate chain.

Prefer Crls

Boolean

How to check certificate validity:

  • true

    Check the Certification Revocation List (CRL) for certificate validity.

  • false

    Use the Online Certificate Status Protocol (OCSP) to check certificate validity.

No Fallback

Boolean

Whether to use the secondary method to check certificate validity:

  • true

    Use the method that wasn’t specified in the Prefer Crls field (the secondary method) to check certificate validity.

  • false

    Do not use the secondary method to check certificate validity.

Soft Fail

Boolean

What to do if the revocation server can’t be reached or is busy:

  • true

    Avoid verification failure.

  • false

    Allow the verification to fail.

### TLS Configures TLS to provide secure communications for the Mule app.
FieldTypeDescriptionDefault ValueRequired

Enabled Protocols

String

Comma-separated list of protocols enabled for this context.

Enabled Cipher Suites

String

Comma-separated list of cipher suites enabled for this context.

Trust Store

Configures the TLS truststore.

Key Store

Configures the TLS keystore.

Revocation Check

Configures a revocation checking mechanism.

### Truststore Configures the truststore for TLS.
FieldTypeDescriptionDefault ValueRequired

Path

String

Path to the truststore. Mule resolves the path relative to the current classpath and file system.

Password

String

Password used to protect the truststore.

Type

String

Type of truststore.

Algorithm

String

Encryption algorithm that the truststore uses.

Insecure

Boolean

If true, Mule stops performing certificate validations. Setting this to true can make connections vulnerable to attacks.

## See Also - [Introduction to Anypoint Connectors](https://docs.mulesoft.com/connectors/introduction/introduction-to-anypoint-connectors) - [Salesforce Help](https://help.salesforce.com) --- product: HL7 MLLP Connector version: 2.2 is-latest-version: true --- # Using Anypoint Studio to Configure HL7 MLLP Connector > For the full documentation index, see: https://docs.mulesoft.com/llms.txt Anypoint Studio (Studio) editors help you design and update your Mule applications, properties, and configuration files. To add and configure a connector in Studio: 1. [Create a Mule project](#create-mule-project). 2. [Add the connector to your Mule project](#add-connector-to-project). 3. [Configure a source for the connector’s flow](#configure-source). 4. [Add a connector operation to the flow](#add-connector-operation). 5. [Configure a global element for the connector](#configure-global-element). When you run the connector, you can view the app log to check for problems in real time, as described in [View the App Log](#view-app-log). If you are new to configuring connectors in Studio, see [Using Anypoint Studio to Configure a Connector](https://docs.mulesoft.com/connectors/introduction/intro-config-use-studio). If, after reading this topic, you need additional information about the connector fields, see the [HL7 MLLP Reference](https://docs.mulesoft.com/hl7-mllp-connector/latest/hl7-mllp-connector-reference). ## Create a Mule Project In Studio, create a new Mule project in which to add and configure the connector: 1. In Studio, select **File > New > Mule Project**. 2. Enter a name for your Mule project and click **Finish**. ## Add the Connector to Your Mule Project Add HL7 EDI Connector to your Mule project to automatically populate the XML code with the connector’s namespace and schema location and add the required dependencies to the project’s `pom.xml` file: 1. In the **Mule Palette** view, click **(X) Search in Exchange**. 2. In the **Add Dependencies to Project** window, type `HL7 MLLP` in the search field. 3. Click **HL7 MLLP** in **Available modules**. 4. Click **Add**. 5. Click **Finish**. Adding a connector to a Mule project in Studio does not make that connector available to other projects in your Studio workspace. ## Configure a Source A source initiates a flow when a specified condition is met. You can configure HTTP Listener as the source for the HL7 EDI Connector to initiate a flow each time the listener receives a request on the configured host and port. To configure an HTTP Listener source, follow these steps: 1. In the **Mule Palette** view, select **HTTP > Listener**. 2. Drag **Listener** to the Studio canvas. 3. On the **Listener** configuration screen, optionally change the value of the **Display Name** field. 4. Specify a value for the **Path** field. 5. Click the plus sign (**+**) next to the **Connector configuration** field to configure a global element that can be used by all instances of the HTTP Listener source in the app. 6. On the **General** tab, specify connection information for the connector. 7. On the **TLS** tab, optionally specify the TLS information for the connector. 8. On the **Advanced** tab, optionally specify reconnection information, including a reconnection strategy. 9. Click **Test Connection** to confirm that Mule can connect with the specified server. 10. Click **OK**. ## Add a Connector Operation to the Flow When you add a connector operation to your flow, you are specifying an action for that connector to perform. To add an operation for HL7 EDI Connector, follow these steps: 1. In the **Mule Palette** view, select **HL7 MLLP** and then select the desired operation. 2. Drag the operation onto the Studio canvas to the right of the input source. ## Configure a Global Element for the Connector When you configure a connector, configure a global element that all instances of that connector in the app can use. Configuring a global element requires you to provide the authentication credentials that the connector requires to access the target HL7 MLLP system. To configure the global element for HL7 MLLP Connector, follow these steps: 1. Select the operation in the Studio canvas. 2. In the configuration screen for the operation, click the plus sign (**+**) next to the **Connector configuration** field to access the global element configuration fields. You can reference a configuration file that contains ANT-style property placeholders (recommended), or you can enter your authorization credentials in the global configuration properties. 3. On the **Advanced** tab, optionally specify reconnection information, including a reconnection strategy. 4. Click **Test Connection** to confirm that Mule can connect with the specified server. 5. Click **OK**. You also can create a TLS configuration, and you can set the timeout configuration and the buffer configuration. The Send operation the procedure is identical, except that you can set the Local Address Settings tab within the connector config with a different host, port, and delimiter that specifies the character used to separate messages. You can also set the send or receive buffer size. > [!NOTE] If your app is running at `mllp-rnnf.us-e1.cloudhub.io`, you can send HL7 messages over > MLLP to your Mule app to `mule-worker-mllp-rnnf.us-e1.cloudhub.io`. ## View the App Log To check for problems, you can view the app log as follows: - If you’re running the app from Anypoint Platform, the output is visible in the Anypoint Studio console window. - If you’re running the app using Mule from the command line, the app log is visible in your OS console. Unless the log file path is customized in the app’s log file (`log4j2.xml`), you can also view the app log in the default location `MULE_HOME/logs/.log`. ## Next Step You can try the [Examples](https://docs.mulesoft.com/hl7-mllp-connector/latest/hl7-mllp-connector-examples). ## See Also - [HL7 MLLP Connector Reference](https://docs.mulesoft.com/hl7-mllp-connector/latest/hl7-mllp-connector-reference) - [Salesforce Help](https://help.salesforce.com)