Skip to content

Main content

Tumor Board Action Owner Label

Record an explicit tumor-board action owner without generating recommendations or assigning responsibility.

Loading tool…

Description

Record an explicit tumor-board action owner.

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.

Record an explicit tumor-board action owner.

When to use this tool

Use Tumor Board Action Owner Label when you already have meetingId, actionId, recordedOwner and need to record an explicit tumor-board action owner.

How to use the tool and how it works

  1. Enter meetingId, actionId, recordedOwner. 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.

Enter meetingId, actionId, recordedOwner using the field constraints below. Encode these values, in exactly that order, as a JSON array and return the serialized array as text in token. String values are preserved without trimming or external terminology lookup.1

Input fieldMeaning and unitsAccepted input
meetingIdMeeting IdRequired. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192.
actionIdAction IdRequired. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192.
recordedOwnerRecorded OwnerRequired. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192.
Output fieldInterpretationReturned shape
tokenTokenRequired. Text; maximum UTF-16 length 8192.
json
{
  "input": {
    "meetingId": "TB17",
    "actionId": "ACTION3",
    "recordedOwner": "Team A"
  },
  "output": {
    "token": "[\"TB17\",\"ACTION3\",\"Team A\"]"
  }
}

Limitations and assumptions

  • The result records supplied values without generating recommendations or assigning responsibility. Sources and asserted relationships are not independently authenticated.
  • 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/tumor-board-action-owner-label — tool.io

Similar or alternative tools