This document is designed to help the user understanding and use of the sample portal application that accompanies IBM(R) WebSphere(R) Business Integration for Healthcare industry solution.
The WebSphere Business Integration for Healthcare sample portal application is not a supported component of the WebSphere Business Integration for Healthcare industry solution. It is provided to serve two main purposes:
The sample portal application is designed for the WebSphere Portal Server. Users logon through a browser, and the application communicates with the Healthcare industry solution components using a database and WebSphere MQ. The high-level architecture is shown in the following diagram:
The sample application uses WebSphere Portal Server as an application framework. This framework provides the following benefits:
The Healthcare sample portal application supports the EMR and Compliance Reporting use cases by implementing the following functionality:
Some of the following installation steps involving DB2(R) or WebSphere MQ will have been performed during installation of the WebSphere Business Integration for Healthcare industry solution. They are listed here for your reference, but do not need to be repeated.
This application has been tested only on WebSphere Portal Server installed on a Microsoft(R) Windows(R) 2000 system with Support Pack 3.
Software prerequisites include the following:
Browsers that have been tested include the following:
Important: The database and tables required for the sample portal application are created during the DB2 configuration in the WebSphere Business Integration for Healthcare installation. If you have already completed those steps, you do not need to complete the steps below.
db2 < Create_ HLTHCARE _Database.txt
db2 < Create_HLTHCARE_Tables.txt
The configured database can be on either the same machine as WebSphere Application Server or on a remote machine. If it is on a remote machine, use the DB2 Control Center on the WebSphere Application machine to create a remote system, instance, and database definition. If the WebSphere Application Server machine will have both a local and remote database, you will need to give the remote database an alias. Only one WebSphere Application Server data source with the JNDI name provided below can be used at any one time.
To configure the data source in WebSphere Application Server, complete the following steps:
The WebSphere MQ queue manager and queue is created during the installation of WebSphere Business Integration for Healthcare. The sample portal application WebSphere MQ is configured using the portal application's System Settings page.
This sample includes a WBIHCSamples.war file that can be installed on WebSphere Portal Server V4.2 or V4.2.1. There are two ways to install the portlet application:
The most efficient method for installing is using the XMLAccess utility. If the requirements of the utility cannot be met, the manual process must be used.
The XMLAccess utility is a component of WebSphere Portal Server. It is the means by which portal administration places and pages are installed. It can also be used to install user applications by importing an XML file that defines the application configuration. To install the sample portal application using XMLAccess complete the following steps:
xmlaccess import.xml wpsadmin:<password> <hostname>/wps/config 1> result.xml
If there are errors or warnings in the result.xml file, it might be because your access rights are handled with an LDAP other than the default WebSphere Portal Server database authentication. You can edit the supplied import.xml using the process below:
This process below is required only if errors occurred when you imported the import.xml file. You can edit the subjectid= and owner= attributes so that the values will allow authentication for importing.
The values in the import.xml are as follows:
If you installed WebSphere Portal Server with an external LDAP, your subjectid= and owner= attributes would be specific to your system, as in the following example:
The exact form of your specification can be determined by exporting your current portal configuration. To export your portal configuration, complete the following steps:
xmlaccess export.xml wpsadmin:<password> <hostname>/wps/config 1>myimport.xml
This command will create a myimport.xml file that contains your current configuration. Check this file to determine your subjectid= and owner= attribute specifications.
The only file needed for a manual installation is WBIHCSamples.war. To install this file to your WebSphere Portal Server V4.2 or V4.2.1, complete the following steps:
Note: If you make changes to the WBIHCSamples.war file, you can update a previously installed application by clicking Portlets > Portlet Applications and doing an Update instead of repeating the installation. If you update rather than re-install, you will not need to redefine the places and pages.
When you have installed the application, you must create the associated place and pages and add the portlets to the pages. The place and page names below can vary due to NLS or other factors. The portlet names must remain as shown.
You can use the Manage Users and Access Control Lists pages to create and assign users access to your place, pages, and portlets.
Return to the Work with Pages, Manage Places and Pages page and select the WBI Healthcare place. Select the Science theme for the place. This allows all of the page tabs to be visible without scrolling through the tabs.
The following section describes how to use the various functions of the sample portal application.
The application is accessed using a browser. Point the browser to the WebSphere Portal Server instance, enter your ID and password, then click Log in:
After logging in, you should see a screen such as the one in the following image:
You can then click the WBI Healthcare tab to enter the various pages of application. Those pages are described in the following sections.
After clicking the WBI Healthcare tab, you will see the Patient Selection page. From the list box, select a patient and then click Select Patient. After selecting the patient, click the page in the menu that you want to open. (Note: The menu on the left of the screen also appears on subsequent pages, but is not included in the screen images that follow.)
The Summary page lists general Patient Information along with four separate tables:
These tables, and all subsequent tables, can be scrolled in both directions and the contents can be sorted by column. The column order can be varied by dragging the column header.
The Problems page displays the Patient Information and Problems table. In a fully functioning application, you can use this page to add or edit patient problems.
The Medications page displays the medications table for the selected patient. Use the Refresh button to show any additional orders that might have been processed since opening the Medications page. Below the medication table is a form to enter an additional medication order, including doctor information and the order details. The doctor information is loaded from the default information supplied on the System Settings page.
Enter the appropriate information and click Order to place the order. The application builds the associated XML message and places it on the queue that was specified on the System Settings page.
After the order is placed, a status message appears next to the Order button indicating that the order was placed, or detailing any problems that might have been encountered.
The Flowsheet page displays the Patient Information and the Flowsheet table. In a fully functioning application, you can use this page to add and edit flowsheet information.
The Documents page displays the Patient Information and the Documents table. In a fully functioning application, you can use this page to add and edit document information.
The Report page displays the compliance report table. These entries are not associated with a particular patient, but rather are records kept to comply with government reporting requirements.
Each user's application system settings are maintained in the DB2 database. There are two categories of settings:
The System Settings page displays the current system settings. The first time a user enters the application, the system displays default values. The user can edit and save the new values so that they are applied on each subsequent use.
The WBIHCSamples.war file includes all of the source elements for the application. This file can be imported into a development environment such as WebSphere Studio Application Developer. To use WebSphere Studio Application Developer for portal development, install the WebSphere Portal Toolkit plug-in before importing the .war file.
The application's Javadoc files are also supplied in the WBIHCSamplesJavadoc.zip file. The Javadoc files provide a view of the various classes of the application.