= CiviCRM =

[[Technical deployment tasks for CiviCRM]]

[[Use case description for Genvasc]]

Currently this page is a record of our deployment of CiviCRM - initially as a recruitment process manager for the GENVASC project.

briccsapp04.xuhl-tr.nhs.uk - test system[[BR]]
briccsapp05.xuhl-tr.nhs.uk - live system[[BR]]

=== CiviCRM Object Model ===


=== Contacts ===
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
  * County - do not use (this is a different division than UK County

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?