Skip Headers

Oracle® Health Sciences Information Gateway CONNECT Gateway and Adapter Installation and Configuration Guide Release 2.0.1 E37024-02 |
Home | Book List | Contents | Index | Contact Us

Previous | Next
| PDF · Mobi · ePub

# 3 Configuring the Oracle Health Sciences Information Gateway CONNECT Gateway and Adapter

This section describes how to do the configure the adapter to connect to Oracle services instead of the internal test services. This chapter contains the following topics:

- Configuring the Adapter with Oracle Health Sciences Information Manager Health Record Locator

- Configuring the Adapter with Oracle Healthcare Master Person Index

- Configuring the Adapter with Oracle Health Sciences Transaction Database

## 3.1 Configuring the Adapter with Oracle Health Sciences Information Manager Health Record Locator

This section describes how to configure the adapter to connect to the Oracle Health Sciences Information Manager (OHIM) registry to Record Locator instead of the internal test document registry.

Prerequisite:

Configuration and validation specified in Section 2.5, "Validating Oracle Health Sciences Information Gateway CONNECT using Universal Client" are completed successfully.

### 3.1.1 Installing Certificates

1. Log in to the adapter host. If not done already, create and import the certificate for the adapter host in to your application server's keystore. For details, refer to the following GlassFish or Weblogic application server documentation:

   Sun GlassFish Enterprise Server v2.1.1

   `http://docs.oracle.com/cd/E19879-01/index.html`

   Oracle® Fusion Middleware Securing Oracle WebLogic Server

   `http://docs.oracle.com/cd/E23943_01/web.1111/e13707/toc.htm`

2. Import the OHIM Health Record Location host's certificate or its CA's certification into your adapter application server's truststore.

3. Log in to the OHIM Health Record Locator host. If not done already, import the OHIM Health Record Locator's certificate into your application server's keystore.

4. Import the OHIG adapter host's certificate or its CA's certification into your OHIM Health Record Locator application server's truststore.

### 3.1.2 Configuring Oracle Health Sciences Information Gateway CONNECT Adapter with Oracle Registry

For information on configuring OHIG CONNECT Adapter with Oracle registry, refer to Section B.1, "Configuring Oracle Health Sciences Information Gateway CONNECT Adapter with Oracle Registry" in Appendix B, "Configuring Oracle CONNECT Adapters with Oracle Components".

### 3.1.3 Setting up Components

#### 3.1.3.1 Loading Test Data in Oracle Health Sciences Information Manager Health Record Locator's Oracle Database

To load test data into Health Record Locator's Oracle Database, perform the following steps:

1. Log in to the OHIG adapter host.

2. Copy the file from `<install_dir>/addons/adapter/hrl/rls_oracle_db_scripts.zip` to the host where you have an SQL Plus client present in the PATH, and Bash or Sh shell is available. Extract the contents.

3. Log in to the host having SQL Plus, and change the directory to where you copied or extracted the files in the previous step.

4. Ensure that SQL Plus is available in the PATH, then run the script as follows:

   `> bash loadTestData.sh`

5. When prompted, enter information for the registry database host, port, SID, ADT user password, and HRLCORE user password.

### 3.1.4 Validating Adapter Configuration with Oracle Health Sciences Information Manager Health Record Locator

Perform the steps specified in Section 2.5, "Validating Oracle Health Sciences Information Gateway CONNECT using Universal Client" to validate the adapter's configuration with OHMPI Health Record Locator. Apart from Universal Client UI, observe HRL logs during these steps to confirm Adapter is configured to connect to HRL.

## 3.2 Configuring the Adapter with Oracle Healthcare Master Person Index

This section describes how to configure the adapter to connect to OHMPI instead of the internal test patient master person index.

Prerequisite:

Configuration and validation specified in Section 2.5, "Validating Oracle Health Sciences Information Gateway CONNECT using Universal Client" are completed successfully.

### 3.2.1 Installing Certificates

1. Log in to the adapter host. If not done already, create and import the certificate for the adapter host in to your application server's keystore. For details, refer to the following GlassFish or Weblogic application server documentation:

   Sun GlassFish Enterprise Server v2.1.1

   `http://docs.oracle.com/cd/E19879-01/index.html`

   Oracle® Fusion Middleware Securing Oracle WebLogic Server

   `http://docs.oracle.com/cd/E23943_01/web.1111/e13707/toc.htm`

2. Import the OHIM Health Record Location host's certificate or its CA's certification into your adapter application server's truststore.

3. Log in to the OHIM Health Record Locator host. If not done already, import the OHIM Health Record Locator's certificate into your application server's keystore.

4. Import the OHIG adapter host's certificate or its CA's certification into your OHIM Health Record Locator application server's truststore.

### 3.2.2 Configuring Oracle Health Sciences Information Gateway CONNECT Adapter with Oracle Master Person Index

For information on configuring OHIG CONNECT Adapter with Oracle MPI, refer to Section B.2, "Configuring Oracle Health Sciences Information Gateway CONNECT Adapter with Oracle Healthcare Master Person Index" in Appendix B, "Configuring Oracle CONNECT Adapters with Oracle Components".

### 3.2.3 Setting up Components

#### 3.2.3.1 Creating Oracle Health Sciences Information Gateway CONNECT Test Patients

Note:

Before proceeding with creating OHIG CONNECT test patients, ensure that you have already validated your configuration with OHIM HRL as described in Section 3.1.3, "Setting up Components" and Section 3.1.4, "Validating Adapter Configuration with Oracle Health Sciences Information Manager Health Record Locator".

Perform the following steps to create OHIG CONNECT test patients:

1. Login to the OHMPI Master Index Data Manager (MIDM) web application.

   `http://<ohmpi_host_url>:8080/PatientMIDM`

2. A default user with MasterIndex.Admin,Administrator group privileges has already been created in the GlassFish file realm.

   User: mdm

   Password: mdm

3. In the Source Record tab, select Add and create the following patients in the MIDM:

       System: SelfTest System 1
       LocalID: D123401
       FirstName: Gallow
       LastName: Younger
       SSN: 999-99-9999
       Gender: Male
       Date of Birth: 06/27/1999
       Address Type: street address line
       Address Line1: 123 Main street
       City: LEESBURG
       State Code: VA
       Postal Code: 20176

       System: SelfTest System 1
       LocalID: D123407
       FirstName: Jordy
       LastName: LaForge
       SSN: 999-99-9999
       Gender: Female
       Date of Birth: 11/14/1923
       Address Type: delivery address line
       Address Line1: 5804 Post Corners Trl
       City: Centerville
       State Code: VA
       Postal Code: 20120

       System: SelfTest System 1
       LocalID: D123409
       FirstName: Audrey
       LastName: Kim
       SSN: 999-99-9999
       Gender: Female
       Date of Birth: 03/14/1980
       Address Type: street address line
       Address Line1: 14701 Demming Drive
       City: Gainsville
       State Code: VA
       Postal Code: 20155

       System: SelfTest System 1
       LocalID: D123402
       FirstName: Anna
       LastName: Schnur
       SSN: 999-99-9999
       Gender: Female
       Date of Birth: 08/13/1956
       Address Type: street address line
       Address Line1: 312 HILL ROAD
       City: HILLSBRO
       State Code: MO
       Postal Code: 37660

4. Note that the EUID returned on each of the above patients and update the PatientIDs in the NHINC and HRL databases by following the instructions below.

Updating the NHINC Database with New Patient IDs

1. Log into OHIG Adapter host.

2. Copy the file from `<install_dir>/addons/adapter/ohmpi/ohmpi_nhinc_db.tgz` to the host where you have an SQL Plus client present in the PATH and Bash or Sh shell is available. Extract the contents (for example, `tar -zxvf ohmpi_nhinc_db.tgz`).

3. Update script `nhinc3_upd_nhinc_patients.sh` with variable oracleDBScriptsDir pointing to the path where the above file was extracted.

4. Run the script `nhinc3_upd_nhinc_patients.sh`.

   `> bash nhinc3_upd_nhinc_patients.sh`

5. The script will prompt for the OHIG Oracle database host, port, SID, and NHINCUSER database user password.

6. When prompted, enter new patient IDs for the patients D123401/GallowYounger, D123407/Jordy LaForge, D123409/Audrey Kim, and D123402/AnnaSchnur.

Updating the HRL Database with New Patient IDs

1. Log in to OHIG Adapter host.

2. Copy the file from `<install_dir>/addons/adapter/ohmpi/ohmpi_rls_db.tgz` to the host where you have an SQL Plus client present in the PATH and Bash or Sh shell is available. Extract the contents (for example, `tar -zxvf hia11_ohmpi_rls_db.tgz`).

3. Update script `nhinc3_upd_rls_patients.sh` with variable oracleDBScriptsDir pointing to the path where the above file was extracted.

4. Run the script `nhinc3_upd_rls_patients.sh`.

   `> bash nhinc3_upd_rls_patients.sh`

5. The script will prompt for the OHIG Oracle database host, port, SID, and ADT and HRLCORE database users passwords.

6. When prompted, enter new patient IDs for the patients D123401/GallowYounger, D123407/Jordy LaForge, D123409/Audrey Kim, and D123402/AnnaSchnur.

### 3.2.4 Validating Adapter Configuration with Oracle Healthcare Master Person Index

Perform the steps specified in Section 2.5, "Validating Oracle Health Sciences Information Gateway CONNECT using Universal Client" to validate the adapter's configuration with OHMPI. Apart from the Universal Client user interface, observe OHMPI logs during these steps to confirm that the adapter is configured to connect to OHMPI.

## 3.3 Configuring the Adapter with Oracle Health Sciences Transaction Database

This section describes how to configure the adapter to connect to the Oracle Health Sciences Health Transaction Database (HTB) instead of the internal test document repository.

Prerequisite:

Configuration and validation specified in Section 2.5, "Validating Oracle Health Sciences Information Gateway CONNECT using Universal Client" are completed successfully.

### 3.3.1 Installing Certificates

1. Log in to the adapter host. If not done already, create and import the certificate for the adapter host in to your application server's keystore. Refer to the GlassFish or Weblogic application server documentation for details.

   Sun GlassFish Enterprise Server v2.1.1

   `http://docs.oracle.com/cd/E19879-01/index.html`

   Oracle® Fusion Middleware Securing Oracle WebLogic Server

   `http://docs.oracle.com/cd/E23943_01/web.1111/e13707/toc.htm`

2. Also import the HTB host's certificate or its CA's certification into your adapter application server's truststore.

3. Log in to the HTB host. If not done already, import the OHIM Health Record Locator's certificate into your application server's keystore.

4. Import the OHIG adapter host's certificate or its CA's certification into your HTB application server's truststore.

### 3.3.2 Configuring Oracle Health Sciences Information Gateway CONNECT Adapter with Oracle Repository

For information on configuring OHIG CONNECT Adapter with Oracle repository, refer to Section 3.3, "Configuring the Adapter with Oracle Health Sciences Transaction Database" in Appendix B, "Configuring Oracle CONNECT Adapters with Oracle Components".