Description
Qualify an explicit missing eligibility-evidence code by source.
Support records distinguish a person's stated preferences from eligibility decisions, service delivery and permission to disclose data. A normalized goal weight describes a declared weighting system, while a voucher or referral time margin describes supplied bookkeeping. Labels and display masks do not establish safety, valid consent, appropriate priority or actual entitlement.
Qualify an explicit missing eligibility-evidence code by source.
When to use this tool
Use Service Eligibility Evidence Missing Code when you already have recordId, suppliedMissingCode, ruleSource and need to qualify an explicit missing eligibility-evidence code by source.
How to use the tool and how it works
- Enter recordId, suppliedMissingCode, ruleSource. 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 recordId, suppliedMissingCode, ruleSource 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 |
|---|---|---|
| recordId | Record Id | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| suppliedMissingCode | Supplied Missing Code | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| ruleSource | Rule Source | 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": {
"recordId": "R17",
"suppliedMissingCode": "EVID2",
"ruleSource": "Policy A"
},
"output": {
"token": "[\"R17\",\"EVID2\",\"Policy A\"]"
}
}Limitations and assumptions
- The result records supplied values without deciding service entitlement. 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 person's recorded preferences, governing service criteria and actual referral or voucher records. For disclosure, apply the relevant access controls to the underlying data rather than treating a display mask or recorded permission flag as the whole process.
References
Similar or alternative tools
- Outreach Safe Channel Choice Token
Preserve an explicitly selected outreach channel and preference source.
- Interpreter Request Language Pair
Pair explicit interpreter request language labels.