Quck links in this article:
Background and overview
Distribution Protocols are created to capture important information regarding the distribution of samples to collaborators or to track samples sent for processing at cores that won’t be returned (like sending an aliquot for NGS that won’t be returned to you). Creating a Distribution Protocol with the important details as outlined in this document ensures that all necessary information is captured for future reference (i.e. audits), but also allows for multiple shipments over time to the same project without having to reenter all of the information.
Specimens are considered ‘distributed’ when they are shared with or given to collaborators or other labs on campus or externally. When a sample is marked as ‘Distributed and Closed’, it no longer is available for any future processing or editing. This is different from a ‘Shipment’ in OpenSpecimen. If a sample is shipped, it remains active and available in the system, but is likely located in a different laboratory. That other laboratory can access the specimen in your protocol (with permissions) and perform and record additional processing on that sample.
In most cases, labs on campus will be ‘distributing’ samples unless the laboratory receiving the samples will also have access to your OpenSpecimen collection protocol to continue to track and process those samples and their derivatives and aliquots. 'Shipments' are specifically used to track the movement of specimens from one location (site) to another. For instance, you can ship samples to the CTRC for processing and long-term storage. In this case, your samples are still active and available for you to see, but their location is elsewhere. And the new location (CTRC) can now perform services on them, like extracting DNA or creating blood separation products, and those events can be tracked within your protocol.
Prerequisites
Step 1: Creating a Distribution Protocol (DP)
What information will you need to create the DP? Consider the below:
Who will be receiving the samples and where are they?
Principal Investigator (Dr. Robert Smith)
Their institute: this is the overarching institute to which the PI belongs (like a University)
Their ‘Site’: this is typically the lab or dept name (like Dr. Smith’s Lab or Center for Integrative Science). If you were to ship the samples to the Dr. Smith at the University of Southern California, where within USC would you be addressing the shipment?
What are the project details?
What is Dr. Smith’s IRB (if applicable)?
What is Dr. Smith’s project title? (What are they studying that warrants sharing these samples with them?) Does the study fall within the consent statements that the participant signed?
Is there an MTA needed and, if so, what is the MTA number?
Who, within you lab, will be responsible for approving this shipment? (PI of your project or a lab manager?)
Who, within your lab, will be responsible for pulling and shipping the samples?
What information about the specimens will you be sending to Dr. Smith?
Specimen type
Quantity
Concentration
Anatomic Site
Do the samples need to be relabeled or de-identified prior to shipping?
Now that you’ve sorted out the above considerations, it’s time to create your DP! Expand below:
Select ‘Distribution Protocols’ from the navigation bar.
Choose ‘Create’.
Complete the fields with the information gathered in the first section.
Required Fields:
Title: descriptive of the DP: “Dr. Smith’s specimen request for Project XYZ”
Short Title: recognizable acronym or shortened discription, “Smith XYZ”
Receiving Institute: (Institute to which requestor belongs; ‘USC’)
Principal Investigator: Requesting PI (must belong to the Institute specified above).
Distributing Site(s): Sites allowed to send samples to the above PI. (Note that sometimes a PI will request specimens from multiple projects. So this DP can be used by multiple users and CPs.)
Optional Fields
Receiving Site: if there is a division, dept, or lab associated with the receiving PI, you can optionally specify this. It would have to be added to OpenSpecimen by an Administrator.
Coordinators: these are the actual members of teh receiving site lab who will be receiving or handling the samples and need to be notified of the shipment and will receive any attachments, like the sample metadata.
Ethics ID: This is the IRB number associated with the project belonging to the receiving site.
Start and End Dates can be added for DPs that will have shipments sent over time. For instance, some DPs request samples that meet specific criteria to be shipped on a weekly or monthly basis.
Label format: this can be specified if samples are being relabeled upon distribution.
Order Custom Fields: These are your custom fields that can be added to any distribution.
Order Report Query: These are the specific data fields that will be sent to the investigator along with the specimens. If no custom query is defined, the manifest will include the standard fields (what are these?).
Order attachment: this specifies whether the email notifications will include sample data as .csv, .pdf, or both types.
Email notifications: if enabled, all users specified in the above fields will receive a notification of sample shipment once the samples are distributed.
Optional features available to add to a DP
Consents: If you capture answers to specific consent statements, you can set requirements that samples can only be distributed to a DP based upon a specific answer to a consent statement. For instance, Samples can only be distributed if the participant answered ‘yes’ to ‘samples may be shared with external researchers' or ‘I consent to genetic analysis’.
Requirements: You can set the DP to only allow specimens that meet certain criteria
Services: You can manually assign services associated with a DP that you can subsequently bill for, such as aliquotting and relabelling, add a cost and note if it will be paid with internal or external funding.
Step 2: Distributing Specimens
There are 2 methods that can be used to distribute specimens, expand each method below to review.