Skip to content

Main content

Aging Panel Death Date Precision Code Tool

Preserve explicitly supplied aging-panel death-date transcription and precision without constructing a date or verifying vital status.

Loading tool…

Description

Attach a declared precision code to a recorded death date.

Aging research distinguishes participant and informant identities, calendar-month coordinates, time-use exposure and event/censoring status. Proxy responses and missing codes carry different meanings from direct observations. Local record summaries do not establish lifespan, legal status, accessibility or appropriate care.

Attach a declared precision code to a recorded death date.

When to use this tool

Use Aging Panel Death Date Precision Code when checking the stated aging-study record, timing, censoring or support convention.

How to use the tool and how it works

  1. Enter participantId, deathDateText, suppliedPrecision. 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 participant ID, death-date text and supplied precision wording. Encode the ordered triple as JSON text.1

Input fieldMeaning and unitsAccepted input
participantIdParticipant IdRequired. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192.
deathDateTextDeath Date TextRequired. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192.
suppliedPrecisionNonempty declared wording, not a validated date-precision vocabulary.Required. 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": {
    "participantId": "P17",
    "deathDateText": "2025-10",
    "suppliedPrecision": "month"
  },
  "output": {
    "token": "[\"P17\",\"2025-10\",\"month\"]"
  }
}

Limitations and assumptions

  • Date text and precision are not parsed or validated; no death record, event timing or mortality estimate is established.
  • 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

Use verified original records and suitable complete research methods; involve qualified health, accessibility or legal professionals for actual care or rights decisions.

References

  1. Calculation and input contract: gerontology/aging-panel-death-date-precision-code — tool.io

Similar or alternative tools