SPE for Healthcare Payer V.8.5.1.1 Release Notes

Content

=====================================================================
CONTENTS
=====================================================================

1. About this release
2. Installation and configuration information
3. Upgrade and migration information
4. Known limitations, problems and workarounds
5. New and changed behavior
6. Contacting customer support
7. Notices and trademarks

=====================================================================
1. ABOUT THIS RELEASE
=====================================================================

Where to find the software to download

To download the software for the SPE for Healthcare Payer V8.5.1.1, go to Passport Advantage Online.

Documentation notes

Online documentation
Online documentation is provided.

Translated documentation
Based upon country requests, the online product documentation is translated from the original English (United States) version into various native languages.

See the English documentation for the latest information.

Inquiries about translating documents into specific languages should be directed to an IBM representative of the respective country.

Back to top

=====================================================================
2. INSTALLATION AND CONFIGURATION INFORMATION
====================================================================

Installation prerequisites

You can install Standards Processing Engine on supported versions of the Linux, UNIX, or Windows operating systems.

Installation of SPE V.2.0.1 / V.8.5.1 is not a prerequisite for installation of SPE V.2.0.1.1 / V.8.5.1.1.

To enable WebSphere Transformation Extender to recognize the SPE server components, install WebSphere Transformation Extender V.8.4.1 prior to installing SPE server components. Alternately, if you prefer to install the SPE server components before WebSphere Transformation Extender, follow the procedure under WebSphere Transformation Extender does not recognize SPE.

Windows and UNIX Installation

If this is a new installation (that is, if SPE V. 2.0.1 / 8.5.1 is not installed), follow the installation procedure in the Knowledge Center.

Uninstall

To uninstall Standards Processing Engine products, see the uninstallation procedure in the Knowledge Center.

Back to top

=====================================================================
3. UPGRADE AND MIGRATION
=====================================================================

If SPE V2.0.1 / 8.5.1 is already installed, use this procedure to upgrade to V2.0.1.1 / 8.5.1.1.

This procedure upgrades your SPE V.2.0.1.1 core components and SPE V.8.5.1.1 packs while retaining your previous customizations. Your existing configuration is maintained for these components during an upgrade:

• SPE continues to use the database that is currently configured.
• Any customizations that you made to the following files are preserved:
  customer_overrides.properties (general SPE properties)
  dbprops.cfg (database properties)
  packs.properties (pack configuration)
  speiib.properties (properties for IIB nodes)
  server.xml (Trading Partner UI configuration)
  jvm.options (Trading Partner UI JVM options)
• The upgrade process deploys the updated compliance check maps and business rules to the SPE database.
• Existing code lists are left in place in the SPE database.
  Note: There are no code list updates associated with this fix pack, so existing code lists are not updated by the pack deploy scripts.

Before you begin

• With the exception of customer_overrides.properties and the other files listed previously, save a copy of any customized files that you want to retain. Otherwise, customized files not on the list might be overwritten and changes made since installation might be lost.
• If you have customized a large number of HIPAA business rules, you can export the rules to a file.
  
  Caution: Re-importing your customized rules from a file that you exported overwrites any rules that were updated in the fix pack. (If you have only a few customized rules, use the Trading Partner UI to change the default version of those selected rules back to the previous version.)

Procedure
To upgrade from Standards Processing Engine V2.0.1 / V8.5.1 to V.2.0.1.1 / V8.5.1.1, follow this procedure:

1. Stop all SPE processes, including the Trading Partner User Interface and any host applications such as IBM Integration Bus or Sterling B2B Integrator.
2. Retain any customizations that you have made to HIPAA business rules:
• If you have customized a significant number of HIPAA business rules, you can use the Trading Partner UI to export them.
• If you have only customized a few rules, you can use the Trading Partner UI to change the default version of those rules back to the previous version after the upgrade.
3. Use the the IBM Install Manager Update option to install SPE common components V.2.0.1.1 and one or more SPE packs V.8.5.1.1.
4. Use the pack deploy scripts to redeploy the packs:
• Use the speresource-packedi or speresource-packhc command to recreate each resource file, as appropriate.
• Use the spedeploy command to update the runtime environment from the resource file.
5. Restart the Trading Partner User Interface and host application.
6. Restore customized HIPAA business rules as needed:
• If you have only a few customized rules, use the Trading Partner UI to change the default version of those selected rules back to the previous version. If you have customized a large number of rules, import the rules from the file that you exported earlier.
  Caution: Re-importing your customized rules from the file that your exported earlier overwrites any rules that were updated in the fix pack.
• If you have customized type 2-4 rules, regenerate the type trees and rebuild the HIPAA type trees. See the type trees documentation in the IBM Knowledge Center for WebSphere Transformation Extender.

Back to top

=====================================================================
4. KNOWN LIMITATIONS, PROBLEMS, AND WORKAROUNDS
=====================================================================


WebSphere Transformation Extender does not recognize SPE after a subsequent WebSphere Transformation Extender installation

Issue: A customer installs WebSphere Transformation Extender after SPE has been installed, and WebSphere Transformation Extender does not recognize SPE.

Background: If WebSphere Transformation Extender is already installed at the time of an SPE installation, SPE updates the WebSphere Transformation Extender dtx.ini file with the location of the SPE installation and sets up the WebSphere Transformation Extender environment variables. However, if WTX is installed after SPE, manual setup is required to integrate the products.

Workaround: Perform these steps:

1. Manually update the WebSphere Transformation Extender dtx.ini file by appending the following lines:

[SPE]
SPE_INSTALL_DIR=C:/IBM/Standards Processing Engine version

2. Edit or create the spewtx64env and/or spewtxenv scripts in the spe_install_dir/bin directory. Change this line to set DTXHOME to the WTX install directory:

%INSTALLREPLACEMENTSTRING%

(Windows) The spewtxenv.bat script should specify the 32-bit WebSphere Transformation Extender installation (if installed), and the spewtx64env.bat script should specify the 64-bit WebSphere Transformation Extender installation (if installed).

The spewtxenv.bat script is always created as part of the SPE install. If you install a 32-bit WTX version after installing SPE, you need to update the %INSTALLREPLACEMENTSTRING% line to set the DTXHOME environment variable. For example, in the spewtxenv.bat script the new line might look like this:

set DTXHOME=C:\IBM\WebSphere Transformation Extender 8.4.1 32bit

The spewtx64env.bat script is only created during the SPE install if a 64-bit WebSphere Transformation Extender version is present at that time. If you install a 64-bit WebSphere Transformation Extender version after installing SPE, you need to create an spewtx64env.bat file by copying the existing spewtxenv.bat file. Then update the %INSTALLREPLACEMENTSTRING% line (or DTXHOME line, if it is set for a 32-bit WTX install) to set the DTXHOME environment variable to the 64-bit WebSphere Transformation Extender directory. For example, in the spewtx64env.bat script the new line might look like this:

set DTXHOME=C:\IBM\WebSphere Transformation Extender 8.4.1 64bit

(Linux and UNIX) On Linux and UNIX platforms, SPE does not use a separate spewtx64env script. The spewtxenv.sh script should specify the WebSphere Transformation Extender installation. For example, in the spewtxenv.sh script the new line might look like this:

DTXHOME="/speinstall/wtxspe64/wtx_8413"; export DTXHOME


Some characters are not available for use in naming a resource

Issue: The following characters are reserved by the SPE Trading Partner UI, and therefore should not be used when naming a resource: "|" (pipe), "^" (caret), and ":" (colon).

Workaround: None

Back to top

====================================================================
5. NEW AND CHANGED BEHAVIOR
====================================================================

Key items in SPE V.8.5.1.1 include the following:

• SPE now ships with Java 1.7, Fix Pack 10.
• SPE can now be installed with IBM Installation Manager 1.8.1 or 1.7.3.
• Addition of SPE.DocumentType to the Local Environment parameters in the SPE Enveloping, SPE Deenveloping, and SPE Transformation nodes in IBM Integration Bus.

SPE Document Type parameter

In the IBM Integration Bus nodes for SPE, SPE.DocumentType is added to the Local Environment parameters to improve handling of intermediate and final documents.The parameter is defined as follows:

SPE.DocumentType
The document type returned by Standards Processing Engine for this data.
Possible values: UNASSIGNED, INPUT, INTERMEDIATE, and FINAL

Back to top

=====================================================================
6. CONTACTING CUSTOMER SUPPORT
=====================================================================

Contact Customer Support at 1-800-IBM-SERV, or go to the or go to the IBM Support Portal.

Back to top

=====================================================================
7. NOTICES AND TRADEMARKS
=====================================================================

This information was developed for products and services offered in the U.S.A.

IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's
responsibility to evaluate and verify the operation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not grant you any license to these patents. You can send license
inquiries, in writing, to:

IBM Director of Licensing
IBM Corporation
North Castle Drive
Armonk, NY 10504-1785
U.S.A.

For license inquiries regarding double-byte character set (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to:

Intellectual Property Licensing
Legal and Intellectual Property Law
IBM Japan, Ltd.
19-21, Nihonbashi-Hakozakicho, Chuo-ku
Tokyo 103-8510, Japan

The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law:

INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION
"AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE
Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you.

This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this
publication at any time without notice.

Any references in this information to non-IBM web sites are provided for convenience only and do not in any manner serve as an endorsement of those web sites. The materials at those web sites are not part of the materials for this IBM product and use of those web sites is at your own risk.

IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you.

Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact:

IBM Corporation
577 Airport Blvd., Suite 800
Burlingame, CA 94010
U.S.A.

Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee.

The licensed program described in this document and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or
any equivalent agreement between us.

Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurements may have been estimated through
extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment.

Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products.

All statements regarding IBM's future direction or intent are subject to change or withdrawal without notice, and represent goals and objectives only.

This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and
products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental.

COPYRIGHT LICENSE:

This information contains sample application programs in source language, which illustrate programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to IBM, for the purposes of developing, using, marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs.

If you are viewing this information softcopy, the photographs and color illustrations may not appear.

[Programming interface information]
Programming interface information, if provided, is intended to help you create application software using this program.

General-use programming interfaces allow you to write application software that obtain the services of this program's tools.

However, this information may also contain diagnosis, modification, and tuning information. Diagnosis, modification and tuning information is provided to help you debug your application software.

Warning: Do not use this diagnosis, modification, and tuning information as a programming interface because it is subject to change.

[Privacy Policy Considerations]
IBM Software products, including software as a service solutions, ("Software Offerings") may use cookies or other technologies to collect product usage information, to help improve the end user experience, to tailor interactions with the end user or for other purposes. In many cases no personally identifiable information is collected by the Software Offerings. Some of our Software Offerings can help enable you to collect personally identifiable information. If this Software Offering uses cookies to collect personally identifiable information, specific information about this offering’s use of cookies is set forth below.

This Software Offering does not use cookies or other technologies to collect personally identifiable information.

If the configurations deployed for this Software Offering provide you as customer the ability to collect personally identifiable information from end users via cookies and other technologies, you should seek your own legal advice about any laws applicable to such data collection, including any requirements for notice and consent.

For more information about the use of various technologies, including cookies, for these purposes, see the IBM Privacy Policy, the IBM Online Privacy Statement section entitled "Cookies, Web Beacons and Other Technologies," and the IBM Software Products and Software-as-a-Service Privacy Statement.

[Trademarks and service marks]
IBM, the IBM logo and ibm.com are trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the web at "Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml.
Java and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/or its affiliates.
Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both.
Microsoft and Windows are trademarks of Microsoft Corporation in the United States, other countries, or both.
UNIX is a registered trademark of The Open Group in the United States and other countries.

Other product and service names might be trademarks of IBM or other companies.


This product includes software developed by the Eclipse Project
(http://www.eclipse.org/).

Back to top