minimal Common Oncology Data Elements (mCODE) Implementation Guide
2.0.0 - STU 2

This page is part of the HL7 FHIR Implementation Guide: minimal Common Oncology Data Elements (mCODE) Release 1 - US Realm | STU1 (v2.0.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

ValueSet: Procedure Intent Value Set

Summary

Defining URL:http://hl7.org/fhir/us/mcode/ValueSet/mcode-procedure-intent-vs
Version:2.0.0
Name:ProcedureIntentVS
Title:Procedure Intent Value Set
Status:Active as of 1/18/22 3:17 AM
Definition:

The purpose of a procedure.

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

Logical Definition (CLD)

 

Expansion

This value set contains 8 concepts

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

All codes in this table are from the system http://snomed.info/sct

CodeDisplay
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
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