Changes between Version 14 and Version 15 of LEGACY - CiviCRM LCBRU Use Case

Timestamp:

09/28/12 16:44:49 (12 years ago)

Author:

Nick Holden

Comment:

--

LEGACY - CiviCRM LCBRU Use Case

@@ -15 +15 @@
 === 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 LCBRU staff and those who might be study subjects, who we will call 'contacts'.
+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
+* Individual - Health worker (includes GPs, practice nurses, 
 
 * Organisation - GP Surgery
@@ -27 +27 @@
 Contact entries for LCBRU staff are created automatically from the relevant drupal account. And the drupal account is created automatically at first log-in using LDAP. Smooth.
 
-Non-staff will have contact records created for them separately and manually.
-
 * Address
   * State / Province - is replaced by 'county' during localization to UK
@@ -34 +32 @@
 
 Custom fields likely to be necessary for participants
-* GP surgery - relationship to an organisational record
 * NHS number
 * UHL S number
@@ -41 +38 @@
 === 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.
+
+=== Relationships ===
+
+Contact A     -> "GP is"         -> GP B
+GP B          -> "GP of"         -> Contact A
+
+Contact A     -> "GP Surgery is" -> GP Surgery B
+GP Surgery B  -> "GP Surgery of" -> Contact A
+
 
 === Tags ===