This page is part of the HL7 FHIR Implementation Guide: minimal Common Oncology Data Elements (mCODE) Release 1 - US Realm | STU1 (v1.16.0: STU 2 Ballot 1) based on FHIR R4. The current version which supercedes this version is 2.0.0. For a full list of available versions, see the Directory of published versions
Summary
Defining URL: | http://hl7.org/fhir/us/mcode/ValueSet/mcode-tnm-distant-metastases-category-vs |
Version: | 1.16.0 |
Name: | TNMDistantMetastasesCategoryVS |
Title: | TNM Distant Metastases Category Value Set |
Status: | Active as of 2021-04-15T12:44:45+00:00 |
Definition: | This value set is intended to contain allowable values for the M category, according to TNM staging rules. AJCC codes (preferably, version 8 for current cancers) SHOULD be used. |
Publisher: | HL7 International Clinical Interoperability Council |
Source Resource: | XML / JSON / Turtle |
References
In AJCC terminology, examples of M categories include ‘cM0’, denoting there is no evidence of distant metastases, and ‘pM1’, an indication that the cancer has metastasized. Please note allowable M categories may vary between clinical, pathologic, and other classifications, and the M category prefix must align with Observation.code. The full set of allowable clinical, pathologic, and other (recurrence/retreatment/autopsy) M 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 |
Source | 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 |