IBM Support

Release notes for IBM SterlingTransformation Extender, Pack for Healthcare, V10.0.3.0

Release Notes


Abstract

These release notes contain the information required to install and configure Transformation Extender, Pack for Healthcare, V10.0.3.0

Content

IBM Transformation Extender Pack for Healthcare V10.0.3.0 release notes.

© Copyright IBM Corporation 2014, 2020. All Rights Reserved.
© Copyright HCL Technologies Ltd, 2017, 2020. All Rights Reserved.

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

=====================================================================
ABOUT THIS RELEASE
=====================================================================

Where to find the software to download

The Pack for Healthcare can be obtained from Fix Central.

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

WHAT'S NEW IN THIS RELEASE

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

HIPAA component:

  • Updates to HIPAA Compliance Checker, include new settings for the HIPAA_TAck_Enabled parameter, to control whether all, none, or only, error transactions are included in the TAck_EDI.html file

HL7 component:

  • Updates to FHIR example, to map from HL7 EDI to FHIR XML or JSON, in addition to mapping to HL7 EDI.

Documentation notes
See the online documentation for the latest information about this product.

Translated documentation:

The online documentation is provided in these languages:

  • English (United States)
  • French


For the latest product information, see the English version in the online documentation.

To display translated content in the online documentation:

  1. Open the online documentation. A typical URL to the documentation is shown below:
    https://www.ibm.com/support/knowledgecenter/SSVSD8_n.n.n/com.ibm.websphere.dtx.welcome.doc/kc_welcome_nnn.html
  2. Edit the URL to include the desired language code immediately after "/knowledgecenter":
    https://www.ibm.com/support/knowledgecenter/<language code>/SSVSD8_n.n.n/com.ibm.websphere.dtx.welcome.doc/kc_welcome_nnn.html
  3. As an example, enter language code "/fr" to display French content.
  4. Remove the "/<language code>"  to return to the English display.

=====================================================================
INSTALLATION
====================================================================

Exit libraries
The installation for the Pack for Healthcare, V10.0.3.0 contains a platform_support folder. The platform_support folder contains exit libraries which are used during system runtime executions for compliance checking.

Transformation Extender V10.0.0, V10.0.1.0, V10.0.2.0 or V10.0.3.0
The installation for the Pack for Healthcare for V10.0.3.0 provides the windows platform exit library in the platform support directory. For all other non-windows platforms, use the exit libraries in the Transformation Extender runtime install\libs folder.
IBM Transformation Extender 9.0.0:
The installation for the Pack for Healthcare, V9.0.0 provides exit libraries for all supported operating systems in the platform support directory.


Installation prerequisites

Before you install this version of the pack, you must install one of the following versions of IBM Transformation Extender:

  • 10.0.3.0
  • 10.0.2.0
  • 10.0.1.0
  • 10.0.0.0
  • 9.0.0.0
  • 8.4.1.0

Installing the pack on Windows systems

To install the Pack for Healthcare on Windows systems, perform the following procedures:

  1. Obtain the image from Fix Central.
  2. Run either of the commands for the application and accept the license agreement: 
    hcp_1003_1003.exe
    hcp_1003_1000.exe
    hcp_1003_900.exe
    hcp_1003_841.exe
  3. Follow the prompts to complete the installation.

Installation directories

The pack components are installed in the following directory:

install_dir\packs\healthcare_v10.0.3.0

Deployment to other operating systems

See the individual component documentation for information on deploying to other operating systems.

Uninstalling the pack

Follow these steps to uninstall the pack from Windows systems:

  1. Click Control Panel > Add/Remove Programs.
  2. Select the pack that you want to remove.
  3. Click Change/Remove and follow the prompts.

=====================================================================
PROJECT FILES
=====================================================================

The following projects are extracted from the IBM_healthcare10.0.3.0.zip file when the contents of the file is extracted. The projects are also in the UIProjectImports directory if you have installed over Design Studio.

The project import files are provided as a convenience and should not be used with windows based Design Studio implementations.

The UIProjectImports directory contains multiple compressed files, each of which contains a project that can be imported into the Design Server.

You must have administrative privileges to import projects.

Each of the projects is described briefly in the following sections:

Project summaries

HIPAA - Compliance Check – hipaaCompliance.zip
Contains maps, schemas and sample data for the HIPAA Compliance Checker. The maps are deployed and executed using one of the ITX API’s or with the command server to validate your data against the HIPAA 5010 Standards.

HIPAA -CMS<>HIPAA – hipaaCMS.zip
Contains maps, schemas and sample data to support the transformation and validation of the Centers for Medicare and Medicaid Services 5010 Flat file format for Claims, Claim Status, and Payments.

HIPAA – Examples – 278N, HIX and 7030 – hipaaExamples.zip
Contains examples that demonstrate how you can enrich or transform your data using the Pack for Healthcare components.  Examples include maps and schemas for two transactions at HIPAA 7030 Draft stage, the 278 transactions for Heath Care Services Review, and the HIPAA FFE 834 Enrollment transaction.

HIPAA – Examples – X12N – hipaaExamplesX12n.zip
Contains schemas that support X12 standard integrity checking (WEDI SNIP Type 1 Validation) for a set of healthcare industry implementation guides produced by ASC X12's Insurance Subcommittee (X12N). These trees do not conform to the industry TR3s but to the base X12 standard. They are useful for data transformation purposes; they should not be used for data validation for any WEDI/SNIP level above 1.

HL7 Examples – hl7Examples.zip
The NCPDP-SCRIPT/ HL7 mapping example is based on the NCPDP-HL7 Electronic Prescribing Coordination Mapping Document. This document provides mapping requirements for interactions between systems using HL7, and systems using NCPDP Script. This project also includes FHIR examples to map from FHIR input to HL7 V2 format.

HL7 Schemas – hl7EDI.zip
The schemas describe the data exchange formats associated with Health Level Seven (HL7). The ITX user interface depicts the HL7 message structure as an expandable, contractible, set of hierarchical components. The schemas enforce compliance of HL7 transmission data with EDI Standard Integrity Testing rules.

HL7 Validation - Multiple files:

  • hl7Compliance2_5.zip
  • hl7Compliance2_5_1.zip
  • hl7Compliance2_6.zip
  • hl7Compliance2_7.zip
  • hl7Compliance2_8.zip
  • hl7Compliance2_8_1.zip
  • hl7Compliance2_8_2.zip
     
These compressed files contain the maps and schemas for the HL7 Validation Utility. These maps and schemas leverage the information in the XSD schemas provided by HL7. These maps and schemas apply structure and data content rules from the schemas to the EDI data. Each compressed file supports one version of HL7.
Before building the maps in any of the projects, update the settings for the HL7in card in the hl7main map to point to one of the sample files shipped with the project for that version:
data/sample/hl7_edi_v2_x_adt_a01.dat
or
data/sample/hl7_xml_v2_x_adt_a01.xml
 Where x is the version number. Or,  point to another data file to validate, that you added to the project after import.

HL7 Validation -- hl7Compliance.zip
This compressed file contains the maps and schemas for the HL7 Validation Utility. These maps and schemas leverage the information in the XSD schemas provided by HL7. These maps and schemas  apply  structure and data content rules from the schemas to the EDI data. In this project, only version 2.7 level messages are supported. The HL7 component in the Design Studio components supports all HL7 versions for which general schema support is provided.

NCPDP – Examples – ncpdpExamples.zip
Contains maps and schemas to demonstrate the transformation and validation of the National Council of Prescription Drug Programs (NCPDP) Script standard for transmitting prescription information, and PACDR (Post Adjudication Claims Data Reporting) for detailed drug or utilization claim information.

NCPDP –  ncpdpTelecom.zip
Contains schemas that support the NCPDP retail pharmacy telecommunications (version D0), batch data (Version 1.2), and Medicaid Subrogation  (Version 3.0)  interchange formats as specified by the National Council for Prescription Drug Programs (NCPDP).

NCPDP Validation -- ncpdpValidation.zip
This compressed file contains the maps, schemas, and sample data for the NCPDP Validation Utility.  This initial version of the NCPDP Validation Utility reports on missing mandatory segments and fields, as well as Not Used segments and fields.

=====================================================================
CONFIGURATION FILES FOR NCPDP VALIDATION
=====================================================================
In the same location as the project compressed files, there is also a ncpdpValidationConfig.tar.gz file.
Before you import the ncpdpValidation.zip file, follow these steps.
  1. Make certain that Design Server is installed and started.
  2. Create a temp directory called packs.
    For example: /home/user/packs
  3. FTP (in binary mode) the ncpdpValidationConfig.tar.gz to the packs directory defined in the previous step.
     
Perform the following steps in the temp directory:
  1. Extract the ncpdpValidationConfig.tar.gz file.
    For example: $ tar -zxf ncpdpValidationConfig.tar.gz
  2. Run the ncpdpsetup.sh script.
    For example: $ ./ncpdpsetup.sh
    This script copies the ncpdp_jexit.jar file to the ITX server.
  3. Restart Design Server: docker restart tx-server
     OPTIONAL: Run the cleanncpdp.sh script.
     For example: $ ./cleanncpdp.sh
     This script moves the ncpdp_jexit.jar file from the ITX server:
     ncpdp_jexit.jar
     Restart Design Server: docker restart tx-server

====================================================================
KNOWN LIMITATIONS, PROBLEMS, AND WORKAROUNDS
====================================================================

ICD-10 functionality

The use of International Classification of Disease, 10th Revision (ICD-10) in HIPAA had a compliance date of October 1, 2015. In order to be compliant, the type trees in the HIPAA EDI Component have been modified to allow only ICD-10 codes. The HIPAA EDI stand-alone component does not enforce the actual codes, but only the qualifiers that indicate the version of the ICD in the data.

To assist with the ICD-10 transition, the following type trees are now provided in the component to allow both the ICD-9 and ICD-10 qualifiers:

hipaa_x12_type_2_icd9_icd10.mtt
hipaa_x12_icd9_icd10.mtt
hipaa_x12_ruleless_icd9_icd10.mtt
hipaa_x12_segment_icd9_icd10.mtt

If these type trees are required, the following steps must be followed to replace the type trees in the compliance check application.

Replacing the ICD-10 compliant type trees

If both the ICD-9 and ICD-10 codes are required, you must replace the type trees in the following maps as described in the table.
 

Maps impacted Input card (number and name) Default type tree ICD-9 and ICD-10 type tree compliance check maps
x12t2precontentcheck #1 X12_Func_Group hipaa_x12_type_2.mtt hipaa_x12_type_2_icd9_icd10.mtt
x12t4precontentcheck #1 X12_Func_Group hipaa_x12.mtt hipaa_x12_icd9_icd10.mtt
xhipaasegmentdataaudit #1 Transaction_Set_Segments hipaa_x12_segment.mtt hipaa_x12_segment_icd9_icd10.mtt

Changes for each map impacted in compliance_check.mms

For each map impacted in the table above, make these changes:
  1. Open compliance_check.mms in the Design Studio.
  2. Double click on the executable map to select it for modification.
  3. Edit the input card for the map to point to the appropriate *_icd9_icd10 type tree instead of the default type tree.
  4. Select YES when prompted, to replace all similar type tree paths in all maps.
  5. Build the map.

Pass through maps
 
Maps impacted Input card (number and name) Default type tree ICD-9 and ICD-10 type tree compliance check maps
hipaa_x12_pass_through #1 HIPAA_X12_Inbound_Transmission hipaa_x12.mtt hipaa_x12_icd9_icd10.mtt
hipaa_x12_pass_through #2 HIPAA_X12_Outbound_Transmission hipaa_x12.mtt hipaa_x12_icd9_icd10.mtt
hipaa_x12_type_2 #1 HIPAA_X12_Inbound_Transmission hipaa_x12_type_2.mtt hipaa_x12_type_2_icd9_icd10.mtt
hipaa_x12_type_2 #2 HIPAA_X12_Outbound_Transmission hipaa_x12_type_2.mtt hipaa_x12_type_2_icd9_icd10.mtt


Changes to maps impacted in hipaa_x12_pass_through.mms

Follow these steps to change each map impacted in hipaa_x12_pass_through.mms:
  1. Use Design Studio to open hipaa_x12_pass_through.mms.
  2. Double-click on the executable map to select it for modification.
  3. Edit the input card listed to point to the appropriate *_icd9_icd10 type tree instead of the default type tree.
  4. Select NO when prompted to replace all similar type tree paths in all maps.
  5. Edit the Output card with the same number as the input card just modified to point to the appropriate *_icd9_icd10 type tree instead of to the default type tree.
  6. Select NO when prompted to replace all similar type tree paths in all maps.
  7. After all the maps are updated, build the maps.

Changes to other maps in the HIPAA EDI Component

The following changes must be made for any of the remaining maps:
  1. Use the Design Studio to open the map source.
  2. Double-click on the executable map to select it for modification.
  3. Edit the input or output card that is using the hipaa_x12.mtt as the default type tree to point to the hipaa_x12_icd9_icd10.mtt.
  4. When prompted, select YES to replace all similar type tree paths in all maps.
  5. After all maps are updated, build the maps.

====================================================================
DEPRECATED MAPS AND TYPE TREES
=====================================================================

Deprecated NCPDP report maps

The report maps listed below were previously located in the NCPDP directory: \ncpdp\maps. The maps listed have been removed as of this release.
These maps were only produced correctly if the NCPDP transactions had no errors. They are  now superseded by the true validation utility.

  • ncpcp_v3_0_request_report.mms
  • ncpcp_v3_0_response_report.mms
  • ncpcp_v5_1_request_report.mms
  • ncpcp_v5_1_ response _report.mms
  • ncpcp_vd_0_request_report.mms
  • ncpcp_vd_0_ response _report.mms
NCPDP Telecom
NCPDP Telecom type trees located in the NCPDP directory: \ncpdp\trees are removed. The only version mandated by HIPAA is VD.0. As a result the following type tress are deprecated
* ncpdp_v3_2.mtt
* ncpdp_v5_1.mtt

Versions of Telecom D.0 and Med Subrocation based on 2014 updates and earlier.

=====================================================================
SAMPLE DATA FILE CHANGES
=====================================================================
HIPAA X12 sample data
The HIPAA X12 sample data includes transmission data for the finalized HIPAA X12 transaction set definitions.
There is one file per version, or industry code, and one file that contains all of the sample data.
The naming convention includes the hipaa transaction version, and the x12 transaction numbers().

For example, the sample data for the 276 transaction defined in the HIPAA 5010X212 TR3 is named hipaa_5010_x212_276_sample.dat.
There is also a sample data file that contains all the transactions supported. This is named all_hipaa_5010_transaction_sets.dat.

CMS sample data
The CMS sample data includes transmission data for the flat file interface data formats associated with the HIPAA 5010 transaction definitions, and the finalized addenda definitions.

The sample data is based on transformations of the HIPAA X12 transaction sets data included with the Pack for Healthcare.

The naming convention includes the HIPAA transaction version, and x12 transaction number(s).

For example, the sample for the CMS 276 flat- file format is cms_flat_5010_x212_276_sample.dat.

 

=====================================================================
RESOLVED AUTHORIZED PROGRAM ANALYSIS REPORTS (APARs)
=====================================================================
For a list of APARs that are fixed in this version of the product, see the fix list.

=====================================================================
CONTACTING CUSTOMER SUPPORT
=====================================================================

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

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


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

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSQ9TT","label":"IBM Sterling Transformation Extender Pack for Healthcare"},"Component":"","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF016","label":"Linux"},{"code":"PF051","label":"Linux on IBM Z Systems"},{"code":"PF035","label":"z\/OS"}],"Version":"V10.0.3.0","Edition":"","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]

Document Information

Modified date:
03 October 2022

UID

ibm12315877

Page Feedback