DF_PTschedule

DF_PTschedule — Display subject scheduling information from DF_QCreports

Synopsis

DF_PTschedule {study} [-c #, #-#] [ [-p all] | [-p fup] | [-p qcs] | [-p notdone] | [-p done] ]
[-idfmt #] [-dtfmt fmt]

Description

DF_PTschedule shows the first visit, last completed visit, and next scheduled visit for each subject. It also shows if there are any outstanding problems, i.e. unresolved queries.

This report uses DF_QCreports to produce an internal Query Report listing the status of subjects from the specified sites. The purpose of DF_PTschedule is to provide a simpler mechanism (than DF_QCreports) for obtaining subject status information only. The only additional functionality added by DF_PTschedule that is not offered by DF_QCreports is through the -p done option.

Options

-c #, #-#

Select subjects from specified sites. By default, subjects from all sites, including the error monitor site, appear in the output.

-p all, -p fup, -p qcs, -p notdone, -p done

Select which subjects to include from the following list.

  • -p all: all subjects
  • -p fup: subjects still under follow-up
  • -p qcs: subjects with outstanding queries
  • -p notdone: subjects under follow-up or with unresolved queries
  • -p done: subjects finished follow-up and no unresolved queries

-idfmt #

Leading zero-pad IDs on output report to the specified number of digits. For example, -idfmt 6 prints IDs as 6 digits with leading zeros. The default is no zero padding of IDs.

-dtfmt fmt

Set the output format for dates. Any combination of dd, mm or mmm, yy or yyyy and delimiters (space, commas, etc.) can be used.

Examples

Example 2.36. show visit scheduling info for subjects still under follow-up at sites 10 and 99

-c 10 99 -p fup -dtfmt "mmm dd, yyyy"
DF_PTschedule: Subject Visit Scheduling.          DFstudy 254. Apr 23,2017 22:28

SUBJECT STATUS SUMMARY  (* identifies subjects with outstanding data queries)

SUBJECT                ENTRY VISIT         LAST FOLLOW-UP         NEXT FOLLOW-UP

     10100*    Day 1: JAN 01, 2016    3 Mo.: APR 01, 2016    4 Mo.: MAY 03, 2016
     10101*    Day 1: OCT 01, 2016    3 Mo.: JAN 01, 2017    4 Mo.: JAN 31, 2017
     10102*    Day 1: JAN 01, 2016    3 Mo.: APR 01, 2016    4 Mo.: MAY 03, 2016
     10103*    Day 1: JAN 01, 2015    3 Mo.: unknown         4 Mo.: MAY 03, 2015
     10104*    Day 1: NOV 01, 2015    3 Mo.: JAN 01, 2016    4 Mo.: MAR 03, 2016
     10105*    Day 1: OCT 01, 2016    3 Mo.: DEC 30, 2016    4 Mo.: JAN 31, 2017
     10200*    Day 1: JAN 02, 2016    Day 1: JAN 02, 2016    1 Mo.: FEB 01, 2016
     10300*    Day 1: JAN 02, 2016    Day 1: JAN 02, 2016    1 Mo.: FEB 01, 2016
     10400*    Day 1: JUN 01, 2016    1 Mo.: JUL 02, 2016    2 Mo.: AUG 01, 2016
     10500*    Day 1: JUN 15, 2016    1 Mo.: JUL 15, 2016    2 Mo.: AUG 15, 2016
     10600*    Day 1: OCT 01, 2015    4 Mo.: MAR 01, 2016      End: JAN 31, 2016
     10601*    Day 1: OCT 08, 2016    Day 1: OCT 08, 2016    1 Mo.: NOV 07, 2016
     99002*    Day 1: MAR 06, 2015    Day 1: MAR 06, 2015    1 Mo.: APR 05, 2015

Limitations

The total space allotted for the visit label and date is 23 characters. Allowing a maximum of 6 characters for the label, 2 characters for ": " between the label and the date, and 2 characters for space between visits, leaves a maximum size for date formats of 23-6-2-2 = 13 characters.

See Also

DF_QCreports