Hear from Salesforce leaders on how to create and deploy Agentforce agents.
Register now
Contact Us 1-800-596-4880
  1. Homepage
  2. Release Notes

  3. HL7 EDI Connector Release Notes - Mule 4

HL7 EDI Connector Release Notes - Mule 4

Support Category: PremiumLeaving the Site

4.2.12

January 22, 2024

What’s New

  • This connector is now compatible with Java 17.

Compatibility

Application/Service Version

Mule

4.1.1 and later

Anypoint Studio

7.1.0 and later

OpenJDK

8, 11, and 17

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

Fixed Issues

Issue Resolution ID

The connector can now read and write subcomponents of subcomponents.

W-14454305

4.2.11

July 11, 2023

What’s New

  • The org.yaml.snakeyaml library is upgraded to version 2.0 to address reported security vulnerabilities.

Compatibility

Application/Service Version

Mule

4.1.1 and later

Anypoint Studio

7.1.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

Fixed Issues

Issue Resolution ID

The carriage return and line feed characters are now escaped correctly.

W-13478241, W-13478259

4.2.10

October 20, 2022

What’s New

  • The org.yaml.snakeyaml library is upgraded to version 1.32 to address reported security vulnerabilities.

Compatibility

Application/Service Version

Mule

4.1.1 and later

Anypoint Studio

7.1.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

4.2.9

March 28, 2022

Compatibility

Application/Service Version

Mule

4.1.1 and later

Anypoint Studio

7.1.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

Fixed Issues

Issue ID

The connector can now use custom ACK .esl files.

W-10801278

4.2.8

March 3, 2022

Compatibility

Application/Service Version

Mule

4.1.1 and later

Anypoint Studio

7.1.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

Fixed Issues

Issue ID

Extension segments are now written back into an HL7 message if they are present in the payload map.

W-10671665

The Disable numeric prefixes for data keys configuration field now works as expected for the Write operation when set to false.

W-10581096

4.2.7

January 3, 2022

Compatibility

Application/Service Version

Mule

4.1.1 and later

Anypoint Studio

7.1.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

Fixed Issues

Issue ID

Upgraded library dependencies.

CONN-9577

4.2.6

December 20, 2021

Compatibility

Application/Service Version

Mule

4.1.1 and later

Anypoint Studio

7.1.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

Fixed Issues

Issue ID

Upgraded library dependencies.

CONN-9577

4.2.5

December 1, 2021

Compatibility

Application/Service Version

Mule

4.1.1 and later

Anypoint Studio

7.1.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

Fixed Issues

Issue ID

When a segment was reused in an Lax schema, the parser sometimes incorrectly threw a segment out of order error.

SE-23264

When a segment had no position assigned in the schema, the parser sometimes assigned an incorrect position, which caused a segment out of order error.

SE-23264

When a too many segment loops error occurred, the segment and its position were not always accurate.

CONN-9426

4.2.4

October 25, 2021

Compatibility

Application/Service Version

Mule

4.1.1 and later

Anypoint Studio

7.1.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

Fixed Issues

Issue ID

When subcomponents were present in an element of the varies type, the index of the subcomponent did not reset correctly.

SE-22918

The segment position provided in the Errors list was not always correct.

SE-23050

When the MSH segment contained an error, the parser did not add it to the Errors list.

SE-23050

In some cases, the parser incorrectly added +1 to the Segment Sequence (ELD-02) in the Acknowledgment.

SE-23050

The parse property Fail when a value length is outside an allowed range did not work as expected.

CONN-8933

The parse property Fail when an invalid character is in a value did not work as expected.

CONN-8933

The parse property Fail when there are too many repeats of a value did not work as expected.

CONN-8933

The parse property Fail when an unused segment is included in a message did not work as expected.

CONN-8933

The parse property Fail when there are too many repeats of a segment did not work as expected.

CONN-8933

When an invalid character error was present, the parser duplicated it in the Acknowledgment (ERR).

CONN-8933

4.2.3

October 4, 2021

Compatibility

Application/Service Version

Mule

4.1.1 and later

Anypoint Studio

7.1.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

Fixed Issues

Issue ID

When an element of type varies had a list of components and the first component was empty, the element was skipped and not parsed.

SE-22379

The connector did not report the error when the number of repeated segments or simple elements exceeded the count value.

SE-22794

The parser property Fail when there are too many repeats of a segment did not work as expected. Now the MSA01 (Acknowledgment Code) changes accordingly.

SE-22794

4.2.2

July 15, 2021

Compatibility

HL7 EDI Connector 4.2.2 is compatible with the following:

Application/Service Version

Mule

4.1.1 and later

Anypoint Studio

7.1.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

Fixed Issue

  • The Write operation did not generate error details in some cases. (SE-21190)

4.2.1

November 12, 2020

Compatibility

HL7 EDI Connector 4.2.1 is compatible with the following:

Application/Service Version

Mule

4.1.1 and later

Anypoint Studio

7.1.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

Fixed Issue

  • In certain error cases, the specific error was not displayed. (SE-18505)

  • An incorrect error message was generated when there was a field that contained a ~ character. (SE-18506)

4.2.0

October 15, 2020

Compatibility

HL7 EDI Connector v4.2.0 is compatible with the following:

Application/Service Version

Mule

4.1.1 and later

Anypoint Studio

7.1.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

Features

  • Added segment terminator character configuration support. Supported values: '\r' (CR) (default) and '\n' (LF)

4.1.1

May 4, 2020

Compatibility

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

Application/Service Version

Mule

4.1.1 and later

Anypoint Studio

7.1.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

Fixed Issue

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

  • Upgraded Scala to version 2.12.10

  • Upgraded Log4j to version 2.11.0

4.1.0

April 14, 2020

Compatibility

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

Application/Service Version

Mule

4.1.1 and later

Anypoint Studio

7.1.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

Fixed Issue

  • Added support for repeated values in extensions segments (Z* segments). (SE-15044)

  • Corrected parser handling of repeated values where some repeats are empty. (SE-15176)

4.0.4

February 13, 2020

Compatibility

HL7 EDI Connector v4.0.4 is compatible with the following:

Application/Service Version

Mule

4.1.0 and later

Anypoint Studio

7.1.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

Fixed Issue

  • Incompatibilities with JRE 11 have been fixed. (SE-14449).

4.0.3

December 14, 2019

Compatibility

HL7 EDI Connector v4.0.3 is compatible with the following:

Application/Service Version

Mule

4.1.0 and later

Anypoint Studio

7.1.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

Fixed Issues

  • Corrected the handling of eventMessageMap paths with a leading '/' character, as it was not found on the classpath. (SE-13668)

  • Corrected the MSH handling for versions 2.2 and 2.3 which resulted in the error: "com.mulesoft.flatfile.lexical.LexicalException: No message structure found in eventMessageMap for message null/null". (SE-13668)

  • All standard schemas now use a minimum length of 0 for simple values, rather than 1. Using a 1 caused empty strings to be padded with a blank when written to the output. (SE-12757)

  • Corrected the ORU_R01 schema structure definition in version 2.4, as this was unusable due to repeated definitions. (SE-11806) The hl7-simplify-4.0.2.jar execution was not working properly. (SE-14016)

Known Issues

Schemas are present for message structures for older versions (up to and including 2.3.1) that are not used in HL7. HL7 reuses message structures for different event types. For example, there is no ADT_A08 message structure because this is a combination of an ADT message type for A08 event reuses the ADT_A01 message structures. This issue is considered of low severity because it does not result in any errors in either sending or receiving data, but may mislead the user to set an incorrect message structure name for the MSH.9/MSG.3 "message structure" field of the header. It is left as a known issue so as to avoid breaking existing applications.

4.0.2

December 14, 2018

Compatibility

HL7 EDI Connector v4.0.2 is compatible with the following:

Application/Service Version

Mule

4.1.0 and later

Anypoint Studio

7.1.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

Fixed Issues

  • Corrected DataSense metadata. Removed the "Heading" level shown in DataSense that was not actually used in data.

  • 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 the schema version.

4.0.1

August 30, 2018

Compatibility

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

Application/Service Version

Mule

4.1.0 and later

Anypoint Studio

7.1.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

Fixed Issues

  • Added delimiter character configuration support

  • Corrected writer to use delimiters from configuration if not supplied in write data map

  • Fixed issue with write exceptions being lost

  • Corrected ACK schema to use list for repeating composite values where appropriate.

Known Issues

  • HL7 EDI Connector doesn’t support Design Center.

4.0.0

January 31, 2018

This release adapts HL7 for use with Mule 4 and Studio 7.

Known Issues

  • Setting default delimiter characters for writing is not supported in the configuration. You can set the delimiters in the output data.

  • Anypoint Studio requires more memory than allowed by the default settings to support HL7 schema definitions. See the Connector Guide for details on changing the Studio memory settings.

  • HL7 EDI Connector doesn’t support Design Center.

See Also