TIBCO ActiveMatrix BusinessWorks(TM) HL7 Plug-in 6.0.0 hotfix 3 has been released.

Products	Versions
TIBCO BusinessWorks HL7 Plug-in	-
Not Applicable	-

Description

Description:
TIBCO ActiveMatrix BusinessWorks(TM) HL7 Plug-in 6.0.0 hotfix 3 has been released.

You can download this Hot Fix from the TIBCO Product Support FTP server using your eSupport username and password, at

ftp://mft.tibco.com

Once you have successfully logged into the server, you will find the hotfix packages under

/AvailableDownloads/BusinessWorks/Plugins/HL7-BW-Plug-in/6.0.0/hotfix-03

Listed below is a summary of updates included. Please refer to the associated readme document for any additional information.

================================================================================

Closed Issues in 6.0.0_HF-003 (This Release)

HL-356

The plugin has thread safe issue during the high load operations.

Defect has been fixed.

================================================================================

Closed Issues in 6.0.0_HF-002

HL-346

The plug-in allowed you to customize timestamp format for the Parse Header

activity and the Generate ACK activity. You could set an option

ìtibco.env.HL7.MSH_ts_formatî in the tra file, such as the designer.tra file

and the bwengine.tra file (for TIBCO Administrator). The valid timestamp formats

were compatible with the formats on the http://www.w3.org/TR/NOTE-datetime website.

For example:

tibco.env.HL7.MSH_ts_format yyyyMMdd

tibco.env.HL7.MSH_ts_format yyyyMMddhhmmss

tibco.env.HL7.MSH_ts_format yyyy-MM/dd-hh:mm:ss

Implemented.

HL-345

The Translate HL7 activity supported the same input encoding that was supported

by the Foresight translator engine. The input_encoding field was added in the

Input tab. You should provide the correct encoding information for the

ìmsg_contentî input parameter (string).

Implemented.

Note:

Currently, the Foresight engine supports UTF-8, UTF-16, and ISO-8859-1 encodings

by default. If no input_encoding is provided, the Translate HL7 activity will use

the default JVM encoding to make the new project compatible with the old project.

The plug-in does not automatically detect the input encoding from the

"msg_content", therefore, you need to set the correct input encoding for

the translation.

HL-331

The translation performance of the plug-in was boosted from the previous version.

Implemented.

HL-329

The acknowledgements generated by the HL7 parseHeader activity were invalid.

There was a character "\r|" in the result which did not match the HL7 standard

format.

Defect has been fixed.

================================================================================

Closed Issues in 6.0.0_HF-001

HL-315

The following functionalities are implemented:

- The Generate ACK activity was added to generate acknowledgements for the

input HL7 messages.

- The HL7ListenAndSend example was packaged with the installation of the

plug-in to help you understand how to use the Generate ACK activity.

- More HL7 error codes were defined.

The following is an introduction of the Generate ACK activity:

- Configuration tab

The Configuration tab of the Generate ACK activity describes the

information similar to the Parse HL7 Header activity. For detailed

information of each field in the Configuration tab, see "Parse

HL7 Header" in TIBCO ActiveMatrix BusinessWorks Plug-in for HL7

User's Guide.

- Input tab

The descriptions of each field in the Input tab are as follows:

- hl7Message

The incoming HL7 message for generating an ACK or NAK message.

- defaultMSHwhenHeaderInvalid

If the MSH segment of the input HL7 message is invalid, specify a

valid MSH segment for the input HL7 message in this field. If you

do not provide a valid MSH segment, the following value will be

used as a default value:

"MSH|^~\\&|||||||ACK||P|2.3||||"

Note: This field only takes effect if the MSH segment of the input

HL7 message is invalid.

- msaTextMsg

The test message in the MSA segment of the input HL7 message. The

default value of this field is null(""). You can override the default

by specifying a text message here.

- msaAckCode

The acknowledgment (ACK) code in the MSA segment of the input HL7

message. The default value of this field is "AE". You can override

the default by specifying an ACK code here.

Twelve valid acknowledgment codes can be used in this field: "AA",

"AE", "AR", "A", "E", "R", "accept", "error", "reject", "CA", "CE",

and "CR".

- Output tab

The descriptions of each field in the Output tab are as follows:

- ackContent

The generated acknowledgment message.

- ackIsNak

Indicates whether the generated acknowledgment is an ACK or an

NAK message.

If the value of this field is true, the generated acknowledgment

is an NAK message.

If the value of this field is false, the generated acknowledgment

is an ACK message. Four types of the ACK codes in the output MSA

segment can be used: "AA", "A", "CA", and "accept".

- Error Output

- msg

Error message description.

- msgCode

The error code. It represents TIBCO ActiveMatrix BusinessWorks Plug-in

for HL7 errors.

================================================================================

Environment

All supported platforms

Issue/Introduction

TIBCO ActiveMatrix BusinessWorks(TM) HL7 Plug-in 6.0.0 hotfix 3 has been released.

Welcome to "KB Articles"