Skip to content

Main content

Utility Observation Death Boundary Tag Tool

Classify supplied utility-observation timing against an explicit death-time boundary policy without assigning utility values or vital status.

Loading tool…

Description

Check an observation's time against a supplied death boundary and equality convention.

Health-economic accounting distinguishes evaluation perspective, reference years, utility tariffs, timing and allocated costs. Missing resource use differs from measured zero, and a caller-supplied weight differs from a validated model correction. One cost or budget contribution does not establish cost effectiveness or an appropriate allocation of care.

Check an observation's time against a supplied death boundary and equality convention.

When to use this tool

Use Utility Observation Death Boundary Tag when checking the stated supplied health-economic record, timing or allocation convention.

How to use the tool and how it works

  1. Enter observationTime, suppliedDeathTime, boundaryCountsAsAfter. 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 afterBoundary. Inspect afterBoundary before interpreting the associated values.

Compare observationTime with suppliedDeathTime. afterBoundary means strictly later, including equality only when boundaryCountsAsAfter=true.1

Input fieldMeaning and unitsAccepted input
observationTimeObservation TimeRequired. Finite number.
suppliedDeathTimeSupplied Death TimeRequired. Finite number.
boundaryCountsAsAfterBoundary Counts As AfterRequired. Boolean.
Output fieldInterpretationReturned shape
afterBoundaryAfter BoundaryRequired. Boolean.
json
{
  "input": {
    "observationTime": 10,
    "suppliedDeathTime": 10,
    "boundaryCountsAsAfter": true
  },
  "output": {
    "afterBoundary": true
  }
}

Limitations and assumptions

  • Time coordinates are supplied and may be signed; no death record, mortality outcome or appropriate utility convention is inferred.
  • 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

Use a complete justified economic model, verified sources and qualified health-economic/financial assessment for real policy or care-allocation decisions.

References

  1. Calculation and input contract: health-economics/utility-observation-death-boundary-tag — tool.io

Similar or alternative tools