From v9.0. OpenSpecimen supports creating the participant and specimen-centric CPs using the bulk import features. In order to use that user has to fill the below template and follow the steps to import the CPs in bulk.
Field Name | Data Type | Mandatory | Description | Validation |
---|---|---|---|---|
Title | String | Yes | Collection Protocol Long Title | Unique within the system |
Short Title | String | Yes | Collection Protocol Short Title | Unique within the system |
Code | String | No | Collection Protocol Code | Unique within the system |
Start Date | Date | No | Collection Protocol Start Date | - |
End Date | Date | No | Collection Protocol End Date | - |
Specimen Centric | Boolean | No | Collection Protocol Type: Participant Centric Or Specimen Centric — Values you need to specify is Yes, No, TRUE, FALSE | |
IRB ID | String | |||
Anticipated Participants Count | Integer | |||
PPID Format | String | |||
Visit Name Format | String | |||
Label Format | String | |||
Derivative Label Format | String | |||
Aliquot Label Format | String | |||
User inputs PPID | String | |||
User inputs Visit Name | String | |||
User inputs Specimen Label | String | |||
Label Pre-print Mode | Boolean | |||
Description URL | String | |||
Activity Status | String | |||
Sites#1#Name | String | |||
Sites#1#Code | String | |||
Sites#2#Name | String | |||
Sites#2#Code | String | |||
PI#PI Email | ||||
Coordinator#1#Coordinator Email |
View file name cp_create_202204200312000 (1).csv height 150
From v7.1, it is possible to bulk import CP event and specimen requirements. This is useful for bulk importing legacy data, managing large CPs, or interfacing with external apps.
...
Field Name | Data type | Mandatory | Description | Validations |
---|---|---|---|---|
Sites | String | Yes | You can select multiple sites from the dropdown where the study is being carried out. | |
Title | String | Yes | The long title of the research study | |
Short Title | String | Yes | Short title to identify the study from the CP list page | Should be unique within the system |
Code | String | No | 'CP code' that can be used to generate the participant IDs | Should be unique within the system |
Principal Investigator | String | Yes | The user who leads the study | |
Protocol Coordinator | String | No | A specialized a researcher who supports the management and coordination of clinical research studies. There can be multiple coordinators selected. | |
Date | Integer | No | Start and End date of the study. Some clinical trials are for a specific duration. | |
Ethics Approval ID/IRB ID | Integer | No | The 'approval ID' given by the Ethics committee to conduct the study | |
Type | String | No | If the study collects participant's information, then select 'Participant centric' else 'Specimen centric' for specimen biobanks. | |
Anticipated Participants Count | Integer | No | The number of participants that will be registered to the protocol. (The number of actual registrations can exceed) | |
SOP Document URL | String | No | Link to the SOP document uploaded on the university web portal | |
SOP Document File | No | During CP creation, the user can also upload the study-related standard operating procedure document files. The users can access the SOPs that have been set at the CP level during data entry. This helps them perform any procedure consistently. | ||
Store SPRs? | No | The visit page will show the SPR tab if enabled. | ||
Extract Text from SPR PDF Docs? | No | The text from the uploaded SPR file is shown in the 'Surgical Pathology Reports' section when enabled. (If the SPR contains scanned images, then there is no text extracted) |
...