HL7 Terminology (THO)
3.1.0 - Publication International flag

This page is part of the HL7 Terminology (v3.1.0: Release) based on FHIR R4. The current version which supercedes this version is 4.0.0. For a full list of available versions, see the Directory of published versions

: ActClassBoundedRoi - XML Representation

Active as of 2014-03-26

Raw xml | Download

<ValueSet xmlns="http://hl7.org/fhir">
  <id value="v3-ActClassBoundedRoi"/>
  <language value="en"/>
    <status value="generated"/>
    <div xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"><ul><li>Include codes from <a href="CodeSystem-v3-ActClass.html"><code>http://terminology.hl7.org/CodeSystem/v3-ActClass</code></a> where concept  is-a  <a href="CodeSystem-v3-ActClass.html#v3-ActClass-ROIBND">ROIBND</a></li></ul></div>
  <url value="http://terminology.hl7.org/ValueSet/v3-ActClassBoundedRoi"/>
    <system value="urn:ietf:rfc:3986"/>
    <value value="urn:oid:2.16.840.1.113883.1.11.20242"/>
  <version value="2.0.0"/>
  <name value="ActClassBoundedRoi"/>
  <title value="ActClassBoundedRoi"/>
  <status value="active"/>
  <date value="2014-03-26"/>
               value="A Region of Interest (ROI) specified for a multidimensional observation, such as an Observation Series (OBSSER). The ROI is specified using a set of observation criteria, each delineating the boundary of the region in one of the dimensions in the multidimensional observation. The relationship between a ROI and its referenced Act is specified through an ActRelationship of type subject (SUBJ), which must always be present. Each of the boundary criteria observations is connected with the ROI using ActRelationships of type &quot;has component&quot; (COMP). In each boundary criterion, the Act.code names the dimension and the Observation.value specifies the range of values inside the region. Typically the bounded dimension is continuous, and so the Observation.value will be an interval (IVL) data type. The Observation.value need not be specified if the respective dimension is only named but not constrained. For example, an ROI for the QT interval of a certain beat in ECG Lead II would contain 2 boundary criteria, one naming the interval in time (constrained), and the other naming the interval in ECG Lead II (only named, but not constrained)."/>
  <immutable value="true"/>
      <system value="http://terminology.hl7.org/CodeSystem/v3-ActClass"/>
        <property value="concept"/>
        <op value="is-a"/>
        <value value="ROIBND"/>