During the next sync, OpenSpecimen will: If no visits collected: Participant is deleted. If visits are collected: Participant will NOT be deleted since visits and possibly specimens, forms, etc., have already been collected You have to first delete or move the visits to another participant. Delete the participant manually in OpenSpecimen (ONLY if the Subject is already deleted in REDCap)

The visit is not deleted from OpenSpecimen

When a synced participant is deleted in OpenSpecimen, it is ignored in all subsequent syncs. The reason is that if the end user manually deletes a participant, it means they no longer want that participant in OpenSpecimen.

This can only be achieved through database updates. Please ensure that a database backup is taken before executing any of the SQL statements below. If you know the OpenSpecimen PPID of the deleted participant : select identifier from catissue_coll_prot_reg_aud where protocol_participant_id = <input_record_id> Use the returned identifier value as the cpr_id in the following query: SELECT * FROM os_redcap_records WHERE cpr_id = <identifier>; Confirm that the above query returns only one row. DELETE FROM os_redcap_records WHERE cpr_id = <identifier>; If you know the REDCap record_id of the deleted participant : SELECT * FROM os_redcap_records WHERE record_id = <record_id> AND project_id = <redcap_project_id>; Confirm that the above query returns only one row. DELETE FROM os_redcap_records WHERE record_id = <record_id> AND project_id = <redcap_project_id>; Once the linkage record has been deleted, rerun the REDCap synchronization from the OpenSpecimen UI. OpenSpecimen will treat the REDCap record as a new participant and create a new participant record during the next synchronization.