Changes between Version 16 and Version 17 of LEGACY - CiviCRM LCBRU Use Case

Timestamp:

10/02/12 09:45:57 (12 years ago)

Author:

Nick Holden

Comment:

--

LEGACY - CiviCRM LCBRU Use Case

@@ -7 +7 @@
 Currently this page is a record of our deployment of CiviCRM - initially as a recruitment process manager for the GENVASC project.
 
+The intention is to use drupal modules to deliver the 'LCBRU' version of civicrm. First, install civicrm. Then install the 'lcbru' module, which will create option group entries, custom fields, contact sub-types, potentially even contacts for GP surgeries, etc., in a consistent way. Then install the ice_messaging module.
+
 briccsapp04.xuhl-tr.nhs.uk - test system[[BR]]
 briccsapp05.xuhl-tr.nhs.uk - live system[[BR]]
 
-=== CiviCRM Object Model ===
+== CiviCRM Object Model ==
 
 
 === Contact Types ===
 
-We can create sub-types which allow for specific custom fields and relationships to be built. This is most important to differentiate between staff (either LCBRU staff or external staff) and those who might be study subjects, who we will call 'contacts'. Records can belong to more than one sub-type, but sub-types cannot be nested.
+We can create sub-types which allow for specific custom fields and relationships to be built. This is most important to differentiate between staff (either LCBRU staff or external staff) and those who might be study subjects, who we will call 'contacts'.
+
+Records can belong to more than one sub-type, but sub-types cannot be nested.
 
 * Individual - Contact
 * Individual - LCBRU staff
-* Individual - Health worker (includes GPs, practice nurses, 
+* Individual - Health worker (includes GPs, practice nurses, and LCBRU staff)
 
 * Organisation - GP Surgery
@@ -31 +35 @@
   * County - do not use (this is a different division than UK County
 
-Custom fields likely to be necessary for participants
+Custom fields for Contacts of sub-type 'contact'
 * NHS number
 * UHL S number
 
+Custom fields for Contacts of sub-type 'health worker'
+* GMC code (optional, only applies to GP)
+* ICE code (optional, only applies to GP)
+* GCP training date - to help track renewals, this might be better being an activity
+
+Custom fields for Contacts of sub-type 'GP Surgery'
+* Practice code
+* ICE code
+
 
 === Groups ===
-* 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'. Needs to interact with the designated contact type.
+
+* 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'? Needs to interact with the designated contact type.
+
 
 === Relationships ===
@@ -47 +62 @@
 GP Surgery B  -> "GP Surgery of" -> Contact A
 
+Use 'employer/employee' relationships to model GPs and practice staff to their respective GP Practices
+
 
 === Tags ===
+
 How are we going to use 'tags'? For the time being delete all tags.
 
+
+=== Option Groups ===
+
+Option Groups provide extensible lists of available options for particular fields.
+
+Gender is pre-set with 'Female', 'Male' and 'Transgender'. Added 'Not Specified' and 'Not Known' to match the NHS national codes.
+
+Individual contact prefixes is pre-set with 'Dr', 'Mr', 'Mrs', 'Ms'. Added 'Professor'
+
 === 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.
+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 validating that it is unique before entry into the database.
 
 Disable the sample case types. Create a new case type for 'GENVASC'.