Changes between Version 4 and Version 5 of Ticket #723, comment 3


Ignore:
Timestamp:
Jan 14, 2015, 12:00:15 PM (9 years ago)
Author:
olle

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #723, comment 3

    v4 v5  
    55Functional specification for the retraction follow-up step:
    66
    7  1. A case name or personal number should be input:[[BR]]a. If a case name is input, the patient related to that case should be found. As is described in the next section, the "patient" item will technically be a biosource item of type "`Retracted`" or "`RetroNo`", instead of "`Patient`", but for for simplicity, it will be referred to as a patient item in this description.[[BR]]b. When part 1, "Mark extracts for retraction", is finished, the patient type is changed to "`Retracted`" or "`RetroNo`". Part 2, "Retraction follow-up", is not intended to be used until part 1 is finished, so it is natural to include a check that the patient type is correct for retraction.
    8  2. a. A form with input fields for seven dates should be presented for the patient in question (regarding requests forwarded to other projects, it is implied that the projects use samples or data stored using the SCAN-B consent):[[BR]]
     7 1. Biosource items of type "`Retracted`" or "`RetroNo`" should keep track of what parts in the retraction module have been finished. To simplify the discussion, lets assumed that biosource items of type "`Retracted`" or "`RetroNo`" should support a new enumerated string annotation "`RetractStatus`" with options "`ReadyForDestruction`" and "`RetractionCompleted`" (`null` is default; option "`RetractionCompleted`" is intended to be set in part 3 "Destruction").
     8 2. A case name or personal number should be input:[[BR]]a. If a case name is input, the patient related to that case should be found. As is described in the next section, the "patient" item will technically be a biosource item of type "`Retracted`" or "`RetroNo`", instead of "`Patient`", but for for simplicity, it will be referred to as a patient item in this description.[[BR]]b. When part 1, "Mark extracts for retraction", is finished, the patient type is changed to "`Retracted`" or "`RetroNo`". Part 2, "Retraction follow-up", is not intended to be used until part 1 is finished, so it is natural to include a check that the patient type is correct for retraction.
     9 3. a. A form with input fields for seven dates should be presented for the patient in question (regarding requests forwarded to other projects, it is implied that the projects use samples or data stored using the SCAN-B consent):[[BR]]
    910|| '''Header''' || '''Date sent prompt''' || '''Date received prompt''' || '''Comment''' ||
    10 || Laboratory || Date sent || Date received || Dates when retraction request sent to and received from laboratory (YYYYMMDD) ||
    11 || Blood samples || Date sent || Date received || Dates when retraction request sent and received for blood samples (YYYYMMDD) ||
    12 || Frozen samples || Date sent || Date received || Dates when retraction request sent and received for frozen samples (YYYYMMDD) ||
     11|| Laboratory || Date sent || Date received || Dates when retraction request sent to and response received from laboratory (YYYYMMDD) ||
     12|| Blood samples || Date sent || Date received || Dates when retraction request sent and response received for blood samples (YYYYMMDD) ||
     13|| Frozen samples || Date sent || Date received || Dates when retraction request sent and response received for frozen samples (YYYYMMDD) ||
    1314|| Forwarded || Date sent || || Date when retraction request forwarded to other projects (YYYYMMDD) ||
    14 [[BR]]b. The date fields should be loaded with previously stored dates for the patient, if any.[[BR]]c. A "`Cancel`" and a "`Register`" button should appear below the form. When the "`Register`" button is clicked, the data in the date fields should be stored in annotations for the patient.
     15[[BR]]b. The date fields should be loaded with previously stored dates for the patient, if any.[[BR]]c. The date input fields should be coupled to a number of sanity checks: apart from normal checks for date syntax, future dates should not be allowed, and for items with both a sent and received date, the latter should not be allowed to be earlier than the sent date.[[BR]]d. A "`Cancel`" and a "`Register`" button should appear below the form. When the "`Register`" button is clicked, the data in the date fields should be stored in annotations for the patient.[[BR]]e. When a registration with all seven dates values filled in is made, "`RetractStatus`" for the patient item is set to "`ReadyForDestruction`", while if any date value is missing, it is set to `null`.