Description
Qualify a supplied cancer-registry topography code by its source.
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.
Qualify a supplied cancer-registry topography code by its source.
When to use this tool
Use Cancer Registry Topography Source Key when you already have registryRecordId, topographyCode, codingSource and need to qualify a supplied cancer-registry topography code by its source.
How to use the tool and how it works
- Enter registryRecordId, topographyCode, codingSource. 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 registryRecordId, topographyCode, codingSource 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 |
|---|---|---|
| registryRecordId | Registry Record Id | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| topographyCode | Topography Code | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| codingSource | Coding Source | 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": {
"registryRecordId": "R17",
"topographyCode": "CODE-A",
"codingSource": "Registry manual v2"
},
"output": {
"token": "[\"R17\",\"CODE-A\",\"Registry manual v2\"]"
}
}Limitations and assumptions
- The result records supplied values without assigning cancer site or validating coding. 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
Similar or alternative tools
- Oncology Line Of Therapy Record Token
Record an explicitly assigned line-of-therapy ordinal and regimen wording.
- Tumor Board Action Owner Label
Record an explicit tumor-board action owner.