...
There is no REDCap API to fetch changes in data that have occurred in a project since a given time point. The API always responds with ‘ALL changes’. The custom PHP plugin solves the problem by implementing an API that provides options like time point from when the changes need to be picked, how many changes, etc.
For longitudinal projects, the REDCap events API does not provide event IDs. It poses a problem in enforcing mapping between REDCap and OpenSpecimen events when there is a change in the REDCap event name (including unique_event_name). The custom PHP plugin implements an API to export project events along with their IDs. The OpenSpecimen plugin then uses these event IDs to create events mapping between REDCap and OpenSpecimen. The event IDs remain the same even when there is a change of event name. Significantly, data change records fetched from REDCap contain references to event ID.
Synchronization Run
How are visits synchronized between REDCap and OpenSpecimen?
>>If the user has multiple visit dates in redcap, and we mapped them into OS, but
>>there is no visit names (required field in OS) in redcap. After we map the visit date into
>>OpenSpecimen, can OS automatically generate visit names and required visit fields in
>>OpenSpecimen to be able to let the user start to enter the specimen information?
...
If PHI is marked as "Disabled", can record matching occur on MRN or DOB or Name ?
Ans: If "Save PHI data" is set to "Disabled," record matching can still occur on fields like MRN, eMPI, External Subj ID, etc if the mapping is added to participant identifier fields. OpenSpecimen will prioritize the participant mapping over the "Save PHI data" setting, ignoring the "Disabled" option for the mapped fields and performing record matching based on the identifiers.
| Note |
|---|
The mapped PHI fields will be visible in the participant overview page. |
How are visits synchronized between REDCap and OpenSpecimen?
>>If the user has multiple visit dates in redcap, and we mapped them into OS, but
>>there is no visit names (required field in OS) in redcap. After we map the visit date into
>>OpenSpecimen, can OS automatically generate visit names and required visit fields in
>>OpenSpecimen to be able to let the user start to enter the specimen information?
Ans: Yes, visits will be created automatically using the default visit naming scheme. You can then collect specimens under that visit.
...
Ans: No. Example case: Append RC project ID to the PPID/MPI in OpenSpecimen.
Forms and Mapping
What
...
Ans: No, the missing fields are automatically created as custom forms/fields by the plugin.
Can the plugin map the REDCap fields into existing custom form fields?
...
is the difference between “Record_id=participant.extensionDetail.attrsMap.redcap_record_id” and “record_id=ppid” mapping?
Ans: The first one is to map the "RC record ID" to a custom field in the OS. Here you will use the option to auto-generate PPID in OS. The next is to directly map "RC record ID" to a PPID field in OS and hence PPID are not auto-generated.
That being said, the purpose of using one option over another depends upon your specific requirements.
What if the fields are not available in OpenSpecimen's default setting? Does it mean that we first need to create the custom form to store these fields?
Ans: No, the missing fields are automatically created as custom forms/fields by the plugin.
Can the plugin map the REDCap fields into existing custom
...
form fields?
Ans: No, the plugin cannot map the REDCap fields into existing custom forms. The plugin will create new forms for each REDCap instrument being synced.
...
When the visit date field is not mapped, its value is set to the date/time of the corresponding REDCap event data entry.
When the visit site field is not mapped, its value is picked either from the mapped event's default site or the project site.
What sites are available for selection in the project site dropdown?
Ans: The project site dropdown is restricted to the sites linked with the collection protocol.
...
the corresponding REDCap event data entry.
When the visit site field is not mapped, its value is picked either from the mapped event's default site or the project site.
What sites are available for selection in the project site dropdown?
Ans: The project site dropdown is restricted to the sites linked with the collection protocol.
REDCap Data
For the value "Save PHI data" please explain the ramifications of clicking "Enabled" or "Disabled".
Ans: When you use the ''Save PHI data" option as Disabled, OS will not pull any RC field marked as 'Identifier' in the RC instrument/form set-up. Usually, these fields are 'First Name', 'Last Name', 'MRN', 'DOB', etc.
PHI such as Name, MRN, DOB must always be saved to identify a record. So what is the use of having a Disabled option for "Save PHI data" ?
Ans: This is a user based preference. We have a few clients who don't want PHI fields pulled in OS. They use these setting as Disabled.
If we remove forms or fields in REDCap after the go-live date, would OS remove them for us automatically during the overnight job?
...