Skip to content

Main content

Oncology Outcome Event Date Token

Record an explicit oncology event code and date without adjudicating an outcome.

Loading tool…

Description

Pair a recorded oncology outcome-event code with a validated calendar date.

Oncology records distinguish individual lesion measurements, missingness reasons, source coding, visit timing and assigned treatment-line labels. A signed axis change is not automatically a response category or stage. Clinical endpoints and regimen records require their verified definitions; local arithmetic and transcription do not determine diagnosis, outcome or treatment.

Pair a recorded oncology outcome-event code with a validated calendar date.

When to use this tool

Use Oncology Outcome Event Date Token when you already have participantId, recordedEventCode, eventDate and need to pair a recorded oncology outcome-event code with a validated calendar date.

How to use the tool and how it works

  1. Enter participantId, recordedEventCode, eventDate. 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 participantId/eventCode nonempty and a real UTC YYYY-MM-DD eventDate; encode [participantId,recordedEventCode,eventDate] as JSON text.1

Input fieldMeaning and unitsAccepted input
participantIdParticipant IdRequired. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192.
recordedEventCodeRecorded Event CodeRequired. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192.
eventDateEvent DateRequired. Text; maximum UTF-16 length 8192. Real proleptic Gregorian YYYY-MM-DD; four-digit years 0000-9999 accepted.
Output fieldInterpretationReturned shape
tokenTokenRequired. Text; maximum UTF-16 length 8192.
json
{
  "input": {
    "participantId": "P17",
    "recordedEventCode": "EVENT-A",
    "eventDate": "2026-11-01"
  },
  "output": {
    "token": "[\"P17\",\"EVENT-A\",\"2026-11-01\"]"
  }
}

Limitations and assumptions

  • A valid date and token do not establish an actual event, survival endpoint, diagnosis or causal outcome.
  • 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 the complete source-defined lesion, registry and outcome criteria with verified records for an assessment. Keep missingness reasons, measurement axes and assigned treatment-line wording explicit; a single signed dimension change or event-date token does not establish response or stage.

References

  1. Calculation and input contract: oncology/oncology-outcome-event-date-token — tool.io

Similar or alternative tools