My Oracle Support Banner

Track back discrepancy after key change (Doc ID 1451231.1)

Last updated on DECEMBER 04, 2019

Applies to:

Oracle Clinical - Version 4.5.1 to 4.6.5 [Release 4.5.1 to 4.6.5]
Information in this document applies to any platform.


During Key change in the RDCI, OC closes all open discrepancies *. During the next batch validation the discrepancy are recreated with status UNREVIEWED with a new discrepancy_entry_id. How can I link both IDs (how can I identify the previous discrepancy ID starting from the new one?).

* Note: The is the the case with a Multivariate discrepancy as per info in 'Overview of 'System' Discrepancy Resolution Codes (used in the 'DISCREPANCY_ENTRIES.DISCREPANCY_RESOLU_TYPE_CODE' column). (Doc ID 1600981.1)' but *not the case* for a UNIVARIATE or MANUAL discrepancy. Here the same discrepancy (including ID) is preserved when doing a key change (e.g. patient number change). Existing discrepancies now reflect the new patient number.



To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.