Skip Headers
Oracle® Healthcare Master Person Index Australia Patient Solution User's Guide
Release 2.0.2
E24708-02
Go to Documentation Home
Home		 Go to Book List
Book List		 Go to Table of Contents
Contents		 Go to Feedback page
Contact Us
Go to previous page
Previous
PDF · Mobi · ePub

1 Australia Patient Solution Using OHMPI

This chapter introduces you to the Oracle Healthcare Master Person Index (OHMPI) Australia 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:

The sections listed here provide information about the Australia 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 Australia Patient Solution.

What You Need to Do

The first section provides a procedure that leads you through using the Australia 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.

Understanding the Benefits of the Australia Patient Solution

This section introduces you to the Australia 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 Australia 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 Australian healthcare, it allows you to create an OHMPI project in a reasonably short amount of time. With a database (Oracle, MySQL or SQL Server) in place, the projects created with this template can be generated, deployed and run. Benefits for using the solution include:

Introducing the Australia Patient Solution Template

The purpose of this section is to introduce you to the Australia Patient Solution 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 Australia Patient Solution".

The Australia Patient Solution object model is based upon descriptions documented in Australian Standard® Health Care Client Identification (AS 5017-2006)Foot 1 , plus some common attributes provided by field engineers for various implementations. The solution template is comprised of all the required and optional data elements as set forth in AS 5017-2006, and they include:

As all of the data element fields have been included with the OHMPI object model, it is recommended that you delete fields your healthcare system does not require, for they will appear as blank entries in your system if not removed.

Using the Australia Patient Solution

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:

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 Australia 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 Australia 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.

What you will need to do is carefully set up your Master Person Index application to meet your healthcare system's requirements. This will require that you look at each of the object fields to determine if it meets your requirements, and if not, to change or eliminate it. But this is not all that you need to consider to make your MPI application fully functional to your needs. You will also need to fine-tune the following:

The following sections provide the information you need to create an OHMPI application from the Australia 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:

Creating and Configuring the Australia Patient Solution Application

Before You Begin

Ensure that OHMPI is installed before beginning this procedure.

To Create an MPI Application

  1. On the NetBeans toolbar, click New Project.

    The New Project wizard appears, and opens on the Choose Project window.

  2. 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.

  3. 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.

  4. Select the application server you are using from the drop down list.

    1. If no application servers appear in the list, click Manage.

      The Servers window appears.

    2. Click Add Server.

      The Add Servers Instance window appears.

    3. Choose a server (for example GlassFish v2.x or Oracle WebLogic Server), and click Next.

    4. 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.

    5. Click Close.

      The Name and Location window reappears.

  5. The J2EE field has been populated; if you want to use another version, make your selection from the drop down list.

  6. The Set as Main Project is selected; if you do not want this master person index to be the main project, deselect the option.

  7. 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).

  8. In the Application field of the Name Application window, enter a name for the new master person index application, and then click Next.

    Note:

    Give the application the same name you will give to the parent object when you define the object structure.

    The Define Source Systems window appears.

  9. In the Name field of the Define Source Systems window, 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 "Step 4: Define Source Systems" in chapter 2 of 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).

  10. 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.

  11. When you have defined all required source systems, click Next.

    The Define Deployment Environment window appears.

  12. 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. You can select MySQL, Oracle, or SQL Server.

    • Date Format - The date format for the master person index system. This defines how dates should be entered and how they appear on the MIDM. You can select MM/dd/yyyy, dd/MM/yyyy, or yyyy/MM/dd.

    • 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.

  13. When you have defined the deployment environment fields, click Next.

    The Define Enterprise Object window appears.

  14. From the drop-down list of the Add Solution icon, select Patient and then AUPatient.

    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, listing which files 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.

  15. In the Projects pane (left side of NetBeans), if not already expanded, expand the Australia Patient Solution you just created.

  16. 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 the Oracle Healthcare Master Person Index User's Guide.

  17. 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.

  18. When you have completed configuring the object fields, right-click the AUPatient application and from the context menu select Generate Master Index Files.

    The patient 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.

Setting Up a Database and 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 a Database (MySQL)

  1. Create the database for your solution.

    All the necessary SQL has been provided for all the supported databases.

    Note:

    For detailed instructions on how to create a database, see chapter 3, "Master Person Index Database," in Oracle Healthcare Master Person Index User's Guide. For additional information, see the tools provided by your database vendor, such as Oracle or MySQL.

    Once you have created a database you are ready to open your application server.

  2. Analyze the Master Person Index database requirements.

  3. Create the Master Person Index database and user, and then grant the user permission to work on the database.

    At the command prompt do the following:

    1. create database <database_name>;

      Where <database_name> is the name you give the database (for example, ohmpi).

    2. create user '<user_name>: to '@'%' identified by '<password>';

      Where <user_name> is the name of the person assigned to administer the database (for example, ohmpi) and <password> is the string of alphanumeric characters that identify the user (for example, ohmpi).

    3. grant all on <database_name> to '<user_name>'@'%' identified by '<password>';

      Where <database_name> is the name of database (for example, ohmpi), <user_name> is the name of the person assigned to administer the database (for example, ohmpi) and <password> is the string of alphanumeric characters that identify the user (for example, ohmpi). This command gives the user permission to work on that database.

    4. use ohmpi;

      This defines which database you are going to use.

  4. Check if the table you created is accessible, and if not set the directory using these commands:

    1. show tables;

      The result will show that the table you created is not available.

    2. mysql -h localhost -u <user_name> -p<password> -D ohmpi

      Where <user_name> is the name of the person assigned to administer the database (for example, ohmpi) and <password> is the string of alphanumeric characters that identify the user (for example, ohmpi). This command sets the directory where the table you created is located.

  5. If needed, define the OHMPI database indexes.

    Note:

    See "Define Master Person Index Database Indexes" in chapter 3 of the Oracle Healthcare Master Person Index User's Guide for information on how to complete this task.

  6. Create custom OHMPI database scripts.

    1. In the left pane in NetBeans IDE under the Projects tab, expand your OHMPI project, expand Database Script, and then double-click create.sql.

    2. In the Configuration Editor, customize the object model (object.xml); then save and generate the application.

      This creates a new create.sql file.

    3. Copy create.sql, and then using the command prompt, run create.sql in the directory where you created the database.

  7. If required, customize the OHMPI code lists (codelist.sql is provided as part of the solution template).

    1. In the left pane in NetBeans IDE under the Projects tab, expand your OHMPI project, expand Database Script, and then double-click codelist.sql.

    2. In the Text Editor, customize codelist.sql, save your changes, and copy the SQL file.

    3. Using the command prompt, run codelist.sql in the directory where you created the database.

  8. If needed define the OHMPI external systems, such as hospitals.

    1. In the left pane in NetBeans IDE under the Projects tab, expand your OHMPI project, expand Database Script, and then double-click systems.sql.

    2. In the Text Editor, customize systems.sql, save your changes, and copy the SQL file.

    3. Using the command prompt, run systems.sql in the directory where you created the database.

  9. If user code is used, define the OHMPI user code lists.

    Note:

    User code is not defined in the solution template. To perform this task, see "Step 6: Define Master Person Index User Code Lists in chapter 3 of the Oracle Healthcare Master Person Index User's Guide.

Creating a Database (Oracle)

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:

  1. 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>

  2. Open systems.sql in a Text Editor, and add the HL7 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 "Step 4: Define Master Person Index External Systems" in Oracle Healthcare Master Person Index User's Guide.

  3. 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 "Step 5: Define Master Person Index Code Lists" in 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.

  4. Log in to the mpi schema as the user you created above.

  5. Run the following SQL files against the mpi schema (<project_name>\ihe-mpi\src\DatabaseScript). The create.sql file must be run first.

    • create.sql

    • systems.sql

    • codelist.sql

Using the Admin Console to Set Resources (GlassFish)

  1. Open the Admin Console.

    Note:

    For the examples in this procedure we used GlassFish.

    1. In the NetBeans IDE, select the Services tab.

    2. Right-click GlassFish v2.x, and select View Admin Console.

      The Oracle GlassFish Enterprise Server Admin Console opens.

  2. Use the Sun GlassFish Enterprise Server Admin Console to define the following:

    1. Create two Connection Pools

      - In the left pane choose Resources->JDBC->Connection Pools.

      - In the Connection Pools pane, click New.

      - In New JDBC Connection Pool (Step 1 of 2), set the name for your connection pool using your database name. For example, cpmysqlDS with cp representing connection pool, mysql representing the database name and DS representing the data source.

      - In the Resource Type field you must make a selection from the drop-down list.

      Note:

      All three of the Resource Type options are valid.

      - In the Database Vendor field select a vendor from the drop-down list.

      - Click Next.

      - In New JDBC Connection Pool (Step 2 of 2), you need to select and define four properties.

      * Database Name: The name you gave the database.

      * Password: The password for the database.

      * URL (do not select "url" in lower case): This must be jdbc:<database>://<host name>:port number/<database name> where database is your database (for example, Oracle or MySQL), host name is the name of your host (for example, localhost), port number is generated, and database name is the name you gave your database when you created it.

      * User: The name you assigned to the User.

      - Click Finish.

    2. Repeat all of step a, only this time set the Sequence Data Source using your application name. For example, cpAUPatientSDS with cp representing connection pool, AUPatient representing the application name and SDS representing the sequence data source.

    3. Create two JDBC Resources

      - In the left pane choose Resources->JDBC Resources.

      - In the JDBC Resources pane, click New.

      - In New JDBC Resource, set the JNDI Name as jdbc/application nameDataSource (for example, jdbc/AUPatientDataSource).

      Note:

      The application name must match the application name you set in NetBeans for both the data source and the sequence data source.

      - In New JDBC Resource, set the Pool Name from the drop-down list. It should be the JDBC Data Source that you just created and click OK.

      - In the JDBC Resources pane, click New.

      - In New JDBC Resource, set the JNDI Name as jdbc/application nameSequenceDataSource (for example, jdbc/AUPatientSequenceDataSource).

      - In New JDBC Resource, set the Pool Name from the drop-down list. It should be the JDBC Sequence Data Source that you just created and click OK.

    4. User ID, Group List, and Password

      - In the left pane choose Configuration->Security->Realms->file.

      - In the Edit Realm pane, click Manage Users.

      - In the File Users pane, click New.

      - In the New File Realm User, set the following.

      Table 1-1 Realm User Settings

      User ID

      Select a user name that is meaningful to you, for example aus.

      Group List

      MasterIndex.Admin,AdministratorFoot 1 

      Password

      The password is of your choosing, for example aus.

      Footnote 1 This is a super group, with all privileges.

      - When ready, click OK.

You are now ready to deploy your application.

Using the Admin Console to Set Resources (WebLogic)

To Create JDBC Data Resources for an MPI Application Project for MySQL

This section provides instructions for creating the JDBC data resources and defining the JDBC connections for an MPI Application Project.

  1. For instructions on how to start and stop your Oracle WebLogic Server, see Starting and Stopping Servers: Quick Reference at http://download.oracle.com/docs/cd/E14571_01/wls.htm.

  2. Launch the Oracle WebLogic Server Administration Console.

  3. Log in using the default user Name (weblogic) and Password (welcome1).

    The Oracle WebLogic Administration Console appears.

  4. 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.

  5. 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.

  6. In the Name field, type <application_name>DataSource.

    The name you enter here will propagate elsewhere, so choose a name that is meaningful (for example, PersonDataSource).

  7. In the JNDI Name field, type jdbc/<application_name>DataSource.

    Use the name you entered in step 6 here (for example, jdbc/PersonDataSource).

  8. Click Save.

    A new page appears in the right panel which is for setting the Database Type.

  9. In the Database Type drop-down list, choose the appropriate type (for example: MySQL).

  10. In the Database Driver drop-down list, choose the appropriate driver; for example: MySQL's Driver (Type 4) Versions:using com.mysql.jdbc.Driver.

  11. Make sure that your data source supports Global Transactions.

  12. Click Next.

    Connection Properties appears on the Create a New JDBC Data Source panel. Use it to define the connection properties.

  13. In the Database Name field, type a name for the database to which you want to connect (for example: Person).

  14. In the Host Name field, type the name or the IP address of the database server (for example: localhost).

  15. In the Port field, type the port on the database server that is used to connect to the database (for example: 3306, the default for MySQL).

  16. In the Database User Name field, type the database account user name you want to use to create database connections (for example: root).

  17. In the Password field, type a password for your database account to use to create database connections.

  18. In the Confirm Password field, re-type the password to confirm it.

  19. Click Next.

    The Settings for PersonDataSource page appears in the right panel.

  20. 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.

  21. 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.

  22. Repeat the above steps to create jdbc/<application_name>SequenceDataSource.

To Create JDBC Data Resources for an MPI Application Project for Oracle

  1. For instructions on how to start and stop your Oracle WebLogic Server, see Starting and Stopping Servers: Quick Reference at http://download.oracle.com/docs/cd/E14571_01/wls.htm.

  2. Launch the Oracle WebLogic Server Administration Console.

  3. Log in using the default user Name (weblogic) and Password (welcome1).

    The Oracle WebLogic Administration Console appears.

  4. 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.

  5. 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.

  6. In the Name field, type <application_name>DataSource.

    The name you enter here will propagate elsewhere, so choose a name that is meaningful (for example, PatientDataSource).

  7. In the JNDI Name field, type jdbc/<application_name>DataSource.

    Use the name you entered in step 6 here (for example, jdbc/PersonDataSource).

  8. Click Save.

    A new page appears in the right panel which is for setting the Database Type.

  9. In the Database Type drop-down list, choose the appropriate type (for example: Oracle).

  10. 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.

  11. Click Next.

  12. Click Next.

    Connection Properties appears on the Create a New JDBC Data Source panel. Use it to define the connection properties.

  13. In the Database Name field, type a name for the database to which you want to connect (for example: Patient).

  14. In the Host Name field, type the name or the IP address of the database server (for example: localhost).

  15. 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).

  16. In the Database User Name field, type the database account user name you want to use to create database connections (for example: root).

  17. In the Password field, type a password for your database account to use to create database connections.

  18. In the Confirm Password field, re-type the password to confirm it.

  19. Click Next.

    The Settings for <application_name>DataSource page appears in the right panel.

  20. 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.

  21. 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.

  22. Repeat the above steps to create jdbc/<application_name>SequenceDataSource.

You are now ready to deploy your application.

Deploying the OHMPI Application

GlassFish

  1. To deploy your application, under Common Tasks, expand Applications, select Enterprise Applications, and in the right pane, click Deploy.

  2. In the Deploy Enterprise Applications/Modules pane, browse to the location of the EAR files for the application.

  3. In the File Upload window, select the patient-project EAR file and click Open and then click OK.

WebLogic

  1. 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.

  2. 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.

  3. Locate your application EAR and click Next.

    The Install Application Assistant page appears in the right panel.

  4. 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.

  5. 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.

  6. Click Finish.

You are now ready to open the MIDM and manage your OHMPI project.

Opening and Using the Master Index Data Manager

  1. 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.

    1. Using a browser, enter the URL to open the MIDM: http://localhost:http-port-number/solution-object-nameMIDM. BUT FOR ME: http://localhost:8080/PersonMIDM

      Note:

      The default port number for GlassFish is 8080 and 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 solution-object-name is the name of the solution template you selected when you began to create the Master Person Index application. For example, solution-object-name is Patient for the AUPatient solution, making the key string PatientMIDM.

    2. 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.

      - Edit the domain.xml file.

      Note:

      This file is found in the <OHMPI-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">

      Note:

      The port number used in this example is for GlassFish. If you performed a similar task on WebLogic the port number would be different.

    3. 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 "Logging in to the Master Index Data Manager" and "Logging Out of the MIDM" in chapter 2 of the Oracle Healthcare Master Person Index Data Manager User's Guide.

  2. 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 Australia 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 "Understanding Master Person Index Wizard Name Restrictions and Field Properties" in chapter 2 of the Oracle Healthcare Master Person Index User's Guide.

    1. In the MIDM GUI, click Source Record.

    2. To a create a new record, click Add.

    3. In the Pick Out System drop down list, choose Oracle.

    4. Enter a Local ID.

      For example, 444-444-4444.

    5. In the AUPatient information section, at a minimum, specify the required values.

    6. 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, see "Working with Potential Duplicate Profiles on the MIDM" in chapter 6 of 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.


Footnote Legend

Footnote 1: As the details provided in the Australian Standard Health Care Client Identification are outside the scope of this guide, obtain a copy of the specification to view the specifics for each data element.
Go to previous page
Previous
Go to Documentation Home
Home		 Go to Book List
Book List		 Go to Table of Contents
Contents		 Go to Feedback page
Contact Us