Importing and Configuring Components in ePM

This section explains how import, create, and configure TPs, Action Groups, Transaction Profiles, and Schedules in the HIPAA PM sample scenario, using the eXchange ePM. Additionally, the section describes how to use ePM to set the configuration parameter values for the Transaction Profiles and their related components.

For detailed procedures on how to use TPs, Action Groups, Transaction Profiles, and Schedules, see the eXchange Integrator User’s Guide.

Getting Started

Before you begin, it is recommended that you do all the procedures given in the previous sections of this chapter. Also, your Integration Server must be running. Also, your LDAP system and eXchange database (Oracle) must be running and accessible. However, Enterprise Designer does not need to be running.

For a general description of the outbound and inbound messaging ToPartner and FromPartner model used by ePM, see Configuring ePM: ToPartner and FromPartner Messaging Model.

You must do the procedures given under Running ePM to run ePM. In addition, after you run ePM, it is recommended that you do the procedures given under Importing B2B Hosts and Importing TPs.

If you want, you can create your own B2B Hosts and TPs using the procedures given in this section and using the sample scenario B2B Hosts and TPs as models. For more details, see the eXchange Integrator User’s Guide.

The remainder of this section explains these operations.

For detailed information on configuring ePM, see Chapter 4, Configuring HIPAA PM.

Exporting the necessary ePM Files

The ePM export files for the B2B Hosts, TPs, and Schedules are located in Project Explorer under eXchange, as follows:

• ePMImport ⇒ HIPAA ⇒ Hosts ⇒ envA_HIPAA_Host.exp and envB_HIPAA_Host.exp

• ePMImport ⇒ HIPAA ⇒ Schedulers ⇒ envA_HIPAA_S1.exp and envB_HIPAA_S1.exp

• ePMImport ⇒ HIPAA ⇒ TP_Profiles ⇒ envA_HIPAA_TP_Berlin.exp and envB_HIPAA_TP_Atlanta.exp

For more information, see Exporting ePM Files. It is recommended that you set up a folder structure to contain these files, which reflects this organization, for example:

C:\temp\eXchange\Sample\HIPAA\TP_Profiles

For more information on how to use ePM, see the eXchange Integrator User’s Guide.

Running ePM

This section explains how to start running eXchange ePM.

To Run ePM

1. Start a browser session.

2. Enter the Logical Host name and ePM port number with epm appended, as follows:

   http://logicalhost:port+1/epm

   For example:

   http://localhost:18001/epm

3. When the sign-in window appears, enter your Enterprise Manager user name (or the new user described under Adding a New User to ePM and Message Tracking), as well as the appropriate password, and click Sign In.

   The initial ePM window appears. See Figure 6–10.

   Figure 6–10 ePM Window

   
   

   The ePM window has the following sections:

   • ePM Explorer

     • B2B Host Configuration tab

     • Trading Partner Configuration tab

   • ePM Canvas

     ---

     Note –

     For complete instructions on how to use ePM, see the eXchange Integrator User’s Guide.

     ---

Importing B2B Hosts

Your next step is importing the Atlanta and Berlin B2B Host files, as explained under this section.

This sample scenario has the following B2B Hosts:

• envA_HIPAA_Host: For Atlanta.

• envB_HIPAA_Host: For Berlin.

To Import the envA B2B Host

1. Log in to ePM for envA (dmnA).

2. Click the B2B Host Configuration tab, if Host Explorer is not already displayed.

3. In Host Explorer, click and expand B2B Repository.

4. Select the B2B Host envA_HIPAA_Host.

5. At the bottom of ePM Canvas, click Import.

6. When you are finished, click Save.

To Import the envB B2B Host

1. Log in to ePM for envB (dmnB).

2. Click the B2B Host Configuration tab, if Host Explorer is not already displayed.

3. In Host Explorer, click and expand B2B Repository.

4. Select the B2B Host envB_HIPAA_Host.

5. At the bottom of ePM Canvas, click Import.

6. When you are finished, click Save.

Using Schedules

Next, you must import the Schedules for the B2B Hosts.

To Import a Schedule

1. Log in to ePM for envA (dmnA) for Atlanta; use envB (dmnB) for Berlin.

2. Click the B2B Host Configuration tab.

3. ePM Explorer with this tab selected appears.

4. Click the Schedule icon in ePM Explorer.

5. Select the Schedule file you want to import (envA_HIPAA_S1.exp for envA and envB_HIPAA_S1.exp for envB).

6. Click Import.

7. When you are finished, click Save.

To Modify an Existing Schedule

1. Log in to ePM for envA (dmnA) for Atlanta; use envB (dmnB) for Berlin.

2. Click the B2B Host Configuration tab.

   ePM Canvas with this tab selected appears.

3. Click the Settings tab.

4. In ePM Canvas, modify the scheduling information for the current Schedule, as necessary. This information is for inbound only.

5. When you are finished, click Save.

Importing TPs

Your next step is importing or creating the Atlanta and Berlin TP files, as explained under this section. Keeping track of the TPs, where they are sent from, and where they are received depends on which company you consider to be your current company. See Configuring ePM: ToPartner and FromPartner Messaging Model.

This sample scenario has the following TPs:

• Berlin: For Atlanta.

• Atlanta: For Berlin.

  ---

  Note –

  Also, you may create and construct these TPs yourself, using the sample TPs as models.

  ---

This sample scenario has the following TP files (under TP_Profiles):

• envA_HIPAA_TP_Berlin.exp: For Atlanta.

• envA_HIPAA_TP_Atlanta.exp: For Berlin.

To Import the Berlin TP to EnvA

1. Click the Trading Partner Configuration tab.

   The ePM window with this tab selected appears. See Figure 6–11.

   Figure 6–11 ePM Window With Trading Partner Configuration Tab Selected

   
   

2. From this window, click Import.

   The Import a Trading Partner - Step 1 of 2 window appears in ePM Canvas.

3. Name the TP Berlin.

4. Browse to the folder where you have stored your TP files and select envA_HIPAA_TP_Berlin.exp, then click Next.

   The Import a Trading Partner - Step 2 of 2 window appears.

5. Choose envA_HIPAA, from the pull-down menu.

6. Click Finish.

To Locate the Berlin TP in the ePM Window

1. In the upper left side of the ePM window, click Select.

   The Select the Trading Partner to Configure window appears in ePM Canvas.

2. Click Search on the canvas.

   Any available TPs appear directly below.

3. In this case, you are looking for Berlin, which appears.

4. Click the TP name, in this case Berlin, to configure the TP.

To Import the Atlanta TP to envB

1. Click the Trading Partner Configuration tab.

   The ePM window with this tab selected appears.

2. From this window, click Import.

   The Import a Trading Partner - Step 1 of 2 window appears in ePM Canvas.

3. Name the TP Atlanta.

4. Browse to the folder where you have stored your TP files and select envB_HIPAA_TP_Atlanta.exp, then click Next.

   The Import a Trading Partner - Step 2 of 2 window appears.

5. Choose envB_HIPAA, from the pull-down menu.

6. Click Finish.

To Locate the Atlanta TP in the ePM Window

1. Use the same procedure as explained for Berlin TP.

Using Action Groups and Transaction Profiles

You do the actual configuration of Action Groups and Transaction Profiles using parameters available using the following levels of the ePM Explorer tree:

• Business Protocols

• Delivery Protocols

• Transports

More information on how to configure Transport parameters is available in the eXchange Integrator User’s Guide. For information on how to configure these parameters in the sample scenario, see Configuring Transports.

Configuring the Sample Scenario

You may use the ePM for the Projects in the sample scenario as a model to complete the configuration of ePM. Enter information in ePM as shown in the sample. For more information, see Chapter 4, Configuring HIPAA PM and the eXchange Integrator User’s Guide.

Using Parameters in ePM

Many of the Business and Delivery Protocol parameters are the same, regardless of the PM and business communication protocol you are using. However, some of them are HIPAA PM-specific and are only present for HIPAA.

This section describes these parameters under:

• Interchange Envelope Parameters

• Functional Group Parameters

For more information on these parameters, see Configuring HIPAA PM ePM Parameters.

For more information on parameters not described under this section, see the eXchange Integrator User’s Guide.

To Enter an Override Value for a Parameter

1. Click the check box next to the parameter you want to override, under the Override column (see Figure 6–12 for an example).

2. Enter the appropriate override in the text box for the parameter.

3. Click Save.

ePM Configuration General Operation

In the sample scenario, you import preconfigured B2B Hosts and TPs.

When you are configuring your own (for example, if you are creating B2B Hosts and TPs from scratch), it is recommended that you use the following general order of configuration operations when setting values in ePM:

• On the B2B Host Configuration tab, create a new B2B Host Transaction Profile.

• Create a new Action Group (ePM here calls this a Business Action Group) for the B2B Host. Be sure to choose the correct Delivery Action and External Transport for the Action Group’s Business Actions.

• On the Trading Partner Configuration tab, create a new TP.

• For the new TP, select the Transaction Profile from the B2B Host.

• Choose the necessary settings (Settings tab) for the current TP Transaction Profile.

• Open any applicable Business Actions and set appropriate overrides, as necessary.

Interchange Envelope Parameters

The HIPAA PM-specific Interchange Envelope (outer envelope or ISA) parameters appear in ePM Canvas as shown in Figure 6–12. The example shown is for the Berlin TP’s 270 ToPartner Transaction Profile.

Figure 6–12 HIPAA PM-specific Interchange Envelope Parameters: Example

You may display the example in Figure 6–12 by using ePM Explorer, under B2B Repository ⇒ envA_HIPAA ⇒ Business Protocols ⇒ HIPAA.

As you can see, there are no override values entered in Figure 6–12, and the configuration accepts all the defaults. You may override the defaults for any parameter by clicking a check box under Override and entering a different value, as necessary.

You may, of course, do the same override operation with other ePM parameters, as described under Configuring eXchange Partner Manager: Overview.

Functional Group Parameters

The HIPAA PM-specific Functional Group (inner envelope or GS) parameters appear in ePM Canvas as shown in Figure 6–13. The example shown is for the Atlanta TP’s 270 FromPartner Transaction Profile.

Figure 6–13 HIPAA PM-specific Functional Group Parameters: Example

You may display the example in Figure 6–12 by using ePM Explorer, under B2B Repository ⇒ envA_HIPAA ⇒ Business Protocols ⇒ HIPAA.

As you can see, four overrides value has been entered in Figure 6–13, and the configuration uses the defaults for all other displayed parameters. As explained previously, you may override the default values, as necessary.

Necessary Overrides

The configured overrides in the imported ePM files may not be appropriate to your system. You may need to configure additional overrides, as necessary, depending on your own system setup. It is recommended that you check the ePM interface for the Projects in the sample scenario as a model to ensure the correct configuration of ePM.

You must configure overrides for the following Business Protocol ePM values, as appropriate to your system:

• Business Message Syntax Validation Handler: Allows you to specify the third-party validation service for HIPAA PM .

• Custom External Unique ID Handler: Allows you to select the external unique ID handlers, and which ones take priority. This parameter also allows you to set up eXchange to use the appropriate messaging unique IDs.

• Save Report to Files and Report File Directory: Allows you to save interleaved error reports to text files and send copies of these files to a predefined directory.

Default for ePM Parameter GS08

The current default value for the GS08 parameter is 00401X091. You must change this default so that it matches the version for each of the HIPAA transactions defined in ePM. For example, you must enter 00401X092A1 for the HIPAA 270 Addenda.

For more information on this parameter, see GS08 Vers/Rel/Indust ID Code. Figure 6–13 shows the parameter in ePM, reflecting an inherited override setting.

Handler Settings

The Custom External Unique ID Handler and Business Message Syntax Validation Handler parameters are located in ePM’s TP Transaction Profile’s Settings tab. Make sure both of these parameters are set correctly, according to their usage in your system. See Figure 6–14, from the sample scenario’s Berlin TP for envA (Atlanta).

Figure 6–14 ePM Handler Settings

If the Unique ID handler is not selected, or if the message itself does not contain the Unique ID field (it is an optional field), random numbers are generated for the message Unique IDs. Third-party defined Unique IDs are not supported.

Configuring Transports

Table 6–2 lists the Transports parameter override values you must enter to configure B2B Host Configuration ⇒ envA_HIPAA ⇒ Transports ⇒ BatchLocalFile.

Table 6–3 lists the Transport parameter override values you must enter to configure B2b Host Configuration ⇒ envB_HIPAA ⇒ Transports ⇒ BatchLocalFile.

Running the Sample

See Running the Sample Scenario for information on how to complete the passing of data between the two TPs.

The results after running the sample scenario:

• ...\HIPAA\Data\Atlanta folder contains

  • one 270 message

  • one 997 message

  • two TA1 messages

• ...\HIPAA\Data\Berlin folder contains

  • one 271 message

  • one 997 message

  • two TA1 messages