Table of Contents |
---|
Introduction
Once all the configuration and mapping of the fields are completed, you can synchronize data from the REDCap server. The synchronization can be conducted manually at the CP level and automatically at System Level.
CP Level Synchronization
The manual synchronization can be performed in two steps:
Synchronization of Instruments
Navigate to CP Overview Page and click on the ‘setting’ tab on the sidebar.
Under the project tab, click on the ‘More’ button and select ‘Synchronize Instruments’.
...
Synchronization of records
Similarly to synchronize the records, click on the ‘More' button under the project tab and select ‘Synchronize Records’.
You will get three options to synchronize the records:
Incremental Updates
It will update the latest changes in the records from the last synchronization run.
All Records
It will pull all the records of the project from the REDCap server.
Selected Records
It will pull user-specified records as shown below in the red box.
Participant Merging
The participant matching is done based on the following attributes:
eMPI
MRN (site + MRN)
UID (SSN).
If a match is found, then that participant is used for registration and update purposes. Otherwise, a new participant is created for registration.
Info |
---|
Please note - The REDCap connector/plugin doesn’t use last name + DOB combination for matching as this requires users’ involvement or confirmation before using the resulting matches. The user’s involvement is ruled out because the synchronization is done automatically at scheduled times. |
Participant identifiers such as MRN, eMPI, SSN are used to merge the incoming REDCap participant records. A simple illustration shown with MRN is below:
REDCap | OpenSpecimen | Outcome |
---|---|---|
New record | The MRN of the incoming record matched the MRN of the participant registered to a different protocol. | The existing participant record should get reused during registration. |
New record |
| The incoming participant record should be linked to the existing registration. |
New record |
| Error: The participant is already registered. |
| Incoming MRN refers to another participant of another protocol. | Error |
| Incoming MRN refers to another participant of the same protocol. | Error |
| Incoming MRN is not available. | Update the MRN for the linked participant. |
Synchronization Status
OpenSpecimen provides an audit log for the synchronization run.
Expand | ||
---|---|---|
| ||
|
Abort synchronization run
Whenever the synchronization starts accidentally, or the server shut down, the user can use the abort feature to stop the synchronization in the middle of the run.
Expand | ||
---|---|---|
| ||
|
System Level (Auto) Synchronization
It is a very tedious task to manually go to the configuration page and perform synchronization every time you update the data in REDCap. Therefore to handle such a problem, OpenSpecimen provides system-level auto-synchronization. It is achieved via the Jobs module as follows:
...
Info |
---|
System-level Auto Synchronization is an incremental synchronization as discussed above. |
Instrument synchronizer
...
Records synchronizer
...