Skip Navigation Links | |
Exit Print View | |
Working With the EDM for Oracle Java CAPS Master Patient Index Java CAPS Documentation |
Working With the EDM for Oracle Java CAPS Master Patient Index
Learning about Patient Profiles
System Record and SBR Components for Oracle Java CAPS Master Patient Index
Identification Numbers for each Patient
Security Permissions for the Patient EDM
Navigation Tips for the Patient EDM
Navigating the Patient EDM Functions
Logging Out of the Patient EDM
Learning About Patient Queries
About the Patient EDM Search Function
The Advanced Person Lookup (Alpha) Page
The Advanced Person Lookup (Phonetic) Page
Types of Searches on the Patient EDM
Advanced Person Lookup (Alpha)
Advanced Person Lookup (Phonetic)
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
To Perform a Social Security Number Lookup
Performing a Local ID Lookup on the Patient EDM
Performing an Advanced Alphanumeric Lookup on the Patient EDM
To Perform an Advanced Alphanumeric Lookup
About Alphanumeric Search Fields on the Patient EDM
Performing an Advanced Phonetic Lookup on the Patient EDM
To Perform an Advanced Phonetic Lookup
About Phonetic Search Fields on the Patient EDM
Performing an EUID Comparison Lookup on the Patient EDM
To Perform an EUID Comparison Lookup
Working with Search Results on the Patient EDM
Viewing the Results of a Search
Selecting a Profile from the Results List
Creating and Printing a Search Result Report
Patient Profile Transaction Histories
Patient Profile Merge Histories
Viewing a Patient's Demographic Information
To View Demographic Information
About Demographic Fields on the Patient EDM
About Address Fields on the Patient EDM
Viewing a Patient's Telephone Numbers
About Telephone Fields on the Patient EDM
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
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
To Compare twoPatient Profiles
Comparing Records in one Patient Profile
To Compare Records in one Patient Profile
Viewing a Patient Profile's Merge History
Viewing a Merge History Tree on the Patient EDM
To View a Patient's Merge History
Viewing a Patient Profile From a Merge History Tree
To View a Patient Profile From a Merge History Tree
Viewing the Patient EDM 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
To Specify a System and Local ID
Step 3: Specify Demographic Information
To Specify Demographic Information
Step 4: Specify Alias Information
Step 5: Specify Address Information
To Specify Address Information
Step 6: Specify Telephone Information
To Specify Telephone Information
Step 8: Add Comments to the Patient Profile
Step 9: Save the Patient Profile
Learning About Patient EDM Maintenance Tasks
Merging Profiles on the Patient EDM
Surviving and Non-surviving Profiles
Updating the SBR and Updating System Records
Maintaining Patient Information
Modifying Demographic Information in a Patient Profile
To Modify Demographic Information
Maintaining Address Information in a Patient Profile
Adding Addresses to a Patient Profile
Deleting Addresses from a Patient Profile
Maintaining Telephone Information in a Patient Profile
Adding Telephone Numbers to a Patient Profile
Modifying Telephone Information
Deleting Telephone Numbers from a Patient Profile
Maintaining Alias Information in a Patient Profile
Adding an Alias to a Patient Profile
Modifying a Patient's Alias Information
Deleting an Alias from a Patient Profile
Maintaining Auxiliary ID Information in a Patient Profile
Adding an Auxiliary ID to a Patient Profile
Modifying Auxiliary ID Information
Deleting an Auxiliary ID from a Patient Profile
Maintaining Comment Information in a Patient Profile
Adding a Comment to a Patient Profile
Modifying a Comment in a Patient Profile
Deleting a Comment from 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
To Add 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
To Deactivate a Patient Profile
Reactivating a Patient Profile
To Reactivate 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
To Resolve two Potential Duplicate 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
Merging System Records on the Patient EDM
To Unmerge two Merged Patient Profiles
Unmerging System Records on the Patient EDM
To Unmerge two Merged System Records
Learning About Patient EDM Reports
Patient EDM Production Reports
Patient EDM Search Result Reports
Configuring Patient EDM Reports
Masked Data and Patient EDM Reports
Oracle Java CAPS Master Patient Index is an enterprise-wide master index application built using the Oracle Java CAPS Master Index platform and provides all of the functionality of a Java CAPS master index application. Oracle Java CAPS Master Patient Index creates a single, consistent view of all patient data by providing an automatic, common identification process regardless of the location or system from which the data originates. Patient profiles from various locations are cross-referenced using an enterprise-wide unique identifier (EUID) assigned to each profile by Oracle Java CAPS Master Patient Index. By creating EUIDs, Oracle Java CAPS Master Patient Index can identify many types of participants, such as patients, customers, employees, contacts, and so on.
The identification and demographic information for all patients is centralized in one shared index. Oracle Java CAPS Master Patient Index is designed specifically to support scattered business locations and disparate information systems across an enterprise, as well as various applications from multiple vendors. Oracle Java CAPS Master Patient Index makes it easy to find information that was previously scattered among multiple systems.
The following topics describe the features and functions of Oracle Java CAPS Master Patient Index.
The components of Oracle Java CAPS Master Patient Index are highly configurable, allowing the application to be customized for your specific data processing needs. Primary features ofOracle Java CAPS Master Patient Index include the following:
Centralized Information – Oracle Java CAPS Master Patient Index maintains a centralized database, enabling the integration of data records throughout the enterprise while allowing local systems to continue operating independently. The index stores copies of local system records and the single best record (SBR), which represents the most accurate and complete data for each patient. This database is the central location of all patient information and identifiers, and it is accessible throughout the enterprise. Records from various systems are cross-referenced using the EUID assigned by Oracle Java CAPS Master Patient Index to each patient profile.
Configurability – Before deploying Oracle Java CAPS Master Patient Index, you can customize the components and processing capabilities of the system. The configurable components include:
The types of objects to index
The types of data stored in Oracle Java CAPS Master Patient Index
The standardization and match engines to use
Matching, standardization, and phonetic conversion rules
Survivorship and weighting rules for determining the SBR
The types of queries available
How queries are blocked, or grouped, for match processing
Patient EDM appearance
Searches available to the Patient EDM
Local ID validation rules
Cross-referencing – Oracle Java CAPS Master Patient Index is a global cross-referencing application, matching profiles across disparate source systems and simplifying the process of sharing data between systems. Oracle Java CAPS Master Patient Index uses the local identifiers assigned by your existing systems as a reference, allowing you to maintain your current systems and practices.
Data Cleansing – Oracle Java CAPS Master Patient Index uses configurable matching algorithm logic to uniquely identify patient profiles and to identify duplicate and potential duplicate profiles. Oracle Java CAPS Master Patient Index provides the ability to easily merge or resolve duplicates, and can be configured to automatically match profiles that are found to be duplicates of one another.
Data Updates – Oracle Java CAPS Master Patient Index provides the ability to add, update, deactivate, merge, and delete data in the database tables through messages received from external systems or the Patient EDM. Messages received from external systems and the Patient EDM are checked for potential duplicates during processing.
Updates to External Systems – The Oracle Java CAPS Enterprise Service Bus provides the master index application with the ability to publish updated information to external systems, provided the external systems can accept incoming messages. This is handled through a JMS Topic to which the master index application publishes XML messages that contain the updates.
Identification – Oracle Java CAPS Master Patient Index employs configurable probabilistic matching technology. This technology uses a matching algorithm to formulate an effective statistical measure of how closely profiles match. Using a state-of-the-art algorithm in real-time mode and establishing a common method of locating patientprofiles, Oracle Java CAPS Master Patient Index consistently and precisely identifies objects within an enterprise.
Integration – Relying on the Oracle Java CAPS Enterprise Service Bus, Oracle Java CAPS Master Patient Index provides the power and flexibility to identify, route, and transform data to and from any system or application throughout your business enterprise. It can accept incoming transactions and distribute updates to any external system, providing seamless integration with the systems in your enterprise.
Matching Algorithm – Oracle Java CAPS Master Patient Index is designed to use the Oracle Java CAPS Match Engine or a custom matching algorithm to provide a matching probability weight between patient profiles. The Oracle Java CAPS Match Engine provides the flexibility to create user-defined matching thresholds, which control how potential duplicates and automatic merges are determined.
Unique Identifier – Oracle Java CAPS Master Patient Index assigns an enterprise-wide unique identifier (EUID) to each object added to the database. The index uses the EUID to cross-reference the local IDs assigned to each patient by the various computer systems throughout the enterprise.
While Oracle Java CAPS Master Patient Index cleanses data automatically as it is entered through external system messages or the Patient EDM, there are instances where it cannot be determined automatically whether two patient profiles truly match one another. In these cases, manual review through the Patient EDM is needed to verify the status of the two profiles and then to possibly join two potential duplicate profiles or separate two profiles that were automatically joined. The Patient EDM provides additional functions to help you maintain the data you store. Using the Patient EDM, you can perform the following activities.
View a Patient’s History – The system provides a complete transaction history of each patient profile by recording all changes to each patient’s data. This allows you to view before and after images of a profile for each change made. The table also records the user ID of the person who made the changes. This history is maintained for both the local system records and the SBR.
Search for Patient Profiles – Using the Patient EDM, you can search for specific patients or sets of patients. The Patient EDM allows you to perform different types of searches using different combinations of data elements, and returns a list of potential matches to your search criteria. Oracle Java CAPS Master Patient Index also parses address components, so you can search for a patient profile by their street address. For certain searches, the results are assigned a matching weight that indicates the probability of a match.
Maintain Patient Data – The Patient EDM supports all the necessary features for maintaining patient profiles. It allows you to add new profiles; view, update, deactivate, or reactivate existing profiles; and compare profiles for similarities and differences. You can also view each local system record associated with an SBR.
Compare Patient Data – The Patient EDM allows you to compare two patient profiles in a side-by-side comparison so you can evaluate their differences or similarities. You can also compare different objects within one patient profile in the same comparison view. For example, you can compare the profile’s SBR with a record from System A; or you can compare a profile’s record from System A with its record from System B.
View and Resolve Potential Duplicates – Using algorithm matching logic,Oracle Java CAPS Master Patient Index has the ability to identify potential duplicate profiles and the Patient EDM provides the ability to correct the duplicate profiles. Profiles that are potential duplicates can be viewed online in a side-by-side comparison. Potential duplication is resolved by either merging the profiles in question or removing their potential duplicate flags.
Merge and Unmerge Profiles – You can compare potential duplicate profiles and then merge the profiles if you find them to be actual duplicates of one another. Using the merge feature, you can determine which profile to retain as the active profile. The Patient EDM also allows you to merge system records between patient profiles and to specify which information from each system record to preserve in the resulting profile. If two patient profiles or system records are merged in error, you can unmerge them, returning the information to the original records. You can also view a history of merges for a profile by viewing its merge tree.
Add and View Comments – You can add free-text comments to a patient profile or system record to provide additional information about the patient that might not be included in the standard fields.
Audit Log – The system administrator can specify that a log be maintained of each instance that patient data is accessed from the Patient EDM. This log provides information such as the user ID of the user who accessed the data, the type of action that was performed against the data, and the date and time of access. From the audit log, you can also view a transaction history for each transaction that caused an audit log entry.
Security – Security is provided through the application server and includes basic access to the database through user login IDs and passwords, as well as access to specific functions and actions of Oracle Java CAPS Master Patient Index. Access can be restricted by functions, actions within functions, data element, and user ID.