| Oracle® Healthcare Master Person Index Data Manager User's Guide Release 3.0 E62301-01 |
|
|
PDF · Mobi · ePub |
| Oracle® Healthcare Master Person Index Data Manager User's Guide Release 3.0 E62301-01 |
|
|
PDF · Mobi · ePub |
This chapter helps you understand and look at the profile views. It includes the following sections:
Once you retrieve a search results list, you can view detailed information of an object, print summary information, compare object profiles, view merge transaction history for a profile, delete a source record, and view history of all transactions for a profile.
You can view object information in any of the following formats:
When you select a profile to view from the search results list, detailed information about the selected object appears on the Record Details page in the view mode. This page displays the SBR of the profile you selected on the left and summary information on the right side of the page. You can further expand the view to include all source records contained in the profile. Parent object information appears first followed by the data for each child object. From the Record Details page, you can perform several actions, such as viewing a transaction history for the object, viewing potential duplicate profiles, viewing merged transactions for the profile, deactivating the profile, updating object information, deleting the profile, and so on.
You can view source record details from the following:
Record Details page - You can view all source records for an object profile. You can also edit the source records belonging to a profile.
Source Record page - You can search and view a specific source record. You can perform several actions against a source record, including adding, editing, deleting, deactivating or reactivating a source record, and merging two to four source records.
You can compare multiple object profiles by performing a EUID comparison lookup for the profiles to compare from the dashboard or by selecting multiple profiles in a search results list. The profiles are displayed in a side-by-side view or tabular format on the Record Details page. Once the profiles are displayed on the Record Details page, you can compare the source records of each object profile.
The Record Details comparison view lets you view the selected profiles in a side-by-side comparison with the differences between the profiles highlighted. You can compare the SBR of a profile with its own source records, and source records in one profile or between multiple profiles. This provides a complete comparison between object profiles and source records.
On the Source Record page, you can compare up to four source records from multiple profiles if they are all from the same source system.
You can view a history of all transactions performed against object profiles either by performing a search for specific records as described in Searching for Object Profiles on the MIDM, or by performing a Transaction History search on the Transactions page as described in Viewing Transaction Histories on the MIDM. You can trace the events that modified an object profile from the time the profile is added to the master person index application to the most previous transaction, including merged and deactivated profiles.
The Transaction History page lets you view a side-by-side comparison of an object profile before and after a transaction occurred against that profile. You can also compare an SBR against an SBR, an SBR against a source record, and a source record against a source record. From associated Transaction History pages, you can unmerge the most recent merged profiles.
You can display a history of the merges that have affected a specific object profile. The merge history for a EUID or Local ID is available to view a transactions page for the specified SBR. The top level displays the EUID of the current active profile. The EUIDs at the second level indicate the profiles that are merged into the top-level EUID to form the top-level profile of the SBR. If there are Local IDs listed, they indicate profiles that are merged to form the profile above them. There may be several levels of merges displayed in the merge history of an object.
The right side of the page displays information about the merge transactions that involved the EUID that is selected in the EUID tree on the left. You can select a specific transaction to view a transaction history comparison for that merge transaction.
The audit log lets you track and view all instances, in which information about the objects in the master person index application is accessed through the MIDM. If audit logging is enabled, an audit log entry is created each time the MIDM accesses database tables that contain object information. The audit log keeps a record of each time the tables are accessed, along with the database function used to access the tables, the login ID of the user accessing the tables, the date and time the tables are accessed, and the EUIDs of the object profiles that are accessed. The audit log is enabled and disabled in the midm.xml file in the master person index project.
The MIDM displays object profiles in a series of pages from which you can search, select, and view object profiles. You can view information associated with any of the SBR or source record components in an object profile. The SBR contains the most current and accurate information about that object from all external systems.
The source records associated with a profile contain information that is stored in the external systems that share information with the master person index application. The information in a source record may not match the information in the SBR. You can view information about an object in different ways, including the following:
The Record Details page displays object profiles in a series of pages from which you can select and view profiles. You can view information associated with any of the SBR or source record components in an object profile. The SBR contains the most current and accurate information about that object from all local systems.
Using one of the search methods described in Searching for Object Profiles on the MIDM, display the object profile you want to view on the Record Details page.
To view different types of information in the SBR for the displayed object, scroll through the visible data fields.
To view source records belonging to the profile, click 
.
All source records for the profile appear in a side-by-side comparison view.
From the Record Details page, perform any of the following functions.
To modify object information, click Edit EUID and follow the appropriate procedure under Modifying Profile Information on the MIDM.
To view a history of transactions for the displayed profile, click 
.
For more information, see Viewing Transaction Histories on the MIDM.
To deactivate a profile, click Deactivate. For more information, see Deactivating a Profile or Source Record.
To delete a source record, click 
on the top-right corner of the source record.
To view a merge history tree for the profile, click 
.
A Transaction page with a merge tree on the left side of the screen and the merged transaction on the right side appears. This option is only available if the displayed profile is currently merged with another profile.
After viewing a profile, perform any of the following. The buttons you click are located at the top of the page.
To return to the search results list, click Back.
To look up another profile by EUID, enter the EUID in the field in the upper-left side and click Search.
To perform an advanced search for another profile, click Advanced Search.
The Source Record page displays source records in a series of search and view pages. You can view information associated with any of the SBR or source record components in an object profile. The source records associated with a profile contain the information that is stored in the external systems that share information with the master person index application. The information in the source records of an object may not match the information stored in the SBR of the object.
In the tabbed headings, click Source Record.
Click the View/Edit subtab, if it is not already selected.
In the System drop-down list, select the system from which the source record originated.
In the Local ID field, enter the local ID number for the source record you want to view.
Note:
If the Local ID field allows alphabetic characters, the search is case-sensitive.Click Search.
If the local ID is found, the source record fields appear in the view mode.
From the Source Record View/Edit page, perform any of the following functions.
To modify field values in the source record, click Edit, and follow the appropriate procedure in Modifying Profile Information on the MIDM.
To view the object profile that contains the displayed source record, click View EUID. For more information, see Viewing Object Profiles on the MIDM.
To deactivate the source record, click Deactivate.
To delete a source record, click Delete.
The MIDM lets you compare two or more object profiles side-by-side to check for similarities and differences. You can also compare different components of the same object profile, and two or more source records from the same or different profiles.
To compare two or more object profiles, you can either perform a EUID comparison lookup from the dashboard, or select multiple records from a Record Details search. From the resulting comparison page, you can compare the resulting profiles, and view the source records for the displayed profiles.
Perform a search for the object profiles you want to compare, using one of the following methods:
If you know the EUIDs of the profiles you want to compare, look up the EUIDs from the dashboard as described in Performing a EUID Comparison Lookup.
If you do not know the EUIDs of the profiles to compare, perform a search on the Record Details page as described in Searching for Object Profiles on the MIDM. Select the check boxes next to the EUIDs to compare and click Compare.
The records appear on the Record Details page in a side-by-side comparison view.
To view the source records for a displayed profile, click .
After viewing the source records for a profile, click to return to the comparison view.
To view a transaction history for one of the displayed profiles, click .
After viewing the transaction history for a profile, click to return to the comparison view.
To merge object information, click the EUIDs of the profiles you want to merge, and then click Preview. Follow the instructions in Merging Object Profiles on the MIDM.
You can view the source records from one or more object profiles displayed on the Record Details page in either the view or comparison mode. This page does not provide merge functionality for source records. To merge source records, compare the records on the Source Record page as described in Viewing a Source Record on the MIDM.
Perform a search for the object profile containing the source records you want to view, as described in Searching for Object Profiles on the MIDM.
In the search results list, select the EUIDs of the profiles you want to view, and click Compare.
The Record Details page appears with SBR information displayed.
For each SBR whose source records you want to compare, click .
The source record that belongs to the profile appears.
To edit any of the displayed source records, click Edit EUID and follow any of the procedures in Modifying Profile Information on the MIDM.
To merge source records in the displayed object profile, make a note of their local IDs, and follow the instructions in Merging Source Records on the MIDM.
To compare source records directly without accessing them from an object profile, you need to know the system and local ID numbers for the records. On the Source Record page, you can only compare records that originated from the same system.
In the tabbed headings, click Source Record.
Click the Merge subtab.
In the Source drop-down list, select the name of the source system from which the records you want to compare originated.
In the Local ID fields, enter one to four local IDs.
Note:
If any of the Local ID fields allows alphabetic characters, the search is case-sensitive.Click View Records.
Any matching source records appear side-by-side in a comparison view.
To view the object profile for one of the source records, click View EUID for that source record.
This takes you to the Record Details page. To return to the Source Record comparison page, click Back.
To merge any of the displayed source records, see Merging Source Records on the MIDM.
Using the Transactions function, you can view historical information for a specific object, and compare the profile of the object before and after a specific transaction occurred to determine what information is modified. You can access the transaction history for a profile from the Record Details page, or for one or more profiles from the Transactions page.
When you display a transaction history from the Record Details page, all transactions for the displayed object profile appear in chronological order, with the earliest transaction on the left, and the most recent transaction on the right. When you display a transaction history record from the Transactions page, the image of the profile as it was before the transaction appears on the left side of the comparison page. The image on the right reflects the information of the object after the transaction occurred.
Perform a search for the object profile whose history you want to view using one of the search procedures described in Searching for Object Profiles on the MIDM.
If necessary, select the profile to view from the search results list.
The profile appears on the Record Details page.
Click .
A history of all transactions performed against the object profile appears.
You must obtain information about the object profile whose history you want to view, such as the EUID, a system in which the object is registered, or a specific transaction performed against the object's profile.
In the tabbed headings, click Transactions.
Enter values in any of the search fields as criteria. For more information about these fields, see Table 4-1.
Note:
The EUID field takes precedence over all other search fields on this page. You can only enter a Local ID as search criteria after entering the corresponding system. You can also search for all transactions related to all objects in a particular system by providing the system code.Click Search.
The Transaction History search results list appears with a list of matching transactions. For more information, see Table 4-1.
Click a transaction number of a result to view the transaction on the Transactions comparison page.
Note:
If you are viewing an unmerge transaction, the active record before unmerge is displayed on the left. The after-image of the two records that are unmerged during the transaction is displayed on the right.To view the source records for either the before or after profile, click .
If you are viewing a merge transaction that is not unmerged, you can unmerge the records here. For more information, see Unmerging Object Information on the MIDM.
To print the transactions, click Print Report.
The fields located on the Transaction History Search page lets you specify search criteria for the transactions you want to view. Note that the label for the Local ID field is customizable and may be changed for your implementation. The search page can also be configured to display additional transaction fields. Table 4-1 lists the fields that are defined by default for a transaction history search.
Table 4-1 Transaction History Search Fields
| Field Name | Description |
|---|---|
|
EUID |
The enterprise-wide unique identifier of an object assigned by the master person index application. |
|
System |
The system in which the local ID is known. |
|
Local ID |
The local ID corresponding to the record you want to find and the system selected in the previous field. This field name may be different for your implementation. |
|
From Date |
The start date for the search. The query is performed for transactions that fall between the From Date and To Date. |
|
From Time |
The start time for the search using 24-hour notation. The query is performed for transactions that fall between the From Time and To Time on the specified dates. If no time is entered, the default value is 00:01 (12:01 AM). |
|
To Date |
The end date for the search. |
|
To Time |
The end time for the search using 24-hour notation. If no time is entered, the default value is 24:00. |
|
System User |
The login ID of the user who performed the transaction for which you are searching. |
|
Function |
The type of transaction that caused the object's profile to change. See Table 4-3 for more information about transaction types. |
The fields located in the Transaction History search results list identifies a specific object profile and transaction to view. Additional fields may be added to this page by the system administrator. The Local ID labels are configurable and may be changed for your implementation.
Table 4-2 Transaction History Results Fields
| Field Name | Description |
|---|---|
|
Transaction No. |
The sequential identification code of the transaction that caused the transaction history record. |
|
EUID1 |
The enterprise-wide unique identification number of the first object profile involved in the transaction. |
|
EUID2 |
The enterprise-wide unique identification number of the second object profile involved in the transaction, if appropriate. |
|
System |
The name of the system in which the transaction that created the history record occurred. |
|
Local ID1 |
The local ID of the first source record involved in the transaction. |
|
Local ID2 |
The local ID of the second source record involved in the transaction, if appropriate. |
|
Function |
The type of transaction that changed the object profile and caused the history record to be written. See Table 4-3 for a description of each transaction type. |
|
System User |
The login ID of the user who performed the transaction. |
|
TimeStamp |
The date and time the transaction occurred. |
Each transaction performed by the master person index application is assigned a transaction type, indicating the type of action that is performed against the profile. Table 4-3 lists and describes each transaction type:
Table 4-3 Transaction Type Descriptions
| Transaction Type | Description |
|---|---|
|
Add |
This transaction type is assigned when a new object profile is added to the database, whether it is through a direct add or through reversing an assumed match. |
|
EUID Activate |
This transaction type is assigned when a deactivated object profile is reactivated. |
|
EUID Deactivate |
This transaction type is assigned when an active object profile is deactivated. |
|
EUID Merge |
This transaction type is assigned when two object profiles are merged. |
|
EUID Unmerge |
This transaction type is assigned when two object profiles are unmerged. |
|
SO Delete |
This transaction type is assigned when a system object is deleted from the application. |
|
System Record Merge |
This transaction type is assigned when two source records are merged. |
|
System Record Transfer |
This transaction type is assigned when a source record is transferred from one object profile to another. |
|
System Record Unmerge |
This transaction type is assigned when two source records are unmerged. |
|
Update |
This transaction type is assigned when an object profile is modified in any way other than those described above. This includes such transactions as modifying an object profile, reversing an assumed match, deactivating or reactivating a source record, and adding or removing a child object (such as an address or telephone number). |
When an object profile that is currently merged is displayed on the Record Details page, you can display a history of all merges performed against the profile, and trace the origin of certain information contained in the profile. The master person index application tracks all merges performed against each object profile in the database. You can view a history of merges that affect a specific object profile and view each EUID that is merged to form the final merge result profile. The merge history appears in a tree structure on the left side of the Transaction page. The right side of the page displays each pair of profiles that are merged for the selected merged transaction.
Using one of the search procedures described in Searching for Object Profiles on the MIDM, perform a search for the object whose merge history you want to view.
If necessary, select the object profile you want to view from the search results list.
The Record Details page appears.
Under the SBR, click .
A Transaction page with a merge tree on the left side of the screen and the merged transaction on the right side appears.
Expand the tree structure to view the EUIDs or LIDs that are combined to create the current record.
To view transaction information for any of the merge transactions, click any of the EUIDs involved in the transaction.
If the profile you are viewing on the Record Details page is merged, you can view the merged profiles that are combined to create the currently displayed profile.
Using one of the search procedures described in Searching for Object Profiles on the MIDM, perform a search for the object whose merge history you want to view.
If necessary, select the object profile you want to view from the search results list.
The Record Details page appears.
Click View Merged Records.
The profiles that are merged to create the current profile are displayed.
Using the Audit Log function, you can view a record of each instance an MIDM user accessed information about any object in the master person index database. The audit log includes instances in which an object profile appeared in a search results list, viewed or compared, added, updated, deleted, or deactivated, and merged or unmerged. The system administrator can enable or disable the audit log.
Note:
You must enable the MIDM Audit Log for it to function.You must obtain information about the instances you want to view such as, the EUID, a time frame when they occurred, the type of function that caused the audit log entries, the user who performed the functions, and so on.
In the tabbed headings, click Audit Log.
Enter values into any of the search fields as criteria. For more information about these fields, see About Audit Log Results Fields on the MIDM.
Note:
The EUID field takes precedence over all other search fields on this page. You can only enter a local ID as search criteria after you have entered the corresponding system.Click Search.
On the Audit Log search results list, view the instances in which the data is accessed. For information about the fields displayed on this page, see About Audit Log Results Fields on the MIDM.
The fields located on the Audit Log Search page lets you enter search criteria about the audit log entries you want to view. These fields are configurable. Table 4-4 describes the fields that are displayed by default.
Table 4-4 Audit Log Search Fields
| Field Name | Description |
|---|---|
|
EUID |
The object's enterprise-wide unique identifier assigned by the master person index application. |
|
System |
The system of the system in which the local ID is known. |
|
Local ID |
The local ID corresponding to the record you want to find and the system selected in the previous field. This field name might be different for your implementation. |
|
From Date |
The start date for the search. The query is performed for audit log entries that fall between the From Date and To Date. |
|
To Date |
The end date for the search. |
|
From Time |
The start time for the search using 24-hour notation. The query is performed for audit log entries that fall between the From Time and To Time on the specified dates. If no time is specified, the default value is 00:01 (12:01 AM). |
|
To Time |
The end time for the search using 24-hour notation. If no time is specified, the default value is 24:00. |
|
System User |
The login ID of the user whose transactions you want to view |
|
Function |
The type of transaction that created the audit log entries you want to view. For more information about transaction types, see Audit Log Functions on the MIDM. |
The fields located on the Audit Log Result page display information about the instances in which object data is accessed, where those instances match the search criteria you entered. These fields are configurable. Table 4-5 describes the fields that are displayed by default.
Table 4-5 Audit Log Results Fields
| Field Name | Description |
|---|---|
|
Audit ID |
The unique ID code in the audit log for the audit log entry. |
|
EUID1 |
The EUID of the first object profile whose information was accessed. |
|
EUID2 |
The EUID of the second object profile whose information was accessed in the same transaction (as in the case of a profile comparison or merge). |
|
Function |
The primary transaction type that is used to access information. For more information about transaction types, see Audit Log Functions on the MIDM. |
|
Detail |
Specific information about the actions taken against the profile such as, the MIDM page that is accessed or the type of function performed against a profile. |
|
Create Date |
The date and time that the information is accessed. |
|
Create User |
The login ID of the user who accessed the information. |
The audit log creates an audit entry whenever data is accessed through the MIDM. Table 4-6 lists and describes each audit log function. Some of these functions refer to the actual viewing of data on an MIDM page. Others refer to an action taken against that data, such as clicking the merge or unmerge Confirm button or resolving a potential duplicate pair.
Table 4-6 Audit Log Function Descriptions
| Audit Log Function | Description |
|---|---|
|
Add |
A user added a new object profile to the database from the Create Source Record page or by reversing an assumed match. |
|
Associated Potential Duplicates |
A user viewed profile summaries on the Associated Records page of a potential duplicate search. |
|
Assumed Match Comparison |
A user viewed two assumed match profiles on the Assumed Match page. |
|
Assumed Match Search Result |
A user viewed the results of a search for assumed matches. |
|
Auto Resolve or Resolve Permanently |
A user permanently resolved two potential duplicate records on the Potential Duplicate Comparison page. |
|
EO Comparison |
A user viewed two object profiles on the Comparison page. |
|
EO Search Result |
A user viewed profile summaries on the Search Results page after performing a search for object profiles. |
|
EO View/Edit |
A user viewed an object profile on the View/Edit page. |
|
EUID Merge Confirm |
A user initiated a merge of two object profiles. This function refers to when the user views the merge result before clicking Confirm. |
|
EUID Unmerge |
A user finalized an unmerge of two object profiles. |
|
EUID Unmerge Confirm |
A user initiated an unmerge of two object profiles. This function refers to when the user views the unmerge result before clicking Confirm. |
|
History Comparison |
A user compared the before and after image of an object profile on the Transaction History Comparison page. |
|
History Search Result |
A user viewed the results of a transaction history search on the Transaction History Search Results page. |
|
LID Merge - Selection |
A user initiated a merge of two source records. This function refers to when the user has selected LID Merge but has not finalized the merge. |
|
LID Merge Confirm |
A user finalized a merge of two source records. |
|
LID Unmerge |
A user finalized an unmerge of two source records. |
|
LID Unmerge Confirm |
A user initiated an unmerge of two source records. This function refers to when the user views the unmerge result record before clicking Confirm. |
|
Matching Review Search Result |
A user viewed the results of a search for potential duplicates. |
|
Merge |
A user finalized a merge of two object profiles or two source records. |
|
Merge Tree Comparison |
A user viewed merge transactions using the merge tree. This function appears for each object profile included in the merge tree. |
|
Potential Duplicate Comparison |
A user viewed two object profiles on the Potential Duplicate Comparison page. |
|
Resolve or Resolve Temporary |
A user resolved two potential duplicate records on the Potential Duplicate Comparison page. |
|
SO Delete |
A user performed the System Object Delete operation. |
|
Undo Assumed Match |
A user reversed an assumed match. |
|
Unmerge Comparison |
A user initiated an unmerge of two source records or two object profiles. This function refers to when the user views the unmerge result record before clicking Confirm. |
|
Unresolve |
A user changed the status of two object profiles on the Potential Duplicate Comparison page from Resolved to Unresolved. |
|
Update |
A user modified a profile on the View/Edit page. Updates include any changes made to a profile, including activating and reactivating source records, adding or removing child objects, and so on. |
|
View Merge Tree |
A user viewed a merge tree. |
|
 Copyright © 2011, 2015, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|
