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

• Content
• Detailed Descriptions
• XML
• JSON
• Turtle

RelationToLandmark

 

The official URL for this extension is:

http://hl7.org/fhir/us/mcode/StructureDefinition/obf-datatype-RelationToLandmark-extension

The relationship between a landmark that helps determine a body location and the body location itself. The location relative to a landmark is specified by:

• Specifying the location and type of landmark using a body site code and optional laterality/orientation,
• Specifying the direction from the landmark to the body location, and
• Specifying the distance from the landmark to the body location.

The RelationToLandmark element is part of BodyLocation, a flexible structure that allows the location to be determined by a single code, or a code plus laterality and/or orientation. The body location can also be specified in relation to one or more body landmarks. SNOMED CT is used in all cases.

• Code only: The code should include (precoordinate) laterality and/orientation to the degree necessary to completely specify the body location.
• Code plus laterality and/or orientation: The basic code augmented by codes specifying the body side and/or anatomical orientation.
• Relation to landmark: The location relative to a landmark is specified by:
  1. Establishing the location and type of landmark using a body site code and optional laterality/orientation, and
  2. Specifying the direction and distance from the landmark to the body location.

Note that BodyLocation is a data type (a reusable structure), not a stand-alone entity. The concept is similar to how a postal address can apply to a person, location, or organization. This contrasts with FHIR’s stand-alone BodySite (aka BodyStructure in r4) which ‘is not … intended for describing the type of anatomical location but rather a specific body site on a specific patient’ (FHIR 3.5).

This extension was published on Thu Aug 01 00:00:00 EDT 2019 as a draft by HL7 International Clinical Interoperability Council.

Downloads: StructureDefinition: (XML, JSON, TTL), Schema: XML Schematron

 

 

Constraints

Id	Path	Details	Requirements
ele-1	Extension	All FHIR elements must have a @value or children : hasValue() or (children().count() > id.count())
ext-1	Extension	Must have either extensions or value[x], not both : extension.exists() != value.exists()

 

Usage

This extension is used in the following profiles:

• AbnormalBodyStructure (on bodySite)
• CancerCondition (on bodySite)
• CancerRelatedRadiationProcedure (on bodySite)
• CancerRelatedSurgicalProcedure (on bodySite)
• CodedNonLaboratoryObservation (on bodySite)
• ComorbidCondition (on bodySite)
• Condition (on bodySite)
• NonLaboratoryObservation (on bodySite)
• Observation (on bodySite)
• PrimaryCancerCondition (on bodySite)
• Procedure (on bodySite)
• QuantitativeNonLaboratoryObservation (on bodySite)
• RadiationProcedure (on bodySite)
• SecondaryCancerCondition (on bodySite)
• SimpleCodedNonLaboratoryObservation (on bodySite)
• SurgicalProcedure (on bodySite)
• Tumor (on bodySite)