Blood Pressure Measurement cancelled (id = "blood-pressure-cancel")

<?xml version="1.0" encoding="UTF-8"?>

<Observation xmlns="http://hl7.org/fhir">
  <id value="blood-pressure-cancel"/> 
  <meta> 
    <profile value="http://hl7.org/fhir/StructureDefinition/vitalsigns"/> 
  </meta>     <!--     EH  Narrative created by build
  <text>
    <status value="generated"/>
    <div xmlns="http://www.w3.org/1999/xhtml">Sept 17, 2012: Systolic Blood pressure
   107/60 mmHg (low)</div>
  </text>
   --><text> <status value="generated"/> <div xmlns="http://www.w3.org/1999/xhtml"><p> <b> Generated Narrative: Observation</b> <a name="blood-pressure-cancel"> </a> <a name="hcblood-pressure-cancel"> </a> </p> <div style="display: inline-block; background-color: #d9e0e7; padding: 6px; margin: 4px; border:
       1px solid #8da1b4; border-radius: 5px; line-height: 60%"><p style="margin-bottom: 0px">Resource Observation &quot;blood-pressure-cancel&quot; </p> <p style="margin-bottom: 0px">Profile: <a href="vitalsigns.html">Vital Signs Profile</a> </p> </div> <p> <b> identifier</b> : <span title="   EH  Narrative created by build
  &lt;text&gt;
    &lt;status value=&quot;generated&quot;/&gt;
    &lt;div xmlns=&quot;http://www.w3.org/1999/xhtml&quot;&gt;Sept 17, 2012: Systolic
         Blood pressure 107/60 mmHg (low)&lt;/div&gt;
  &lt;/text&gt;
 "><a href="http://terminology.hl7.org/5.5.0/NamingSystem-uri.html" title="As defined by RFC 3986 (http://www.ietf.org/rfc/rfc3986.txt)(with many schemes
           defined in many RFCs). For OIDs and UUIDs, use the URN form (urn:oid:(note: lowercase)
           and urn:uuid:). See http://www.ietf.org/rfc/rfc3001.txt and http://www.ietf.org/rfc/rfc4122.t
          xt 

This oid is used as an identifier II.root to indicate the the extension is an absolute
           URI (technically, an IRI). Typically, this is used for OIDs and GUIDs. Note that
           when this OID is used with OIDs and GUIDs, the II.extension should start with urn:oid
           or urn:uuid: 

Note that this OID is created to aid with interconversion between CDA and FHIR
           - FHIR uses urn:ietf:rfc:3986 as equivalent to this OID. URIs as identifiers appear
           more commonly in FHIR.

This OID may also be used in CD.codeSystem.">URI</a> /urn:uuid:187e0c12-8dd2-67e2-99b2-bf273c878281</span> </p> <p> <b> status</b> : cancelled</p> <p> <b> category</b> : Vital Signs <span style="background: LightGoldenRodYellow; margin: 4px; border: 1px solid khaki"> (<a href="http://terminology.hl7.org/5.5.0/CodeSystem-observation-category.html">Observation Category Codes</a> #vital-signs)</span> </p> <p> <b> code</b> : Blood pressure systolic &amp; diastolic <span style="background: LightGoldenRodYellow; margin: 4px; border: 1px solid khaki"> (<a href="https://loinc.org/">LOINC</a> #85354-9 &quot;Blood pressure panel with all children optional&quot;)</span> </p> <p> <b> subject</b> : <a href="patient-example.html">Patient/example</a>  &quot;Peter CHALMERS&quot;</p> <p> <b> effective</b> : 2012-09-17</p> <p> <b> performer</b> : <a href="practitioner-example.html">Practitioner/example</a>  &quot;Adam CAREFUL&quot;</p> <p> <b> interpretation</b> : <span title="  an interpretation offered to the combination observation
        generally, it would only be appropriate to offer an interpretation
        of an observation that has no value if it has &quot;COMP&quot; (component)
        observations  ">Below low normal <span style="background: LightGoldenRodYellow; margin: 4px; border: 1px solid khaki"> (<a href="http://terminology.hl7.org/5.5.0/CodeSystem-v3-ObservationInterpretation.html">ObservationInterpretation</a> #L &quot;low&quot;)</span> </span> </p> <p> <b> note</b> : In this example, the blood pressure measurements are not available due to cancellation
         of the order.  Data absent reason is present for each component</p> <p> <b> bodySite</b> : <span title="  for an observation with components, these cannot disagree with the flags on the
         components  ">Right arm <span style="background: LightGoldenRodYellow; margin: 4px; border: 1px solid khaki"> (<a href="https://browser.ihtsdotools.org/">SNOMED CT</a> #368209003)</span> </span> </p> <blockquote> <p> <b> component</b> </p> <p> <b> code</b> : <span title=" 
           Observations are often coded in multiple code systems.
           - LOINC provides a very specific code (though not usefully more specific
           in this particular case)
           - snomed provides a clinically relevant code that is usually less granular
           than LOINC
           - the source system provides its own code, which may be less or more
           granular than LOINC
   this instance shows the concept. The other codes only have a LOINC code  ">Systolic blood pressure <span style="background: LightGoldenRodYellow; margin: 4px; border: 1px solid khaki"> (<a href="https://loinc.org/">LOINC</a> #8480-6; <a href="https://browser.ihtsdotools.org/">SNOMED CT</a> #271649006; clinical-codes#bp-s &quot;Systolic Blood pressure&quot;)</span> </span> </p> <p> <b> dataAbsentReason</b> : <span title="  no value due to some error
    &lt;valueQuantity&gt;
      &lt;value value=&quot;107&quot;/&gt;
      &lt;unit value=&quot;mm[Hg]&quot;/&gt;
    &lt;/valueQuantity&gt;
 ">Not Asked <span style="background: LightGoldenRodYellow; margin: 4px; border: 1px solid khaki"> (<a href="http://terminology.hl7.org/5.5.0/CodeSystem-data-absent-reason.html">DataAbsentReason</a> #not-asked)</span> </span> </p> </blockquote> <blockquote> <p> <b> component</b> </p> <p> <b> code</b> : Diastolic blood pressure <span style="background: LightGoldenRodYellow; margin: 4px; border: 1px solid khaki"> (<a href="https://loinc.org/">LOINC</a> #8462-4)</span> </p> <p> <b> dataAbsentReason</b> : <span title="  no value due to some error
    &lt;valueQuantity&gt;
      &lt;value value=&quot;60&quot;/&gt;
      &lt;unit value=&quot;mm[Hg]&quot;/&gt;
    &lt;/valueQuantity&gt;
 ">Not Asked <span style="background: LightGoldenRodYellow; margin: 4px; border: 1px solid khaki"> (<a href="http://terminology.hl7.org/5.5.0/CodeSystem-data-absent-reason.html">DataAbsentReason</a> #not-asked)</span> </span> </p> </blockquote> </div> </text> <identifier> 
    <system value="urn:ietf:rfc:3986"/> 
    <value value="urn:uuid:187e0c12-8dd2-67e2-99b2-bf273c878281"/> 
  </identifier> 
  <status value="cancelled"/> 
  <category> 
    <coding> 
      <system value="http://terminology.hl7.org/CodeSystem/observation-category"/> 
      <code value="vital-signs"/> 
      <display value="Vital Signs"/> 
    </coding> 
  </category> 
  <code>     <!--    replaced by 85354-9
    <coding>
      <system value="http://loinc.org"/>
      <code value="85354-9"/>
      <display value="Blood pressure systolic &amp; diastolic"/>
    </coding>
   --><coding> 
      <system value="http://loinc.org"/> 
      <code value="85354-9"/> 
      <display value="Blood pressure panel with all children optional"/> 
    </coding> 
    <text value="Blood pressure systolic &amp; diastolic"/> 
  </code> 
  <subject> 
    <reference value="Patient/example"/> 
  </subject> 
  <effectiveDateTime value="2012-09-17"/> 
  <performer> 
    <reference value="Practitioner/example"/> 
  </performer>     <!--    an interpretation offered to the combination observation
        generally, it would only be appropriate to offer an interpretation
        of an observation that has no value if it has "COMP" (component)
        observations    --><interpretation> 
    <coding> 
      <system value="http://terminology.hl7.org/CodeSystem/v3-ObservationInterpretation"/> 
      <code value="L"/> 
      <display value="low"/> 
    </coding> 
    <text value="Below low normal"/> 
  </interpretation> 
  <note> <text value="In this example, the blood pressure measurements are not available due to cancellation
     of the order.  Data absent reason is present for each component"/> </note>     <!--    for an observation with components, these cannot disagree with the flags on
   the components    --><bodySite> 
    <coding> 
      <system value="http://snomed.info/sct"/> 
      <code value="368209003"/> 
      <display value="Right arm"/> 
    </coding> 
  </bodySite> 
  <component>     <!--   
           Observations are often coded in multiple code systems.
           - LOINC provides a very specific code (though not usefully more specific
     in this particular case)
           - snomed provides a clinically relevant code that is usually less granular
     than LOINC
           - the source system provides its own code, which may be less or more
     granular than LOINC
   this instance shows the concept. The other codes only have a LOINC code    --><code>     <!--    LOINC - always recommended to have a LOINC code    --><coding> 
        <system value="http://loinc.org"/> 
        <code value="8480-6"/> 
        <display value="Systolic blood pressure"/> 
      </coding>     <!--    SNOMED CT Codes - becoming more common    --><coding> 
        <system value="http://snomed.info/sct"/> 
        <code value="271649006"/> 
        <display value="Systolic blood pressure"/> 
      </coding>     <!--    Also, a local code specific to the source system    --><coding> 
        <system value="http://acme.org/devices/clinical-codes"/> 
        <code value="bp-s"/> 
        <display value="Systolic Blood pressure"/> 
      </coding>     <!--    that shows the concept. The next two names only have a LOINC code    --></code>     <!--    no value due to some error
    <valueQuantity>
      <value value="107"/>
      <unit value="mm[Hg]"/>
    </valueQuantity>
   --><dataAbsentReason> 
      <coding> 
        <system value="http://terminology.hl7.org/CodeSystem/data-absent-reason"/> 
        <code value="not-asked"/> 
        <display value="Not Asked"/> 
      </coding> 
    </dataAbsentReason> 
  </component> 
  <component> 
    <code> 
      <coding> 
        <system value="http://loinc.org"/> 
        <code value="8462-4"/> 
        <display value="Diastolic blood pressure"/> 
      </coding> 
    </code>     <!--    no value due to some error
    <valueQuantity>
      <value value="60"/>
      <unit value="mm[Hg]"/>
    </valueQuantity>
   --><dataAbsentReason> 
      <coding> 
        <system value="http://terminology.hl7.org/CodeSystem/data-absent-reason"/> 
        <code value="not-asked"/> 
        <display value="Not Asked"/> 
      </coding> 
    </dataAbsentReason> 
  </component> 
</Observation>