The topics listed here provide information about the United Kingdom Patient Solution, why you should use it, and an overview on how to use it. This solution is geared for users of Oracle databases, and Oracle database scripts are supplied. The purpose of the solution is to help you solve a business problem. If you have any questions or problems and have purchased a support contract, see the JavaTM Composite Application Platform Suite (Java CAPS) support web site at http://goldstar.stc.com/support.
To access all the Java CAPS documentation in HTML format on the Sun Developer Network (SDN) web site, go to http://developers.sun.com/docs/javacaps/.
What You Need to Know
These topics provide conceptual information about the solution.
What You Need to Do
The first of these topics provides a general overview on using the United Kingdom Patient Solution with MDM and then points you to detailed instructions on how to alter the solution to suit your company's requirements, while the second provides you with the scripts you need to create an Oracle database.
You could probably create a database using MySQL or SQL Server. However, the United Kingdom Patient Solution has only been tested with the Oracle database.
This topic 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.
As this template was specifically designed for United Kingdom healthcare, use it with the Master Data Management (MDM) product suite, specifically the Master Index portion of MDM, when implementing your system.
The patient solution was created to enable 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. Benefits for using the solution include:
Set up of patient solution template using MDM's Master 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
For the link to the United Kingdom Patient Solution template, go to https://open-dm-mi.dev.java.net/docs/solutions/uk-patient.html.
See Also
This topic provides the link to the United Kingdom Patient Solution template. The purpose is introduce you to the template, but not instruct you on how to use the template. For links to instructions on the various tasks when setting up your healthcare solution, see United Kingdom Patient Solution Uses.
To see the United Kingdom Patient Solution template, go to https://open-dm-mi.dev.java.net/docs/solutions/uk-patient.html.
The 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
NI 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.
The National Insurance number 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, D, or a space.
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.
See Also
If you are new to Master Data Management, you may want to see a video on how to set up a master index application.
Go to: https://open-dm-mi.dev.java.net/media/start/MIQuickStart.html. The video illustrates the steps to create a master index application and start the Master Index Data Manager (MIDM), and features the following:
Create the master index application
Configure code lists
Create the database
Define the database connection
Define security
Build and deploy the project
Launch Master Index Data Management
The purpose of the video is to give you an overall view of the steps involved to create a master 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. Download the United Kingdom Patient Solution project from the web, and then open the project in the NetBeans IDE. As the project has already been created and the object structure is in place, all you have to do is tweak it so that it serves your company's requirements.
Links are provided for detailed instructions for completing all of the major steps.
Ensure that the Sun Master Index is installed before beginning this procedure.
Download the United Kingdom Patient Solution project.
Open all the United Kingdom Patient Solution projects.
In the NetBeans IDE, select File->Open Project.
Highlight UKPatient, select Open Required Projects in the right pane, and click Open Project.
This opens the following under the Projects tab:
UKPatient
UKPatient-ejb
UKPatient-war
Create the database for your solution.
All the necessary SQL has been provided for an Oracle database.
For instructions on creating a database using the Oracle scripts that are provided for you, go to Creating a Database for the United Kingdom Patient Solution.
The Oracle scripts that come with the solution create a user identified as uk. They are located in the Solutions\NB\MI\project\UKPatient\sca\source\DatabaseScript directory. For detailed instructions on how to create a database, go to http://developers.sun.com/docs/javacaps/designing/jcapsdevsmidxm.jcapsdevsmidxm_intro.html.
Creating the database is a multistep process and not in the scope of this topic. The steps include:
Analyze the Master Index database requirements.
Create a Master Index database and user.
You create the database using tools provided by your database vendor, such as Oracle.
Define the Master Index database indexes.
Define the Master Index external systems.
Define and customize the Master Index code lists for Oracle.
Define the Master Index user code lists.
Create custom Master Index database scripts.
Specify a starting EUID for a Master Index.
An EUID is an enterprise-wide unique identification number that is assigned to a profile.
If the GlassFish server is not running, start the server.
Right-click the UKPatient project and select Generate Master Index Files.
This project has already been created. For detailed instructions on how to create a project, go to http://developers.sun.com/docs/javacaps/designing/jcapsdevsmidxm.dsgn_eview-application_p.html. When you create fields in the object structure of the master index application you can specify several properties for each field. What you specify determines how the fields appear and function in the wizard. For details about the Master Index general field properties that you define in the wizard, go to http://developers.sun.com/docs/javacaps/designing/jcapsdevsmidxm.dsgn_eview-field-props_r.html.
Build and deploy the UKPatient project.
Open the GlassFish Admin Console.
Use the Sun GlassFish Enterprise Server Admin Console to define the following:
Connection Pool
In the left pane choose Resources->JDBC->Connection Pools.
In the Connection Pools window, click New.
In New JDBC Connection Pool (Step 1 or 2), set the name as UKPatient.
All three of the Resource Type options are valid, and one must be selected. Also, you must name the Database Vendor, such as Oracle.
JDBC Resources
User ID, Group List, and Password
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 index applications you create using the Sun Master Index. 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.
To open the MIDM, go to http://localhost:<http-port-number>/UKPatientMIDM.
The default port number is 8080. For http-port-number you need to use the port number defined during your Java CAPS installation. The angle brackets (< >) are not part of the port number.
If you changed the default port but cannot remember the new port number, do one of the following.
Edit the port number of the HTTP server.
From the NetBeans IDE, bring up the HTTP monitor.
Select the Client and Server tab, and edit the port number which is listed as Port number of HTTP server.
Edit the domain.xml file.
This file is found in the <JavaCAPS6-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. In the following example, the port is 9090 instead of the default, which is 8080.
<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="9090" security-enabled="false" server-name="" xpowered-by="true">
Log into the MIDM using uk for the User ID and Password.
For information about logging in and logging out of the MIDM, go to http://developers.sun.com/docs/javacaps/administering/wedmevs.admn_mi-edm-logon_t.html.
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.
For detailed instructions on how to perform the following tasks working with the MIDM, go to http://developers.sun.com/docs/javacaps/administering/wedmevs.wedmev_intro.html.
To see a table that describes the properties you define on the MIDM Field Properties page of the wizard, go to http://developers.sun.com/docs/javacaps/designing/jcapsdevsmidxm.dsgn_eview-edm-props_r.html.
In the MIDM GUI, click Source Record.
To a create a new record, click Add.
In the Pick Out System drop down list, choose Sun.
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.
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 MYSQL as the system for the second record.
Add different people.
Add the same person twice but give them different National Insurance numbers. Be sure to select MYSQL as the system for the second record.
Check for duplicates.
For information about finding, merging, and resolving duplicate profiles on the MIDM, go to http://developers.sun.com/docs/javacaps/administering/wedmevs.admn_mi-edm-pd_p.html.
For information about duplicate records search fields, go to http://developers.sun.com/docs/javacaps/administering/wedmevs.admn_mi-edm-pd_search_r.html.
Look at the various tabs and try different queries or actions once you have some duplicates.
Update the UKPatient model.
For detailed information on how to update, which includes building and deploying, go to http://developers.sun.com/docs/javacaps/deploying/jcapsdplymidx.jcapsdplymidx_intro.html. These instructions relate to Sun Master Index (Repository) only.
Make the desired changes to the Master Index configuration files.
Right-click the UKPatient project and select Generate Master Index Files.
Update the database definitions by running the following SQL commands as the uk user.
Be sure to run the drop.sql script first. Then run the create.sql script.
drop.sql
create.sql
codelist.sql
systems.sql
createIndexes.sql
createUserCodeData.sql
Build and deploy the UKPatient project.
This topic provides an example on how to create a user called uk. To create a different user, edit the createuser-uk.sql file. For links to instructions on the various tasks when setting up your healthcare solution, see United Kingdom Patient Solution Uses.
To see the United Kingdom Patient Solution template, go to https://open-dm-mi.dev.java.net/docs/solutions/uk-patient.html.
The Oracle scripts that come with the solution create a user identified as uk. They are located in the Solutions\NB\MI\project\UKPatient\sca\source\DatabaseScript directory.
As a SYSDBA user run the createuser-uk.sql script.
As the uk user, with a password of uk, run the following scripts.
Run the create.sql script first.
create.sql
codelist.sql
systems.sql
createIndexes.sql
createUserCodeData.sql