Switch to standard view 
  Sybase logo
 
 
 



Document ID: DC79167-01-0420-02

Topic

Page

1. Accessing current release bulletin information

2. Product summary

3. What’s in the box?

4. Installation and configuration instructions

5. Changed functionality in this version

6. Migrating your HIPAA Repository Database

7. What’s new in HIPAA Repository 4.2

8. Documentation updates and clarification

9. Limitations

10. Known problems

11. Technical support

12. Other sources of information

1. Accessing current release bulletin information

A more recent version of this release bulletin may be available on the Web. To check for critical product or document information added after the release of the product CD, use the Sybase Technical Library Product Manuals Web site.

Accessing release bulletins at the Technical Library Product Manuals Web site

  1. Go to Product Manuals.

  2. Follow the links to the appropriate Sybase product.

  3. Select the Release Bulletins link.

  4. Select the Sybase product version from the Release Bulletins list.

  5. From the list of individual documents, select the link to the release bulletin for your platform. You can either download the PDF version or browse the document online.


2. Product summary

Enclosed is one of the following products: Sybase HIPAA Repository 4.2 or Sybase HIPAA Repository for Providers 4.2.

Sybase® HIPAA Repository provides a structure through physical and conceptual data models for storing original data for HIPAA-compliant request/response X12 transactions.

HIPAA Repository is used by payers, providers, state agencies and clearinghouses to store data content that is not accommodated by many back-end systems, but must be attached to the remittance advice that payers send back to providers in order for organizations to comply with Health Insurance Portability and Accountability Act (HIPAA) regulations. HIPAA Repository stores and processes HIPAA transactions such as claims, eligibility, and enrollment data.

While most back-end adjudication systems cannot house such large volumes of data without major modifications to the entire system, HIPAA Repository easily manages these incoming EDI transactions.

2.1 Supported platforms

HIPAA Repository supports the following operating system platforms:



Note:

All platforms require approximately 250 MB of hard disk space for the installation. For additional requirements see the HIPAA Repository Installation and Configuration Guide.


2.2 Supported databases

HIPAA Repository 4.2 has been certified to run on the following databases:

2.3 Product compatibility

HIPAA Repository is fully compatible with all Sybase HIPAA technology.

When you work with a database, all your requests and commands go through a driver to the database itself. Sybase HIPAA Repository requires two main types of drivers, JDBC and ODBC:

  1. HIPAA Repository Data Loader and the Java component of Data Delivery require JDBC driver. See Table 1.

  2. HIPAA Repository Data Delivery requires an ODBC driver. See Table 2.

    Vendor and version number are not critical for Windows ODBC connection.

2.3.1 JDBC connections and driver requirements

Neither Data Loader nor Data Delivery require vendor-specific JDBC drivers. Table 1 lists the JDBC drivers Sybase has tested and certified for use within HIPAA Repository.

Table 1: JDBC driver requirements

Operating system

ASE 12.5

Oracle

MS SQL Server

Windows

Jconnect 5.5

Oracle JDBC

Microsoft JDBC

Solaris

Jconnect 5.5

Oracle JDBC

Microsoft JDBC

HP-UX

Jconnect 5.5

Oracle JDBC

Microsoft JDBC

AIX

Jconnect 5.5

Oracle JDBC

Microsoft JDBC

JDBC drivers for Oracle and Microsoft SQL Server 2000 can be found at the following Web sites:



Note:

You do not need to download JDBC drivers if you use Sybase Adaptive Server Enterprise.


2.3.2 ODBC connections and driver requirements

ODBC drivers are optional on UNIX Platforms unless you plan to run Data Delivery, where they are required.

Table 2 lists the ODBC drivers available for all HIPAA Repository certified platforms.

Table 2: ODBC driver requirements

Operating system

ASE 12.5

Oracle

MS SQL Server

Windows

Microsoft or DataDirect

Microsoft or DataDirect

Microsoft or DataDirect

Solaris

Sybase Catalog #18819

Sybase Catalog #18819

Sybase Catalog #18819

HP-UX

Sybase Catalog #18818

Sybase Catalog #18818

Sybase Catalog #18818

AIX

Sybase Catalog #18817

Sybase Catalog #18817

Sybase Catalog #18817



Note:

The Sybase catalog numbers listed for UNIX platforms are current as of April 2004.


If you do not already have ODBC installed, you can purchase Data Direct drivers from a third-party vendor or from Sybase. If you would like to order ODBC drivers from Sybase, please contact your Sybase technical representative.

3. What’s in the box?

Sybase HIPAA Repository includes the following components.

4. Installation and configuration instructions

The following sections describe where to look for installation instructions.

4.1 Installing HIPAA Repository

For installation instructions for HIPAA Repository for Windows and UNIX platforms, see the HIPAA Repository Installation and Configuration Guide on the Getting Started HIPAA Repository CD.

4.2 Installing Warehouse Studio

For installation instructions for Warehouse Studio components, such as Warehouse Control Center, Adaptive Server Anywhere, and PowerDesigner, see the Release Bulletin Warehouse Studio 4.1 on the Warehouse Studio Getting Started CD.

4.3 Configuring ODBC drivers on UNIX platforms

Use the following procedure to configure DataDirect ODBC drivers on HP-UX, SunOS or AIX. This process is required to ensure that the Data Loader and Delivery applications connect to HIPAA Repository properly.

  1. Under the ODBC installation directory (assuming it is /opt/odbc and you are running C Shell), locate odbc.csh.

  2. Modify myhrenv.csh for the appropriate driver. For example, type the following:

    source /opt/odbc/odbc.csh



    Note:

    myhrenv.csh is a script that sets the environmental variables required to run the Data Loader and Data Delivery components of HIPAA Repository.


    The myhrenv script will add the shared library directory to LD_LIBRARY_PATH on Solaris, SHLIB_PATH on HP-UX, and LIBPATH on AIX.

  3. Modify myhrenv.csh again by inserting:

    setenv ODBCINI /opt/odbc/odbc.ini

  4. Modify the odbc.ini file to assign a data source name (DSN) to your ODBC database. For example, below see three DSNs, to which the properties file can refer as either ORAhipaa for Oracle databases, SQLhipaa for Microsoft SQL Server, or ASEhipaa for Sybase Adaptive Server Enterprise databases, respectively.

    [ORAhipaa]

    Driver=/opt/odbc/lib/NNora18.so
    Description=DataDirect 4.10 Oracle Wire Protocol
    LogonID=IK_HIPAA
    Password=password
    HostName=hipaa
    PortNumber=1521
    SID=HIPAA
    CatalogOptions=0
    ProcedureRetResults=0
    EnableDescribeParam=0
    EnableStaticCursorsForLongData=0
    ApplicationUsingThreads=1

    [SQLhipaa]

    Driver=/opt/odbc/lib/NNmsss18.so
    Description=DataDirect 4.10 SQL Server Wire Protocol
    Database=JS_HIPAA
    LogonID=hipaa
    Password=password
    Address=HIPAA,1433
    QuotedId=No
    AnsiNPW=No

    [ASEhipaa]

    QEWSD=37705
    Driver=/opt/odbc/lib/NNase18.so
    Description=DataDirect 4.10 Sybase Wire Protocol
    Database=IK_HIPAA
    LogonID=hipaa
    Password=password
    NetworkAddress=bluesky, 5555
    EnableDescribeParam=1
    EnableQuotedIdentifiers=0
    OptimizePrepare=1
    RaiseErrorPositionBehavior=0
    SelectMethod=0
    ApplicationUsingThreads=1

  5. To test your ODBC configuration, go to the /opt/odbc/example directory and type the following:

    source ../odbc.csh

    setenv ODBCINI /opt/odbc/odbc.ini

    Run ./example and follow the instructions on the screen.

  6. Correct problems encountered in Step 5. Do not proceed until the example works. If it does not, the problem may be either the database or the driver configuration or both. For example, be sure of the following:

    • The DSN entry is correct

    • ODBCINI points to the correct .ini file

    • Your directory has a shared library opt/odbc/lib:

      • LD_LIBRARY_PATH on Solaris

      • SHLIB_PATH on HP-UX

      • LIBPATH on AIX

  7. If step 5 is successful, you are ready to use ODBC with HIPAA Repository’s Data Delivery application.

4.4 Uninstalling HIPAA Repository

See the HIPAA Repository Installation and Configuration Guide on the Getting Started HIPAA Repository CD to uninstall HIPAA Repository components.

5. Changed functionality in this version

This release supports AIX 5.1.

6. Migrating your HIPAA Repository Database

Sybase provides an upgrade mechanism in the form of SQL scripts so you can migrate your existing data to a new HIPAA Repository release. This upgrade mechanism assumes your schemas are within the same database type on the same server.

This release contains updated scripts that support the FORM_ID, SPRT_DOC and TXN_SET_TLR_835 tables. See the HIPAA Repository Installation and Configuration Guide for database migration instructions.

7. What’s new in HIPAA Repository 4.2

The following sections describe new features and other changes in HIPAA Repository 4.2.

7.1 837/835 response processing feature

The 837/835 response processing feature takes HIPAA Repository one step beyond the basic infrastructure for loading, storing, and delivering claim payment transactions. Object-oriented programming interfaces make it easier for you extract and load X12 information from the HIPAA Repository data models by freeing you from having to know specific X12 structures.



Note:

HIPAA Repository 4.2 provides a programmatic interface to 835 response processing transactions and supports the 4010A standard only. Other response processing transactions that Sybase supports (for example, 271, 277, and 278) have not been addressed with a programmatic interface and still require site development.


See the HIPAA Repository User’s Guide for details of this feature.

7.2 HIPAA Staging Repository

HIPAA Repository 4.2 contains several new tables known as the HIPAA Staging Repository. These tables are used by the response processing interfaces and are transparent to the user.

See HIPAA Repository User’s Guide for information on both the Staging Repository and using the example code.

7.3 Data Loader changes

This section describes changes to the HIPAA Repository Data Loader application.

7.3.1 Data Loader interface

An extension of HIPAA Repository functionality lets you call the Data Loader through a programmatic interface rather than having to invoke it as a standalone process. See HIPAA Repository User’s Guide for details.

7.3.2 Unique claim identifier

Data Loader assigns a unique claim identifier for each 837 claim it processes. In order to identify a specific claim, HIPAA Repository establishes a unique number for each claim and associates all of its owned segments with a single identifier of up to 15 characters. See HIPAA Repository Installation and Configuration Guide for details.

7.4 Data Delivery changes

Data Delivery manages and spawns two new tasks:

See the HIPAA Repository User’s Guide for details.

7.5 Schema changes

HIPAA Repository 4.2 added the HDR_CLM_ID column to the FORM_ID and SPRT_DOC tables for unique claim identifier support. See the HIPAA Repository User’s Guide, Chapter 6 for details.

8. Documentation updates and clarification

Table 3 summarizes the documentation distributed with this release.

Table 3: Sybase Documentation Summary.

Title

Description

Location

Release Bulletin HIPAA Repository 4.2

Summarizes key product features, installation steps, and known issues relating to this release.

hipaarb.pdf on Getting Started HIPAA Repository CD

HIPAA Repository Installation and Configuration Guide

Provides installation and configuration procedures to set up and run HIPAA Repository.

hipaaig.pdf in \doc folder of your install directory

HIPAA Repository User’s Guide

Describes HIPAA standard and describes how HIPAA Repository processes transactions, giving you tools to use HIPAA Repository.

hipaaug.pdf in \doc folder of your install directory

HIPAA Repository Model Descriptions

Describes the diagrams, tables, and columns in the HIPAA Repository data model.

ModelDescrHIPAA.pdf in \doc folder of your install directory

PowerDesigner License Key

Contains the product key you need to install PowerDesigner from the installation CD.

Print only

Adaptive Server Anywhere License Key

Contains the product key you need to install Adaptive Server Anywhere from the Warehouse Studio installation CD.

Print only

Release Bulletin Warehouse Studio 4.1

Summarizes key product features and installation steps for Warehouse Control Center, ADaptive Server Anywhere, and PowerDesigner, and describes known issues that relate to Warehouse Studio 4.1.

Warehouse Studio Getting Started CD

Warehouse Control Center Installation and Configuration Guide

Describes installation and configuration procedures required to set up Warehouse Control Center.

Warehouse Studio Getting Started CD

Correction

In HIPAA Repository 4.2, the DDL files, Repository_DDL_ASE.sql, Repository_DDL_ORA9i.sql, and Repository_DDL_MSSQL2000, contain two fields in table PRN_PROC_CD that are named incorrectly: H101DTTM_QUAL should be HI01DTTM_QUAL and H101PROC_CD should be HI01PROC_DT.

9. Limitations

Read this section! Your system may produce unexpected results if you ignore the limitations and other instructions listed below.

The following sections include operation information that needs emphasis.

9.1 General compliance issues

HIPAA Repository maps and processes assume that all inbound X12 transactions have been validated as compliant. Processing non-compliant transactions may result in unpredictable data being placed into HIPAA Repository.

9.2 Path names require double quotes

When you update path names in batch files to identify source and target directories, remember to use double quotes to wrap the string. Double quotes are required for path names in all batch files.

If the Data Loader batch file resides in a directory path that has spaces, surround the full path, including batch file, with double quotes. For example:

ACTION: cmdString = “C:\Program Files\Sybase\HIPAA_Repository_42\bin\runsample.bat”  270

9.3 HIPAA Repository installation on UNIX platforms

Setting space requirements on TML directory

Installing HIPAA 4.2 on UNIX platforms requires at least 150MB of space on your TMP directory. If TMP does not have adequate space, set the following before you install: setenv TMPDIR XXX where xxx represents a directory with at least 150MB available.

X window requirement

HIPAA Repository 4.2 installer is an X client. To run it successfully, you must meet the requirements for X application. For example, X system should be initialized and X server should be running. If you connect to X server running on a remote site, your host name should be in an “allow to connect” list. Also, set the DISPLAY environment variable to point to the machine to which the display is physically connected.

9.4 ODBC limitation on AIX 5.1

When running data delivery for 271A transactions, an ODBC restriction on AIX 5.1 returns incorrect 2110D HSD02 values. To avoid errors, the value of HDS02 (benefit quantity) must be under 184,668.

This error does not occur on other platforms.

10. Known problems

This section summarizes known problems and other issues related to this release.

10.1 Multiple ISA in single physical file support [CR 310614]

HIPAA Repository does not currently support processing of clearinghouse transactions that have multiple ISAs (Interchange Control Header) in single file.

10.2 Running Data Delivery on Adaptive Server Enterprise 12.5

If you are using Adaptive Server Enterprise ODBC drivers for your ASE ODBC DSN, you need EBF 10719 for Adaptive Server Enterprise 12.5.

Point your web browser to the Sybase Support Page to update your ASE ODBC Driver to version 4.10.00.28.



Note:

Adaptive Server Enterprise is case sensitive. When supplying connection information to your working or production directories, Warehouse Studio, or Sybase HIPAA Repository, use the appropriate case.


11. Technical support

Each Sybase installation that has purchased a support contract has one or more designated people who are authorized to contact Sybase Technical Support. If you have any questions about this installation or if you need assistance during the installation process, ask the designated person to contact Sybase Technical Support or the Sybase subsidiary in your area.

12. Other sources of information

Use the Sybase Technical Library and the Product Manuals web site to learn more about your product:

Most HIPAA Repository books are in PDF format. You need Adobe® Acrobat® Reader version 4 or higher to view these PDF files. Acrobat Reader is a small program that you can download for free from the Adobe web site.

12.1 Sybase certifications on the Web

Technical documentation at the Sybase Web site is updated frequently.

Finding the latest information on product certifications

  1. Point your Web browser to Technical Documents.

  2. Select Products from the navigation bar on the left.

  3. Select a product name from the product list and click Go.

  4. Select the Certification Report filter, specify a time frame, and click Go.

  5. Click a Certification Report title to display the report.


Creating a personalized view of the Sybase Web site (including support pages)

Set up a MySybase profile. MySybase is a free service that allows you to create a personalized view of Sybase Web pages.

  1. Point your Web browser to Technical Documents.

  2. Click MySybase and create a MySybase profile.


12.2 Sybase EBFs and software maintenance

Finding the latest information on EBFs and software maintenance

  1. Point your Web browser to the Sybase Support Page.

  2. Select EBFs/Maintenance. Enter user name and password information, if prompted (for existing Web accounts) or create a new account (a free service).

  3. Select a product.

  4. Specify a time frame and click Go.

  5. Click the Info icon to display the EBF/Maintenance report, or click the product description to download the software.




Back to Top
© Copyright 2010, Sybase Inc.