This chapter provides detailed procedures that describe how to construct, run, and monitor the HIPAA PM sample implementation scenario.
If you prefer to see runtime results quickly without learning the detailed procedures, use the Quick Start.
To perform the sample scenario implementation, you need to set up the sample projects, their environments, and their components using the eGate Enterprise Designer with eInsight and eXchange.
The sample implementation scenario demonstrates inbound and outbound message processing between the Atlanta Company and the Berlin Company. In the sample's business scenario, each company has an eXchange installation, and the two companies trade data. This sample scenario and its Projects demonstrate the configuration of eXchange to support HIPAA. The current viewpoint is assumed to be Atlanta.
The resulting B2B solution functions as follows:
HIPAA 270 Health Care Eligibility Benefit Inquiry payloads are read from a local (internal) file.
The individual payloads are wrapped in the inner and outer HIPAA envelopes and sent to the Berlin TP.
Berlin replies with a TA1 and 997 Functional Acknowledgments.
Berlin delivers an 271 Health Care Eligibility Benefit Response eXchange prepares and writes the individual response payloads to an internal file and displays the messages in Message Tracking.
For more information solving business problems using eXchange with eInsight and eGate, including additional details on implementation, see the eXchange Integrator User’s Guide, eInsight Business Process Manager User’s Guide, and eGate Integrator User’s Guide.
Figure 6–1 shows an operational diagram of the sample scenario.
The sample assumes you use default configurations for all servers, where possible, and that you make any changes in Enterprise Designer, where needed, for example:
Oracle – You must create a new outbound Oracle external system instance for each environment and configure it for your system, even if you imported the sample environments. Sample parameters are for reference only. Any Oracle database used by eXchange must be accessible to eGate. You must know the database's Oracle SID, user name, and password. Create and configure the eXchange database using the Oracle510.zip file. For more information see the Oracle eWay Adapter User’s Guide.
LDAP – You must create a new outbound LDAP external system instance for each Environment and configure it for your system, even if you imported the sample Environments. Sample parameters are for reference only. Any LDAP application used by eXchange must be accessible to eGate. For more information see the LDAP eWay Adapter User’s Guide.
HTTPS – For information on how to configure your HTTP server or client to use SSL, see the HTTP(S) eWay Adapter User’s Guide.