Description
Calculate finding response coverage share 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 finding response coverage share from explicit caller-supplied inputs.
When to use this tool
Use it for finding response coverage share when the required inputs and conventions are already available.
How to use the tool and how it works
- Enter findingIds, responseFindingIds. Keep parallel arrays aligned and use the stated units and conventions.
- Run the calculation. Correct any input error before interpreting a result.
- Read coveredFindings, totalFindings, share, defined. Inspect any known, defined, inclusion, or boundary flags before interpreting numeric values.
Deduplicate findingIds for totalFindings, count distinct findings occurring in responseFindingIds, and divide coveredFindings by totalFindings. Return share zero with defined false when there are no findings.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| findingIds | Finding Ids | Required. Array of Text; maximum UTF-16 length 8192.; maximum items 256. |
| responseFindingIds | Response Finding Ids | Required. Array of Text; maximum UTF-16 length 8192.; maximum items 256. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| coveredFindings | Covered Findings | Required. Safe integer. |
| totalFindings | Total Findings | Required. Safe integer. |
| share | Dimensionless fraction using the denominator described above; not a percentage numeral. | Required. Finite number. |
| defined | Whether the associated denominator or quantity is defined; read this before interpreting a zero placeholder. | Required. Boolean. |
{
"input": {
"findingIds": [
"a",
"b",
"b"
],
"responseFindingIds": [
"b"
]
},
"output": {
"coveredFindings": 1,
"totalFindings": 2,
"share": 0.5,
"defined": true
}
}Limitations and assumptions
- A linked response counts as coverage regardless of content or approval. Extra response identifiers are ignored, and duplicates cannot increase coverage.
- 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 finding response coverage share, 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.
- CAPA Response Unknown Clock Token
Preserve missing administrative response clocks with explicit definition flags.