Description
Qualify an explicit quality-evidence reference by version.
Quality assurance links actions, evidence, document versions, responsible roles and controlled dates. A recorded closed or approved label differs from verified completion and effectiveness. Due-date margins and missing-training flags organize supplied records while substantive review, competence and applicable quality obligations remain separate questions.
Qualify an explicit quality-evidence reference by version.
When to use this tool
Use Quality Evidence Record Version when you already have actionId, evidenceRecordId, version and need to qualify an explicit quality-evidence reference by version.
How to use the tool and how it works
- Enter actionId, evidenceRecordId, version. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read token. Use the output convention below.
Enter actionId, evidenceRecordId, version using the field constraints below. Encode these values, in exactly that order, as a JSON array and return the serialized array as text in token. String values are preserved without trimming or external terminology lookup.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| actionId | Action Id | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| evidenceRecordId | Evidence Record Id | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| version | Version | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| token | Token | Required. Text; maximum UTF-16 length 8192. |
{
"input": {
"actionId": "ACT17",
"evidenceRecordId": "EV2",
"version": "v2"
},
"output": {
"token": "[\"ACT17\",\"EV2\",\"v2\"]"
}
}Limitations and assumptions
- The result records supplied values without assessing sufficiency. Sources and asserted relationships are not independently authenticated.
- Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.
Alternative or Complementary methods
Review the controlled action, training, agreement and evidence records for actual completion and effectiveness. Reconcile versions, named responsibility and approval history rather than inferring a verified quality status from one marker or calendar gap.
References
Similar or alternative tools
- Quality Complaint Batch Reference
Qualify an explicit complaint by product and batch identifiers.
- Quality Agreement Party Role
Preserve an explicit agreement party-role record.