Chapter 3 Using HIPAA OTDs

This chapter describes how you use HIPAA OTDs provided in the HIPAA OTD Library, such as building HIPAA Collaborations.

This chapter contains the following topics:

• Displaying HIPAA OTDs

• Building HIPAA OTD Collaborations

• Possible Differences in Output When Using Pass-Through

Displaying HIPAA OTDs

After installing the HIPAA OTDs, you can view the OTDs in the OTD Editor.

To Display HIPAA OTDs

1. If you are not already in Enterprise Designer, access it by running the following script:

   c:\...\edesigner\bin\runed.bat

2. Click the Project Explorer tab.

3. Expand the following folders:

   • Sun SeeBeyond

   • OTD Library

   • HIPAA

   • 2000_Standard or 2000_Addenda

   The Project Explorer tab displays the available OTDs.

   

   The following table below describes the OTD naming conventions.

   x12_

   X12 protocol name

   vnnnn_

   X12 version

   00_

   2000 HIPAA

   hipaa_

   Protocol name

   qn_

   Optional; indicating quarter

   820_PayMOrdeAdvi

   Transaction code and transaction name abbreviation

   _Full

   Fully enveloped OTD version that includes the inner and outer envelopes

   The folder also includes a Metadata folder, which holds a .zip file that contains all HIPAA SEF files for the OTDs..

Building HIPAA OTD Collaborations

This section describes how you build Java Collaborations that use the HIPAA OTDs provided in the HIPAA OTD Library.

Before you can build the Collaboration, you must have installed the .sar file for the particular OTD to be used. For information, see Installing the HIPAA OTD Library.

To Build HIPAA OTD Collaborations

1. Access the Enterprise Designer.

2. Click the Project Explorer tab.

3. Click mouse button three on the Project name for which you want to create a Collaboration. Click New. Click Collaboration Definition (Java).

   The Collaboration Definition Wizard dialog box appears.

4. Type the name of the Collaboration and click Next.

   The Select Web Service Operation page appears.

5. Select the Web service operation to be implemented by this collaboration, which will trigger the execution of this Java Collaboration Definition, for example, SeeBeyond⇒eGate⇒JMS⇒receive, and click Next.

   

   The Select OTDs page appears.

6. Under Look In, navigate to the OTDs by double-clickingSeeBeyond⇒OTD Library⇒HIPAA⇒2000_Standard or 2000_Addenda.

   The Look In area displays the OTDs for the selected HIPAA directories. The following table describes the naming convention for the OTDs.

   x12_

   X12 protocol

   vnnnn_

   X12 version

   00_

   2000 HIPAA

   hipaa_

   Protocol name

   q1_

   Optional; indicating quarter

   820_PayMOrdeAdvi

   Transaction code and transaction name abbreviation

   _Full

   Fully enveloped OTD version that includes the inner and outer envelopes

7. Double-click the OTDs to be used. The OTDs are added to the Selected OTDs list.

   

8. Click Finish.

   The Collaboration appears in the Collaboration Editor. You can now use the eGate and OTD methods to build the business logic for the Collaboration. For information about the HIPAA OTD methods, refer to Chapter 4, Java Methods for HIPAA OTDs.

Possible Differences in Output When Using Pass-Through

If you are using pass-through, the output file contains essentially the same data as the input file.

Certain differences in output, based on variations in acceptable interpretation of the information, are acceptable, provided that the data conforms to the formats specified for the elements. For example:

• If the input file includes a six-digit date, the output file might represent this as an eight-digit value. For example, 070205 in the input file might be represented as 20070205 in the output file.

• The number of trailing zeros after a decimal point might vary. For example, an input value of 10.000 might be represented as 10 in the output file.

The reason these changes occur is that, during pass-through, certain data fields are parsed and stored as Java objects other than strings, for example, Date or Double.

The actual value of all the information must remain the same.