minimal Common Oncology Data Elements (mCODE) Implementation Guide
3.0.0-ballot - 2023May United States of America flag

This page is part of the HL7 FHIR Implementation Guide: minimal Common Oncology Data Elements (mCODE) Release 1 - US Realm | STU1 (v3.0.0-ballot: STU 3 Ballot 1) based on FHIR R4. The current version which supercedes this version is 2.1.0. For a full list of available versions, see the Directory of published versions

ValueSet: Cancer Disorder Value Set

Official URL: http://hl7.org/fhir/us/mcode/ValueSet/mcode-cancer-disorder-vs Version: 3.0.0-ballot
Active as of 2023-03-28 Maturity Level: 4 Computable Name: CancerDisorderVS

Copyright/Legal: This value set includes content from SNOMED CT, which is copyright © 2002+ International Health Terminology Standards Development Organisation (IHTSDO), and distributed by agreement between IHTSDO and HL7. Implementer use of SNOMED CT is not covered by this agreement

A broad cancer-related value set containing both primary and secondary tumor types, with codes from ICD-10 and SNOMED CT, including both diagnosis and histology/morphology/behavior codes. ICD-O-3 morphology codes may also be used and are considered conformant to the specification. For SNOMED, the value set includes all codes descending from 363346000 ‘Malignant neoplastic disease (disorder)’ and 108369006 ‘Neoplasm (morphologic abnormality)’.

References

Logical Definition (CLD)

This value set includes codes based on the following rules:

 

Expansion

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