Skip to content

Main content

Mental Health Goal User Priority

Record a user-supplied goal priority on explicit scale bounds without inferring urgency or a clinical priority.

Loading tool…

Description

Normalize a user-stated goal priority within supplied scale endpoints.

Mental-health records preserve instrument versions, recall wording, reporter roles, unknown responses and a person's own priorities. A missing code differs from a symptom rating, and a normalized preference is a scale position rather than a clinical urgency score. Recording these values does not assess mental state, diagnose a condition or choose care.

Normalize a user-stated goal priority within supplied scale endpoints.

When to use this tool

Use Mental Health Goal User Priority when you already have goalId, userPriority, scaleMinimum, scaleMaximum and need to normalize a user-stated goal priority within supplied scale endpoints.

How to use the tool and how it works

  1. Enter goalId, userPriority, scaleMinimum, scaleMaximum. 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 label, normalizedPosition. Use the output convention below.

Require maximum>minimum and rating in [minimum,maximum]; return (priority-minimum)/(maximum-minimum) and preserve the raw priority label.1

Input fieldMeaning and unitsAccepted input
goalIdGoal IdRequired. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192.
userPriorityUser PriorityRequired. Finite number.
scaleMinimumScale MinimumRequired. Finite number.
scaleMaximumScale MaximumRequired. Finite number.
Output fieldInterpretationReturned shape
labelLabelRequired. Text; maximum UTF-16 length 8192.
normalizedPosition(userPriority-min)/(max-min), a scale coordinate rather than a clinical score.Required. Finite number.
json
{
  "input": {
    "goalId": "G17",
    "userPriority": 4,
    "scaleMinimum": 1,
    "scaleMaximum": 5
  },
  "output": {
    "label": "G17; user priority=4",
    "normalizedPosition": 0.75
  }
}

Limitations and assumptions

  • Normalization preserves a stated scale position, not clinical urgency, treatment value or comparison across different scales.
  • 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.
  • Numeric calculations use binary floating point unless exact decimal-integer arithmetic is explicitly stated. No hidden measurement tolerance or decimal rounding is added; nonfinite or out-of-contract results are rejected. Numeric signed-zero results are exported as zero.

Alternative or Complementary methods

Consult the original instrument, language/version and reporter context for any substantive assessment. Preserve missing responses and user-selected goals explicitly; use the instrument's complete scoring process rather than treating one label or normalized preference as a clinical score.

References

  1. Calculation and input contract: psychiatry/mental-health-goal-user-priority — tool.io

Similar or alternative tools