This page is part of the HL7 FHIR Implementation Guide: minimal Common Oncology Data Elements (mCODE) Release 1 - US Realm | STU1 (v2.1.0: STU 2) based on FHIR (HL7® FHIR® Standard) R4. The current version which supersedes this version is 4.0.0. For a full list of available versions, see the Directory of published versions
Official URL: http://hl7.org/fhir/us/mcode/ValueSet/mcode-tnm-primary-tumor-category-vs | Version: 2.1.0 | |||
Active as of 2023-03-21 | Computable Name: TNMPrimaryTumorCategoryVS |
This value set is intended to contain allowable values for the T category, according to TNM staging rules. AJCC codes (preferably, version 8 for current cancers) SHOULD be used.
References
Using AJCC terminology, examples of T categories include ‘ycTX’, used for post-therapy clinical staging if the tumor primary tumor cannot be evaluated, ‘pT0’, denoting there is no evidence of a primary tumor, and ‘pTis’, referencing carcinoma in situ (with some cancer-specific exceptions). Other T categories refer to increasing size of the primary tumor. Please note allowable T categories may vary between clinical, pathologic, and other classifications, and the T category prefix must align with Observation.code. The full set of allowable clinical, pathologic, and other (recurrence/retreatment/autopsy) T categories, along with current descriptions, can be accessed through the AJCC Staging Manual and any applicable updates and corrections, as well as the AJCC API.
http://cancerstaging.org
No Expansion for this valueset (Unknown Code System)
Explanation of the columns that may appear on this page:
Level | A few code lists that FHIR defines are hierarchical - each code is assigned a level. In this scheme, some codes are under other codes, and imply that the code they are under also applies |
System | The source of the definition of the code (when the value set draws in codes defined elsewhere) |
Code | The code (used as the code in the resource instance) |
Display | The display (used in the display element of a Coding). If there is no display, implementers should not simply display the code, but map the concept into their application |
Definition | An explanation of the meaning of the concept |
Comments | Additional notes about how to use the code |