...
Go to the CP Overview Page of choice and click on the 'settings' tab on the left sidebar.
Select ‘REDCap Project Configuration' and click on the 'Add Project’ button.
Add the name of your choice, appropriate server, API token generated for the project and default site for CP. You can save the PHI data to OS by selecting the ‘Enabled’ option for ‘Save PHI Date'. Furthermore, you can also add users to notify them about the errors that occurred during synchronization.
‘Snapshot Download Page Size’ specifies the maximum number of records OS server fetch for RC server each time. This is repeated ‘N' number of times until all records are pulled to the OS server. It helps to minimize the overload to the OS server. The default value for it is '1000’.
If you want, you can also add a new server of your choice. To do so, click on the ‘Add New’, provide details on server name, host base URL, plugin path and time zone, and click on the ‘save’ button.
...
Like 'Participant Level Mapping', map visits fields between RC project and OS CP as shown below in the red box.
Additionally, you can map events from RC with events from OS, as shown below.
Those events from RC which are not mapped to OS can create unwanted, unplanned events in OS. To avoid this, click on the 'Ignore Unmapped Events’ checkbox.
...
REDCap | OpenSpecimen | Description |
|---|---|---|
Project | Collection Protocol | The RC project can be synchronized with a particular CP in OS. |
Instruments/Forms | Forms | The instruments from RC can be synchronized with forms linked with a particular CP in OS. |
Participant fields | Participant fields | The participant fields from RC can be synchronized with participant fields linked with a particular CP in OS. |
Visit fields | Visit fields | The visit fields from RC can be synchronized with visit fields linked with a particular CP in OS. |
Events | Events fields | The events from RC can be synchronized with planned events linked with a particular CP in OS. |
...