Changes between Version 9 and Version 10 of LEGACY - CiviCRM LCBRU Use Case


Ignore:
Timestamp:
09/21/12 14:35:49 (12 years ago)
Author:
Nick Holden
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • LEGACY - CiviCRM LCBRU Use Case

    v9 v10  
    2323
    2424Custom fields likely to be necessary for participants
    25 * GP surgery
     25* GP surgery - relationship to an organisational record
    2626* NHS number
    2727* UHL S number
    … …  
    3131* LCBRU staff (ACL group, to allow for ACL role of 'LCBRU staff' to have edit permissions on contacts etc) - could this be a 'SMART GROUP' based on the drupal account being in the associated drupal role 'LCBRU staff'.
    3232
     33=== Tags ===
     34How are we going to use 'tags'? For the time being delete all tags.
     35
    3336=== Case type ===
    34 Represents the study
     37Represents the study.
    3538
    3639Needs custom fields to represent the study ID number? Since 4.2.0 custom fields can be attached to a specific case type. This works quite nicely but will need the use of 'hooks' to intercept the data and validate it is unique before entry into the database.
     40
     41Disable the sample case types. Create a new case type for 'GENVASC'.
     42
     43Each case type requires an xml configuration file in /civicrm/CRM/Case/xml/configuration/
    3744
    3845
    … …  
    5057* Case type
    5158
    52 * Case roles - what are we doing with this?
     59* Case roles - recruiter, venepuncturist, case administrator, project manager, lab processor, principal investigator.
    5360
    54 * Case workflow - defined in the associated xml file, what activities are we presenting as a workflow for GENVASC?
    55 
     61* Case status - defined four so far: recruited (opened), declined (closed), withdrawn (closed), excluded (closed).