| Oracle® Healthcare Master Person Index Provider Index User's Guide Release 4.0 E68422-01 |
|
|
PDF · Mobi · ePub |
| Oracle® Healthcare Master Person Index Provider Index User's Guide Release 4.0 E68422-01 |
|
|
PDF · Mobi · ePub |
This chapter introduces you to the Oracle Healthcare Master Person Index (OHMPI) Provider Indexes. It also provides instructions that help you to use a solution template to create and generate a provider index application using OHMPI, set up a database, set resources in an application server, and then build and deploy the application. But it goes beyond this, for you will need to set your matching and standardization levels to ensure that your project is set up to function per your specifications. You will also need to configure your application specifically to your healthcare enterprise. This guide will provide pointers to OHMPI documents that contain detailed information on what you need to know to perform these tasks.
This chapter is divided into:
What you Need to Know
What You Need to Do
These sections provide information about the Provider Indexes, why you should use them, and an overview on how to use it. The purpose of a solution is to help you solve a business problem of creating an individual or organizational provider index in short amount of time.
What You Need to Know
The following section provides conceptual information about a Provider Index.
What You Need to Do
The first section provides a procedure that leads you through using a Provider Index Solution with OHMPI to create an application, configure it, and then deploy it. The second details setting-up a database (if one is not in place) and setting resources in an application server. The final section presents an overview procedure for using the Master Index Data Manger (MIDM) to manage a Provider Index project.
Creating a Provider Index Application Using a Template in OHMPI
This section includes the following sections:
Healthcare providers are individuals or organizations that identify, prevent, or treat illnesses and disabilities. That is, they are individual or organizational providers of health or medical services. There are many terms associated with these professionals and organizations, such as primary care provider, health professional, caregiver, and they are associated with all facets of the healthcare industry ranging from, but not limited to, the following:
Individual Medical Practitioners
Physicians, nurses, and so on
Surgical and other medical specialists
Dental care
Public health
Mental health
Maternal and newborn care
...
Organizations and Institutions
Hospitals
Medical Laboratories
Medical nursing homes
Health care centers
Pharmacies
...
The Provider Indexes are out-of-the-box solutions that leverage the framework and services of OHMPI and provide preconfigured data models and matching configurations, which you can quickly customize. The OHMPI-based solutions also allow you to create cross-references on provider data across the source systems in your healthcare network. They also support de-duplication of healthcare provider data.
This section introduces you to the Provider Index templates. The purpose is to help you solve a business problem by providing you with templates that are configurable to your specific requirements, enabling you to create single provider index solutions that include all required and optional bits of information that are specific to each and every provider in your healthcare system. After the database is completed and operational, you will have organizational and/or individual provider models that eliminate errors inherent in systems that have provider information spread throughout a number of hard copy and electronic systems that are easy to access and use.
The provider index templates come with an object model, code modules in codelist.sql, a set of match fields, and block searches.
Note:
In reality, all OHMPI projects require much more fine-tuning and custom plug-ins to satisfy site specific requirements.As these templates were specifically designed as Provider Index solutions to healthcare needs, they allow you to create an OHMPI projects in a reasonably short amount of time. With the Oracle database in place, the projects created with these templates can be generated, deployed and run.
You can specify that a sub-object becomes a required object. For example, IndProvider is a primary object and it has a Names sub-object. As an IndProvider object has at least one name, and it is impossible to create an IndProvider without a name, the Names sub-object can now be set as required. Use the OHMPI Configuration Editor to specify whether a sub-object is required. When you set this information, it is saved to the object.xml file.
Benefits for using the solution include:
Set up of provider index solution templates using Oracle Healthcare Master Person Index:
Enables easy alteration of the templates to suit your requirements
Provides a data model for individual and organizational providers
Provides preconfigured matching and standardization for out-of-the-box use
Provides a pre-populated code list
Completed Provider Index application:
Provides easy integration through web services or the Java API
Reduces healthcare provider identity errors
Increases reliability while reducing cost
If you are new to OHMPI, see the Oracle Healthcare Master Person Index User's Guide for it gives you an overview and provides detailed steps for setting up a master person index application. For information on how to start and use the Master Index Data Manager (MIDM), see the Oracle Healthcare Master Person Index Data Manager User's Guide. These guides feature the following:
Create the OHMPI application
Configure code lists
Create the database
Define the database connection
Define security
Build and deploy the project
Launch Master Index Data Manager
The purpose of the previously mentioned guides is to give you an overall view of the steps involved to create a master person index application. However, and this is important, if you decide to use a Provider Index Solution as your model, you do not need to create it from scratch. From within NetBeans IDE use OHMPI's project wizard to navigate to and select the Provider project icon and then select Organization or Individual. As the project has already been created and the object structure is in place, all you have to do is move through a number of steps and set-up the template so that it serves your company's requirements.
The following sections provide the information you need to create an OHMPI application from a Provider Index template, set-up a database (if you have not done so already), setting your resources in an application server, and using the MIDM to manage your project:
Ensure that OHMPI is installed before beginning this procedure.
On the NetBeans toolbar, click New Project.
The New Project wizard appears, and opens on the Choose Project window.
Under Categories select OHMPI, under Projects select Master Person Index Application, and then click Next.
The Name and Location window appears with default NetBeans project name and directory paths.
Enter a NetBeans project name and the path where you want to store the project files in the upper portion of the window or accept the defaults.
Select the application server you are using from the drop-down list.
If no application servers appear in the list, click Manage.
The Servers window appears.
Click Add Server.
The Add Servers Instance window appears.
Select the Oracle WebLogic Server, and click Next.
Under Server Location, browse to the location of your application server, or accept the defaults and click Finish.
You are returned to the Servers window with the application server you selected listed under Servers in the left pane.
Click Close.
The Name and Location window reappears.
The J2EE field has been populated.
The Set as Main Project is selected; if you do not want this master person index to be the main project, deselect the option.
Click Next.
The Name Application window appears with a default application name.
Before you can configure a new master person index application, you should give the application a unique name. It is a good practice to give each master person index application a unique name you create because certain services within the application server are based on the application name. Dependent services include the data source for the JDBC connection and the outbound Topic (if one is used).
In the Application field of the Name Application window, enter a name for the new master person index application, and then click Next.
The Define Source Systems window appears.
In the Name field of the Define Source Systems window, enter the processing code of one of the source systems (for example, HOS or MC), and then click Add (see below).
The source system is the key to your network. If it is a hospital (for example, Hospital or Medical Center, the system might be HOS or MC), all of its patient records would be sent into the master person index with a system code/LID of HOS/120210210 or MC/48481234. For more information on the LID, see Oracle Healthcare Master Person Index User's Guide.
You can enter any of the following characters:
! _ ~ ( ) { } + \Q # $ % & : ; - /
a-z
A-Z
0-9
þ ÿ Þ ß 'à-ö ø-ý À-Ö Ø-Ý
The value you entered appears in the Systems box.
Note:
Be sure to enter the processing code of the system and not the name. This value is entered in
update.xml for defining survivor strategies for the single best record (SBR).Do any of the following:
To define additional systems, repeat the above step for each source system that will share information with the master person index application.
To remove a system from the list, highlight the name of that system in the Systems box, and then click Remove.
To remove all systems from the list, click Remove All.
When you have defined all required source systems, click Next.
The Define Deployment Environment window appears.
On the Define Deployment Environment window, enter the following information to specify information about the deployment environment, including the database, date format, and transaction mode:
Database - The type of database being used for the master person index application. Select Oracle.
Date and Time Formats - The date and time formats for the master person index system. This defines how date and time must be entered and how they appear on the MIDM. These formats acts as a default format if you do not set the field level format.
Object Date Format: This is the default or application level format used by OHMPI backend for the date data type.
Object Time Format: This is the default or application level format used by OHMPI backend for the timestamp data type.
MIDM Date Format: This is the default or application level format used by MIDM for the date data type.
MIDM Time Format: This is the default or application level format used by MIDM for the timestamp data type.
Transaction Mode - An indicator of whether transactions are distributed. Select one of the following options:
XA (across applications), if the transactions will be distributed across multiple applications.
XA (within application only), if the transactions will be distributed just across the master person index application.
Local, if the transactions will not be distributed.
Click Next.
The Define Enterprise Object window appears.
Click the Properties tab.
Enter the required values.
The date format that you configure here gets copied to object.xml.
Click the MIDM tab.
Enter the required values.
The date format that you configure here gets copied to midm.xml.
From the drop-down list of the Add Solution icon, select Provider and then Organization or Individual.
The object model is populated. It has been pre-set, that is all the object fields were already created with a set of default properties that define each field, and you are unable to change anything (you can change it using the OHMPI Configuration Editor later).
Note:
If you mistakenly selected the wrong provider solution when you started the procedure, you can remove this provider solution by clicking the red X in the tool bar and selecting another provider solution.Click Next.
The Generate Project Files window appears which lists the files that will be generated. You can choose to generate the remaining master person index files now by checking the box, but if you intend to change the configuration you will need to again generate all the application files.
Click Finish.
The Provider Index project is created.
In the Projects pane (left side of NetBeans), if not already expanded, expand the Provider Index application you just created.
To configure the created project, right-click Configuration and then select Edit.
The OHMPI Configuration Editor opens on the right side of the window. For detailed information about the Master Person Index object field properties, see the Oracle Healthcare Master Person Index User's Guide.
Note:
As the Individual and the Organization solution templates were created to be as useful as possible to all locales, they are general in format. This means that you may see fields that are not applicable to your healthcare needs. When this happens and you see an object or sub-object field that is pre-set to true when in fact it is not required, use the OHMPI Configuration Editor to either set it to false or right-click the field in the Object Definition column and select Delete.As desired, modify the object properties for any field to suit your data processing, storage, and display requirements. After you modify a property value, press Enter to apply the change.
To save your change, click the Save icon on the OHMPI Configuration tool bar.
When you have completed configuring the object fields, right-click the Provider Index application and from the context menu select Generate Master Index Files.
The provider solution came with codelist.sql and system.sql; when you generate the master index files, two additional SQL files are created: create.sql and drop.sql.
You are now ready to set up the database and resources on the application server.
Before you are able to use the Master Index Data Manager, you need to perform a few tasks that are required for runtime to function properly. These include creating one of the following databases and configuring one of the following applications servers:
All the necessary SQL scripts have been provided for the supported databases.
Note:
For detailed instructions on how to create a database, see the Oracle Healthcare Master Person Index User's Guide.Before you begin, make sure you have Oracle installed as a service with the remote host access enabled. Perform the following steps to create all databases:
Create an Oracle environment and user for the Master Person Index tables by running the following command:
grant CREATE SESSION, CREATE TABLE, CREATE TRIGGER, CREATE PROCEDURE, UNLIMITED TABLESPACE, CREATE TYPE to USER_NAME identified by PASSWORD
where USER_NAME is the user's name (for example: ind).
Open systems.sql, and if needed add additional source systems.
Open codelist.sql in a Text Editor, and add any common code information you need for the master person index system.
Note:
See Step 5 for the location of this file.For more information about code lists and modifying this file, see the Oracle Healthcare Master Person Index User's Guide.
Note:
This step is optional. The default configuration does not use common code tables. Adding this feature will cause additional validations to be performed against incoming data.Log in to the ind schema as the user you created above.
Run the following SQL files against the ind schema (project_name\ihe-mpi\src\DatabaseScript). The create.sql file must be run first.
create.sql
systems.sql
codelist.sql
To Create JDBC Data Resources for an MPI Application Project for Oracle
Start and stop the Oracle WebLogic Server. For instructions, see Oracle Fusion Middleware Online Documentation 12c Release 1 (12.1.3).
Launch the Oracle WebLogic Server Administration Console.
Log in using the default user Name (weblogic) and Password (welcome1).
The Oracle WebLogic Administration Console appears.
On the left panel, under Domain Structure, expand Services, click JDBC, and then choose Data Sources.
A Summary of JDBC Data Sources appears in the right panel.
To create a new JDBC Data Source click New at the bottom of the right panel.
Settings for a new JDBC Data Source appears in the right panel of the page. It is here that you will create a new JDBC Data Source.
In the Name field, type application_nameDataSource.
The name you enter here will propagate elsewhere, so choose a name that is meaningful (for example, PersonDataSource).
In the JNDI Name field, type jdbc/application_nameDataSource.
Use the name you entered in step 6 here (for example, jdbc/OrgProviderDataSource).
Click Save.
A new page appears in the right panel which is for setting the Database Type.
In the Database Type drop-down list, choose the appropriate type (for example: Oracle).
In the Database Driver drop-down list, select the appropriate driver. For example, Oracle's Driver (Thin XA) for Instance Connections; Versions: 9.0.1; 9.2.0; 10, 11.
Click Next.
Click Next.
Connection Properties appears on the Create a New JDBC Data Source panel. Use it to define the connection properties.
In the Database Name field, type a name for the database to which you want to connect (for example: ind).
In the Host Name field, type the name or the IP address of the database server (for example: localhost).
In the Port field, type the port on the database server that is used to connect to the database (for example: 1521, the default for Oracle).
In the Database User Name field, type the database account user name you want to use to create database connections (for example: ind, as created in the database step).
In the Password field, type a password for your database account to use to create database connections.
In the Confirm Password field, re-type the password to confirm it.
Click Next.
The Settings for application_nameDataSource page appears in the right panel.
Click the Connection Pool tab, click Test Configuration, and then click Next.
Select Targets appears on the Create a New JDBC Data Source page in the right panel. Here you select one or more targets to deploy the new JDBC data source.
In the Servers check list, select one or more target servers and click Finish.
Note:
If you do not select a target, the data source will be created but not deployed. You will need to deploy the data source at a later time.Repeat the above steps to create jdbc/application_nameSequenceDataSource.
You are now ready to deploy your application.
Use the following tables to create a user and group on WebLogic:
Table 1-1 Realm User Settings (MIDM Login)
|
User ID |
Select a user name that is meaningful to you, for example ohmpi. |
|
Group List |
|
|
Password |
The password is of your choosing, for example ohmpi. |
Footnote 1 This is a super group, with all privileges.
Table 1-2 Realm User Settings (Web Server Security)
|
User ID |
This user name must be MasterIndex.WSUser. |
|
Group List |
|
|
Password |
The password is of your choosing, for example test123. |
Footnote 1 This is a super group, with all privileges.
On the left panel of the WebLogic Server Admin Console, under Domain Structure, select Deployments.
The Summary of Deployments panel appears.
On the right side of the panel under Deployments, click Install.
A Summary of Deployments panel with a Deployments table containing a list of EAR files appears.
Locate your application EAR and click Next.
The Install Application Assistant page appears in the right panel.
Locate the deployment you want to install and prepare for deployment.
Tip:
Select the file path that represent the application root directory, archive file, exploded archive directory, or application module descriptor that you want to install. You can also enter the path of the application directory or file in the Path field.Note:
Only valid file paths are displayed. If you cannot find your deployment files, upload your file(s) and/or confirm that your application contains the required deployment descriptors.Click Next.
Note:
When deploying an OHMPI EAR file through the WebLogic Admin Console, under Security make sure that you choose DD Only. If you choose one of the other options, you will not be able to log into the MIDM.Click Finish.
You are now ready to open the MIDM and manage your OHMPI project.
Open the Master Index Data Manager.
The Master Index Data Manager (MIDM) is a web-based interface that allows you to access, monitor, and maintain the data stored by the master person index applications you create using OHMPI. Use the MIDM to search for, add, update, deactivate, merge, unmerge, and compare object profiles. You can also view and correct potential duplicate profiles, view transaction histories, view an audit log, and print reports.
The MIDM is your primary tool to view and maintain the data stored in the master index database and cross-referenced by a master index application.
Using a browser, enter the URL to open the MIDM: http://localhost:http-port-number/application_nameMIDM.
Note:
The default port number for WebLogic is 7001. For http-port-number you need to use the port number defined during your OHMPI installation. The application_name is the name of the solution template you selected when you began to create the Master Person Index application. For example, you might choose to name the solution-object-name Organization for the Provider Index Organization solution, making the key string OrganizationMIDM.If you changed the default port but cannot remember the new port number, do one of the following.
- From the NetBeans IDE, bring up the HTTP monitor and edit the port number of the HTTP server by selecting the Client and Server tab and then editing the port number which is listed as Port number of HTTP server.
- Open the domain.xml file.
Note:
This file is found in theOHMPI-install\appserver\domains\domain1\config directory.Find a line similar to the following example. The line you are looking for has the following values:
- http-listener acceptor-threads="1" - default-virtual-server="server" - security-enabled="false"
This is usually the first http-listener entry in the domain.xml file.
<http-listener acceptor-threads="1" address="0.0.0.0" blocking-enabled="false" default-virtual-server="server" enabled="true" family="inet" id="http-listener-1" port="7001" security-enabled="false" server-name="" xpowered-by="true">
Log into the MIDM using ohmpi or your user for the User ID and Password.
For information about logging in and logging out of the MIDM, see the Oracle Healthcare Master Person Index Data Manager User's Guide.
Use the MIDM to add new records.
This provides the initial steps for creating a new record, and then offers suggestions for you to try as you familiarize yourself with the Organization or Individual Provider Index application and using Master Index Data Manager to tweak the solution to meet your particular requirements.
To view tables that describe the properties you define on the MIDM Field Properties page of the wizard, see the Oracle Healthcare Master Person Index User's Guide.
In the MIDM GUI, click Source Record.
To create a new record, click Add.
In the Pick Out System drop-down list, select GMH.
Enter a Local ID.
For example, 444-444-4444.
In the OrgProvider (or IndProvider) information section, at a minimum, specify the required values.
To add the record, click Submit.
The following are examples of what you might try to increase your knowledge of the Master Index Data Manager GUI.
Add the same person twice, but give the two records different dates of birth. Be sure to select MCT as the system for the second record.
Add different people.
Add the same person twice. Be sure to select MCT as the system for the second record.
Check for duplicates.
For information about finding, merging, and resolving duplicate profiles on the MIDM, see the Oracle Healthcare Master Person Index Data Manager User's Guide.
Note:
This includes a section that discusses duplicate records search fields.Look at the various tabs and try different queries or actions once you have some duplicates.
|
 Copyright © 2012, 2016, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|