SIMPLIFIER.NET - FHIRPath Playground

FHIRPath

If you Log in or sign up, you can edit this script yourself.

name

<ValueSet xmlns="http://hl7.org/fhir">
  <id value="anatomical-orientation" />
  <meta>
    <lastUpdated value="2019-12-20T21:26:03.846+00:00" />
  </meta>
  <text>
    <status value="generated" />
    <div xmlns="http://www.w3.org/1999/xhtml">
      <h2>Anatomical Orientation</h2>
      <div>
        <p>Terms that specify anatomical orientation. The orientation 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.</p>
        <ul>
          <li>Code only: The code should include (precoordinate) laterality and/orientation to the degree necessary to completely specify the body location.</li>
          <li>Code plus laterality and/or orientation: The basic code augmented by codes specifying the body side and/or anatomical orientation.</li>
          <li>Relation to landmark: The location relative to a landmark is specified by:</li>
        </ul>
        <ol>
          <li>Establishing the location and type of landmark using a body site code and optional laterality/orientation, and</li>
          <li>Specifying the direction and distance from the landmark to the body location.</li>
        </ol>
        <p>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>
      <p>This value set includes codes from the following code systems:</p>
      <ul>
        <li>Include codes from <a href="http://www.snomed.org/"><code>http://snomed.info/sct</code></a> where concept  is-a  272424004 (Relative sites)</li>
      </ul>
    </div>
  </text>
  <url value="http://ga4gh.org/fhir/phenopackets/ValueSet/anatomical-orientation" />
  <version value="0.1.0" />
  <name value="AnatomicalOrientation" />
  <title value="Anatomical Orientation" />
  <status value="draft" />
  <experimental value="false" />
  <date value="2019-12-20T18:15:04+00:00" />
  <publisher value="Global Alliance for Genomics and Health" />
  <contact>
    <telecom>
      <system value="url" />
      <value value="http://ga4gh.org" />
    </telecom>
  </contact>
  <description value="Terms that specify anatomical orientation. The orientation 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.&#xA;&#xA;* Code only: The code should include (precoordinate) laterality and/orientation to the degree necessary to completely specify the body location.&#xA;* Code plus laterality and/or orientation: The basic code augmented by codes specifying the body side and/or anatomical orientation.&#xA;* Relation to landmark: The location relative to a landmark is specified by:&#xA;1. Establishing the location and type of landmark using a body site code and optional laterality/orientation, and&#xA;2. Specifying the direction and distance from the landmark to the body location.&#xA;&#xA;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)." />
  <compose>
    <include>
      <system value="http://snomed.info/sct" />
      <filter>
        <property value="concept" />
        <op value="is-a" />
        <value value="272424004" />
      </filter>
    </include>
  </compose>
</ValueSet>

name : AnatomicalOrientation

{

}