Table of Contents | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Introduction
‘Specimen Type’ is the most an important and specialized dropdown. Each specimen type corresponds belongs to a 'Specimen class,' such as Fluid, Molecular, Tissue, Cell, and others. In the recent updatesversions, OpenSpecimen has begun incorporating several frequently requested implemented customizations, like the ability to create custom specimen classes and support for multiple specimen units per specimen type per Collection Protocol."
Create a custom ‘Specimen Class’
Before v10.3, only 4 specimen class classes (Fluid, Molecular, Tissue, and Cell) were supported. From v10.3 onwards you can add different specimen class classes like plants, microbes, etc. depending on your requirementrequirements.
Expand | ||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| You can now
| classes from v10.3 onwards
| ||||||||||||||
Below are the specimen-type properties
|
Specimen Units (Dropdown)
From v11.x0 onwards, you can define a list of Units which configure the units you want to use in the system. You can use the units defined in this dropdown to define specimen quantity/concentration units for specimen class/ type on system/CP level.
Specimen Units (Define specimen class/ CP specific units)
From v11.x0, OpenSpecimen supports specimen units per CP. A common issue for clients with multiple groups was to make units uniform across the collection protocols. E.g., some groups wanted to use ul vs ml as units for fluids like serum/ plasma. With this feature, users will be able to can keep the units specific per specimen type within one collection protocol.
Expand | ||
---|---|---|
| ||
Configure specimen quantity/ concentration units using the UISystem-level
CP level
|
Working with units for live clients
With From v11.x upgrade, 0 onwards the system will automatically pick up all the specimen units defined at individual specimen level levels in specimen units (dropdown as well as the Extras cardCP or system level). Manual intervention is not required.
If units are updated after specimens are collected, then the existing specimens won't be automatically recalculated. E.g.For example, if blood is changed from ml to μL, then the system won't change the values proportionately to μL. 1 ml won’t be updated to 1000 μL automatically. Users will have to change it manually via bulk upload.
Display the unit using the following logic:
Use the units specified either at the CP level or system level using the following fallback mechanisms: (cp, class, type) -> (cp, class, *) -> (*, class, type) -> (*, class, *)
where * represents all of that category
E.g., (cp, class, *): All specimen types of a given class for a specific CP.When specimen type is changed, use the units specified either at the CP or system level for the selected type/class using the above mechanism.
There is no support for displaying specimen units in the query results view nor in the query exported CSV
Units are not stored with the specimen or specimen requirements. Their units are auto-computed based on what is configured either at the system or CP level
There is no mechanism to allow the lab user to override the units for any particular or selected specimens. Any update to the unit is applicable applies to all the specimens of that type.