Skip to content
LambogeniusDocs

HL7 v2 Codec for Azure Logic Apps

Getting schemas

Generate schemas from HL7's v2.xml with the free generator, or use your existing BizTalk-style schemas.

Service provider/serviceProviders/lamboHl7CodecLicensed together with the HL7 MLLP Connector. One token covers both.

Generate them from HL7's v2.xml schemas

HL7 International publishes XML schemas for HL7 v2. Download them from hl7.org with your own HL7 account, then generate one self-contained XSD per message structure with the free HL7 v2 Schema Generator for VS Code. It writes straight into your Logic App's Artifacts/Schemas, locally, with BizTalk-style names such as PID_5_PatientName.

  • Output: <version>/ADT_A01_25.xsd with root ADT_A01_25, so several versions can share a folder. A plain-root option writes ADT_A01.
  • Cardinality (required fields, repeats, required segments and groups) comes from v2.xml. Coded values aren't restricted, because v2.xml has no table enumerations.
  • Namespace http://lambogenius.com/HealthCare/HL7/2X on the root, configurable.
  • No VS Code? The open-source repository also has a PowerShell 7 script and a .NET command line.
HL7's content

The v2.xml schemas, and the XSDs generated from them, are derived from HL7 International's content. Use them under your own HL7 license terms, and don't redistribute them.

Or use the schemas you have

BizTalk HL7 schemas that include MSH in the message (or follow the rules on Schemas) work as they are. Schemas that enumerate HL7 table values make validation reject codes outside those tables; turn validateXml off or extend the tables if your partners send local codes.