User can create/Update visits in bulk, follow below steps to create/update visits:
- Go to collection protocols list page, click on 'Import' button and select option 'Import OR
- Go to participants list page of the CP whose visit has to be created/updated, click on 'More' button and select option 'Import
- Select 'Visits' from 'Select Record Type' dropdown and click on 'Download Template File' to download the template file
- Enter all valid data in the template file as mentioned in the below table
- Upload the filled template file in 'Input Records File' field, select 'Import Type' as 'Create' to create or 'Update' to update visits
- Click on 'Validate and Import' button
- Refer 'Import status' to check the status of import job
Please note: On updating the activity status of the visits to 'Disabled', the dependent data - specimens collected under this will be deleted. This is the force delete feature that is available on the UI as well.
Column Name | Data type | Mandatory? (Create) | Mandatory? (Update) | Description | Permissible Values | Validations |
|---|---|---|---|---|---|---|
| Identifier | Number | No | Depends | System auto generated unique number for every visit | ||
| CP Short Title | String | Yes | No | Collection Protocol of the visit to be added | Should be existing and unique within OS | |
| PPID | String | Yes | No | The participant for whom this visit is being created. | Existing PPID. | |
| Event Label | String | No | No | Event Point Label from the protocol for which this event corresponds. E.g. baseline, surgery, etc. | In v3.4, if left blank, system will add visit with event label as 'Unplanned Visit' | |
| Name | String | Depends | Yes | Name of the visit. Mandatory if the auto label generation set to OFF | Should be unique within OS | |
| Visit Date | Date | No | No | Select the correct date format from UI based on the data in the file. In v3.4, if left blank, system will add current date by default | ||
| Visit Site | String | No | No | Valid site name | In v3.4, if left blank, system will add recent visit site | |
| Visit Status | String | No | No | Complete, Pending, Missed Collection | In v3.4, if left blank, system will add 'Complete' status | |
| Clinical Diagnosis | String | No | No | In v3.4, if left blank, system will display 'Not Specified' | ||
| Clinical Status | String | No | No | 'No Diagnosis / Control' /New Diagnosis /Pre-Therapy /Post-Therapy /Pre-Operative /Operative /Post-Operative /Remission /Relapse, Primary Site /Relapse, Distant Site /Relapse, Not Specified /Not Specified | In v3.4, if left blank, system will display 'Not Specified' | |
| Cohort | String | No | No | The group to which the visit belongs | By default this field is not visible. In order to display this field, system administrator needs to add values in database table 'catissue_permissible_value' or user can add values through 'Dropdown Manager'. The dropdown is visible in visit page only if it has PVs added. | |
| Path. Number | String | No | No | Surgical Pathology Number | In v3.4, if left blank, system will display 'Not Specified' | |
| Pathology Report Name | String | No | No | File name of the surgical pathology report | This is used to upload pathology reports. The document file name is specified in this column and the actual file is uploaded along with the CSV in a zip file. For more details refer 'File Upload via BO' | |
| Missed Reason | String | No | No | Reason for missed visit | Beyond processing time/ Insufficient sample collected / available/ Laboratory error/ Patient declined collection/ Poor sample quality/ Sample damaged/ Sample not collected by clinic / Clinic error/ Visit cancelled | In v3.4, if left blank, system will display 'Not Specified' |
| Comments | String | No | No | |||
| Activity Status | String | No | No | Active | Value should be 'Active' during creation or kept blank in which case it will take default value as 'Active' | |
| Missed By#Email Address | String | No | No | Email address of the user who missed the visit | Should be an existing user in OpenSpecimen |