OpenSpecimen - Overview
Initial Considerations
OpenSpecimen is a Laboratory Management software program designed specifically for labs to track specimen storage and processing based upon clinical study design.
The OpenSpecimen General Design
The standard workflow of collecting specimens:
There are two types of protocols that are supported by OpenSpecimen:
Specimen-centric: for studies in which no patient data is collected or tracked with the sample (biobanking)
Participant-centric: for studies in which participant demographic and disease-specific data is collected, stored, and linked to specimen data.
Planned: Longitudinal studies can be designed to specify details regarding specimen collection for predefined time points.
Unplanned: No defined visits or specimen requirements are set allowing the user to record the collection of any specimen type at any time.
Listed below are key features associated with each Collection Protocol:
Feature | Specimen-centric | Participant-centric |
Customized storage container design and organization | X | X |
Automatically assign next available storage location | X | X |
Restrict storage location by sample type or study protocols | X | X |
View of storage container contents by specimen ID | X | X |
Maintain traceability of derivatives and aliquots | X | X |
Track specimen processing events | X | X |
Track distributed samples | X | X |
Record samples received back from customers or processing labs | X | X |
Customized Queries, Reports, Invoices | X | X |
Bulk operations | X | X |
Store samples without patient data (Biobanking) | X | |
Track storage of legacy samples without participant data | X |
|
Patient data is collected with specimen |
| X |
Consent statements are tracked and stored |
| X |
Collect multiple specimens over time from the same participant |
| X |
Collection events and specimen requirements can be set in advance |
| X |
What OpenSpecimen Offers
Opportunity for labs to comply with FDA and CLIA regulations for securing specimens
Assign roles to users that will restrict access to PHI and access to specific Protocols
Associate Individual consent statements with each patient
Query users by specific consent events
Attach signed consent pdfs
Upload and extract text from Pathology Reports
Design specimen requirements per visit instructing coordinators regarding collection criteria
Query samples or participants based on any criteria recorded in your Collection Protocol
Create a customized dashboard with your metrics of interest
Create custom forms to record study-specific information
Create derivatives and aliquots (may be defined in CP)
Automatically generate and print labels according to a predefined schema
Automatic assignment of storage locations to parent specimen, derivatives, and aliquots
Restrict sample storage by Sample Type and/or Collection Protocol
Record Processing Events, for example:
Freeze (recording freeze media used)
Fixation (record fixative used)
DNA/RNA extraction, etc.
Reserve specimens for specific projects or collaborators
Automatically mark specimens as ‘closed’ when exhausted
Distribute and receive specimens for outsourcing or collaborations
What OpenSpecimen Does Not Provide or Offer
A clinical laboratory information management system (LIMS)
Direct interface with Epic (this option is supported by OS, but the University of Utah does not yet support this option).
If you are interested in interface for your lab, the laboratory director should complete a Help Desk ticket
Ability to use your legacy sample numbering system as the primary participant ID or specimen IDs.
Automatic translation and upload of legacy data
Supports manual upload of bulk data in .csv format
User must map legacy data fields to fields in OpenSpecimen
Unique Considerations
If projects are assigned different IRB numbers, use one Collection Protocol per IRB.
Add the same participant to multiple CPs with the click of a button
Restricts study-specific data to the appropriate protocol
Distribute specimens to the specimen-centric Tissue Bank Protocol for storage without compromising PHI
Tissue Banks that store PHI and other patient data will use a Participant-centric protocol.
You must be open to change regarding modifications to the sample process flow and specimen labeling schema used by your laboratory.
Import of legacy data can be performed maintaining the current sample labeling, but implementing new specimen labeling will likely be necessary.
If custom data fields are required by the Collection Protocol, custom forms can be designed, but this process involves a learning curve to use the advanced features. The BMIC is here to help with that.
A networked label printer is required for label printing.