HL7 EDI Connector Release Notes - Mule 3

Anypoint Connector for HL7 EDI (HL7 EDI Connector) enables you to convert HL7 ER7 messages to and from DataWeave-compatible representations using lists and maps.

Support Category: Premium

3.1.7

January 4, 2022

Fixed Issues

Upgraded library dependencies. (CONN-9671)

Compatability

HL7 EDI Connector v3.1.7 is compatible with the following:

Application/Service Version

Mule

3.6.0 and later

Anypoint Studio

5.0.0 and later

HL7

v2.1, v2.2, v2.3.1, v2.3, v2.4, v2.5, v2.5.1, v2.6, 2.7, 2.7.1, 2.8, 2.8.1

3.1.6

September 7, 2020

Fixed Issues

  • Fixed the issue that caused the connector to fail when running on earlier versions of Mule runtime engine, even when the Fail when value length outside allowed range was disabled (SE-16869)

  • Added backward compatibility for Log4j to avoid conflicts with a previous Mule runtime engine, such as 3.8.3 EE (SE-16890)

Compatability

HL7 EDI Connector v3.1.6 is compatible with the following:

Application/Service Version

Mule

3.6.0 and later

Anypoint Studio

5.0.0 and later

HL7

v2.1, v2.2, v2.3.1, v2.3, v2.4, v2.5, v2.5.1, v2.6, 2.7, 2.7.1, 2.8, 2.8.1

3.1.5

August 26, 2020

Fixed Issues

  • Corrected error position for REPETITION (~) type elements (SE-16890)

  • Downgraded the Scala compiler version to 2.11.7 for compatibility with the Scala version used by DataWeave. (CONN-6860)

Compatability

HL7 EDI Connector v3.1.5 is compatible with the following:

Application/Service Version

Mule

3.6.0 and later

Anypoint Studio

5.0.0 and later

HL7

v2.1, v2.2, v2.3.1, v2.3, v2.4, v2.5, v2.5.1, v2.6, 2.7, 2.7.1, 2.8, 2.8.1

3.1.4

July 16, 2020

Fixed Issue

Upgraded Scala Compiler version to 2.12.10 and log4j version to 2.11.0 (CONN-6428).

Compatability

HL7 EDI Connector v3.1.4 is compatible with the following:

Application/Service Version

Mule

3.6.0 and later

Anypoint Studio

5.0.0 and later

HL7

v2.1, v2.2, v2.3.1, v2.3, v2.4, v2.5, v2.5.1, v2.6, 2.7, 2.7.1, 2.8, 2.8.1

3.1.3

June 17, 2020

Fixed Issue

When (~) arrays were sent with null values, the connector parser skipped the rest of the segment. (SE-16354).

Compatability

HL7 EDI Connector v3.1.3 is compatible with the following:

Application/Service Version

Mule

3.6.0 and later

Anypoint Studio

5.0.0 and later

HL7

v2.1, v2.2, v2.3.1, v2.3, v2.4, v2.5, v2.5.1, v2.6, 2.7, 2.7.1, 2.8, 2.8.1

3.1.2

June 8, 2020

Fixed Issue

Added specific trace fields for errors.

Compatability

HL7 EDI Connector v3.1.2 is compatible with the following:

Application/Service Version

Mule

3.6.0 and later

Anypoint Studio

5.0.0 and later

HL7

v2.1, v2.2, v2.3.1, v2.3, v2.4, v2.5, v2.5.1, v2.6, 2.7, 2.7.1, 2.8, 2.8.1

3.1.1

December 14, 2018

Fixed Issues

  • Added support for all standard escape sequences. However, escape sequences that change character encoding are not supported.

  • Fixed writing a String value to a timestamp field. By default this expects XMLGregorianCalendar, but a correctly formatted String is also supported.

  • Corrected handling of MSH-18 character encoding field, allowing either a simple String or a list of Strings, depending on schema version.

  • Fixed validateHL7Version configuration option.

Compatability

HL7 EDI Connector v3.1.x is compatible with the following:

Application/Service Version

Mule

3.6.0 and later

Anypoint Studio

5.0.0 and later

HL7

v2.1, v2.2, v2.3.1, v2.3, v2.4, v2.5, v2.5.1, v2.6, 2.7, 2.7.1, 2.8, 2.8.1

3.1.0

January 3, 2018

Version 3.1.0 provides bug fixes and greatly improved usability.

HL7 EDI Connector v3.1.0 is compatible with the following:

Application/Service Version

Mule

3.6.0 and later

Anypoint Studio

5.0.0 and later

HL7

v2.1, v2.2, v2.3.1, v2.3, v2.4, v2.5, v2.5.1, v2.6, 2.7, 2.7.1, 2.8, 2.8.1

New Features

  • Separate sets of schemas for lax validation (all data elements treated as strings; length, repetition count, and usage restrictions not enforced).

  • Drops numeric prefixes used on segment keys.

  • Uses MSH segment definition from (first) configured schema.

  • Allows configuration of ACK message schema.

  • Provides a tool to generate a simplified schema definition based on one or more sample documents.

Fixed Issues

  • Apply configured character encoding when writing.

  • Throw an exception when the wrong data type is found when writing (previously just stopped the write).

  • Correct handling of message structure segment groups with optional leading segments.

  • Correct handling of choice groupings of segments.

Backward Compatibility

Version 3.0.0 always used numeric position prefixes on segment keys (such as "01_MSH"). This has been disabled by default in 3.1.0, so that the segment key is normally just the segment tag (modified with a numeric suffix, if necessary because the segment is used in multiple locations within the same level of the message structure). For compatibility with 3.0.0 mappings you can turn off the "Disable numeric prefixes for data keys" configuration option (identKeys="false").

Known Issues

  • The validateHL7Version configuration option is not working and results in a NullPointerException when trying to read a message with this option enabled.

3.0.0

January 6, 2017

Release notes for version 3.0 of the HL7 EDI Connector. Anypoint Connector for HL7 is a collection of features that facilitates integration with healthcare systems by providing the tools needed to easily create, read, and transform HL7 version v2.x messages within Mule.

HL7 EDI Connector v3.0.0 is compatible with the following:

Application/Service Version

Mule

3.6.0 and later

Anypoint Studio

5.0.0 and later

HL7

v2.1, v2.2, v2.3, v2.3.1, v2.4, v2.5, v2.5.1, v2.6, v2.7, v2.7.1, v2.8, v2.8.1

  • Extension segments supported using overlay or custom schemas, or by generic handling for segments matching a pattern.

  • Parsing throws an exception when the message is not properly formatted or an error occurs when reading the input stream.

  • Fatal errors in parsing (as per configuration) result in acknowledgment code 'AR' (for Application Reject) in the ACK message generated by the parse; non-fatal errors result in acknowledgment code 'AE'.

Fixed Issues

There are no bug fixes in this release.