3. Click on 'Download Template File' to download the template file from the 'Import Events' page. 4. Enter all valid data in the template file as mentioned in the 'Data Dictionary' table. 5. Upload the filled template file in the 'Input Records File' field, select 'Import Type' as 'Create' to create or 'Update' to update events. 6. Click on the 'Validate and Import' button. 7. Refer to 'Import status' to check the status of the import job. |
We come across use cases where events in live Collection Protocols (CPs) needs to be updated or client analysts make changes across multiple CPs and needs to move them into other env. From v10.3 it is possible to export-import events across single/multiple/all collection protocols. Steps:
|
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. |