Oracle® Healthcare Master Person Index Data Manager User's Guide Release 3.0 E62301-01 |
|
|
PDF · Mobi · ePub |
This chapter introduces you to MIDM reports and provides a procedure on how to run the reports. It includes the following sections:
OHMPI provides a set of production and activity reports that can be generated from the MIDM. The production reports provide information about the current state of the data in the master person index application to monitor stored data and determine how that data needs to be updated. This information helps to verify if the matching logic and weight thresholds are defined correctly. Activity reports provide statistical information for transactions over specific period of time.
The following sections provide additional information on how to work with the default reports:
Production reports provide information about the transactions that are processed through the master person index database. These reports provide lists of potential duplicate profiles, merge transactions, unmerge transactions, assumed matches, updates, and deactivated profiles for a specified time period. These reports provide valuable information about how data is processed with the current configuration. In addition to running the production reports daily, you must run them against any data that is loaded from existing systems into the master person index database in the batch format. Production reports are run based on a date range you specify.
Assumed Match Report - This report displays information about any profiles that are automatically updated by incoming data during the specified time period. The information in this report along with data from the potential duplicate report, determines the accuracy of the threshold for assumed matches. You must review this report daily to ensure that no assumed matches are made in error.
Deactivated Record Report - This report displays a list of all profiles that are deactivated during the specified time period. Review this report daily to ensure that no profiles are deactivated in error. Master person index applications provide the ability to reactivate any deactivated profile.
Potential Duplicate Report - This report displays information about object profiles that are marked as potential duplicates of one another during the specified time period. The information provided in this report determines if the matching threshold and the duplicate threshold are configured accurately. Review this report daily to ensure potential duplicates are managed in a timely manner, and use this report as a work list when processing potential duplicates.
Merge Transaction Report - This report displays a list of all object profiles and their source records that are merged during the specified time period. Review this report daily to ensure that no profiles are merged in error. You can unmerge any merged profiles using the Master person index applications.
UnMerge Transaction Report - This report displays a list of all object profiles that are unmerged during the specified time period.
Update Report - This report displays object profiles whose information is updated during the specified time period. Review this report daily to verify the updates for a given day. This report details the reason why a resolved potential duplicate listing was reinstated to the potential duplicate list.
Activity reports must be run weekly, monthly, and yearly to obtain statistical data about the transactions that are processed through the master person index database. These reports give the number of each type of transaction performed for the specified week, month, or year. They also provide cumulative information for the week, month, or year to date. The information you find in these reports help you analyze the condition of the data by providing the number of potential duplicates created, the number of assumed matches, and so on.
Weekly Activity Report - This report displays a summary of transactions that occurred against the database on each day for the specified calendar week (always Sunday through Saturday). The information provided in this summary includes the number of each of the following transactions performed each day.
Add
EUID Deactivate
EUID Merge
EUID Unmerge
LID Merge
LID Unmerge
LID Delete
Unresolved Potential Duplicates
Resolved Duplicates
Monthly Activity Report - This report displays a summary of transactions that occurred against the database during the specified month. You can run this report for any calendar month. The information provided in this report includes a summary of each transaction listed for the weekly activity report above.
Yearly Activity Report - This report displays a summary of transactions that occurred against the database for the specified calendar year. You can run this report for any calendar year. The information provided in this report includes a summary of each transaction listed for the weekly activity report above.
The report files are configured in the midm.xml file in the master person index project. For detailed information and instructions on configuring the reports, see Oracle Healthcare Master Person Index Configuration Guide and Oracle Healthcare Master Person Index Configuration Reference.
Though the MIDM can be configured to hide certain fields from users who do not have the appropriate security permissions, reports generated from the MIDM displays the hidden data if those fields are configured to appear on the reports. Ensure to grant access to users who can view this information, or do not include hidden fields in the reports.
Reports are run from the Reports page of the MIDM. You need appropriate security permissions to run the production and activity reports from the MIDM. Production and activity reports require a time period to be defined in the search criteria, and certain reports take additional search criteria.
In the MIDM tabbed headings, click the Reports tab.
The Reports Search page appears.
On the Reports Search page, select the type of report to run from the Reports subtab.
Enter the search criteria. For more information, see About Report Search Fields on the MIDM.
Click Search.
The selected report appears.
To sort the report by a single column, click that column name.
To change whether the column is sorted by ascending or descending order, click again on the column.
To print the report, click Print Report.
The report search fields let you specify a date range for each report. For Potential Duplicate reports, you can also specify the status of the potential duplicates returned by the search.
Table 7-1 Report Search Fields
Field Name | Description |
---|---|
From Date |
The start date for the report. The report retrieves transaction that occurred starting on this date through the date specified in the To Date field. |
From Time |
The start time for the report in the HHmmss format. |
To Date |
The end date for the report. |
To Time |
The end time for the report in the HHmmss format. |
Report Maximum Size |
The number of records to display. This is applicable only for Potential Duplicate and Assumed Match reports. This lets you limit the size of the report, which can be large in some cases. |
System |
The source system of the potential duplicate profiles to retrieve. This is applicable only for Potential Duplicate reports and is not visible for other reports. You can specify all systems by leaving this field blank. |