New TMS IN PROGRESS Disc On Rdc Onsite Verified And Approved Pages (Doc ID 1246934.1)

Last updated on DECEMBER 15, 2010

Applies to:

Oracle Clinical - Version: 4.5.3 and later   [Release: 4.5 and later ]
Information in this document applies to any platform.

Goal

User sees that 'Approved' and 'Verified' pages are remaining so even if a new TMS IN PROGRESS discrepancy is created after running Batch Validation Session (BVS). Is this expected behavior?

Further detail discussion:

You understand that any changes to an RDC page would trigger the re-verification and re-approval status. This does not appear to be true for new TMS IN PROGRESS discrepancies generated by the following steps.

Steps taken:

1. Upgrade TMS Base dictionary attached to the study's question set

2. Run Batch Validation Session (BVS)

3. Terms that used to be auto coded are no longer auto coded. This is expected because the MSSO removed several thousand terms with version 13.0. A TMS IN PROGRESS discrepancy was created for the page.

4. Pages that were 'Approved' and 'Verified' are still 'Approved' and 'Verified'.

Is it expected that the pages still remain VERIFIED and APPROVED even though a new discrepancy (TMS IN PROGRESS) was created for the pages?


Solution

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms