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-cancer-disease-status-evidence-type-vs |
Version: | 1.16.0 |
Name: | CancerDiseaseStatusEvidenceTypeVS |
Title: | Cancer Disease Status Evidence Type Value Set |
Status: | Active as of 2021-04-15T12:44:45+00:00 |
Definition: | The type of evidence backing up the clinical determination of cancer progression. |
Publisher: | HL7 International Clinical Interoperability Council |
Copyright: | 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 |
Source Resource: | XML / JSON / Turtle |
References
This value set contains 5 concepts
Expansion based on SNOMED CT United States edition 01-Mar 2021
All codes from system http://snomed.info/sct
Code | Display | Definition |
363679005 | Imaging (procedure) | |
108257001 | Anatomic pathology procedure (procedure) | |
711015009 | Assessment of symptom control (procedure) | |
5880005 | Physical examination procedure (procedure) | |
386344002 | Laboratory data interpretation (procedure) |
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 |