Installing Upgrading Designing Configuring Deploying Monitoring Administering Troubleshooting Reference JBI Components
Close Print View
Administering: Patient Profile Components
 

Classic Java CAPS

Managing Java CAPS Users

Using LDAP with Java CAPS

Administering the Sun Business Process Manager Database

Using the Sun Business Process Manager Worklist Manager for User Activities

Maintaining Sun Master Indexes (Repository)

Working With the EDM for Sun Master Patient Index

Related Topics

About the Patient EDM

About Sun Master Patient Index

Features of Sun Master Patient Index

Functions of the Patient EDM

Learning about Patient Profiles

Patient Profile Components

Patient Profile Indicators

System Record and SBR Components for Sun Master Patient Index

Identification Numbers for each Patient

Working with the Patient EDM

Logging in to the Patient EDM

Security Permissions for the Patient EDM

Navigation Tips for the Patient EDM

Logging Out of the Patient EDM

Learning About Patient Queries

About the Patient EDM Search Function

Types of Searches on the Patient EDM

Searching by Ranges on the Patient EDM

Required Fields on the Patient EDM

Searching for Patient Profiles

Performing an EUID Lookup on the Patient EDM

Performing a Social Security Number Lookup on the Patient EDM

Performing a Local ID Lookup on the Patient EDM

Performing an Advanced Alphanumeric Lookup on the Patient EDM

About Alphanumeric Search Fields on the Patient EDM

Performing an Advanced Phonetic Lookup on the Patient EDM

About Phonetic Search Fields on the Patient EDM

Performing an EUID Comparison Lookup on the Patient EDM

Working with Search Results on the Patient EDM

Patient Profile Views

Patient Profile Details

Patient Profile Comparisons

Patient Profile Transaction Histories

Patient Profile Merge Histories

The Patient EDM Audit Log

Viewing Patient Profiles

Viewing a Patient's Demographic Information

About Demographic Fields on the Patient EDM

Viewing a Patient's Addresses

About Address Fields on the Patient EDM

Viewing a Patient's Telephone Numbers

About Telephone Fields on the Patient EDM

Viewing a Patient's Aliases

About Alias Fields on the Patient EDM

Viewing a Patient's Auxiliary IDs

About Auxiliary ID Fields on the Patient EDM

Viewing Comments Associated with a Patient

About Comment Fields on the Patient EDM

Comparing Patient Information

Viewing a Patient's Transaction History

About Transaction History Search Fields on the Patient EDM

About Transaction History Results Fields on the Patient EDM

Transaction History Transaction Types on the Patient EDM

Comparing two Patient Profiles

Comparing Records in one Patient Profile

Viewing a Patient Profile's Merge History

Viewing a Merge History Tree on the Patient EDM

Viewing a Patient Profile From a Merge History Tree

Viewing the Patient EDM Audit Log

To View the Audit Log

About Audit Log Search Fields on the Patient EDM

About Audit Log Search Results Fields on the Patient EDM

Audit Log Functions on the Patient EDM

Adding a Patient Profile on the Patient EDM

Step 1: Obtain Information about the Patient

Step 2: Specify a System and Local ID

Step 3: Specify Demographic Information

Step 4: Specify Alias Information

Step 5: Specify Address Information

Step 6: Specify Telephone Information

Step 7: Specify Auxiliary IDs

Step 8: Add Comments to the Patient Profile

Step 9: Save the Patient Profile

Learning About Patient EDM Maintenance Tasks

Matching Probability Weights

Merging Profiles on the Patient EDM

Assumed Matches

Potential Duplicates

Handling Potential Duplicates

Patient EDM Update Tips

Maintaining Patient Information

Modifying Demographic Information in a Patient Profile

Maintaining Address Information in a Patient Profile

Maintaining Telephone Information in a Patient Profile

Maintaining Alias Information in a Patient Profile

Maintaining Auxiliary ID Information in a Patient Profile

Maintaining Comment Information in a Patient Profile

Updating the Single Best Record Directly

Locking an SBR Field on the Patient EDM

Unlocking an SBR Field on the Patient EDM

Maintaining System Records on the Patient EDM

Adding a System Record to a Patient Profile

Deactivating a System Record in a Patient Profile

Reactivating a System Record in a Patient Profile

Changing Patient Profile Status

Deactivating a Patient Profile

Reactivating a Patient Profile

Working with Potential Duplicate Patient Profiles

Finding Potential Duplicate Patient Profiles

About Matching Review Search Fields on the Patient EDM

About Potential Duplicate Results Fields on the Patient EDM

Merging Potential Duplicate Patient Profiles

Resolving Potential Duplicate Patient Profiles

Working with Assumed Matches on the Patient EDM

Finding Assumed Matches on the Patient EDM

About Assumed Match Results Fields on the Patient EDM

Reversing an Assumed Match on the Patient EDM

Combining Patient Information

Merging Patient Profiles

Merging System Records on the Patient EDM

Unmerging Patient Information

Unmerging Patient Profiles

Unmerging System Records on the Patient EDM

Learning About Patient EDM Reports

Patient EDM Production Reports

Patient EDM Activity Reports

Patient EDM Search Result Reports

Configuring Patient EDM Reports

Masked Data and Patient EDM Reports

Running Patient EDM Reports

To Run Reports From the Patient EDM

About Report Search Fields on the Patient EDM

Working With the EDM for Sun Master Index

Java EE Based Components

Working With the Master Index Data Manager

Maintaining Sun Master Indexes

Analyzing and Cleansing Data for Sun Master Index

Loading the Initial Data Set for a Sun Master Index

Patient Profile Components

A patient profile, also known as an enterprise object, is a set of information that describes characteristics of an individual patient in Sun Master Patient Index. Figure 1 illustrates an EUID tree for a patient profile, which shows all components of a profile.

Figure 1 Patient Profile Components
Figure shows the structure of a patient profile, including child objects and system records.

A patient profile contains two types of records:

System Records

System records are different from the SBR in that each system record contains a system and local ID pair and only contains data from a specific system. The information in the system records of a patient profile is used to determine the best value for the SBR in that profile. If a patient profile only contains one system record, the SBR will be identical to that system record. However, if a patient profile contains multiple system records, the SBR might be identical to one system record but will more likely include a combination of information from all system records. Certain actions against a system record will cause the SBR to be changed, such as updating, deactivating, or merging a system record. Each active patient profile must have at least one active system record. If all system records in a profile are deactivated, then the entire profile will also be deactivated.

Single Best Record

The single best record (SBR) for a patient profile is made up of a combination of information from all active system records associated with that patient profile. The SBR represents the information that is determined by Sun Master Patient Index to be the most reliable and current of all system records in a patient profile. The SBR is dynamic and is recalculated each time an update is made to an associated system record, a merge or unmerge affects the patient profile, or a system record in the profile is deactivated or reactivated. You can use the overwrite capability of the Patient EDM to update the SBR directly or you can update a system record and allow the survivor calculator to determine how to update the SBR (for more information, see Survivor Calculator).

If you use the overwrite capability to update a field, that field remains locked and cannot be updated by changes to system records until the field is unlocked. For more information about the overwrite function and locked fields, see Updating the SBR and Updating System Records.

Survivor Calculator

The survivor calculator determines which information from each system record in a patient profile is stored in the SBR for that profile. The calculator uses information defined by the system administrator to calculate the SBR. By default, the survivor calculator uses a weighted strategy for most fields, using the relative reliability assigned to each system in combination with the reliability given to the most recently updated value.

For some fields, such as alias and auxiliary IDs, a union strategy is typically used. This means that all unique alias names and auxiliary IDs from all systems are included in the SBR. For detailed information about the survivor calculator and configuring the survival strategy, see Configuring Sun Master Indexes (Repository) and Understanding Sun Master Index Configuration Options (Repository).