DF_ATcrfs — Track keys associated with a CRF page over time
DF_ATcrfs
{study}
[-all]
{-f CRFpageID}
The study number and key fields (ID, visit, plate) associated with a CRF page may change over time, because the key fields were entered incorrectly and later fixed, or because the CRF page was moved to a different study. DF_ATcrfs tracks these changes by searching the audit trail of the current study, or optionally all studies registered in DFdiscover, for all journal records related to a specified CRF page. If the option to search all studies is enabled, all known studies are searched, whether the study is currently active or not.
For each journal record identified, DF_ATcrfs displays:
In addition to showing the above information from the journal files, DF_ATcrfs also checks the router and prints a message at the end of the report indicating that the CRF page is currently located in the router, if that is the case. A CRF page will be placed in the router on arrival if the barcode could not be read. It will also be moved to the router from a study database if Change Keys (in DFexplore) is used to change the study number. When this happens the data record and any metadata records (queries and/or reasons) are deleted from the original study database, and the CRF image starts over when it is routed to the new study database.
-all | Search all DFdiscover study databases, not just the current one. All known studies are searched, whether the study is currently active or not. This generates exhaustive output but at the expense of report speed. |
-f CRFpageID | The identifier for the CRF page to be tracked
(required).
The CRFpageID must be specified in the standard
YYWW/SSSSPPP format.
|
Example 2.1. Report the audit trail for CRF page 1525/0016001
DF_ATcrfs: Track keys associated with a CRF page over time. Jul 28,2015 13:04
Keys history for CRF page 1525/0016001
yyyy/mm/dd hh:mm:ss DBN study id visit plate level status user
2015/06/21 14:25:59 253 253 1019 0 1 0 new datafax
2015/06/21 14:49:51 253 253 1019 0 1 1 final user1
2015/07/28 13:02:17 253 253 1019 0 1 2 delete user2
2015/07/28 13:03:28 252 252 1019 0 1 0 new datafax
2015/07/28 13:04:16 252 252 1019 0 1 1 final user2
The output shows that CRF page 1525/0016001 was originally entered into study 253
on June 21, 2015. Then on July 28, 2015 it was moved from study 253 to study 252.
The record with status delete was created when Change Keys
was used in DFexplore to move the CRF page to the router.
The subsequent record with status new was created when
the CRF page was identified in DFexplore as belonging to study 252.
Note that new records,
arriving at level 0 and attributed to user datafax, indicate that the CRF page
has been placed in the new record queue to await validation by data management
staff.
DF_ATcrfs is really an administrative report and for maximum benefit should
be restricted to user datafax.
DF_ATcrfs determines the history of the CRF by reading the journal records from the requested studies. If any journal record cannot be read due to permission problems, it will be quietly skipped. This may result in incomplete information concerning the history of the CRF.
DF_ATcrfs will report all known keys history information, independent of any access permission restrictions placed on the current user.
[1] In almost all cases, this study number value will be identical to the study number value in the previous column. The two values will differ only when a database is copied, outside of DFdiscover, from one study number to another. In this case, the original study will report identical study number values in the two columns, while the copied study will have a database study number (the new study number) which differs from the study number found in the journal record (the old study number).