-
-
Notifications
You must be signed in to change notification settings - Fork 152
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Added Limit of Quantification (LOQ) for services and analyses #2682
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
For formal scientific, technical, or regulatory contexts, Limit of Quantification (LOQ) is better choice than Quantification Limit (QL) as it aligns with standard usage and is more widely recognized. LOQ is the term standardized by international organizations such as IUPAC, ISO, and regulatory agencies like the FDA and EPA.
ramonski
approved these changes
Mar 11, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great, thanks for adding this!
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description of the issue/feature this PR addresses
This Pull Request makes possible to define the Limit of Quantification (LOQ)1 for services and analyses, so that:
Detected but < LLOQ
is displayed when the result below the Lower Limit of Quantification (LLOQ), but above the Lower Limit of Detection (LLOD/LDL).Not detected
is displayed when the Lower Limit of Detection (LLOD) is below the Lower Limit of Quantification (LLOQ) and the result is lower than both.< LLOD
is displayed when the Lower Limit of Detection (LLOD) equals to the Limit of Quantification (LLOQ) and the result is lower than both.LOQ
,LLOQ
,ULOQ
,BELOWLOQ
,BELOWLLOQ
,ABOVEULOQ
Current behavior before PR
Is not possible to define the Limit of Quantification (LOQ), but Lower and Upper Limits of Deteciton only.
Desired behavior after PR is merged
Is possible to define the Limit of Quantification (LOQ), along with Lower and Upper Limits of Deteciton only.
--
I confirm I have tested this PR thoroughly and coded it according to PEP8
and Plone's Python styleguide standards.
Footnotes
Term "Quantification Limit" is used as well, with the acronym "QL". However, LOQ is the term standardized by international organizations such as IUPAC, ISO, and regulatory agencies like the FDA and EPA. LOQ is widely used in scientific literature, analytical chemistry and regulatory guidelines as well. Therefore, for formal scientific, technical, or regulatory contexts, LOQ is the better choice, as it aligns with standard usage and is more widely recognized. ↩