Learn more about the consequences of changing a subject's site.
Update site: (e.g. from site A to site B)
If, for example, a subject relocates during your study then you can update the site for this patient. Here is a list of consequences you need to consider when proceeding with this action.
Site: If you move the subject from site A to site B it will disappear from the subject overview in site A and will be visible in site B. This means that collaborators with access to site A (and without access to site B) will no longer be able to see this subject. Before a subject is technically transferred to another site, we recommend to export all subject related data for documentation purposes
SIC: The SIC (and if applicable the PID) will be transferred from site A to site B with exactly the same ID. Example: Subject had the SIC 00010012 in site A. The same SIC is now also displayed in site B after the update.
If after this change site A wants to use the same SIC (00010012) again for the next patient, site B must manually change the SIC of the transferred subject before the next subject gets enrolled in site A. Remember: The SIC is unique and can only be used once in a study!
ePRO: In general, the scheduling of ePROs will remain the same across sites. However, if the new Site B is in a different time zone, all subsequent ePROs for the subject will be scheduled in the new time zone (including reminders & expiration).
Queries and (S)AEs: The subject's queries and (S)AEs will disappear from the query overview from site A and will be visible for site B. Site B will still be able to see comments of queries from site A (if any), but site B personnel will not be able to see the respective user names of site A.
Audit Trail: The new site B will see the audit trail for this subject as soon as its updated to site B, but will not see the past audit trail up to this point.
✉️ Still have questions? Please contact your study coordinator. |
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article