Orphaned Discrepancy remains for a Derived Question after the Derivation Procedure is either 'Retired' or made 'Provisional'.
(Doc ID 760571.1)
Last updated on DECEMBER 20, 2019
Applies to:Oracle Clinical Remote Data Capture Option - Version 4.5.3 and later
Oracle Thesaurus Management System - Version 4.5.1 and later
Oracle Clinical - Version 4.5.1 and later
Information in this document applies to any platform.
TMS / MANUAL discrepancies associated with a derived question remain when a derivation procedure is either made PROVISIONAL or RETIRED i.e.
- Derivation procedure is set to Provisional => derived responses will be *HARD* deleted / orphaned current discrepancy remains
- Derivation procedure is set to Retired => derived responses will be *SOFT* deleted / current discrepancy remains
In the case of TMS then the below is observed :
- When there is an Oracle Clinical discrepancy created by TMS on a derived response, and the derivation procedure that generated the response is made PROVISIONAL, the derived response is hard-deleted as expected. The associated Oracle Clinical discrepancy and TMS omission should also be hard-deleted, but instead the discrepancy remains current with status 'TMS IN PROGRESS' and the associated TMS omission remains in the system.
- When there is an Oracle Clinical discrepancy created by TMS on a derived response, and the derivation procedure that generated the response is RETIRED, the derived response is soft-deleted as expected. However, any associated OC discrepancies remain current with status 'TMS IN PROGRESS' when they should be obsoleted. In addition, the corresponding TMS omission remains in the TMS database, when it should have been hard-deleted.
When this issue occurs then the following errors can also appear in the Remote Data Capture application => Data Entry Window :
Error The data entry window has encountered an unexpected error and will shut down. If the problem recurs, please report the following information for diagnostic purposes: Log code xxxxxx, internal error
Invalid JSON received
and the log.xml / dump file contains errors like :
Exception Details:SQL Exception. Unable to proceed further. oracle.pharma.rdc.de.exception.FailedOperationException: SQL Exception. Unable to proceed further. at oracle.pharma.rdc.de.service.dcs.RDCI.populateDiscrepancies(RDCI.java:1333) at oracle.pharma.rdc.de.service.dcs.DciFormData.populateDiscrepancyDetails(DciFormData.java:9119) at oracle.pharma.rdc.de.service.dcs.DataCaptureService.performAction(DataCaptureService.java:389) at oracle.pharma.rdc.de.service.dcs.DataCaptureService.processCommand(DataCaptureService.java:252) at oracle.pharma.rdc.de.servlet.RuntimeController.doPost(RuntimeController.java:608) Caused by: java.sql.SQLException: ORA-20001: Could not find data for discrep id xxxxxx ORA-06512: at "RXC.OCL_DISC", line 576 ORA-06512: at "RXC.OCL_DISC", line 667 at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:137) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:315) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:281) at oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java:638)
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