Leave a comment at the end of this page or email contact@krishagni.com
Longitudinal Collection Protocol
In a longitudinal Collection Protocol, subjects are followed over time with continuous or repeated timepoints to collect biospecimens. The list of biospecimens too be collected per timepoint and their processing details are predefined.
Introductory Video
In OpenSpecimen, you can create a CP with basic details for your study.
Details for all the fields on the CP overview page,
Note:
The CP level PI and Coordinators will not be assigned roles automatically or by default.
After creating the CP, the admin has to manually assign specific roles to all the users who need to access the CP.
Defining Consents
Consents statements are created at the system level by super admins and institute admins. Once created, the User can use it in multiple CPs. Refer 'Coded consents' for more details.
Defining Timepoints
For longitudinal collections, you have the ability to configure event points and specify specimen requirements. By predefining more CP events, you can significantly reduce the amount of daily data entry needed. The system is equipped to manage various types of deviations, such as instances where the collected quantity is less than planned, during the collection process.
Adding Events
An event represents one collection time point in which one or more specimens are collected. E.g. Day 0, Day 30, Cycle 1 etc.
Adding Specimen Requirements (SR)
Specimen requirement defines what specimens are expected to be collected and how they should be processed at each time point. E.g., Collect two whole blood specimens, process one into plasma and the other into the serum.
Adding Derivatives and Aliquots
A derivative is the parent specimen's processed outcome (e.g., plasma or serum from blood), whereas an aliquot is the smaller portion of the parent specimen.
Edit Event/SR
Copy Event/SR
Some studies may have similar events or SRs. In such cases, you can copy the event/SR. Copying an event also copies all the SRs under it. Similarly, copying the SR also copies all the child SRs under it.
Delete Event/SR
You can delete unwanted events/SR, e.g., event/SR created by mistake. But only if you have not collected any data respective to those set events or SRs.
Deleted event/SR will not be visible in the CP.
No new visit/specimen can be collected for the deleted event/SR.
Impact of closing an event/SR:
Any visit and specimens collected before the closing of the event will be visible after closing.
No new visit/specimen can be collected for the closed event/SR.
Close and Reopen Event/SR
Sometimes you may need to discontinue an event or SR. In such cases, the event/SR can be "closed."
Close and Reopen Event:
Leave a comment at the end of this page or email contact@krishagni.com