Skip to content

Main content

Care Visit Personal Preference Tag Tool

Preserve an explicit care-visit preference and source without inferring care needs or capacity.

Loading tool…

Description

Attach a personal-preference label to a care visit.

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.

Attach a personal-preference label to a care visit.

When to use this tool

Use Care Visit Personal Preference Tag when checking the stated older-adult record, assistance, coverage or care-log convention.

How to use the tool and how it works

  1. Enter visitId, preferenceText, suppliedSource. Use the units and conventions below.
  2. Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
  3. Read token. Use the output convention below.

Require nonempty visit ID, preference text and supplied source. Encode the ordered triple as JSON text.1

Input fieldMeaning and unitsAccepted input
visitIdVisit IdRequired. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192.
preferenceTextPreference TextRequired. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192.
suppliedSourceSupplied SourceRequired. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192.
Output fieldInterpretationReturned shape
tokenJSON-encoded ordered tuple or literal token under the convention above; not a database lookup or authentication result.Required. Text; maximum UTF-16 length 8192.
json
{
  "input": {
    "visitId": "V17",
    "preferenceText": "morning visit",
    "suppliedSource": "self report"
  },
  "output": {
    "token": "[\"V17\",\"morning visit\",\"self report\"]"
  }
}

Limitations and assumptions

  • Preferences are recorded, not authenticated or interpreted as consent; no care decision or suitability assessment occurs.
  • 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

  1. Calculation and input contract: geriatrics/care-visit-personal-preference-tag — tool.io

Similar or alternative tools