Steps to Import CSV
Copy events from one env to other
We come across use cases where events in live Collection Protocols (CPs) needs to be updated. From v10.3 it is possible to export-import events across single/multiple/all collection protocols.
Steps:
Select collection protocol/s from list view from env 1 (e.g.Test)
Export events which you need to update
Remove the 'Identifier' column in CSV
Import into env 2 (e.g.Prod )(if CP short title matches, system will update events)
In Prod, 'Close' all the events/ SRs which you don't want people to use
OpenSpecimen does allow you to update the events for existing collection protocols. If there are any associated visits/ specimens collected, you will not be able to delete event. However, you have an option to close current event and start collecting using new event.
Sample CSV
Data Directory
Column Name | Data type | Mandatory? (Create) | Mandatory? (Update) | Description | Permissible Values | Validations |
---|---|---|---|---|---|---|
Identifier | Number | No | Yes | System auto-generated unique number for every event. | Mandatory while updating events. | |
CP Short Title | String | Yes | Yes | CP Short Title, in which event needs to be added | It should be unique within the system. | |
Event Code | String | No | No | |||
Event Point | Integer | No | No | |||
Event Point Unit | String | No | No |
| ||
Event Label | String | Yes | Yes | Event Name | ||
Clinical Diagnosis | String | No | No | Any Valid Clinical Diagnosis present in PV's | ||
Clinical Status | String | No | No | Any Valid Clinical Status present in PV's | ||
Default Site | String | No | No | |||
When to Print | String | No | No | |||
Print Copies | Integer | No | No | |||
Activity Status | String | No | No | Activity status for an event | Active/Disabled | Use 'Disabled' to delete the events. |