| Oracle® Healthcare Master Person Index United Kingdom Patient Solution User's Guide Release 3.0 E62310-01 |
|
|
PDF · Mobi · ePub |
| Oracle® Healthcare Master Person Index United Kingdom Patient Solution User's Guide Release 3.0 E62310-01 |
|
|
PDF · Mobi · ePub |
This chapter introduces you to the Oracle Healthcare Master Person Index (OHMPI) United Kingdom Patient Solution. It also provides instructions that help you to use the solution template to create and generate a patient 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
The sections provide information about the United Kingdom Patient Solution, why you should use it, and an overview on how to use it. The purpose of the solution is to help you solve a business problem.
What You Need to Know
The following sections provide conceptual information about the United Kingdom Patient Solution.
What You Need to Do
The first section provides a procedure that leads you through using the United Kingdom Patient 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 an OHMPI project.
Using the United Kingdom Patient Solution
This includes the following sections:
This section introduces you to the United Kingdom Patient Solution template. The purpose is to help you solve a business problem by providing you with a template that is configurable to your specific requirements, enabling you to create a single patient solution that includes all required and optional bits of information that are specific to each and every patient in your healthcare system. After the database is completed and operational, you will have a patient model that eliminates errors inherent in systems that have patient information spread throughout a number of hard copy and electronic systems that is easy to access and use.
This patient template comes with an object model, code modules in codelist.sql, a set of match fields, and block searches. The configurations include ballpark numbers that function. The United Kingdom Patient Solution template provides much more completeness than our previously released "Person" object model and enables you to set up your healthcare solution without having to create everything from scratch. When studying the solution, observe that it addresses all pertinent bits of patient information, including insurance, medical condition, and medications.
Note:
In reality, all OHMPI projects require much more fine-tuning and custom plug-ins to satisfy site specific requirements.As this template was specifically designed for United Kingdom healthcare, it allows you to create an OHMPI project in a reasonably short amount of time. With an Oracle database in place, the projects created with this template can be generated, deployed and run. Benefits for using the solution include:
Set up of patient solution template using Oracle Healthcare Master Person Index
Enables easy alteration of the template to suit your requirements
Combines and standardizes records into a single patient database
Enables merging of disparate legacy patient databases
Completed United Kingdom Patient Solution
Enables web services connectivity
Enables fully-functioning patient knowledge base
Reduces patient identity errors
Increases reliability while reducing cost
The purpose is to introduce you to the template, but not instruct you on how to use the template. For instructions on the various tasks when setting up your healthcare solution, see Using the United Kingdom Patient Solution.
In England and Wales the National Health Service (NHS) Number is a unique identifier for a patient. It is also the primary identifier of a person. It is 10 digits long (for example, 222 444 7777), with the tenth digit's function to ensure that the NHS Number is valid. People born prior to 1996 have a NHS Number that consists of a combination of alphanumeric characters, and these people have an old and a new identifier. For more information about the NHS Number in its present form, that is, after 1996, and how it is validated, see the following:
Although the NHS Number is the unique and primary identifier for a patient and a person, and if the main identifier for health identification, IdNumType and IdNum fields are sometimes used as HealthID identifiers for United Kingdom healthcare patients. If they are used they can be helpful when creating block-search definitions and matches. The IdNumType and IdNum fields are included as two of the keys for matching information on the main UKPatient node in the template. The seven matching keys for searches are:
FamilyName
GivenName
Gender
DOB
DOB is the person's date of birth.
NI Number
The NI Number is the National Insurance number. It is used for state pension and social security claims. Everyone in the United Kingdom has a National Insurance number. It must be 9 characters long, and it is broken down as follows:
First 2 characters are alpha but the first character cannot be D, F, I, Q, U, or V, and the second character cannot be D, F, I O, Q, U, or V. Also, the 2 characters cannot pair up as GB, NK, TN, or ZZ.
Characters 3 through 8 are numeric.
Last character can be an A, B, C, or D.
The format for the NI Number would be similar to QQ 14 37 58 B. For more details, see http://www.hmrc.gov.uk/manuals/nimmanual/nim39110.htm.
IdNumType
IdNum
In the template, only the UKPatient node contains mandatory variables. All the sub-nodes, for example UKAddress and Consent, are optional.
Every effort has been made to make the template specific to the United Kingdom healthcare industry.
If you are new to OHMPI, you may want to 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 the United Kingdom Patient 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 United Kingdom Patient Solution project icon. 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 the United Kingdom Patient Solution, 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 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 components within the application server are based on the application name. Dependent components include the data source for the JDBC connection and the outbound Topic (if one is used).
In the Application field, enter a name for the new master person index application (for example, UKPatient), and then click Next.
The Define Source Systems window appears.
In the Name field, enter the processing code of one of the source systems that will share data in the master person index system (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 the 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).Perform 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.
Enter the following information to specify information about the deployment environment, including the database, date and time formats, 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. In this window, you can define the field level date format.
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 Patient and then select UKPatient.
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.
Note:
If you mistakenly selected the wrong patient solution when you started the procedure, you can remove this patient solution by clicking the red X in the tool bar and selecting another patient 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.
In the Projects pane (left side of NetBeans), if not already expanded, expand the United Kingdom Patient Solution you just created.
Right-click Configuration and then select Edit.
The Configuration Editor opens on the right side of the window. For detailed information about the Master Person Index object field properties, see Oracle Healthcare Master Person Index User's Guide.
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.
When you have completed configuring the object fields, right-click UKPatient application and select Generate Master Index Files.
The patient solution came with codelist.sql and systems.sql. When you generate the master index files, four additional SQL files are created: create.sql, drop.sql, create-index.sql, and drop-index.sql.
You are now ready to set up a database, the application server, and begin using the Master Index Data Manager in runtime.
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:
Before you begin, make sure you have Oracle installed as a service with 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 (assuming that mpi is the USER_NAME in the following steps):
grant CREATE SESSION, CREATE TABLE, CREATE TRIGGER, CREATE PROCEDURE, UNLIMITED TABLESPACE, CREATE TYPE to <USER_NAME> identified by <PASSWORD>
Open systems.sql in a Text Editor, and add the source systems with which you will be sharing data.
Note:
See Step 5 for the location of this file.For more information about modifying this file, see in the Oracle Healthcare Master Person Index User's Guide.
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 mpi schema as the user you created above.
Run the following SQL files against the mpi schema (<project_name>\src\DatabaseScript). The create.sql file must be run first.
create.sql
systems.sql
codelist.sql
create-index.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 appear. It is here that you will create a new JDBC Data Source.
In the Name field, type <application_name>DataSource.
For example, UKPatientDataSource. For information on the application name, see Creating and Configuring the United Kingdom Patient Solution Application.
In the JNDI Name field, type jdbc/<application_name>DataSource.
Use the name you entered in step 6 here (for example, jdbc/UKPatientDataSource).
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, choose 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: Patient).
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: mpi).
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_name>DataSource 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_name>SequenceDataSource.
You are now ready to deploy your application.
On the left panel of the WebLogic Server Admin Console, under Domain Structure, select Environment and then choose 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-name>MIDM.
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 application you entered when you began to create the Master Person Index application. For example, UKPatient for the UKPatient solution, making the key string UKPatientMIDM.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 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 United Kingdom Patient Solution 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 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, choose Oracle.
Enter a Local ID.
For example, 444-444-4444.
In the UKPatient information section, at a minimum, specify the required values.
To add the record, click Submit.
|
 Copyright © 2012, 2015, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|