| Oracle® Healthcare Master Person Index Data Manager User's Guide Release 4.0 E68417-01 |
|
|
PDF · Mobi · ePub |
| Oracle® Healthcare Master Person Index Data Manager User's Guide Release 4.0 E68417-01 |
|
|
PDF · Mobi · ePub |
This chapter provides information and procedures about MIDM, including logging in and out of the MIDM, using the dashboard, and learning about object queries.
This chapter includes the following sections:
The MIDM is the primary tool to view and maintain the data stored in the master person index database and cross-referenced by a master person index application. It is a web-based application. The MIDM uses standard web-based features, such as hyperlinks, data fields, icons, and action buttons, to help you enter information and navigate through the different pages.
The following sections provide basic information about the design of the MIDM and logging in and out of the application:
The MIDM is supported on Mozilla Firefox 24 and higher, Internet Explorer 10 and higher, and Google Chrome 30 and higher. Oracle recommends that you use Internet Explorer or Mozilla Firefox to access the MIDM application in the WebLogic Clustering environment.
For the browser you use, ensure that pop-up windows are allowed for the MIDM URL, and that JavaScript is enabled. Additionally, if you are working with sensitive data, disable the feature that automatically fills in field values as you type. These options are configured on the Options (Mozilla Firefox) or Internet Options (Internet Explorer) window accessed from the Tools menu.
Before using the MIDM, you must first log in to the application in your web browser. Ensure you have a user ID and password for the master person index application before logging in. The application server running the master person index application must be started before you can log in to the MIDM.
The URL for the MIDM is:
http://host:http_port/application_nameMIDM
where,
host is the name of the server machine.
http_port is the HTTP port number of the application server.
application_name is the name of the master person index application.
Note:
The application name is created when the project is created. The MIDM at the end of the URL is case-sensitive and must be entered in capital letters.The HTTP port number for the application server is listed in the config.xml file in the listen-port element under the sever element (7001 by default). The config.xml file is located in the user_projects\domains\domain_name\config directory.
Launch a web browser.
In the Address field, enter the appropriate URL.
The login page appears.
In the upper-right portion of the page, select the language for the MIDM display from the drop-down list.
Note:
This performs only a partial translation and you must configure your system. For additional information, see Oracle Healthcare Master Person Index Configuration Guide and Oracle Healthcare Master Person Index Configuration Reference.Enter your user ID and password in the appropriate fields.
Click Login.
The initial page appears. By default, the initial page is the Record Details page, but this is configurable.
Note:
After a certain period of inactivity, the session for the user terminates. The MIDM automatically logs off and returns you to the Login page when you try to perform an activity on the MIDM. To access the MIDM, re-enter your user name and password. The system administrator can set the inactivity period at the server level in the session-timeout element of
default-web.xml (in appserver_home\domains\domain_name\config) or at the application level in web.xml in the master person index application .war file (located in the deployment .ear file) or in the deployment folder. The application level overrides any values set at the server level. The default inactivity period is 30 minutes.Security for the MIDM is defined at the function level. You may not be able to perform all functions described in this guide depending on the security permissions you are assigned. For more information about functions you can perform, contact your system administrator. Security for the MIDM is defined in the application server. For information about defining security for the MIDM, see Defining Master Index Data Manager Security.
The MIDM provides hyperlinks, icons, and command buttons to access and move through the MIDM pages. When you place the cursor over links, icons, and images on the MIDM pages, tooltips are displayed, which provide additional information. Information is also provided to facilitate the use of screen readers and other assistive technology.
The actions you can perform on the MIDM are grouped into these primary functions: Dashboard, Duplicate Records, Record Details, Assumed Matched, Transactions (history), Source Record, Reports, and Audit Log. The main menu on all MIDM pages provides hyperlinks to each of these functions. The first page is the Search page that is displayed for each function, except the Source Record function. You can modify the names of these headings for your application.
Dashboard - This provides a summary of recent transactions, quick links to commonly used functions, and quick lookup functions. The information, links, and lookup functions on this page can be configured by the system administrator.
Duplicate Records - This lets you perform a search for potential duplicate profiles. Potential duplicate profiles are those whose matching probability weight indicates that they might match but is not high enough to automatically match the two profiles. From the associated pages, you can compare, merge, or resolve potential duplicate profiles.
Record Details - This lets you perform a search for an object profile or a set of object profiles in the master person index application. From the associated pages, you can compare two object profiles, compare records in one object profile, view all information for one object profile, view and print summary information for a profile, update an object profile or source record, delete an object profile, view a transaction history of an object profile, view potential duplicates of an object, and merge object profiles. It also allows you to view relationships associated with the searched EUID within Relationship Management.
Assumed Matches - This lets you perform a search for any profiles that are updated by an assumed match transaction. It also shows the transaction history that generated the assumed match. An assumed match occurs when the matching probability weight is high enough to indicate that two records represent the same object. From the associated pages, you can view and reverse assumed match transactions.
Transactions - This lets you perform a search for transaction histories. From the Transaction History pages, you can compare information about an object before and after a transaction occurred, select object profiles to unmerge (the last merged transaction), and view a merge history for an object profile. From associated Transaction History pages, you can unmerge object profiles.
Reports - This lets you display and print reports about certain transactions performed from the MIDM and from messages sent in from external systems. You can run reports from either the MIDM or from a command line.
Source Record - The Create Source Record function lets you create new object profiles by creating a source record. When you save the information in the source record, the master person index application automatically generates the SBR using the survivor calculator. You can also edit, delete, or merge source records from the Source Record page.
Audit Log - When enabled, this lets you perform a search for audit log entries. From the Audit Log pages, you can view information about transactions in which data about an object is accessed through the MIDM. This enforces HIPAA privacy rules for healthcare master indexes.
The detail pages display the SBR of the object profile on the left and summary information on the right side of the screen. You can further expand the pages to view source records on the right side. Child objects appear below the parent object, and you can expand and collapse the information for each type of object. If you are viewing a comparison of object profiles, you can expand the source records of one object profile at a time.
Table 2-1 displays the list of icons used in the MIDM application to provide enhanced usability to the end-users.
| Icon | Tool Tip | Description |
|---|---|---|
|
|
View Sources |
Displays all the source objects associated with the Enterprise object. |
|
|
View History |
Displays history of the Enterprise object. |
|
|
View Merge Tree |
Displays the hierarchy of the merged records. |
|
|
View Transaction |
Directs to the transactions page where you can view the transaction details for the assumed match record. |
|
|
View Summary |
Displays the summary for the Enterprise object. |
|
|
Print SBR |
Displays details for the SBR in a report format. |
|
|
Delete |
Deletes the source object. |
|
|
Potential Duplicate |
Marks a record as potential duplicate. |
|
|
Different Records |
Marks a record as different. |
|
|
System Record Transfer |
Transfers system object to an Enterprise object. |
|
|
View Relationships |
Redirects you to Relationship Management UI screen to provide a list of relationships associated with the EUID. For more information, see Oracle Healthcare Master Person Index Relationship Management User's Guide. |
Before you exit the MIDM, ensure you have saved the changes (if any). To exit the MIDM, click Sign Out in the upper-right corner of the page. The Login page reappears.
The following sections provide step-by-step instructions to perform various functions available from the MIDM dashboard. The information in these topics is based on the default configuration.
The dashboard provides a short summary of important transactions that have occurred in the past 24 hours. You can view how many transactions occurred and link to the search pages to view more information.
In the tabbed headings, click Dashboard.
The Summary box displays the number of potential duplicate and assumed match transactions that have occurred in the past 24 hours.
To view additional information about potential duplicates, click Potential Duplicates in the Summary field, and then perform a search as described in the section Working with Potential Duplicate Profiles on the MIDM.
To view additional information about assumed match transactions, click Assumed Matches in the Summary field, and then perform a search as described in the section Working with Assumed Matches on the MIDM.
The dashboard provides quick links to the search pages for different type of production reports that gives information about the status of your data.
In the tabbed headings, click Dashboard.
To view a merged record report, click Merged Records, and perform a search as described in the section Running MIDM Reports.
To view a deactivated record report, click Deactivated EUIDs, and perform a search as described in the section Running MIDM Reports.
To view an unmerged record report, click Unmerged Records, and perform a search as described in the section Running MIDM Reports.
To view an audit log report, click Audit Log, and perform a search as described in the section Viewing the MIDM Audit Log.
To search for an object profile using only the EUID of an object, you can enter the EUID number in the Quick Search box of the dashboard. This type of search results in only one matching profile.
In the tabbed headings, click Dashboard.
In the Quick Search section, enter the EUID of the object.
Click Search to initiate the search.
The Record Details page appears, displaying detailed information about the object.
To perform a more advanced search with multiple criteria fields and options, click Advanced Search.
You can perform a lookup of multiple EUIDs from the dashboard to compare object profiles in a side-by-side view on the Record Details page. To lookup multiple EUIDs, specify each EUID in the Compare EUIDs field on the dashboard. You can enter two to four EUIDs to compare in the search results list.
Before viewing or updating object information, you must perform a search for the object. There are several different search capabilities within the MIDM. You can perform lookups for specific object profiles using unique identifiers, such as the EUID or local ID, and you can perform broader searches using data from the parent or child objects as criteria.
The following topics provide information about working with general searches that find specific records in the master person index database. Most of these searches are performed from the Record Details page, but some are performed from the dashboard. Searches for specific functions, such as finding potential duplicates or assumed matches, are described in the topics for those functions.
There are several different methods of searching for objects, depending on the search criteria you enter. By default, the Record Details page includes three different search types: Advanced ProjectName Lookup (Alpha), Advanced ProjectName Lookup (Phonetic), and Simple ProjectName Lookup. You can also perform a EUID lookup from the dashboard to view record details. The search functionality provides flexibility in designing database queries. You can narrow a search for a specific object or a range of objects using various fields on the search pages, and then view your search results in the search results list. When you select a specific object from the Search Result page, detailed information for that object appears on the Record Details page in the view mode.
Note:
The names of the search types are configurable. Searches are described in the following sections by their default names, and images show customized search criteria. Contact your system administrator if you have questions about how your search pages are configured.The Simple Lookup on the Record Details page lets you perform lookups using unique identifiers to find a specific object profile. By default, the unique identifiers you can use as search criteria include the EUID, and the local ID and system. When you perform this type of search, the search results list is bypassed and the Record Details page appears in the view mode, displaying information about the matching profile.
You can perform a EUID lookup from either the Dashboard or the Record Details page. Other simple lookups include system and local ID lookups, which can be performed from the Record Details page or the Source Record page. To increase search accuracy, you can select only the system listed in the drop-down list and the Local ID field is case-sensitive.
The Advanced Alphanumeric Lookup on the Record Details page lets you perform various types of searches against the database using a field or combination of fields as criteria. This type of search is an exact match search, which returns profiles that exactly match the criteria you specify. You can specify any combination of fields as long as any fields that are required for the search are entered. Most fields in this search allow wildcard characters if the exact value is unknown.
The fields displayed on the Search page are configured by the system administrator. You can enter as much information as needed to narrow down the search appropriately.
The Advanced Phonetic Lookup on the Record Details page lets you perform various types of searches against the database using predefined combinations of fields as criteria. This type of search compares the phonetic values of certain fields entered as criteria. The object profiles returned by a phonetic search are assigned a matching probability weight to indicate how closely they match the search criteria. Phonetic searches are not exact match searches and allow for misspellings or data entry errors.
The fields displayed on the Search page are configured by the system administrator. You can enter as much information as needed to narrow down the search appropriately. For phonetic searches, certain combinations of criteria are required to perform a search. The search is only carried out for combinations that have complete data.
For example, in a master company index, a blocking search might be configured to search on the following combinations:
Company Name and Sales Region
Company Name and Address Line1
Tax Payor ID
Stock Symbol and Address Line1
If Company Name, Address Line1, and Stock Symbol are entered as criteria, only the second and fourth combinations are carried out. The returned result set includes any records that match on Company Name and Address Line1 or that match on Stock Symbol and Address Line1. If only Company Name is entered as the criteria, no records are returned since it does not fulfill any of the combination requirements.
The search results list appears under the search fields and displays a list of object profiles found in the database that closely match the search criteria you entered. The results list appears in a table, with the number of profiles returned for the search displayed above the table. This page displays information to identify the object profile, such as the EUID or address information. The search results list appears differently depending on which type of search is performed and how the lists are configured. For more information about search results, see Working with Search Results on the MIDM.
Your system administrator can configure the search pages to let you enter a range to search for certain fields. For example, you might want to search for profiles with a specific name, but with a date that falls within a five-year range. If a field is defined to search by a user-defined range, the MIDM displays a from field and a to field so you can specify the range (for example, Date From and Date To). If you enter a value only in the from field, the MIDM searches for profiles with a value greater than or equal to that value. If you only enter a value only in the to field, the MIDM searches for profiles with a value less than or equal to that value.
Ranges can also be defined as an entered value plus or minus a specific value. For example, a date field can be configured to search for dates that fall within a range five years earlier than the date you enter, and five years later than the date you enter. Ranges can be defined as specific upper and lower limits. These limits are used when no value is entered. For example, if you perform a search without the date, the MIDM searches between the defined lower and upper limits. If you enter only the from date, the MIDM searches between the date you entered, and the defined upper limit. For more information about how your system is configured for range searching, contact your system administrator.
Certain fields are mandatory for searches on the MIDM. If a field is marked with an asterisk (*), it indicates that it is mandatory. If multiple fields are marked with daggers (†), at least one of these fields must be populated to perform the search. The required fields can vary depending on the type of search you perform.
|
 Copyright © 2011, 2016, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|
