Remediation Request Handler (In Progress)
|
Topics: |
Advanced Remediation allows the data steward to evaluate the results of the Cleansing and Matching rules for accuracy. There are times where the data steward needs to override data submitted from the Source System, or override the result of the Match to more accurately portray the single version of the truth.
The following outlines some of the supported functionality.
Manual Cleansing Overrides
- Allows a data steward to override null or incorrect values from the Source System to facilitate better accuracy in Cleanse, Match, and Merge processes.
- Must have the ability to Preview the results and Persist so that the Overrides can be applied to each subsequent update of the Subject OID.
Manual Matching Overrides
- Allows a data steward to resolve False Negative and False Positive matches that may occur in the Matching engine.
- Ability to manage
a whitelist and blacklist of other instance records for any given instance
record.
- Blacklist. Regardless of what the match rules indicate, these records are not the same as me.
- Whitelist. Regardless of what the match rules indicate, these records are the same as me.
Remediation Request Handler Overview
The Omni-Patient Server is required to process and persist the Manual Cleansing and Manual Matching Overrides submitted by the data steward during Advanced Remediation.
In addition, it must support the ability to execute the Prepare Subject subprocess, and communicate the result back to Advanced Remediation for the data steward to preview the results of a set of Manual Cleansing Overrides prior to submitting them.
The Remediation Request Handler subprocess transforms the request into the appropriate OID, and either routes to the Omni-Patient OID Handler, or to the Manual Cleanse Validation subprocess.
Notes:
- Manual Cleanse Validation is implemented as web service in order to provide synchronous response to Advanced Remediation. The Omni-Patient OID Handler processes the Manual Match Submit.
- The Omni-Patient OID Handler processes the Manual Match Submit and Manual Cleanse Submit asynchronously on an internal queue.
The following diagram illustrates a high level process flow that is followed by the Remediation Request Handler.
Manual Cleanse Validation (In Progress)
As stated previously, the Omni-Patient Server must support the ability to execute the Prepare Subject subprocess, and communicate the result back to Advanced Remediation for the data steward to preview the results of a set of Manual Cleansing Overrides prior to submitting them.
For a given Subject OID, the Manual Cleansing Overrides are applied to the document during OID Enhancement. Code Standardization is executed, and the current Cleansing rules are applied.
Any issues that result are communicated back on the web service response as a Cleansing ticket.
The following diagram illustrates a high level process flow that is followed by Manual Cleanse Validation.
