Description
Record an explicitly assigned line-of-therapy ordinal and regimen wording.
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 explicitly assigned line-of-therapy ordinal and regimen wording.
When to use this tool
Use Oncology Line Of Therapy Record Token when you already have recordId, recordedLineNumber, regimenWording and need to record an explicitly assigned line-of-therapy ordinal and regimen wording.
How to use the tool and how it works
- Enter recordId, recordedLineNumber, regimenWording. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read token. Use the output convention below.
Enter recordId, recordedLineNumber, regimenWording 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 field | Meaning and units | Accepted input |
|---|---|---|
| recordId | Record Id | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| recordedLineNumber | Recorded Line Number | Required. Safe integer; minimum 1. |
| regimenWording | Regimen Wording | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| token | Token | Required. Text; maximum UTF-16 length 8192. |
{
"input": {
"recordId": "R17",
"recordedLineNumber": 2,
"regimenWording": "Regimen A"
},
"output": {
"token": "[\"R17\",2,\"Regimen A\"]"
}
}Limitations and assumptions
- The result records supplied values without determining treatment sequence. 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.
- 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 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
Similar or alternative tools
- Cancer Registry Topography Source Key
Qualify a supplied cancer-registry topography code by its source.
- Tumor Board Action Owner Label
Record an explicit tumor-board action owner.