7 MIDM Reports

This chapter introduces you to MIDM reports and provides a procedure that shows you how to run the reports.

This chapter includes the following sections:

• "Learning About MIDM Reports"

• "Running MIDM Reports"

Learning About MIDM Reports

Oracle Healthcare Master Person Index 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, helping you monitor stored data and determine how that data needs to be updated. This information also helps verify that the matching logic and weight thresholds are defined correctly. Activity reports provide statistical information for transactions over specific periods of time.

The following sections provide additional information to help you understand and work with the default reports:

• "MIDM Production Reports"

• "MIDM Activity Reports"

• "Configuring MIDM Reports"

• "Masked Data and MIDM Reports"

MIDM Production 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 being processed with the current configuration. In addition to running the production reports daily, you should run them against any data that has been loaded from existing systems into the master person index database in batch format. Production reports are run based on a date range you specify.

• Assumed Match Report - This report displays information about any profiles that were automatically updated by incoming data during the specified time period. The information in this report, in combination with data from the potential duplicate report, helps you determine whether the matching threshold for assumed matches is accurate. You should review this report daily to ensure that no assumed matches were made in error.

• Deactivated Record Report - This report displays a list of all profiles that were deactivated during the specified time period. Review this report daily to ensure that no profiles were 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 were marked as potential duplicates of one another during the specified time period. The information provided in this report can help you determine whether 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 that were merged during the specified time period. Review this report daily to ensure that no profiles were merged in error. Master person index applications provide the ability to unmerge any merged profiles.

• UnMerge Transaction Report - This report displays a list of all object profiles that were unmerged during the specified time period.

• Update Report - This report displays object profiles whose information was updated during the specified time period. Review this report daily to verify the updates made in a given day. This report can help explain why a resolved potential duplicate listing was reinstated to the potential duplicate list.

MIDM Activity Reports

Activity reports should 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 helps analyze the condition of the data by giving you 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

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

Configuring MIDM Reports

The report files are configured in midm.xml in the master person index project. For detailed information and instructions on configuring the reports, see "Configuring the MIDM Pages" in Oracle Healthcare Master Person Index Configuration Guide and "Master Index Data Manager Configuration" in Oracle Healthcare Master Person Index Configuration Reference.e.

Masked Data and MIDM Reports

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 will display the hidden data if those fields are configured to appear on the reports. Be sure to only give access to users who should be able to view this information, or do not include hidden fields in the reports.

Running MIDM Reports

Reports are run from the Reports page of the MIDM. You need the appropriate security permissions to run the production and activity reports from the MIDM. Production and activity reports require that a time period be defined in the search criteria, and certain reports take additional search criteria.

To Run Reports From the MIDM

1. In the MIDM tabbed headings, click the Reports tab.

   The Reports Search page appears.

2. On the Reports Search page, select the type of report to run from Reports sub-tabs.

3. Enter the search criteria (for more information, see "About Report Search Fields on the MIDM").

4. Click Search.

   The selected report appears.

5. To sort the report by a single column, click that column name.

6. To change whether the column is sorted by ascending or descending order, click again on the column.

7. To print the report, click Print in the upper right portion of the window.

About Report Search Fields on the MIDM

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

In this field ...	type or select ...
From Date	The start date for the report. The report will retrieve transactions that occurred beginning on this date through the date specified in the To Date field.
From Time	The start time for the report, in the format HHmmss.
To Date	The end date for the report.
To Time	The end time for the report, in the format HHmmss.
Report Maximum Size	For Potential Duplicate and Assumed Match reports only, the number of records to display for the report. This allows you to limit the size of the report, which can grow quite large in some cases.
System	For Potential Duplicate reports only, the source system of the potential duplicate profiles to retrieve. You can specify all systems by leaving this field blank. This field is not visible for any other type of report.