HL7 FHIR Implementation Guide: minimal Common Oncology Data Elements (mCODE) Release 1 - US Realm | STU Ballot 1

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

LandmarkTypeVS


<ValueSet xmlns="http://hl7.org/fhir">
  <id value="obf-datatype-LandmarkTypeVS"/>
  <text>
    <status value="generated"/>
    <div xmlns="http://www.w3.org/1999/xhtml">
<p><b>LandmarkTypeVS ValueSet</b></p>
<p>The type of feature that constitutes the landmark, for example, particularly if the landmark is an acquired body structure or physical object. The landmark type value set 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).</p>
</div>
  </text>
  <url value="http://hl7.org/fhir/us/mcode/ValueSet/obf-datatype-LandmarkTypeVS"/>
  <version value="0.9.1"/>
  <name value="LandmarkTypeVS"/>
  <title value="LandmarkTypeVS"/>
  <status value="draft"/>
  <date value="2019-08-01T00:00:00-04:00"/>
  <publisher value="HL7 International Clinical Interoperability Council"/>
  <contact>
    <telecom>
      <system value="url"/>
      <value value="http://www.hl7.org/Special/committees/cic"/>
    </telecom>
  </contact>
  <description
               value="The type of feature that constitutes the landmark, for example, particularly if the landmark is an acquired body structure or physical object. The landmark type value set 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&#39;s stand-alone BodySite (aka BodyStructure in r4) which &#39;is not ... intended for describing the type of anatomical location but rather a specific body site on a specific patient&#39; (FHIR 3.5)."/>
  <compose>
    <include>
      <system value="http://snomed.info/sct"/>
      <filter>
        <property value="concept"/>
        <op value="is-a"/>
        <value value="40388003"/>
      </filter>
    </include>
    <include>
      <system value="http://snomed.info/sct"/>
      <concept>
        <code value="361083003"/>
        <display value="Normal anatomy (body structure)"/>
      </concept>
      <concept>
        <code value="341000119102"/>
        <display value="Tattoo of skin"/>
      </concept>
      <concept>
        <code value="275322007"/>
        <display value="Scar"/>
      </concept>
      <concept>
        <code value="38033009"/>
        <display value="Amputation stump (body structure)"/>
      </concept>
      <concept>
        <code value="13136005"/>
        <display value="Injection site (morphologic abnormality)"/>
      </concept>
      <concept>
        <code value="43526002"/>
        <display value="Operative site (morphologic abnormality)"/>
      </concept>
    </include>
  </compose>
</ValueSet>