Changes between Version 29 and Version 30 of LEGACY - CiviCRM LCBRU Use Case


Ignore:
Timestamp:
11/15/13 14:39:07 (11 years ago)
Author:
Nick Holden
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • LEGACY - CiviCRM LCBRU Use Case

    v29 v30  
    142142As 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'.
    143143
     144== Mailings, templates and tokens ==
     145CiviCRM uses tokens as placeholders for mailings. Additional tokens can be defined in the drupal module LCBRU, in the civicrm_hooks.php file - this will be the general repository for 'clever' civicrm work.
     146
    144147== Note regarding GP practice data ==
    145148As more studies come on board and use Civi as their contact management tool, it is important to apply some consistency to the way records are created.