Description
Record the source of a contact-priority code in a care plan.
Older-adult care records combine preferences, respondent roles, assistance, handoffs, services and medication-list text. Recorded coverage hours differ from adequate care, and a textual medication match differs from clinical medication reconciliation. Consent and proxy authority are contextual questions that a supplied flag cannot settle.
Record the source of a contact-priority code in a care plan.
When to use this tool
Use Care Plan Contact Priority Source Token when checking the stated older-adult record, assistance, coverage or care-log convention.
How to use the tool and how it works
- Enter carePlanId, contactId, priorityText, sourceId. 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.
Require nonempty care-plan, contact, priority-text and source IDs. Encode the ordered quadruple as JSON text.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| carePlanId | Care Plan Id | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| contactId | Contact Id | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| priorityText | Priority Text | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| sourceId | Literal source identifier, not a retrieved or verified document. | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| token | JSON-encoded ordered tuple or literal token under the convention above; not a database lookup or authentication result. | Required. Text; maximum UTF-16 length 8192. |
{
"input": {
"carePlanId": "P17",
"contactId": "C4",
"priorityText": "first",
"sourceId": "S2"
},
"output": {
"token": "[\"P17\",\"C4\",\"first\",\"S2\"]"
}
}Limitations and assumptions
- Priority is not ranked or acted upon; contacts, authority and appropriateness of a care-plan decision are not verified.
- 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 verified source records and individual needs with qualified medical/care professionals; use appropriate legal and accessibility assessment for actual authority, services and care decisions.
References
Similar or alternative tools
- Care Visit Personal Preference Tag
Attach a personal-preference label to a care visit.
- Functional Item Proxy Respondent Label
Record the proxy respondent of a functional-assessment item.