Académique Documents
Professionnel Documents
Culture Documents
Document control
Superseded documents
Document File Version Issue Date with- Replaced by Reason
Name Name Number Date drawn
Version history
Version Date Author Comments Sections Circulated Purpose
affected to:
0-02 All
Sorting Functionality
Design Specification
Section Change Reason for change
Version: 1.1
Distribution control
Author:
Shelley Tworoger
Owner and approver for
distribution: Shelley Tworoger
Signature: Date:
Distribution List
Company Entity Recipient Name Action
Shelley Tworoger
Mark Magid
Rakesh Kukatla
Helena Judge-Ellis
Jeanne Sparrow
Eric Rimm
Sue Hankinson
Contents
1. Introduction 4
1.1 Purpose of document................................................................................4
1.2 Background................................................................................................4
1.3 Scope of the specification.........................................................................4
1.4 Input 4
1.5 Output 4
1.6 Glossary of Terms and Definitions.............................................................8
1.7 Contacts10
1.7.1 List of comments of final sign off..........................................................10
2. Functional Overview................................................................................11
2.1 Business Objectives
(See separate, expanded flow chart for sorting)............................................11
2.2 .a Functional Diagram..............................................................................11
2.2.b Functional Diagram in more detail......................................................12
“Original Sort List”
instructions to go from pulled order to aliquot order.......................................12
“Sending Sort List”........................................................................................12
2.3 Design Mock-up.......................................................................................13
2.4 Requirements..........................................................................................13
2.4.1 Primary.................................................................................................13
2.5 Non-Functional Requiremets...................................................................13
2.6 Outstanding Issues..................................................................................14
1.Introduction
1.1Purpose of document
The Sorting Functionality will continue the process of pulling samples from the freezer
and ultimately sending to a laboratory. This functionality will build on the information
generated in the Pull List Functionality, specifically the location of pulled vials into
Freezer Pull Boxes. The purpose of this document is to outline the specifications for
the Sorting functionality in HealthTrack to create Sort Lists for the NHS, NHS2, PHS,
and HPFS cohorts.
1.2Background
Sort Lists are instructions for placing participant vials from a Freezer Pull Box to an
Original Sort Box or Final Sending Box. This is a critical step before aliquoting large
original vials into smaller subvial aliquots and for sorting subvials into the Final
Sending Boxes. It is important to sort these vials such that cases and their matched
controls can be aliquoted at the same time, when possible, and are next to each other
in the Final Sending Box. The purpose of this project will be to create a Sort List
application as part of HealthTrack that will allow the research assistant to sort from
Freezer Pull Boxes to Original Sort Boxes and Final Sending Boxes and create labels
for the new boxes.
1.4Input
Sort List functionality input data comprises of:
• A Pull List ID number in which all samples have been pulled and the pull list is
updated to reflect any changes that may have occurred during pulling (i.e. the
pull list is finalized);
• User specified parameters such as Original Sort / Aliquot / Sending Box type
and size, Permanent Storage Box type and size, Aliquot preferences such as
Vial type, Volume and Number of Aliquots.
1.5Output
Primary output – Aliquot Sort List
A list of original ID’s (separately for original vial sizes), their location in a Freezer Pull
Box of a specific Pull List, and their new expected location in the Original Sort Box.
Information should be stored in the database to notate the status of the location and a
history/audit table are highly suggested. The format is described below:
o A primary header denoting Original vial type, the type of report (Aliquot Sort
List), and the Pull List ID
o A secondary header that notes user name, date, pull list id, number of sort
boxes per vial type, sample type, collection, endpoint, lab code(s), lab name(s),
follow-up cycles.
o A table containing the following fields: Participant ID, Current location of vial in
Freezer Pull box, new location in Original Sort Box,
o The sorting of the samples into the Original Sort Box should be as follows:
Case-control order (sort on the variable MATCHID from sending list),
when possible i.e. when the case and control are both the same vial
type.
Case-control samples should be randomly ordered within a set
If the matched case (or matched control) for any ID is of a different vial
type, then sort the single ID into the Aliquot Sort Box.
Generate labels for the Original Sort boxes and should have the format below:
ORIGINAL SORT BOX
Pull list ID: < ID >
Box: < # > of <total #>
Cohort: < name >
Collection: < name >
Endpoint/project: < name >
Volume: < volume >
Labcode (s): < number >
Lab Name(s) <name>
2. Primary output – Aliquot Ship Sort List/ Aliquot Store Sort List
A list of original ID’s (separately for original vial sizes), their location in a Original Sort
Box of a specific Pull List, and their derivative ID's expected location in the Aliquot
Ship Box or Aliquot Store Box. Information should be stored on the database to
notate the status of the location and a history/audit table are highly suggested. The
o The sorting of the samples into the Aliquot Ship Box and Aliquot Store Box are
the same as the original vial sort box with sorting as further identified in the
Aliquot Specifications.
o The formatting of the Aliquot Ship Sort List and Aliquot Store list should be as
follows:
First column is Participant ID in the intended order (caco order) the in
Aliquot Ship Box or Aliquot Store box.
Second column in the current location in the Original Sort Box
Third column is expected location in the Aliquot Ship Box or Aliquot
Store Box (see Aliquot Specs)
Generate labels for the Ship-Aliquot Sort Box and Stor-Aliquot Sort Box should
have the format below:
ALIQUOT SHIP BOX
Pull list ID: < ID >
Box: < # > of <total #>
Cohort: < name >
Collection: < name >
Endpoint/project: < name >
Labcode (s): < number >
Lab Name(s) <name>
Information should be stored in the database to notate the status of the location and a
history/audit table are highly suggested. The format is described below:
o A primary header denoting current subvial location (Aliquot Sort Box or Freezer
Pull Box), the type of report (Sending Sort List), and the Pull List ID
o A secondary header that notes user name, date, pull list id, number of Final
Sending Boxes, sample type, collection, endpoint, lab code, follow-up cycle,
and volume. NOTE ONLY ONE LABCODE PER FINAL SENDING SORT LIST.
o A table containing the following fields: Participant ID, Current location of vial in
Aliquot Box or Freezer Pull Box, and new expected location in Final Sending
Box
o The sorting of the samples INTO THE FINAL SENDING BOX should be as
follows:
Case-control order (sort on the variable MATCHID from sending list)
Case-control samples should be randomly ordered within a set (Note:
this can be the same order as in the Original Sort Box and Aliquot Sort
Box)
Case-control sets should be randomly ordered
Generate labels for the Final Sending boxes and should have the format below:
FINAL SENDING BOX
Labcode (s): < number >
Box: < # > of <total #>
Cohort: < name >
Collection: < name >
Endpoint/project: < name >
Volume: < volume >
Term Definition
Assay Any type of measurement done on a biological sample
A oracle view that combines fields from a normalized structure of
Translation Table many fields to create one long but shallow table of permutations that
can be used in the UI for user’s ease
Vial A tube filled with biological specimen to be used in an assay request
or as part of a pull list.
General term for the functionality that generates the all the vial lists
Pull List including freezer locations, used to pull biospecimens from freezers
for a set of labcodes.
STAGES OF PULL LIST
Entering the initial data for a pull list, choosing labcodes, setting
Initialization parameters. Includes making decisions about appropriate parameter
settings and changing those parameters to get the best list. Vials are
temporarily reserved until the parameters are changed or approved.
Approved and finalized the pull list, all final parameter settings
selected. Vials are reserved in the database. Pull list has been
Active (Activate) generated and blood lab personnel are actively pulling samples out
of the freezer. Includes updating the freezer file when an incorrect
tube is found, getting new locations of alternate vials, and noting
what new subvials have been created.
Completed and After all vials have been pulled for a particular pull list, updates are
Updated made to the freezer file, including marking of original vials (and
subvials) as removed. Also includes final update to the sub-sending
list that notes which vials were sent for which assay requests.
TYPES OF LISTS IN PULL LIST FUNCTIONALITY
Original vial list List of original vials, separated by vial type (i.e. vial size), with
locations in the freezer and other information (see appendix) to be
used for pulling vials for a Pull List. Generated by the pull list
functionality.
Subvial list List of subvials, separated by assay request, with locations in the
freezer and other information (see appendix) to be used for pulling
vials for a Pull List. Generated by the pull list functionality.
Index number A sequential set of numbers, beginning at 1, assigned to each vial in
a pull list overall all original and sub-vial lists. In other words, no
number is repeated and this acts as a unique identifier within pull
list.
Unique Vial ID ID number assigned by oracle for every vial handled in a pull list or
other project
Participant ID The ID number assigned to a participant when he or she entered the
study
Pull list ID ID number assigned by oracle for each Pull List generated for a set
of assay requests.
Sub-sending list A list of all potential IDs/vials in an assay request. Notes what vial
was sent for that individual, whether a vial was sent for that
individual, and if not sent then why.
Original Sort List A set of instructions, with list of original vials (separated by vial
type/size), their locations in the Freezer Pull Box and their new
expected locations in the Original Sort Box to prepare for aliquoting
Author: Shelly Tworoger Page 9 of 15 Date: 24/12/2008
/var/www/apps/scribd/scribd/tmp/scratch8/11632880.doc
Document Title : [11632880.doc]
1.7Contacts
Name Job Title/ Position/ Signoff Telephone E-mail
Role
Shelley Project Lead 5-2087 nhsst@channing.ha
Tworoger rvard.edu
Mark Magid Project 5-0074 mgmagi@hotmail.c
Development om
Rakesh Project 5-2575 rkukatla@hsph.harv
Kukalta Development ard.edu
Helena Lab Manager 617-732-5781 nhhje@channing.ha
Judge Ellis rvard.edu
End User
Jeanne Data Manager 5-4220 nhjms@channing.h
Sparrow arvard.edu
2.Functional Overview
2.1Business Objectives
(See separate, expanded flow chart for sorting)
* **
Actual aliquots recorded Add QCS w/ labels that have fake ID’s
in healthtrack Put subvials into
sending box
QC vials added to
Storing Final Sending Boxes
2.3Design Mock-up
2.4Requirements
2.4.1Primary
Below are the fields that should be included on the Sort List Request user-interface:
Pull List ID - single selection pull down list based on previous inputs
The following fields will be shown: Cohort, End point, Specimen Type,
and other criteria selected in the pull list.
Original Sort Box type- single selection simple table (with columns Box Type Name, Box ID
Prefix, Box Type Description, Width, Height) is used to specify type of
the temporary boxes where vials will be placed for aliquoting. Only box
types with the attribute “Can be a Sort box” = “Yes” are retrieved from
DB and displayed in the table. NOTE: This box type applies to the
following subsequent boxes: Aliquot sort box, aliquot store box, and final
sending box.
Aliquot Preferences - multiple selection simple table (with columns Vial Type, Volume,
Number) is used to specify the number of aliquots (of a specific volume)
that need to be made for each vial type.
Permanent Storage Box type - single selection simple table (with columns Box Type Name,
Box ID Prefix, Box Type Description, Width, Height) is used to specify
type of the temporary boxes where vials will be placed for final sending
to the laboratory. Only box types with the attribute “Can be a Permanent
Storage box” = “Yes” are retrieved from DB and displayed in the table.
2.5Non-Functional Requiremets
Research Assistants and Lab Technicians are not typically technically advanced. The
user interface of this and any part of Htrack needs to accommodate for their skill set
and ensure usability by making the product as easy to use for non-technical people
as possible.
2.6Outstanding Issues
None
Appendix A
Breast Cancer 90-98 Assay Requests 1422, 1423, 1424 Rifai, Hollis, Shu