Changes between Version 1 and Version 2 of CiviCRM GENVASC Use case description


Ignore:
Timestamp:
09/14/12 12:03:41 (12 years ago)
Author:
Nick Holden
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • CiviCRM GENVASC Use case description

    v1 v2  
    99
    1010Genvasc ID labels will be produced prior to recruitment, using an approach similar to BRICCS, but written as a php library to facilitate later integration with CiviCRM. The output of this process should be a series of single barcode labels, each one guaranteed unique, with human readable and barcode representation of a unique identifier of the form: LCBRU-Gxxxxxxxx (where x represents a random integer). A database of used identifiers will be maintained to ensure no duplication.
     11
     12Note: [[GENVASC ID and label generation]] now being written as a drupal module.
    1113
    1214Participants will be recruited in primary care setting. The GP surgery will -complete- print a consent form populated with participant demographics within their practice IT system, and including -print out- copies for local records and one copy to be signed and then attached to the sample bag. If the participant has given consent for Genvasc specific study samples, these will be in the sample bag. If not, the bag will be empty. Vascular Health Check samples for processing will travel in a separate bag, even where the participant has given permission for the residue of these samples to be used for the Genvasc study. The GP surgery will submit via iLab details of the samples being submitted, either Genvasc study specific samples or VHC samples with permission for residual use.