Skip to content
LambogeniusDocs

HL7 MLLP Connector for Azure Logic Apps

Security

Where message data goes, secrets, encryption in transit, and locking down the gateway.

Service provider/serviceProviders/lamboHl7MllpLicensed together with the HL7 v2 Codec. One token covers both.

PHI stays in your environment

  • No calls home: message content and the license check stay inside your environment.
  • Keep secrets out of files: trigger URLs (they contain a signature), API keys, certificates and connection strings belong in Key Vault references or environment variables.
  • Encrypt in transit: use TLS for MLLP, turn on the TLS requirement, pin partner certificates, and keep the gateway's environment VNet-internal (the Bicep default).
  • Limit the gateway: require an API key, list only the destinations you need, and leave untrusted-certificate options off outside tests.
  • Logs carry metadata (control ID, message type, sizes, endpoints), not message text. Negative ACKs never include internal error details.
  • Run history holds the full message in trigger outputs and action inputs. Turn on Secure inputs/outputs on the trigger and actions to keep it out.