Changes between Version 23 and Version 24 of LEGACY - CiviCRM LCBRU Use Case


Ignore:
Timestamp:
03/14/13 15:04:30 (11 years ago)
Author:
Nick Holden
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • LEGACY - CiviCRM LCBRU Use Case

    v23 v24  
    135135
    136136Initially we thought that 'withdraw' needed to be an activity. But in fact the enrolment status captures it better, and 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 withdrawal activity. But we might well need additional custom data to reflect the various possible 'levels' of withdrawal in a study.
     137
     138Following 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').
     139