Patient In The Disc Table/View Does Not Match The Rdcms And Rdcis Tables.
(Doc ID 436952.1)
Last updated on DECEMBER 25, 2019
Applies to:Oracle Clinical - Version 4.5.1 and later
Information in this document applies to any platform.
When using OC 4.5.1, our users began to notice an inconsistency between the patient and
patient_position_id numbers found in the discrepancy_entries table and discrepancy_management view
versus what was in the received_dcms and received_dcis tables.
When we go to menu Data Entry => Browse and try to pull up data for the patient that we see in the
discrepancy_entries and discrepancy_management, there is NO data for the patient; however, if we
go to the menu Conduct => Data Validation => Discrepancy Database and pull up data based on the
discrepancy_entry_id a discrepancy comes up.
### Steps to Reproduce ###
We have not been able to determine the exact steps that may have caused this problem; however, our
best scenario to reproduce the problem is below:
1) Create two patients (i.e. PT001 and PT002).
2) Create a DCM and activate it.
3) Create validation procedure for the DCM created in step 2 and activate it.
4) Enter data for only one of the patients created in step 1 (i.e. PT001)and make sure the data
will kick out a multivariate discrepancy based on the validation procedure you wrote isn step 3.
5) Run batch validation.
6) Verify that a multivariate discrepancy was created for the patient.
7) Go to the menu Data Entry => Key Changes and query up the header for the data entered in step 4
above. Change the patient from PT001 to PT002. Save Change.
Now if you go back and query the discrepancy_entries table and the discrepancy_management view
you will notice that the patient and patient_position_id in does NOT match what is in the
received_dcms and received_dcis table. We have even ran batch validation and the change to the
patient is still not cascading down to the discrepancy.
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