Description
Calculate deviation discovery report lag term from explicit caller-supplied inputs.
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.
Calculate deviation discovery report lag term from explicit caller-supplied inputs.
When to use this tool
Use it for deviation discovery report lag term when the required inputs and conventions are already available.
How to use the tool and how it works
- Enter eventDay, discoveryDay, reportDay, allowedLag. Use the stated units and boundary conventions.
- Run the calculation. Correct any input error before interpreting a result.
- Read discoveryLag, reportingLag, totalLag, reportWithinLimit. Inspect any known, defined, inclusion, or boundary flags before interpreting numeric values.
Require nonnegative integer allowedLag and eventDay<=discoveryDay<=reportDay. Calculate discoveryLag, reportingLag, totalLag, and reportWithinLimit using reportingLag<=allowedLag.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| eventDay | Event Day | Required. Safe integer. |
| discoveryDay | Discovery Day | Required. Safe integer. |
| reportDay | Report Day | Required. Safe integer. |
| allowedLag | Allowed Lag | Required. Safe integer; minimum 0. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| discoveryLag | Discovery Lag | Required. Safe integer. |
| reportingLag | Reporting Lag | Required. Safe integer. |
| totalLag | Total Lag | Required. Safe integer. |
| reportWithinLimit | Report Within Limit | Required. Boolean. |
{
"input": {
"eventDay": 100,
"discoveryDay": 103,
"reportDay": 105,
"allowedLag": 3
},
"output": {
"discoveryLag": 3,
"reportingLag": 2,
"totalLag": 5,
"reportWithinLimit": true
}
}Limitations and assumptions
- The allowed limit applies from discovery to report, not event to report. Numeric day indices do not implement business-day, holiday, or reporting-authority rules.
- 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 deviation discovery report lag term, 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
- Audit Finding Repeat Source Pair
Check explicit finding recurrence links and category identity.
- Audit Sample Selection Weight One Record
One Horvitz-Thompson contribution from a supplied inclusion probability.