BRICCS

BRICCS, the Biomedical Informatics Centre for Cardiovascular Science, is the founding project behind the BRICCS platform, now the LCBRU IT Platform. BRICCS is a cohort discovery project to accelerate recruitment into translational medicine studies, recruiting patients with cardiovascular conditions (ACS, Aortic Stenosis, CHD, heart failure, etc) into a population from which cohorts can be isolated for common phenotypes.

BRICCS uses - and provided the initial impetus for development of - most of the tools in the LCBRU IT Platform.

Onyx: For recruitment management and electronic data capture / questionnaire.
CaTissue: For specimen collection management and inventory.
i2b2: For cohort discovery and clinical data integration.

Remote sites

Multiple sites came on board with BRICCS in September 2014, using REDCap as the data collection tool on an externally-facing server accessed over the NHS N3 secure network. See External BRICCS Sites for details.

SUPERCEDED

See Northampton Recruitment into BRICCS for details of the parallel recruitment project, whereby patients are being recruited into the BRICCS population from non-UHL hospitals, initially Northampton General Hospital.

In addition we're planning to roll out recruitment to Leeds and potentially Derby, Burton and Kettering. For these sites recruitment will only be for Aortic Stenosis in the initial phase. As a result, a reduced recruitment questionnaire is needed to accelerate recruitment. Work on that BRICCS reduced questionnaire is ongoing.

Recruitment reporting

As of February 2013, the BRICCS project was included in the Leicestershire, Northamptonshire and Rutland CLRN Portfolio. Monthly reporting is therefore required for the CLRN, starting with an initial report of recruitment from the start until the end of January:

• mysql -h briccsdb -u auditor -p briccs -e "SELECT barcode, start_date, status FROM participant ptone, interview WHERE NOT EXISTS (SELECT 1 FROM participant pttwo WHERE pttwo.enrollment_id = ptone.enrollment_id LIMIT 1, 1 ) AND barcode is not null AND status <> 'CANCELLED' AND ptone.id = interview.participant_id order by start_date;" > briccs_enrollment_to_date.txt

After that first report, each month the report should be re-populated with a specific month's recruitment FROM BOTH THE LEICESTER AND NORTHAMPTON DATABASES

Examples from Jan 2014:

• mysql -h briccsdb -u auditor -p briccs -e "SELECT barcode, site_no, start_date, status FROM participant ptone, interview WHERE NOT EXISTS (SELECT 1 FROM participant pttwo WHERE pttwo.enrollment_id = ptone.enrollment_id LIMIT 1, 1 ) AND barcode is not null AND status <> 'CANCELLED' AND start_date > '2014-01-01 00:00:00' AND start_date < '2014-02-01 00:00:00' AND ptone.id = interview.participant_id order by start_date;" > briccs_enrollment_leicester_2014_01.txt

• mysql -h briccsdb -u auditor -p briccs_northampton -e "SELECT barcode, site_no, start_date, status FROM participant ptone, interview WHERE NOT EXISTS (SELECT 1 FROM participant pttwo WHERE pttwo.enrollment_id = ptone.enrollment_id LIMIT 1, 1 ) AND barcode is not null AND status <> 'CANCELLED' AND start_date > '2014-01-01 00:00:00' AND start_date < '2014-02-01 00:00:00' AND ptone.id = interview.participant_id order by start_date;" > briccs_enrollment_northampton_2014_01.txt

Reports are generated and sent to Angel Christian at angel.christian@…