Changes between Version 6 and Version 7 of LEGACY - CiviCRM LCBRU Use Case

Timestamp:

09/12/12 16:11:57 (13 years ago)

Author:

Nick Holden

Comment:

--

LEGACY - CiviCRM LCBRU Use Case

@@ -13 +13 @@
 
 
-User
+=== Contacts ===
+We will create contact entries for LCBRU staff by creating drupal accounts for them.
+
+Non-staff will have contact records created for them separately and manually.
+
 * Address
-  * State - use Word Replacement to substitute 'County'
+  * State / Province - is replaced by 'county' during localization to UK
   * County - do not use (this is a different division than UK County
 
-
-Groups
-* LCBRU staff (ACL group, to all for ACL role of 'LCBRU staff' to have edit permissions on contacts etc)
+Custom fields likely to be necessary for participants
+* GP surgery
+* NHS number
+* UHL S number
 
 
+=== Groups ===
+* LCBRU staff (ACL group, to all for ACL role of 'LCBRU staff' to have edit permissions on contacts etc) - could this be a 'SMART GROUP' based on the creation of a drupal account?
+
+=== Case type ===
+Represents the study
+
+Needs 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.
+
+
+=== Cases ===
+Represents the recruitment of a participant against a specific study.[[BR]]
+Might need a revised form template as 'details', 'duration' and 'subject' are not really relevant.[[BR]]
+
+
+* Medium (represents the recruitment method) - needs additional options (it's the 'encounter medium' option group):
+  * GP surgery
+
+* Location
+* Details
+* Subject
+* Case type
+
+* Case roles - what are we doing with this?
+
+* Case workflow - defined in the associated xml file, what activities are we presenting as a workflow for GENVASC?
+