minimal Common Oncology Data Elements (mCODE) Implementation Guide
1.16.0 - STU Release 2 (Ballot Version)

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

ValueSet: Treatment Intent Value Set

Summary

Defining URL:http://hl7.org/fhir/us/mcode/ValueSet/mcode-treatment-intent-vs
Version:1.16.0
Name:TreatmentIntentVS
Title:Treatment Intent Value Set
Status:Active as of 2021-04-15T12:44:45+00:00
Definition:

The purpose of a treatment.

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

Usage

Use these terms with the following definitions in mind:

  • Curative is defined as any treatment meant to reduce or control a disease process, even if a ‘cure’ is not anticipated.
  • Palliative treatments are intended to improve the quality of life, typically without concurrent curative treatments. Examples are pain medications or surgery to reduce the size (but not fully remove) a tumor close to the spine that could impact mobility. Palliative care most often refers specifically to end-of-life care.
  • Supportive treatments do not treat or improve the underlying condition, but could extend life or be used in conjunction with curative treatments to improve patient comfort. They could be preventive drugs administered to preemptively manage side effects or toxicities from an anti-neoplastic (e.g.: G-CSFs to manage neutropenia, epoetins for anemia, dexamethasone for delayed nausea and vomiting, etc.). Supportive drugs could also be chemoprotective, or chemo-enhancing, and in some cases even included as part of the regimen even though the drug in itself is not an antineoplastic (e.g.: leucovorin is not an antineoplastic but an chemoprotectant oftentimes combined with the antineoplastics 5-FU and methotrexate).
  • Diagnostic refers to procedures carried out to identify the nature of an illness
  • Preventive refers to treatments designed to keep an illness or harm from occurring.
  • Screening relates to procedures carried out to detect disease in individuals who do not have any symptoms of disease.
  • Guidance relates to education and counselling, such as smoking cessation programs.
  • Forensic in the medical context refers to procedures carried out to determine the cause of death.

These values appear in SNOMED-CT under “Intents (nature of procedure values)” (code 363675004). There are certain terms under the same heading that were not included in this value set:

  • Prophylaxis is essentially synonymous with preventive. See https://en.wikipedia.org/wiki/Preventive_healthcare for the distinction between these terms.
  • Neo-adjuvant deals with the timing of a treatment relative to other treatments, not the intent. SNOMED’s classification of this term is questionable.
  • Adjuvant also relates to the relative timing of a treatment. Again, SNOMED’s classification of this term is questionable.
  • Adjunct refers to a treatment accompanying or in support of another therapy. This is a situation or circumstance, not an intent.

Logical Definition (CLD)

 

Expansion

This value set contains 8 concepts

Expansion based on SNOMED CT United States edition 01-Mar 2021

All codes from system http://snomed.info/sct

CodeDisplayDefinition
373808002Curative - procedure intent
363676003Palliative - procedure intent
399707004Supportive - procedure intent
261004008Diagnostic intent
129428001Preventive - intent
429892002Guidance intent
360156006Screening - procedure intent
447295008Forensic intent

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