| Oracle® Healthcare Master Person Index Release 1.1 |
|
|
This chapter introduces you to the Oracle Healthcare Master Person Index (OHMPI), its features, and the OHMPI Installer. It also provides a listing of what is required prior to installing OHMPI, including design-time and runtime application servers, the operating systems on which they run, and a procedure for installing the Java Development Kit (JDK) and setting JAVA_HOME.
This chapter includes the following sections:
Oracle Healthcare Master Person Index v1.1 is the release of the single person view application that was acquired from Sun Microsystems. This product has been developed over many years and is an established person identity resolution solution in the market with extensive customer base in the healthcare segment. It provides a flexible framework for you to design and create custom single-view applications, or master person indexes, which cleanse, match, and cross-reference healthcare objects across an enterprise. A master person index that contains the most current and accurate data about each healthcare object will ensure availability of unified, trusted data to all systems in the enterprise.
The OHMPI Installer includes the following software:
NetBeans IDE v6.9.1
Note:
IDE is an acronym for an Integrated Development Environment. It consists of a number of components, such as a compiler, source code editor, build tools, debugger, browser, object inspector, class hierarchy diagram, and so on. These components can be used when performing object-oriented software development. The integrated tools can also be used to build a graphical user interface (GUI).GlassFish Enterprise Server v2.1.1 Patch 7
Note:
The Audit Record Repository (ARR) is installed with GlassFish. If you intend to use WebLogic and not GlassFish, you still need to install GlassFish if you want to use ARR. Sample files will be installed in the directory where GlassFish is installed.Master Person Index Plug-in
IHE Plug-in
Uninstallation software
Oracle Healthcare Master Person Index includes the following features:
OHMPI provides a wizard that takes you through all the steps of creating a master person index application. Using the wizard, you can define a custom master person index with a data structure, processing logic, and matching and standardization logic that are completely geared to the type of data you are indexing. OHMPI provides a graphical editor so you can further customize the business logic, including matching, standardization, queries, match weight thresholds, and so on.
Data Quality and Load Tools
By default, Master Person Index uses the OHMPI Match Engine and OHMPI Standardization Engine to standardize and match incoming data. Additional tools are generated directly from the master person index application and use the object structure defined for the master person index. These tools include the Data Profiler, Data Cleanser, and the Initial Bulk Match and Load (IBML) tool.
OHMPI Standardization Engine
The OHMPI Standardization Engine is built on a highly configurable and extensible framework to enable standardization of multiple types of data originating in various languages and counties. It performs parsing, normalization, and phonetic encoding of the data being sent to the master person index or being loaded in bulk to the master person index database. Parsing is the process of separating a field into individual components, such as separating a street address into a street name, house number, street type, and street direction. Normalization changes a field value to its common form, such as changing a nickname like Bob to its standard version, Robert. Phonetic encoding allows queries to account for spelling and input errors. The standardization process cleanses the data prior to matching, providing data to the match engine in a common form to help provide a more accurate match weight.
OHMPI Match Engine
The OHMPI Match Engine provides the basis for deduplication with its record matching capabilities. The OHMPI Match Engine compares the match fields in two records and calculates a match weight for each match field. It then totals the weights for all match fields to provide a composite match weight between records. This weight indicates how likely it is that two records represent the same entity. The OHMPI Match Engine is a high-performance engine, using proven algorithms and methodologies based on research at the U.S. Census Bureau. The engine is built on an extensible and configurable framework, allowing you to customize existing comparison functions and to create and plug in custom functions.
Runtime features a number of data independent management tools.
Data Profiler
When gathering data from various sources, the quality of the data sets is unknown. You need a tool to analyze, or profile, legacy data in order to determine how it needs to be cleansed prior to being loaded into a master person index database. It uses a subset of the Data Cleanser rules to analyze the frequency of data values and patterns in bulk data. The Data Profiler performs a variety of frequency analyses. You can profile data prior to cleansing in order to determine how to define cleansing rules, and you can profile data after cleansing in order to fine-tune query blocking definitions, standardization rules, and matching rules.
Data Cleanser
Once you know the quality of the data to be loaded to a master person index database, you can clean up data anomalies and errors as well as standardize and validate the data. The Data Cleanser validates, standardizes, and transforms bulk data prior to loading the initial data set into a master person index database. The rules for the cleansing process are highly customizable and can easily be configured for specific data requirements. Any records that fail validation or are rejected can be fixed and put through the cleanser again. The output of the Data Cleanser is a file that can be used by the Data Profiler for analysis and by the Initial Bulk Match and Load Tool. Standardizing data using the Data Cleanser aids the matching process.
Initial Bulk Match and Load Tool (IBML Tool)
Before your Master Data Manager (MDM) solution can begin to cleanse data in real time, you need to seed the master person index database with the data that currently exists in the systems that will share information with the master person index. The IBML tool can match bulk data outside of the master person index environment and then load the matched data into the master person index database, greatly reducing the amount of time it would normally take to match and load bulk data. This tool is highly scalable and can handle very large volumes of data when used in a distributed computing environment. The IBML Tool loads a complete image of processed data, including potential duplicate flags, assumed matches, and transaction information.
The Master Index Data Manager is your primary tool to view and maintain the data stored in a master person index database and cross-referenced by a master person index application. The web-based interface allows you to access, monitor, and maintain the data stored by the master person index applications you create using OHMPI. The MIDM provides the ability to search for, add, update, deactivate, merge, unmerge, and compare object profiles. It also enables you to view and correct potential duplicate profiles, view transaction histories, view an audit log, and print reports.
Integrating the Healthcare Enterprise (IHE) has created a number of standards and profiles that help create, process, and manage electronic health records in secure patient cross-reference applications. They work in conjunction with native Health Level 7 (HL7) v2 and v3 messaging and transport standards, which define how the information is packaged and shared between systems. OHMPI has incorporated a number of the IHE profiles (listed below), as they increase the efficiency of sharing trusted cross-references of healthcare person entities. A number of the IHE profiles function with HL7 v2 and v3 encoding standards to integrate healthcare networks.
With OHMPI R1.1 you have the capability to create an IHE project that contains a pre-configured master person index project. See "IHE-MPI Projects" in Oracle Healthcare Master Person Index Working With IHE Profiles (Part Number E18591-01).
Patient Identifier Cross Referencing (PIX) allows cross-referencing of patient identifiers across a network of healthcare sites.
Patient Demographics Query (PDQ) queries and retrieves patient demographics.
Audit Record Repository (ARR) includes an audit server and an audit repository. It also supports ATNA (see below).
Audit Trail and Node Authentication (ATNA) uses certificates and transmits and receives audit events to a secure repository to maintain patient confidentiality, and is built on top of Security Audit and Access Accountability Message XML Data Definitions for Healthcare Applications, the Syslog Protocol, Transmission of Syslog Messages over Transport Layer Security (TLS), and Transmission of Syslog Messages over User Datagram Protocol (UDP).
Consistent Time (CT) synchronizes time stamps and system clocks on computers functioning within a healthcare network.
Patient Identity Management (PIM) under Patient Administration Management (PAM) creates a patient record, updates the record, links the record to another patient record, and if the records represent the same patient, merges the records (these records can be unlinked if the records do not represent the same patient).
Patient Identifier Cross-Reference and Patient Demographics Query for HL7v3 (PIX/PDQ/v3) leverages HL7 version 3 to extend the capability of these profiles.
Oracle Healthcare Master Person Index requires that the computer on which you plan to install it already has an appropriate Java Development Kit with JAVA_HOME set prior to beginning the process. See "Installing JDK Software and Setting JAVA_HOME".
OHMPI can be installed on PC and UNIX computers; see "Supported IDE, Application Servers, and Operating Systems" for details about the supported platforms.
A typical PC running Microsoft Windows might have the following:
4 GB of RAM
2.8 GHz processor
40 GB of disk space
Installation requirement vary depending upon the operating system on which you are installing. For example:
On Window you need 1.5 GB of free storage space
On Solaris you need 1.5 GB of free storage space
Note:
The OHMPI Installer informs you how much free storage space is required.OHMPI supports the following application servers:
Integrated Design-time Environment (IDE)
NetBeans IDE 6.9.1 is a design-time application used to create, generate, and build OHMPI applications.
Note:
Table 1-1 lists the design-time operating systems that are compatible with Master Person Index design-time components and NetBeans IDE v6.9.1.Runtime Application Servers
The following runtime application servers support the IHE interface and run an OHMPI application after it has been created and built.
GlassFish Server 2.1.1 Patch 7
Oracle Web Logic Server 11gR1
Note:
Table 1-1 lists operating systems that are compatible with Master Person Index runtime components and the GlassFish Server 2.1.1 Patch 7 or the Oracle Web Logic Server 11gR1.Table 1-1 Design-Time and Runtime Supported Platforms
| PlatformFoot 1 | Design-time NetBeans IDE | Runtime GlassFish | Runtime WebLogic | Runtime JVM |
|---|---|---|---|---|
|
IBM AIX 6.1 |
--- |
32 & 64 bit |
64 bit |
32 & 64 bit |
|
IBM AIX 5.3 |
--- |
32 bit |
64 bit |
32 & 64 bit |
|
Microsoft Windows 2008 |
--- |
32 bit |
32 & 64 bit |
32 & 64 bit |
|
Microsoft Windows 2008 R2 |
--- |
64 bit |
32 & 64 bit |
32 & 64 bit |
|
Microsoft Windows 7 Professional |
32 bit |
--- |
32 & 64 bit |
32 bit |
|
Microsoft Windows Vista SP1+ |
32 bit |
32 bit |
32 bits |
32 bit |
|
Microsoft Windows XP SP3 |
32 bit |
32 bit |
32 bit |
32 bit |
|
Microsoft Windows 2003 R2 SP2 |
--- |
32 bit |
32 & 64 bit |
32 & 64 bit |
|
Oracle Enterprise Linux 5 |
32 & 64 bit |
32 & 64 bit |
32 & 64 bit |
|
|
Red Hat Linux 5.4 |
32 & 64 bit |
32 & 64 bit |
32 & 64 bit |
|
|
Red Hat Linux 5.3 |
32 & 64 bit |
32 & 64 bit |
32 & 64 bit |
32 & 64 bit |
|
Solaris 10 SPARC |
64 bit |
64 bit |
64 bit |
32 & 64 bit |
|
Solaris 10 x86 |
32 & 64 bit |
32 & 64 bit |
-- |
32 bit |
Footnote 1 The supported bits for the platforms are noted in the table.
OHMPI requires the following software:
OHMPI also requires a web browser to view the Master Index Data Manager (MIDM) and a database.
OHMPI requires that a Java Development Kit is installed, and on UNIX systems the JAVA_HOME environment variable set, on the computer on which you install a Master Person Index prior to beginning the installation.
For OHMPI Release 1.1, the supported JDK is the minimum required to run the OHMPI Installer and install the program.
JDK 1.6.0_18
If you do not already have the JDK software installed or if JAVA_HOME is not set, the Master Person Index installation will not be successful. The following tasks provide the information you need to install the JDK software on Windows and UNIX systems. Set JAVA_HOME on UNIX systems only if you have more than one JDK installed on your system as the installation automatically selects first installed version.
Caution:
NetBeans IDE and GlassFish require the JDK for installation, in particular JDK 1.6 Update 18 or later. If you select a Java Runtime Environment (JRE) instead of a JDK, you cannot install or configure NetBeans IDE or GlassFish.Oracle WebLogic Server, which is a separate installation, automatically installs JRockit JDK. However, if you intend to use Oracle JDK, it must be installed before you install the WebLogic Server.
Select the appropriate JDK version and click Download. The JDK software is installed on your computer (for example, at C:\Program Files\Java\jdk1.6.0_18).
Note:
You can change this location.Install the JDK software.
Select the appropriate JDK version and click Download. The JDK software is installed on your computer, for example, at /usr/jdk/jdk1.6.0_18.
Note:
You can change this location.Set JAVA_HOME
Korn and bash shells:
export JAVA_HOME=<jdk-install-dir>
export PATH=$JAVA_HOME/bin:$PATH
Bourne shell:
JAVA_HOME=<jdk-install-dir>
export JAVA_HOME
PATH=$JAVA_HOME/bin:$PATH
export PATH
C shell:
setenv JAVA_HOME <jdk-install-dir>
setenv PATH $JAVA_HOME/bin:$PATH
OHMPI supports the following web browsers:
Firefox 3.5x or later
Internet Explorer Version 7 or 8
Firefox is the preferred browser for the MIDM web application. Any operating system that can run on Firefox or Internet Explorer is capable of opening and using the MIDM, including Apple Macintosh.
OHMPI supports the following databases:
Oracle 11gR2, Oracle 10gR2
MySQL Community Server 5.1.51
Microsoft SQL Server 2005SP3, 2008SP1
Note:
IHE Profiles Application does not support Microsoft SQL Servers.
