Changes between Version 10 and Version 11 of BRICCS Study

Timestamp:

10/08/14 12:43:18 (10 years ago)

Author:

Nick Holden

Comment:

--

BRICCS Study

@@ -6 +6 @@
 
 Onyx: For recruitment management and electronic data capture / questionnaire.[[BR]]
+CiviCRM: For electronic data capture / questionnaire, from October 2014.[[BR]]
+REDCap: For recruitment management, from October 2014.[[BR]]
 CaTissue: For specimen collection management and inventory.[[BR]]
 i2b2: For cohort discovery and clinical data integration.[[BR]]
@@ -13 +15 @@
 
 As from October 2014, recruitment into BRICCS will be performed using REDCap not Onyx. We will therefore need a revised process in CiviCRM to ensure that the full set of recruited participants is accurate in CiviCRM, which currently relies on an automated feed from the Onyx database to populate CiviCRM records.
+
+=== CiviCRM ===
+
+There is a basic case type definition for BRICCS in CiviCRM. This currently provides a standard timeline for only a 'Recruit and Interview' event and a 'Participant loaded into i2b2' event. There is also a 'Withdrawal' activity available.
+
+This will need expanding to enable full study management in CiviCRM. Enrolments will need an activity or status to indicate that recruitment is completed, mirroring the 'available for cohorting' concept in GENVASC.
+
+In the case type definition XML, the 'Recruit and Interview' activity should no longer be created in the 'Completed' state, but 'Scheduled'. Ultimately, the BRICCS module should enable data submitted in CiviCRM to be passed via the REDCap API to create a stub record in REDCap for data entry. 
+
+But as an interim, manual data entry in both CiviCRM and REDCap would be acceptable. Process should be: search for patient first in CiviCRM to ensure no duplicate entry, create a record in CiviCRM and enrol the participant in the BRICCS study, entering custom data manually. Then switch to REDCap and enter the questionnaire data (note that for the time being this involves a small amount of double entering of consent data etc).
+
+When we roll out data flows between CiviCRM and REDCap, the process will be that administrators can create enrolments in CiviCRM at the time of invitations being issued, which automatically creates a stub record in REDCap. When the nurse interviews the participant in REDCap, the data flows back into CiviCRM to update the enrolment with custom data and an updated status.
+
+We also need to verify that all Onyx data is accurately captured in CiviCRM. This can be performed as part of the '[[Onyx closedown]]' process.
+
 
 === Remote sites ===