Description
Check supplied result method/version against an explicitly effective reference.
Quality records separate measured results, reference values, acceptance rules, and supporting evidence. Arithmetic consistency and record coverage can be checked against supplied criteria without establishing traceability, approving a method, or deciding product conformity.
Check supplied result method/version against an explicitly effective reference.
When to use this tool
Use it for qc result method version consistency when the required inputs and conventions are already available.
How to use the tool and how it works
- Enter resultMethod, methodVersion, approvedMethod, approvedVersion, executedDay, effectiveDay. Use the stated units and boundary conventions.
- Run the calculation. Correct any input error before interpreting a result.
- Read methodMatches, versionMatches, effective, consistent. Inspect any known, defined, inclusion, or boundary flags before interpreting numeric values.
Compare resultMethod with approvedMethod and methodVersion with approvedVersion using exact string equality. Test executedDay>=effectiveDay and set consistent only when all three checks hold.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| resultMethod | Result Method | Required. Text; maximum UTF-16 length 8192. |
| methodVersion | Method Version | Required. Text; maximum UTF-16 length 8192. |
| approvedMethod | Approved Method | Required. Text; maximum UTF-16 length 8192. |
| approvedVersion | Approved Version | Required. Text; maximum UTF-16 length 8192. |
| executedDay | Executed Day | Required. Safe integer. |
| effectiveDay | Effective Day | Required. Safe integer. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| methodMatches | Method Matches | Required. Boolean. |
| versionMatches | Version Matches | Required. Boolean. |
| effective | Effective | Required. Boolean. |
| consistent | Consistent | Required. Boolean. |
{
"input": {
"resultMethod": "M1",
"methodVersion": "v2",
"approvedMethod": "M1",
"approvedVersion": "v2",
"executedDay": 110,
"effectiveDay": 100
},
"output": {
"methodMatches": true,
"versionMatches": true,
"effective": true,
"consistent": true
}
}Limitations and assumptions
- This does not order version strings, authenticate an approval, or test an end-of-validity date. Day indices require a common origin and calendar convention.
- The field tables describe structural bounds; the mechanics also state cross-field requirements. Malformed input shapes, disallowed keys, and invalid domains cause input errors. Results must remain finite and within the declared output contract. A successful false flag or zero placeholder is distinct from an error.
- Numeric arithmetic uses binary floating point. Exact comparisons have no hidden tolerance or decimal rounding; negative zero is exported as zero. Decimal-text integer operations retain the exactness specifically stated above.
Alternative or Complementary methods
For qc result method version consistency, check the source records and the supplied rule before comparing the result with another method. Use a separate evidence or method review when arithmetic consistency alone cannot establish the required conclusion.
References
Similar or alternative tools
- QC Result Rounding Closure Token
Inspect a supplied nearest-rounding interval and tie endpoint convention without rerounding an assay result.
- QC Analyst Replicate Weight Term
Inverse-variance replicate combination under supplied independent standard uncertainties.