This is a description of the tables found in the Biobank database schema for version 3.10.0.
The street address for a center.
The aliquots / derivatives that are collected by a study.
Used for CSV file import.
This information does not need to be imported.
Used for CSV file import of annotations for a study.
This information does not need to be imported.
Used for CSV file import of patients for a study.
This information does not need to be imported.
Used for CSV file import of processing events for patient.
This information does not need to be imported.
Used for CSV file import of specimens for a patient.
This information does not need to be imported.
A center can be a storage site or a collection site. A collection site is also referred to as a clinic.
Used to record comments left by users for a center.
A record of when specimens were collected from a patient.
Used to record comments for an individual collection event.
A generic table used for storing comments.
Contact information for an individual that is associated with a study.
A physical container. There are two types of containers: top level and non top level:
- A top level container is one that cannot be contained by any others and is usually for freezers.
- A non top level container can be conained by other containers and is usually for a rack or an N sized well plate.
Used to record comments for an individual container.
How the child containers or specimens within a container are labelled.
Holds the position of this container in its parent container.
Storage containers share common attributes, these attributes are grouped into and defined in a container type. Some containers hold sub-containers, while others hold specimens.
Used to record comments for an individual container type.
Maintains a relationship between a parent container_type and a child container_type.
Maintains a relationship between a container type and the specimen types it can hold.
A caCORE table.
A caCORE table.
A caCORE table.
A caCORE table.
A caCORE table.
A caCORE table.
A caCORE table.
A caCORE table.
A caCORE table.
A caCORE table.
A caCORE table.
A caCORE table.
A caCORE table.
Dispatches allow for specimens to be transferred from one center to another.
Used to record comments for an individual dispatch.
Contains information of which spcimens were contained in an individual dispatch.
Used to record comments for an individual specimen in a dispatch.
Some specimens are annotated with DNA lab results data. This is the annotation data.
Stanford nor CBSR currently store this type of information.
This table is used to track permission information for individual users or user groups. A domain can apply to sets of centers and studies or ALL centers and / or all studies.
When a domain applies to a set of centers, an rows in this table will specify which centers.
When a domain applies to a set of studies, an rows in this table will specify which centers.
This table is used by the Biobank Advanced Reports feature.
This information does not need to be imported.
This table is used by the Biobank Advanced Reports feature.
This information does not need to be imported.
This table is used by the Biobank Advanced Reports feature.
This information does not need to be imported.
This table is used by the Biobank Advanced Reports feature.
This information does not need to be imported.
The attribute added to all collection events for a particular study.
Collection events can have user specified annotations. This table is used in conjunction with event_attr_type, global_event_attr, and study_event_attr.
The type of the annotation. It can be one of:
- number
- text
- date_time
- select_single
- select_mutiple
This table is hard coded and the user cannot modify this table.
Collection events can have user specified annotations. This table is used in conjunction with event_attr, global_event_attr, and study_event_attr.
Used for CSV file import of specimens for a patient.
This information does not need to be imported.
Used for CSV file import of specimens for a patient.
This information does not need to be imported.
This table lists all the possible annotations that can be associated with collection_events for a study.
Collection events can have user specified annotations. This table is used in conjunction with event_attr, event_attr_type, and study_event_attr.
Used for user permissions. Specifies which users belong to which groups.
This table is not used at the moment.
Used for generating patient labels.
This information does not need to be imported.
Tracks the activity of individual users.
This information does not need to be imported.
Used for user permissions. Specifies what the actions a group or user is allowed to perform.
Used for user permissions. Specifies the permissions this membership holds.
Used for user permissions. Specifies the roles associated with a membership. See role.
The center where a set of specimens originated from.
A comment a user can attach to an individual origin_info.
The information stored for an individual participant. No identifying information is stored.
A comment a user can attach to an individual patient.
The principal is the base class for a user and group.
Used for printing patient labels.
This information does not need to be imported.
Used for printing patient labels.
This information does not need to be imported.
Information stored when a specimen is processed.
A comment a user can attach to an individual processing_event.
This table is used by the Biobank Advanced Reports feature.
This information does not need to be imported.
This table is used by the Biobank Advanced Reports feature.
This information does not need to be imported.
This table is used by the Biobank Advanced Reports feature.
This information does not need to be imported.
This table is used by the Biobank Advanced Reports feature.
This information does not need to be imported.
This table is used by the Biobank Advanced Reports feature.
This information does not need to be imported.
This table is used by the Biobank Advanced Reports feature.
This information does not need to be imported.
Contains information related to a request for specimens for an individual study.
Contains information related to a request for specimens for an individual study.
This table is used by the Biobank Advanced Reports feature.
This information does not need to be imported.
This table is used by the Biobank Advanced Reports feature.
This information does not need to be imported.
A name given to a set of permissions. A role can then be given to a user group or an individual user.
The individual permissions associated with a role.
This table is used by the Biobank schema upgrade feature.
This information does not need to be imported.
Storage sites can receive shipments containing specimens from collection sites that do not use the Biobank software. This table stores information about the shipment.
The company or method used to send a shipment to a storage site.
An association between a center and a study. Only sites associated with a study can store specimens for a study.
Information about the specimens collected at a collection site for a study.
Information stored for a specimen, aliquot, or derivative.
A comment a user can attach to an individual specimen.
The position within the container this specimen is stored at.
The type of a specimen.
Used to maintain a hierarchy of specimens to aliquots / derivatives.
Defines how specimens are collected and aliquos / derivatives are processed.
A comment a user can attach to an individual study.
Maintains which contacts are associated with a study.
This table lists all the collection event annotations currently selected for a study.
Collection events can have user specified annotations. This table is used in conjunction with event_attr, event_attr_type, and global_event_attr.