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 R4. This is the current published version in its permanent home (it will always be available at this URL). For a full list of available versions, see the Directory of published versions

Resource Profile: Tumor - Mappings

Mappings for the mcode-tumor resource profile.

Mappings for RIM Mapping (http://hl7.org/v3)

Tumor
BodyStructureEntity. Role, or Act, ActSIte
   textAct.text?
   containedN/A
   extension
   extension (relatedCondition)
      idn/a
      urlN/A
      value[x]N/A
   modifierExtensionN/A
   identifier.id
   identifier (tumorIdentifier)n/a, II - The Identifier class is a little looser than the v3 type II because it allows URIs as well as registered OIDs or GUIDs. Also maps to Role[classCode=IDENT]
   activestatusCode
   location.targetSiteCode
   locationQualifier.targetSiteCode
   description.text
   imageoutboundRelationship[typeCode=COMP].target
   patient.scoper or .scoper.playsRole

Mappings for Open EHR Archetype Mapping (http://openehr.org)

Tumor
BodyStructureArchetype ID openEHR-EHR-CLUSTER.anatomical_location.v1 Concept name Anatomical Location Concept description Record details about an anatomical location. Keywords location, site, anatomical Copyright © openEHR Foundation Purpose To record details about anatomical location. Misuse Not for specifiying unilateral/bilateral occurrence - this is related to an evaluation which perhaps includes multiple locations. Author Author name: Heather Leslie Organization: Ocean Informatics Email: heather.leslie@oceaninformatics.com Date of Origination: 2008-11-10 Translator Norwegian Bokmål: Lars Bitsch-Larsen, Haukeland University Hospital of Bergen, Norway, MD, DEAA, MBA, spec in anesthesia, spec in tropical medicine. Arabic (Syria): Mona Saleh Other contributors Heather Leslie, Ocean Informatics, Australia (Editor) Ian McNicoll, freshEHR Clinical Informatics, United Kingdom (Editor) Dunmail Hodkinson, Black Pear Software Ltd, UK References Use cases: - 5LICS, midclavicular line - L forearm, 2cm anterior to the cubital fossa - Right iliac fossa - 5 cm below L tibial tuberosity - 2 cm medial to R nipple - 4 cm below R costal margin in midclavicular line - R femur - midline nose - medial aspect of R great toe nail.
   identifierSpecific location Cluster Optional (0..1) Cardinality: Mandatory, repeating, unordered (1..*)
   locationName of location
   locationQualifierCombines Side, Numerical identifier, Anatomical plane,and Aspect
   descriptionDescription of anatomical location/Visual markings/orientation
   imageImage

Mappings for FiveWs Pattern Mapping (http://hl7.org/fhir/fivews)

Tumor
BodyStructure
   identifierFiveWs.identifier
   activeFiveWs.status
   morphologyFiveWs.what[x]
   locationFiveWs.what[x]
   locationQualifierFiveWs.what[x]
   descriptionFiveWs.what[x]
   imageFiveWs.what[x]
   patientFiveWs.subject[x], FiveWs.subject

Mappings for HL7 v2 Mapping (http://hl7.org/v2)

Tumor
BodyStructure
   identifier (tumorIdentifier)CX / EI (occasionally, more often EI maps to a resource id or a URL)
   morphologySPM-4/SPM-5
   locationOBX-20/SPM-8/SPM-10
   locationQualifierNo distinct element defined in V2.x. The IHE Radiology Technical Framework directs the use of OBR-15-specimen source to contain laterality for imaging studies./SPM-9
   descriptionNTE
   imageOBX
   patientPID-3