Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Table of Contents
minLevel1
maxLevel6
outlinefalse
typelist
printablefalse

Summary

Requirements

#

Requirement

User Story

Acceptance Criteria

Jira Issue

Notes

1

Display progress breakdown

As a data manager, I want to see a breakdown of data cleaning progress by subject and item group level, because this provides me with a logical breakdown of data still outstanding or under review.

Display progress of data cleaning at both subject and item group level

FHSD-942

Subject view shows things at a ‘birds eye’ view, but doesn’t show what is outstanding.
Item group view breaks down what data is actually ‘outstanding’ and requiring review.

2

Review progress per subject

As a data manager, I want to see the progress of data cleaning per subject, so get an understanding of how far along each subject is with data collection and data review.

Track the percentage of completed data
Track review progress from one-to-many reviewers, including review by a given department.For example, monitors or data managers.

Track percentage of locked data per subject
Track subject lock status, including lock date, when applicable
Track PI signoff status (Y/N) and date of signoff, when applicableDriven by use of ‘PISIGN’ alias on item intended to track PI signature.

FHSD-942

Alias information for the PI Signature item:
Alias Name: PISIGN
Alias Context: does not matter how context is defined

Design

The report will be generated as an XLS file containing two tabs, containing subject level and item level details (respectively).

Filters

The Filters allow to include Randomized Subjects only or all Subjects.

...

It is also possible to select one or more Subjects from the list.

Example Reports

Data Cleaning Progress Report Example:

...

View file
nameData Review Locked Status Report.xlsx

Role Dependencies

Certain areas of this report are dependent on strict Role definitions and make an assumption about how certain Roles are named in customer environments. Certain data may not be produced in these sections if the Role names do not match what is defined in the reporting configuration logic.

...