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
<CodeSystem xmlns="http://hl7.org/fhir">
<id value="mcode-resource-identifier-cs"/>
<text>
<status value="generated"/>
<div xmlns="http://www.w3.org/1999/xhtml"><p>This code system http://hl7.org/fhir/us/mcode/CodeSystem/mcode-resource-identifier-cs defines the following codes:</p><table class="codes"><tr><td style="white-space:nowrap"><b>Code</b></td><td><b>Display</b></td><td><b>Definition</b></td></tr><tr><td style="white-space:nowrap">mcode-patient<a name="mcode-resource-identifier-cs-mcode-patient"> </a></td><td>mCODE Patient Group Resource</td><td>Identifies a Group resource containing mCODE cancer patients that conforms to the MCODEPatientGroup profile.</td></tr><tr><td style="white-space:nowrap">mcode-radiotherapy-course-summary<a name="mcode-resource-identifier-cs-mcode-radiotherapy-course-summary"> </a></td><td>Radiotherapy Course Summary Resource</td><td>Identifies a Procedure resource that summarizes a radiotherapy treatment that conforms to the RadiotherapyCourseSummary profile.</td></tr><tr><td style="white-space:nowrap">mcode-teleradiotherapy-treatment-phase<a name="mcode-resource-identifier-cs-mcode-teleradiotherapy-treatment-phase"> </a></td><td>Teleradiotherapy Treatment Phase Resource</td><td>Identifies a Procedure resource that describes delivery of teleradiotherapy (external beam radiation) and conforms to the TeleradiotherapyTreatmentPhase profile.</td></tr><tr><td style="white-space:nowrap">mcode-brachytherapy-treatment-phase<a name="mcode-resource-identifier-cs-mcode-brachytherapy-treatment-phase"> </a></td><td>Brachytherapy Treatment Phase Resource</td><td>Identifies a Procedure resource that describes delivery of brachytherapy (internal or surface radiation) and conforms to the BrachytherapyTreatmentPhase profile.</td></tr></table></div>
</text>
<url
value="http://hl7.org/fhir/us/mcode/CodeSystem/mcode-resource-identifier-cs"/>
<version value="1.16.0"/>
<name value="ResourceIdentifierCS"/>
<title value="mCODE Resource Identifier Code System"/>
<status value="active"/>
<date value="2021-04-15T12:44:45+00:00"/>
<publisher value="HL7 International Clinical Interoperability Council"/>
<contact>
<name value="HL7 International Clinical Interoperability Council"/>
<telecom>
<system value="url"/>
<value value="http://www.hl7.org/Special/committees/cic"/>
</telecom>
<telecom>
<system value="email"/>
<value value="ciclist@lists.HL7.org"/>
</telecom>
</contact>
<description
value="Concepts describing instance types, to be used in the `code` element of instances. These codes were created because no appropriate concept could be found in established vocabularies. These concepts are analogous to LOINC codes for laboratory observations: they identify the type of thing an instance represents.
Please note that while these codes may imply conformance to the profiles that use them, they are not synonymous with profiles and do not serve the same purpose in a FHIR resource for several reasons:
1. An instance of a resource like Group, Observation, or Procedure may conform to multiple profiles, but may only have one 'type of thing' as determined by the value of `code` (which has a maximum cardinality of 1).
2. `Procedure.code`, `Observation.code`, and `Group.code` elements require a [CodeableConcept data type](http://www.hl7.org/fhir/datatypes.html#CodeableConcept), which can be satisfied with a code from this code system. In contrast, a profile is identified with a [canonical URL](http://www.hl7.org/fhir/structuredefinition-definitions.html#StructureDefinition.url), which is represented by a [URI data type](http://www.hl7.org/fhir/datatypes.html#uri). In other words, a profile's canonical URL belongs in the `meta.profile` element, whereas the codes in this code system belong in `Resource.code` elements.
3. The same `code` can correspond to more than one profile (although not the case here)."/>
<jurisdiction>
<coding>
<system value="urn:iso:std:iso:3166"/>
<code value="US"/>
<display value="United States of America"/>
</coding>
</jurisdiction>
<content value="complete"/>
<count value="4"/>
<concept>
<code value="mcode-patient"/>
<display value="mCODE Patient Group Resource"/>
<definition
value="Identifies a Group resource containing mCODE cancer patients that conforms to the MCODEPatientGroup profile."/>
</concept>
<concept>
<code value="mcode-radiotherapy-course-summary"/>
<display value="Radiotherapy Course Summary Resource"/>
<definition
value="Identifies a Procedure resource that summarizes a radiotherapy treatment that conforms to the RadiotherapyCourseSummary profile."/>
</concept>
<concept>
<code value="mcode-teleradiotherapy-treatment-phase"/>
<display value="Teleradiotherapy Treatment Phase Resource"/>
<definition
value="Identifies a Procedure resource that describes delivery of teleradiotherapy (external beam radiation) and conforms to the TeleradiotherapyTreatmentPhase profile."/>
</concept>
<concept>
<code value="mcode-brachytherapy-treatment-phase"/>
<display value="Brachytherapy Treatment Phase Resource"/>
<definition
value="Identifies a Procedure resource that describes delivery of brachytherapy (internal or surface radiation) and conforms to the BrachytherapyTreatmentPhase profile."/>
</concept>
</CodeSystem>