Skip Headers
Oracle® Health Sciences Information Manager Policy Engine Installation and Configuration Guide
Release 1.1
E21366-01
  Go To Table Of Contents
Contents
Previous
Previous 		 Next
Next		  

1 Installing and Configuring HIM Policy Engine

This chapter provides the instructions to install and configure the Policy Engine VM template. Also, it provides the instructions on how to configure CONNECT software on HIG Adapter/Gateway VMs to make use of openSSO-based Policy Engine.

This chapter includes the following sections:

1.1 Understanding HIM Policy Engine Components and Templates

The HIM Policy Engine template uses the "Paravirtualized" virtualization method. The template is distributed as a compressed tar file (*.tgz). The compressed tar file contains two binary files and a text file. The binary files are the disk images taken from a fully configured and functional VM. The text file is a VM configuration file.

1.1.1 HIM Policy Engine Components

The contents of the compressed tar file is listed below:

  • Disk Image with Oracle Software

    /appliance.img

  • Disk Image with Operating System

    /System.img

  • VM Configuration File

    /vm.cfg

1.1.2 HIM Policy Engine VM Template

The VM consists of the following pre-installed software:

  • Oracle Enterprise Linux 5 (as in System.img)

    http://www.oracle.com/technetwork/topics/linux/whatsnew/index.html

  • HIM specific software (as in appliance.img)

    • Apache Ant 1.8.1

      Install directory: /home/common/ant

    • Java Development Kit 1.6.0_X

      Install directory: /home/common/java/latest (symbolic link to JDK 1.6.0_X)

    • For hiauser only:

      • HIM Ant Configuration Utility

        Install directory: /home/hiauser/config

      • Netbeans 6.7.1

        Install directory: /home/hiauser/netbeans-6.7.1

      • Glassfish Enterprise Server 2.1.1

        Install directory: /home/hiauser/SUNWappserver

        Admin user

        - Username: admin

        - Password: adminadmin

        Admin Console

        - http://<VM_IP or VM_HOST_NAME >:4848

      • OpenSSO 8.0 Update 2

        Install directory: /home/hiauser/opensso

        OpenSSO Admin user

        - Username: amAdmin

        - Password: adminadmin

        OpenSSO Admin Console

        - http://<VM_IP or VM_HOST_NAME >:8080/opensso

  • VM Memory Settings:

    • 2 GB (2048 MB) of RAM


      Note:

      The RAM memory setting can be changed after installation in VM Manager.

    • 16 GB of Disk Space

  • Linux Users:

    • Root user

      • Username: root

      • Linux Group: root

      • Password: ovsroot

    • HIM specific user

      • Username: hiauser

      • Linux Group: hiauser

      • Password: hiapass


    Tip:

    For security purposes, it is recommended that you change the default passwords after installation.

1.2 Importing the HIM Policy Engine Template

To import the HIM Policy Engine VM template:

  1. Copy the HIM Policy Engine VM template .tgz file to the /OVS/seed_pool directory of your Oracle VM Server machine.

  2. Uncompress the .tgz file:

    > tar -zxvf <FILENAME>.tgz

    This step creates a directory with the name of the template.

    Example:

    > cd /OVS/seed_pool
> tar -zxvf /OVS/seed_pool/OVM_HIAV11_X86_POLICYENGINE_PVM.tgz

    Creates the directory:

    /OVS/seed_pool/OVM_HIAV11_X86_POLICYENGINE_PVM

  3. Log in to the Oracle VM Manager


    Note:

    The default location for the Oracle VM Manager log in screen is http://<VM_MANAGER_HOST_NAME>:8888/OVS.

  4. From the Oracle VM Manager console:

    1. Click the Resources tab. The Virtual Machine Templates screen is displayed.

    2. Click the Import button. The Source screen is displayed.

    3. Choose the Select from Server Pool (Discover and register) radio button.

    4. Click Next. The General Information screen is displayed.

      Enter or select the following general information:

      - The server pool on which the virtual machine will be located.

      Server Pool Name: <SERVER_POOL_NAME>

      - The operating system of the Virtual Machine Operating System:

      Oracle Enterprise Linux 5

      - The Oracle VM template to be imported.

      Virtual Machine Template Name: <VM_TEMPLATE_NAME>

      - The username used to log in to the Virtual Machine.

      Virtual Machine System Username: root

      - The password used to log in to the Virtual Machine.

      Virtual Machine System Password: ovsroot

    5. Click Next. The Confirm Information screen is displayed.

    6. Click Confirm. The Virtual Machine Template screen is displayed with a message to confirm the VM template has been imported.

  5. Click the Resources tab to see the list of available VM templates.

  6. To make the Virtual Machine template available for use, select the Virtual Machine template and click Approve, moving the VM template from the "Pending" state to the "Active" state.

    The VM template is imported and ready for use in Oracle VM Manager.

1.3 Creating the HIM Policy Engine VM

To create the HIM Policy Engine VM from the VM template:

  1. Create a new VM using the Policy Engine VM template just installed by following the instructions in the VM Manager 2.2 User's Guide (refer to Section 6.3.1, "Creating Virtual Machine from a Template").

  2. To power on the Virtual Machine select the Virtual Machines tab, select the Virtual Machine Name, and click Power On.

  3. In the VM Manager Console ensure that the Policy Engine VM is now in the running state (Status=Running).

1.4 Configuring the HIM Policy Engine VM

This section provides instructions for configuring the HIM Policy Engine VM.

1.4.1 How to VNC into a VM

To VNC into a VM:


Note:

To enable the VNC Port link in the VM Manager follow the instructions in "Installing OVM Console" at http://oss.oracle.com/oraclevm/manager/RPMS/README-console.

Expand the details of the VM by clicking the + on Show. You can VNC into the box from the VM Manager by clicking on the VNC Port link under the VM details, or you can use a VNC client to log in using the address:

<VM_SERVER_HOST_NAME>:<VM_VNC_PORT>

1.4.2 Configuring the VM Network Settings

To configure the VM to use static IP:


Note:

The VM is configured by default to use DHCP to assign an IP address.

If you are using DHCP addressing you can skip the following steps.

  1. To configure the VM to use static IP, log in as the root user (default password: ovsroot) and set the IP using the following steps:

    1. Select System, Administration, and then Network.

    2. Choose Devices, click Edit, select the Statically Set IP Address radio button, and then enter the following values:

      - Address: <VM_IP>

      - Subnet mask: <SUBNET_MASK>

      - Default Gateway address: <DEFAULT_GATEWAY_ADDRESS>

    3. Click OK.

    4. Choose File and then click Save.

    5. Click the DNS tab and then enter the following values:

      - Hostname: <VM_HOST_NAME>

      - Primary DNS: <PRIMARY_DNS>

      - Secondary DNS: <SECONDARY_DNS>

      - Tertiary DNS: <TERTIARY_DNS>

      - DNS search path: <VM_NAME_SUFFIX>

    6. Choose Next and then click Save.

    7. Choose the Hosts tab, click New, and then enter the following values:

      - Address: <VM_IP>

      - Hostname: <VM_HOST_NAME>

      - Aliases: <VM_NAME_PREFIX> hostname

    8. Click OK.

    9. Choose File and then click Save.

    10. Restart Network Services from a terminal window.

      > service network restart

    11. Check the output for <VM_IP>.

      > ifconfig

    12. Check the output for <VM_HOST_NAME>.

      > hostname

    13. Check the success of:

      > ping <VM_IP>

    14. Check the success of:

      > ping <VM_HOST_NAME>

1.4.3 Configuring HIM Policy Engine VM

To configure the HIM Policy Engine VM:

  1. Log in to the VM as hiauser (default password: hiapass).

  2. Start the application server using the following commands

    1. > cd /home/hiauser/SUNWappserver/bin

    2. > asadmin start-domain domain1

  3. Navigate to the directory: /home/hiauser/config.

  4. Run the script import-policyengine-svc-cfg.sh to import the service configuration data to the opensso configuration datastore, and to update the bootstrap file which is used by opensso to retrieve configuration data to bootstrap itself.


    Note:

    You can run ifconfig on your VM to determine the ip address.

    Example:

    >sh import-policyengine-svc-cfg.sh                – The VM_IP address of your Policy Engine Virtual Machine                   Enter policy_engine_host_ip: <POLICY_ENGINE_VM_IP>               - The VM_IP address of your Gateway Virtual Machine        Enter gateway_host_ip: <GATEWAY_VM_IP>         - For the commnad, "Directory Service contains existing data. Do you want to delete it? [y|N]"                 Provide y as the option, and hit Enter key. You will see the following message on the console           Please wait while we import the service configuration...                Upon successful completion of the service configuration import, you will see the message                Service Configuration was imported.

  5. Stop the application server using the following commands:

    1. > cd /home/hiauser/SUNWappserver/bin

    2. > asadmin stop-domain domain1

  6. Navigate to the directory: /home/hiauser/config.


    Note:

    Before proceeding to the next step, configure a fully-qualified-hostname for the Virtual Machine.

    The following step produces a self-signed certificate for use during initial installation and testing. Use appropriate signed certificates for production use.

  7. Run the script create-and-import-selfsigned-certs.sh to install the self-signed certificate. It does the following things.

    • Creates the keystore for the private internal key

    • Exports the certificate that will authenticate the internal key

    • Imports the trusted certificates into the truststore

    • Provides these certificates to appserver to use for authentication purposes

    >sh create-and-import-selfsigned-certs.sh

1.5 Installing Patches and Self-signed Certificates on HIG Adapter VM (if not done already)

  1. Log in to the Adapter VM as hiauser (password: hiapass)

  2. Get the /home/hiauser/config/hig_patch001.tgz file from Policy Engine VM using hiauser (password: hiapass).

  3. Stop the application server using the following commands:

    1. > cd /home/hiauser/SUNWappserver/bin

    2. > asadmin stop-domain domain1

  4. Navigate to the directory /home/hiauser/config using the following command:

    > cd /home/hiauser/config

  5. Uncompress the .tgz file:

    > tar -zxvf <FILE_PATH>/hig_patch001.tgz

    This creates the directory: /home/hiauser/config/hig_patch001.


    Note:

    FILE_PATH should be replaced with the absolute path where you downloaded the hig_patch001.tgz file.

  6. Navigate to the directory /home/hiauser/config/hig_patch001 using the following command:

    > cd /home/hiauser/config/hig_patch001

  7. Run the script install-adapter-patches.sh to install the patches into the CONNECT software on HIG Adapter VM:

    > sh install-adapter-patches.sh


    Note:

    Before proceeding to the next step, configure a fully-qualified-hostname for the Virtual Machine.

    The following step produces a self-signed certificate for use during the initial installation and testing. Use appropriate signed certificates for production use.

  8. Run the script create-and-import-selfsigned-certs.sh to install the self-signed certificate. It does the following things:

    • Creates the keystore for the private internal key

    • Exports the certificate that will authenticate the internal key

    • Imports the trusted certificates into the truststore

    • Provides these certificates to appserver to use for authentication purposes

    > sh create-and-import-selfsigned-certs.sh

1.6 Installing Patches and Self-signed Certificates on HIG Gateway VM (if not done already)

  1. Log in to the Gateway VM as hiauser (password: hiapass)

  2. Get the /home/hiauser/config/hig_patch001.tgz file from Policy Engine VM using hiauser (password: hiapass).

  3. Stop the application server using the following commands:

    1. > cd /home/hiauser/SUNWappserver/bin

    2. > asadmin stop-domain domain1

  4. Navigate to the directory /home/hiauser/config using the following command:

    > cd /home/hiauser/config

  5. Uncompress the .tgz file:

    > tar -zxvf <FILE_PATH>/hig_patch001.tgz

    This creates the directory: /home/hiauser/config/hig_patch001.


    Note:

    FILE_PATH should be replaced with the absolute path where you downloaded the hig_patch001.tgz file.

  6. Navigate to the directory /home/hiauser/config/hig_patch001 using the following command:

    > cd /home/hiauser/config/hig_patch001

  7. Run the script install-gateway-patches.sh to install the patches into the CONNECT software on HIG Gateway VM:

    > sh install-gateway-patches.sh


    Note:

    Before proceeding to the next step, configure a fully-qualified-hostname for the Virtual Machine.

    The following step produces a self-signed certificate for use during the initial installation and testing. Use appropriate signed certificates for production use.

  8. Run the script create-and-import-selfsigned-certs.sh to install the self-signed certificate. It does the following things:

    • Creates the keystore for the private internal key

    • Exports the certificate that will authenticate the internal key

    • Imports the trusted certificates into the truststore

    • Provides these certificates to appserver to use for authentication purposes

    > sh create-and-import-selfsigned-certs.sh

1.7 Installing HIG Adapter and Gateway VM Certificates on Policy Engine VM

  1. Log in to the Policy Engine VM as hiauser (password: hiapass)

  2. Ensure that the application server is not running. If it is running, stop it using the following commands:

    1. > cd /home/hiauser/SUNWappserver/bin

    2. > asadmin stop-domain domain1

  3. Navigate to the directory /home/hiauser/config using the following command:

    > cd /home/hiauser/config


    Note:

    Before proceeding to the next step, copy the certificate of the Adapter VM <ADAPTER_VM_HOSTNAME.cer> to the /home/hiauser/SUNWappserver/domains/domain1/config folder.

  4. To install the Adapter VM certificate, run the script import-others-cert.sh:

    > sh import-others-cert.sh

    • The hostname of the Adapter VM whose certificate is being imported into the appserver's truststore

      Enter the hostname of the machine whose certificate is being imported into appserver's truststore:

      <ADAPTER_VM_HOSTNAME>


    Note:

    Before proceeding to the next step, copy the certificate of the Gateway VM <GATEWAY_VM_HOSTNAME.cer> to the /home/hiauser/SUNWappserver/domains/domain1/config folder.

  5. To install the Gateway VM certificate, run the script import-others-cert.sh:

    > sh import-others-cert.sh

    • The hostname of the Gateway VM whose certificate is being imported into the appserver's truststore

      Enter the hostname of the machine whose certificate is being imported into the appserver's truststore:

      <GATEWAY_VM_HOSTNAME>

  6. Start the application server using the following commands:

    1. > cd /home/hiauser/SUNWappserver/bin

    2. > asadmin start-domain domain1

1.8 Installing HIG Gateway VM and Policy Engine VM Certificates on HIG Adapter VM

  1. Log in to the Adapter VM as hiauser (password: hiapass)

  2. Ensure that the application server is not running. If it is running, stop it using the following commands:

    1. > cd /home/hiauser/SUNWappserver/bin

    2. > asadmin stop-domain domain1

  3. Navigate to the directory /home/hiauser/config/hig_patch001 using the following command:

    > cd /home/hiauser/config/hig_patch001


    Note:

    Before proceeding to the next step, copy the certificate of the Gateway VM <GATEWAY_VM_HOSTNAME.cer> to the /home/hiauser/SUNWappserver/domains/domain1/config folder.

  4. To install the Gateway VM certificate, run the script import-others-cert.sh:

    > sh import-others-cert.sh

    • The hostname of the Gateway VM whose certificate is being imported into the appserver's truststore

      Enter the hostname of the machine whose certificate is being imported into appserver's truststore:

      <GATEWAY_VM_HOSTNAME>


    Note:

    Before proceeding to the next step, copy the certificate of the Policy Engine VM <POLICY_ENGINE_VM_HOSTNAME.cer> to the /home/hiauser/SUNWappserver/domains/domain1/config folder.

  5. To install the Policy Engine VM certificate, run the script import-others-cert.sh:

    > sh import-others-cert.sh

    • The hostname of the Policy Engine VM whose certificate is being imported into the appserver's truststore

      Enter the hostname of the machine whose certificate is being imported into the appserver's truststore:

      <POLICY_ENGINE_VM_HOSTNAME>

1.9 Installing HIG Adapter VM and Policy Engine VM Certificates on HIG Gateway VM

  1. Log in to the Gateway VM as hiauser (password: hiapass)

  2. Ensure that the application server is not running. If it is running, stop it using the following commands:

    1. > cd /home/hiauser/SUNWappserver/bin

    2. > asadmin stop-domain domain1

  3. Navigate to the directory /home/hiauser/config/hig_patch001 using the following command:

    >> cd /home/hiauser/config/hig_patch001


    Note:

    Before proceeding to the next step, copy the certificate of the Adapter VM <ADAPTER_VM_HOSTNAME.cer> to the /home/hiauser/SUNWappserver/domains/domain1/config folder.

  4. To install the Adapter VM certificate, run the script import-others-cert.sh:

    > sh import-others-cert.sh

    • The hostname of the Adapter VM whose certificate is being imported into the appserver's truststore

      Enter the hostname of the machine whose certificate is being imported into appserver's truststore:

      <ADAPTER_VM_HOSTNAME>


    Note:

    Before proceeding to the next step, copy the certificate of the Policy Engine VM <POLICY_ENGINE_VM_HOSTNAME.cer> to the /home/hiauser/SUNWappserver/domains/domain1/config folder.

  5. To install the Policy Engine VM certificate, run the script import-others-cert.sh:

    > sh import-others-cert.sh

    • The hostname of the Policy Engine VM whose certificate is being imported into the appserver's truststore

      Enter the hostname of the machine whose certificate is being imported into the appserver's truststore:

      <POLICY_ENGINE_VM_HOSTNAME>

1.10 Configuring CONNECT Software on HIG Adapter VM for OpenSSO Policy Engine


Note:

Make sure that HIG_Patch001 is applied to HIG Adapter before proceeding

  1. Log in to the Adapter VM as hiauser (password: hiapass).

  2. Get the /home/hiauser/config/ada_gw_pe_config.zip file from the Policy Engine VM using hiauser (password: hiapass).

  3. Ensure that the application server is not running. If it is running, stop it using the following commands:

    1. > cd /home/hiauser/SUNWappserver/bin

    2. > asadmin stop-domain domain1

  4. Navigate to the directory /home/hiauser/config using the following command:

    > cd /home/hiauser/config

  5. Unzip the ada_gw_pe_config.zip file to the config folder

    > unzip <FILE_PATH>/ada_gw_pe_config.zip


    Note:

    FILE_PATH should be replaced with the absolute path to which the ada_gw_pe_config.zip file was downloaded.

  6. Run the script config-adapter-policyengine.sh to configure the CONNECT Adapter which enables it to interact with openSSO-based Policy Engine.


    Note:

    You can run ifconfig on your Policy Engine VM to determine the ip address.

    > sh config-adapter-policyengine.sh

    • The VM_IP address of your Policy Engine Virtual Machine

      Enter policy_engine_host_ip: <POLICY_ENGINE_VM_IP>

    • The HTTP Port of the GlassFish Application Server which is installed on Policy Engine Virtual Machine

      Enter policy_engine_http_port: <GF_HTTP_PORT>

  7. Start the application server using the following commands:

    1. > cd /home/hiauser/SUNWappserver/bin

    2. > asadmin start-domain domain1

1.11 Configuring CONNECT Software on HIG Gateway VM for OpenSSO Policy Engine


Note:

Make sure that HIG_Patch001 is applied to HIG Adapter before proceeding.

  1. Log in to the Gateway VM as hiauser (password: hiapass).

  2. Get the /home/hiauser/config/ada_gw_pe_config.zip file from the Policy Engine VM using hiauser (password: hiapass).

  3. Ensure that the application server is not running. If it is running, stop it using the following commands:

    1. > cd /home/hiauser/SUNWappserver/bin

    2. > asadmin stop-domain domain1

  4. Navigate to the directory /home/hiauser/config using the following command:

    > cd /home/hiauser/config

  5. Unzip the ada_gw_pe_config.zip file to the config folder

    > unzip <FILE_PATH>/ada_gw_pe_config.zip


    Note:

    FILE_PATH should be replaced with the absolute path to which the ada_gw_pe_config.zip file was downloaded.

  6. Run the script config-gateway-policyengine.sh to configure the CONNECT Gateway which enables it to interact with openSSO-based Policy Engine.


    Note:

    You can run ifconfig on your Policy Engine VM to determine the ip address.

    > sh config-gateway-policyengine.sh

    • The VM_IP address of your Policy Engine Virtual Machine

      Enter policy_engine_host_ip: <POLICY_ENGINE_VM_IP>

    • The HTTP Port of the GlassFish Application Server which is installed on Policy Engine Virtual Machine

      Enter policy_engine_http_port: <GF_HTTP_PORT>

  7. Start the application server using the following commands:

    1. > cd /home/hiauser/SUNWappserver/bin

    2. > asadmin start-domain domain1

1.12 Consumer Preferences Document Creation Using SoapUI

This section assumes the following have already been setup, and applications/services on the HIG Adapter and Gateway are ready to test from the SoapUI project.

  1. If the GlassFish Application Server is not running on any of the VMs, start it by using the following commands:

    1. > cd /home/hiauser/SUNWappserver/bin

    2. > asadmin start-domain domain1

  2. Launch the SoapUI application on the test machine.

  3. Copy the /home/hiauser/config/files/opensso/soapui/AdapterPEPWS-soapui-project.xml file from Policy Engine VM to a directory on the test machine.

  4. From the File menu, click the Import Project sub-menu. This will display the "Select soapUI Project Files dialog" window

  5. Enter <FILEPATH>/AdapterPEPWS-soapui-project.xml as the filename.


    Note:

    FILE_PATH represents the absolute path to which the AdapterPEPWS-soapui-project.xml file has been copied.

  6. Click the Open button. The AdapterPEPWS-soapui-project.xml file is imported into your soapUI application.

  7. Open the test by selecting AdapterPEPWS -> AdapterPIPBindingSoap -> StorePtConsent -> StorePatientConsent1.


    Note:

    While testing using the default CONNECT Adapter provided Master Patient Index (mpi.xml), use the Patient ID: D123401.

  8. In the StorePatientConsent1 window, using the edit current option, set the endpoint URL for the request by using the correct IP address of HIG Adapter VM.

  9. Run the test by clicking the green arrow near the top left corner of the StorePatientConsent1 window.

  10. Run the test AdapterPEPWS -> AdapterPIPBindingSoap -> RetrievePtConsentByPtId -> RetrievePatientConsent to verify that the document was stored successfully.

  11. Update the patient preference by modifying the StorePatientConsent2 (AdapterPEPWS -> AdapterPIPBindingSoap -> StorePtConsent -> StorePatientConsent2) SOAP request where you use "false" for the "optIn" element, and include the policyOID element, which can be found in the response of the RetrievePatientConsent request.

    The modified request looks like:

    <soapenv:Envelope xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope"               xmlns:urn="urn:gov:hhs:fha:nhinc:common:nhinccommonadapter">             <soapenv:Header/>            <soapenv:Body>               <urn:StorePtConsentRequest>          <urn:patientPreferences>             <urn:patientId>0000000000</urn:patientId>         <urn:assigningAuthority>1.1</urn:assigningAuthority>              <urn:optIn>false</urn:optIn>              <urn:fineGrainedPolicyMetadata>              <urn:policyOID>20.200.20.31</urn:policyOID>               </urn:fineGrainedPolicyMetadata>             </urn:patientPreferences>            </urn:StorePtConsentRequest>         </soapenv:Body>              </soapenv:Envelope>

    Execute the modified StorePatientConsent2 request. This will update the patient's preference.

  12. Open the test AdapterPEPWS -> AdapterPEPBindingSoap -> CheckPolicy -> DocumentQueryIn.


    Note:

    While testing using the default CONNECT Adapter provided Master Patient Index (mpi.xml), for the resource-id attribute, use the string D123401 as the attribute value.

  13. In the DocumentQueryIn window, using the edit current option, edit the endpoint URL for the request by using the IP address of HIG Gateway VM.

  14. Run the test by clicking the green arrow near the top left corner of the DocumentQueryIn window. You will observe "Deny" in the response.

  15. Run the SOAP request AdapterPEPWS -> AdapterPIPBindingSoap -> StorePtConsent -> StorePatientConsent2. This time use "true" for the "optIn" element. This will again update the patient's preference.

  16. Rerun the test AdapterPEPWS -> AdapterPEPBindingSoap -> CheckPolicy -> DocumentQueryIn. This time you will observe "Permit" in the response.

1.13 Validating CONNECT on HIG Gateway and Adapter VMs

To validate the CONNECT software on the HIG Gateway and Adapter VMs after they are configured to use openSSO Policy Engine:

  1. Ensure that the GlassFish Application Server is up and running on Policy Engine, Gateway, and Adapter VMs using the following commands:

    1. > cd /home/hiauser/SUNWappserver/bin

    2. > asadmin start-domain domain1

  2. Validate the configuration using the sample universal client distributed with the Gateway:

    1. Launch the application by navigating to the following URL:

      http://<GATEWAY_VM_IP>:8080/UniversalClientGUI/

      The authentication page is displayed asking for user account details.

    2. Enter a valid username and password (user1/password)

    3. Click the Login button.

      - If the account details are correct, the Universal Client GUI Main page has the patient search tab enabled, while the rest of the tabs are disabled.

      - If the provided account details are incorrect, you will be prompted to enter the correct account details again.

    4. Search for a patient with the last name: “Younger”.

    5. If the installation is correct, this returns a page with the PatientId for the patient.

    6. Click the PatientId hyperlink for additional details on the patient.

    7. The Document tab is now enabled and you can search for patient documents by date range. Search for date range 08/01/2000 to 08/01/2010

    8. Click on the document URL to retrieve the document.

  Previous
Previous 		 Next
Next
  Go To Table Of Contents
Contents