minimal Common Oncology Data Elements (mCODE) Implementation Guide, published by HL7 International / Clinical Interoperability Council. This guide is not an authorized publication; it is the continuous build for version 4.0.0-ballot built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/fhir-mCODE-ig/ and changes regularly. See the Directory of published versions
Official URL: http://hl7.org/fhir/us/mcode/ValueSet/mcode-brachytherapy-permanent-seeds-technique-vs | Version: 4.0.0-ballot | |||
Active as of 2024-10-30 | Maturity Level: 3 | Computable Name: BrachytherapyPermanentSeedsTechniqueVS | ||
Other Identifiers: OID:2.16.840.1.113883.4.642.40.15.48.10 | ||||
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 |
Allowed techniques for brachytherapy modality internal radiotherapy - permanent seeds
References
Changes since version true:
Generated Narrative: ValueSet mcode-brachytherapy-permanent-seeds-technique-vs
http://snomed.info/sct
Code | Display |
113120007 | Interstitial brachytherapy (procedure) |
Generated Narrative: ValueSet
Expansion based on SNOMED CT International edition 01-Feb 2024
This value set contains 1 concepts
Code | System | Display |
113120007 | http://snomed.info/sct | Interstitial brachytherapy |
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 |