Leave a comment at the end of this page or email contact@krishagni.com
Label Configuration
Introduction
Labels uniquely identify an object, like Participant, Visit, Specimen, etc. Labels can be either manually entered by users or auto-generated by OpenSpecimen.
OpenSpecimen supports auto-generation of labels for fields such as:
Participant Protocol ID (PPID)
Visit Name
Specimen Label
These formats can be configured at either the system level (global setting) or at the collection protocol (CP) level.
When to auto-generate labels vs enter manually?
Scenario | Recommended | Reason |
|---|---|---|
Specimens are labeled at the time of collection | Auto-generate | Generates labels based on pre-defined rules. Reduces human error, increases efficiency, and ensures consistency. |
Specimens arrive pre-labeled (e.g., from an external lab) | Enter Manually | OpenSpecimen labels must match existing physical labels |
Legacy Data Migration Data entry done from Excel/paper forms | Enter Manually | Labels are already defined and must be kept as it is |
What is a token?
A label is configured using multiple "tokens". Each token represents the value of a field. E.g., event label, specimen type abbreviation, visit date, CP Code, etc.
How to define a label?
A format can be defined using one or more tokens or fixed text. Users can generate different label formats using permutations and combinations of tokens.
It is essential to ensure that the format results in a unique label.
If the format produces duplicate labels, you will encounter errors during data entry.
The simplest way to ensure uniqueness is to add a UID token.
More Details
Leave a comment at the end of this page or email contact@krishagni.com