Changes between Version 25 and Version 26 of LEGACY - CiviCRM LCBRU Use Case


Ignore:
Timestamp:
06/06/13 10:27:30 (11 years ago)
Author:
Nick Holden
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • LEGACY - CiviCRM LCBRU Use Case

    v25 v26  
    138138Following a meeting with Chris and Emma, we are implementing the following: a custom group ('GENVASC withdrawal status') with one field ('GENVASC withdrawal status', alphanumeric, radio button options), with three options: not withdrawn ('0'), withdrawal but keep data and samples ('A') or withdrawal, destroy samples and data ('B'). There is an SOP for processing withdrawal requests.
    139139
     140=== Completion of study ===
     141
     142As with 'withdraw' the best way to capture the fact that a participant has reached the end of a study protocol is to change their status, and this records an activity of type 'change enrolment status'. So we should use the 'Change Enrolment Status' function (by editing the status) rather than using a 'completed' activity. A new status therefore needs to be added of 'completed'.
     143