How to differentiate non-accessible received pages depending on their previous status?
(Doc ID 1375824.1)
Last updated on NOVEMBER 17, 2011
Applies to:Oracle Clinical - Version: 4.5.1
Information in this document applies to any platform.
- from brand new pages
- from previously accessible pages (PASS 1/2 COMPLETE) which are marked as blank by a user
Given a simple accessible CRF in Pass 1 Complete (if the study does not require second pass) or Pass 2 Complete(if the study requires second pass), a site user blanks out a page, consequently changing its status in RECEIVED and making it non-accessible
After reviewing, the data manager decides that the page should be deleted so he puts a header discrepancy on the page, asking the site user to delete that particular page. But later this DM user will not be able to track the newly created discrepancy in Discrepancy Database with "Accessible Data Only" ticked, he will need to un-check this option but this will generate further complications since all non-accessible data will be returned.
The DM or CRA puts on a discrepancy to ask the site to enter the data because it's in the mandatory source. Again, the discrepancy is associated with a blank page to make it easy for the site, but it's not listed with "accessible" data in OC.
Given the above, a page coming from a blanked accessible page needs to be treated differently from a brand new page so that the two scenarios will return also the blanked pages, allowing a more efficient communication.
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