What a specimen record holds
Each specimen has an ID, a type such as plasma or DNA, and a storage location. It can also hold a study code, a participant code, a visit or time point, the collection date, an amount and unit, the label on the tube, use restrictions, and notes.
Leave the ID empty and the app numbers specimens S-000001, S-000002, and so on. To keep the IDs already on your tubes, type them in, up to 80 characters. Each ID must be unique in a workspace, and PL-001 and pl-001 count as the same ID. IDs in the form S-000123 are reserved for the app's own numbering.
A specimen is Stored, Checked out, Shipped, Used up, Destroyed, or Entered in error. Its record and its custody log are kept in every status, and no specimen is ever deleted.
Boxes with positions
On the Locations page, add or edit a location of the type Box and choose its positions: 9 by 9 (81 positions), 10 by 10, 8 by 12, 5 by 5, or another size up to 26 rows and 48 columns. Rows are lettered from A and columns are numbered from 1, so the first position is A1.
The box's page shows a map of its positions. Each position is free, holds a stored specimen, or is reserved for a checked-out specimen. In a core facility, a researcher sees their own specimens on the map, and other labs' positions show as taken.
Specimens fill a box's free positions in order, row by row, from A1 or from the first position you choose. If the box has fewer free positions than there are specimens, nothing is saved, and the message says how many positions are free.
Two specimens never share a position. A checked-out specimen keeps its position until it is returned. While a box holds specimens, its type cannot change, and it cannot shrink below the rows and columns in use. A location that holds stored or checked-out specimens cannot be archived.
Shelves, racks, and other locations without positions can hold specimens too.
Register specimens
- Open Specimens and choose Register specimens. On a box's page, choose Register specimens here to open the same form with that box chosen.
- Choose where the specimens are stored. In a box, you can give one specimen its position, or give many the first position to fill.
- Enter one specimen, or choose Up to 500 from a spreadsheet to paste rows or upload a CSV file.
- Choose Register.
A spreadsheet starts with a header row. The form reads the columns ID, Type, Study, Participant, Visit, Collected on, Amount, Unit, Label on the tube, Use restrictions, Notes, and Position, and common other names for them, such as Specimen ID or Volume. Only Type is required. Leave Position empty to fill the box in order. Choose Download a template for a file with every column.
Every row is checked before anything is saved. If a value needs a correction, nothing is saved, and the form lists each row and value to fix.
In a core facility, staff can name the lab and the depositor that the specimens belong to. The depositor and the lab's members can then see them.
Check a shipment against its sample list
When the tubes for a request arrive, the staff of its service check them against the request's sample list. The workspace's owners, admins, and managers can too. On the request, choose Check against the list, scan or type each tube's label on its own line, and choose Check labels.
Each label matches a sample by the code the app printed on the sample label, such as SR-0042-003, or by the sample's name on the list. Case and extra spaces are ignored. If two samples on the list share a name, tubes with that name go to them in list order, starting with samples not yet received.
Nothing is saved yet. The check lists the samples matched, the samples already received, the labels not on the list, the labels read more than once, and the samples not received. If a tube's label is not on the list but you know which sample it is, choose that sample beside the label. If a label read more than once really is on two or more tubes, select it.
Choose Save check. The matched samples, and the samples you chose beside a label, are marked Received. Saving also opens one issue for each kind of problem found:
| Issue | What it lists |
|---|---|
| Not on the list | The labels read on tubes that match no sample, unless you chose a sample for them. |
| Mislabeled | Each label you chose a sample for, and each label on two or more tubes. |
| Missing | The samples not received, if you select No more samples are coming. A sample already on an open Missing issue stays on that issue. |
| Damaged | What you write under Problem with the shipment, such as a box that arrived thawed. |
Owner of the issues starts as the request's assignee, or you when the request has no assignee. The owner is emailed unless it is you. The requester gets one email listing each new issue's number, kind, and summary, and can read the issues and add notes on the request.
When a later check marks a missing sample Received, the issue's history records it. Once every sample on the issue is Received, the issue is resolved and the requester is emailed. If the request's samples changed after the check was shown, nothing is saved, and the check runs again with the same labels. The request's history lists each check with the number of labels read, the samples received, and the issues opened.
Store the samples from a request
Once a request is approved, the managers and staff of its service's facility, and the workspace's owners, admins, and managers, can store its samples. On the request, they choose Store as specimens, then a box, the first position, and the specimen type. Each sample marked Received or Done is stored as a specimen in the next free position. To store only some samples, select them first.
Each specimen keeps its sample's label and names the requester as its depositor. The requester then sees each specimen's ID and position on the request. When you store a sample that is on an issue, its specimen is added to that issue. The specimen's page lists the issue, and while the issue is open, the Specimens list shows On an open issue under the specimen's status. Each sample can be stored only once, unless its specimen is marked entered in error.
Move, check out, ship, and aliquot
Select specimens in the list or on a box map, then choose what to do. Specimens chosen together must all have a status that allows the action. For example, only stored specimens can be moved.
| Action | What it records |
|---|---|
| Move | A new location, or new positions in a box, filled from the first position you choose. Only stored specimens move. |
| Check out | Who has the specimen, or where it is. Its position is reserved until it is returned. |
| Return | The specimen back at the position it was checked out from, or at another location. |
| Record a thaw | One more freeze-thaw cycle for each specimen. |
| Make aliquots | From 1 to 96 new specimens from one, with IDs such as S-000004-01. They go to the parent’s location or another you choose, in a box’s next free positions. Each keeps the parent’s study, participant, visit, use restrictions, depositor, and lab. The parent can be marked used up. |
| Ship | Where the specimen is going. Its position is freed. |
| Mark used up | That the specimen was used. Its position is freed. |
| Destroy | The reason, such as consent withdrawn. Its position is freed. |
| Mark entered in error | A specimen registered by mistake, with the reason. Its position is freed. |
| Edit | A correction to the specimen’s facts. The log keeps each changed value before and after. |
In a research lab, members, managers, admins, and owners can update specimen records, and viewers can see them. In a core facility, the workspace's owners, admins, and managers and each facility's managers and staff can update specimen records. Auditors see every specimen. Researchers see the specimens they deposited and the specimens that belong to their lab.
Release specimens to researchers
A specimen request lists the specimens to release. A specimen can be on one open request at a time. When that request is completed, cancelled, or rejected, any of its specimens still stored or checked out can go on another request.
A researcher selects their specimens on the Specimens page and chooses Request these. A new request opens with those specimens listed, and with the core's specimen release service chosen if it has one. A specimen already on another open request is left off, and the form names it.
Staff can add specimens to any open request for a service they work on. On the request, they choose Add specimens and paste specimen IDs or tube labels, one per line, or choose Use the sample list to paste in the request's samples. On the Specimens page, they can select specimens and choose Add to a request.
Each line can be a specimen ID or a tube label. If a line matches nothing, or its tube label is on more than one stored or checked-out specimen, nothing is added and the message names the lines to fix. A paste can hold up to 500 lines, and a request can list up to 500 specimens.
Before approving, staff check each specimen's use restrictions against the requester's stated use. They also see each specimen's study and visit, participant code, storage location, and depositor. The requester sees each specimen's ID, type, study and visit, amount, use restrictions, and status, but not its participant code, storage location, or depositor. The requester agrees to the terms of use by signing the service's statements when they send the request.
After the core approves the request, staff work through its Specimens to release list. Pulling and shipping apply to every specimen on the list, or only to the ones staff select first.
| Step | What happens |
|---|---|
| Pick list | A printable list of the stored and checked-out specimens, grouped by box in position order, with each tube label, to tick off as you pull them. |
| Pull from storage | Once the tubes are out, records each stored specimen on the request as checked out, with the note Pulled for SR-0042. Each keeps its position until it ships. |
| Manifest | A printable shipping manifest listing each specimen and its tube label, with lines for the packer and the receiver to sign. Tick Participant codes to print them. |
| Ship or hand over | Once the specimens have gone, records each one as shipped, with where it went or who picked it up, and frees its position. The form suggests the request’s shipping address or, for a pickup, Picked up by and the requester’s name. |
| Take off the request | The selected specimens leave the request. A pulled specimen stays checked out until staff return it. A shipped specimen can’t be taken off: it stays on the request as its record. |
Each specimen's custody log names the request in its checked-out and shipped entries. The request's history, which the core sees, lists each step with who took it.
Show available specimens on the public page
Your core's public page can show researchers how many stored specimens they can request from each study, by type and visit. A researcher who finds what they need chooses Request on that row to ask for the specimens. This list is the sample explorer. It is off until you turn it on.
- Turn on Specimens in Settings, under Branding and menu.
- In Settings, under Public page, tick Show the studies chosen below on the public page.
- Tick each study to show. Settings lists every study that has specimens in the core, by study code, with the number available in each. Give a study a public name and a short description if you like. A study with no public name shows by its code.
- Look over What visitors see, then choose Save public page.
The public page then has a Specimens section. Each chosen study has a row for each type and visit, with the number available. A specimen counts as available while it is stored and not on an open request. A checked-out specimen does not count until it is returned. The explorer ignores capitals and extra spaces, so Plasma and plasma count as one type. Each row uses the spelling most of its specimens have. Specimens with no visit are counted under Not recorded.
A count under 5 shows as Fewer than 5. The page shows no totals for a study or a type, so no one can work out a small count by subtraction. Participant codes, specimen IDs, tube labels, storage locations, collection dates, amounts, depositors, labs, use restrictions, and notes never show. A study with no specimens available says None available right now.
A visitor who chooses Request signs in or creates an account first. If they are already a member of the core, they choose Start the specimen request. A new request opens with its title and first sample filled in from the row. If the core has a specimen release service, the request starts on that service. Anyone else asks for access to the core, and their note to the manager already names the specimens. Once a manager approves them, the researcher sends the request from the core's Requests page.
The requester adds a line under Samples for each specimen they need, says what the specimens are for, and sends the request. Staff then choose the specimens and add them to the request, as described in Release specimens to researchers.
On the Publications page, each publication can have a plain-language summary of two or three sentences. It shows under the publication on the public page. Under Specimens from these studies, managers can also tick the studies that supplied the publication's specimens. Studies left out of the sample explorer stay hidden. The public page names a ticked study only while the sample explorer shows it, and members who are not managers see its link only once the study is chosen for the explorer.
When a participant withdraws consent
On the Specimens page, staff who can edit specimens choose Consent withdrawal and enter the participant code, and the study code if they know it. The app lists every specimen with that participant code, including aliquots made from them. P-002 and p-002 count as the same code.
When the code appears in more than one study, the app asks which study the withdrawal is for, with a choice for specimens that have no study.
The list shows the stored and checked-out specimens to destroy, in pull order. It also shows the specimens that already left storage, with where each went and the request it was released on. Below that are any open requests that include this participant's specimens.
The reason is filled in as Consent withdrawn. Under Who reported it, and when, enter who told the core and the date.
Pull and destroy the specimens in the order listed, then choose Record 3 as destroyed to record them all at once. Each one gets a destroyed entry in its custody log with the reason, who reported it, and the participant code, and its position is freed. If the specimens changed after the list was shown, nothing is recorded, and the list loads again.
The list keeps showing where each shipped specimen went, so the core can notify the recipients.
Track and resolve issues
An issue records one problem with samples or specimens, such as a sample that never arrived or a specimen missing from its box. Each issue has a number (such as Issue 3), a kind, a one-line summary of what is wrong, and, if you add it, what was found.
| Kind | What it covers |
|---|---|
| Missing | On the list or in the records, and not found. |
| Not on the list | Arrived, and not on the depositor’s list. |
| Mislabeled | The label differs from the list or the record. |
| Wrong place | Sent or put in the wrong place. |
| Damaged | Broken, leaking, or thawed. |
| Data mismatch | The tube, the list, and the record disagree, such as on the visit. |
| Other | Anything else. |
| Who | What they can do |
|---|---|
| Staff: the people who update specimen records | See every issue. Report issues, add notes, change the owner, resolve, and reopen. In a core, they can also add staff-only notes. |
| Auditors in a core, and viewers in a research lab | See every issue, including staff-only notes. They change nothing and add no notes. |
| Researchers in a core | See the issues on requests they made and the issues that list their own or their lab’s specimens. They add notes, and report issues on their own requests. |
On an issue, a researcher sees only their own and their lab's specimens, and those on their requests, without participant codes or storage locations. They also read the issue's summary, what was found, and its notes, except staff-only notes. Keep participant codes and storage locations in staff-only notes.
Staff report an issue on the specimens they select on the Specimens page, or from a specimen's page. On a request, the staff of its service report an issue on the whole request or on the samples they select. Staff choose the owner, who is emailed unless it is the person reporting.
A requester can report an issue on a request they made, but only on the whole request. The request's assignee owns it and is emailed. When the request has no assignee, the issue has no owner, and the staff of the request's service are emailed.
The Issues view on the Specimens page lists open issues, newest first, and filters by status, kind, and owner. Staff and auditors in a core, and everyone in a research lab, can download the list as CSV, up to 20,000 issues. As with the specimen list, the activity log records each download with its number of rows and the file's SHA-256 digest.
An issue's page shows its request, samples, specimens, and history. An issue opened on a sample that is already stored also lists the sample's specimen. Resolving an issue means saying what was done. Reopening one needs a reason, and the history keeps the earlier resolution.
An issue never changes a specimen. To move or destroy one, use Move or Destroy on its page. A sample or specimen on an open issue says so beside its status.
The owner can be one of the staff, the requester of the issue's request, or a depositor of one of its specimens. An issue can also have no owner, and the owner filter can show only those. The owner and the person who reported the issue are emailed when someone else adds a note, resolves the issue, or reopens it. After a check against the list, the requester is emailed the issues it opened and resolved. Staff-only notes are emailed only to staff. Email subjects show only the request number, issue numbers, and an issue's kind, never a sample name or a tube label.
The database refuses to delete an issue, or to change or delete an entry in its history.
The custody log
A specimen's page lists every change to it, oldest first: registered, moved, checked out, returned, thawed, aliquoted, shipped, used up, destroyed, marked entered in error, and edited. Each entry records who made the change, when, and the locations the specimen moved from and to.
The database refuses to edit or delete a log entry, and it refuses to delete a specimen record. As a second check, each entry carries a SHA-256 digest of its contents and of the entry before it, so a change made directly in the database shows. The specimen's page recomputes every digest when it opens and names the first entry that no longer matches.
Labels and downloads
Select up to 100 specimens and choose Print labels. Each label shows the specimen's ID, type, study, participant, and visit, with a QR code that opens the specimen's page. The page opens only after the person signs in, and only for someone who can see that specimen.
Choose Download this list as CSV to save the specimens that the filters show, up to 20,000. The workspace's activity log records each download with its number of rows and the file's SHA-256 digest, so you can later check that a file is the one downloaded.