...
Expand | ||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||
Below are the specimen-type properties
|
...
From v11.0, you can create/update a list of the units you want to use in the system (Extras → Dropdown Manager → Specimen Unit). This list can be used to define specimen quantity/concentration units for specimen class/ type on system/CP level.
Note: After upgrading to v11, all the values present in the specimen type properties for quantity and concentration will be added to this list automatically.
Expand | ||
---|---|---|
| ||
|
Specimen Units (Define specimen class/ CP specific units)
From v11.0, 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 ‘ul’ vs ml ‘ml’ as units for fluids like serum/ plasma or capture quantity of DNA or RNA in ‘ul’ vs ‘ug’. With this feature, users can keep have the ability to configure the units specific per to each specimen type within one a single collection protocol.
Expand | ||
---|---|---|
| ||
Configure specimen quantity/ concentration units using the UISystem-level
CP level
Specimen Class Units
Specimen Type Units
CP levelThere are 2 methods to add the CP specific units
|
Working with units for live clients
From v11.0 onwards, the system will automatically pick all the specimen units defined at individual specimen levels in specimen units (CP 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. 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 applies to all the specimens of that type.