QI-Core Implementation Guide, published by HL7 International / Clinical Quality Information. This guide is not an authorized publication; it is the continuous build for version 7.0.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/fhir-qi-core/ and changes regularly. See the Directory of published versions

• Narrative Content
• XML
• JSON
• TTL

: Communication negation example - XML Representation

Raw xml | Download

<Communication xmlns="http://hl7.org/fhir">
  <id value="negation-example"/>
  <meta>
    <profile
             value="http://hl7.org/fhir/us/qicore/StructureDefinition/qicore-communicationnotdone"/>
  </meta>
  <text>
    <status value="extensions"/>
    <div xmlns="http://www.w3.org/1999/xhtml"><p class="res-header-id"><b>Generated Narrative: Communication negation-example</b></p><a name="negation-example"> </a><a name="hcnegation-example"> </a><a name="negation-example-en-US"> </a><p><b>Event Recorded</b>: 2014-12-12 18:01:10-0800</p><p><b>status</b>: Not Done</p><p><b>statusReason</b>: <span title="Codes:{http://snomed.info/sct 184081006}">Patient has moved away (finding)</span></p><p><b>category</b>: <span title="Codes:{http://terminology.hl7.org/CodeSystem/communication-category alert}">Alert</span></p><p><b>medium</b>: <span title="Codes:{http://terminology.hl7.org/CodeSystem/v3-ParticipationMode WRITTEN}">written</span></p><p><b>subject</b>: <a href="Patient-example.html">Jim Chalmers  Male, DoB: 1974-12-25 ( Medical record number (use: usual, period: 2001-05-06 --&gt; (ongoing)))</a></p><p><b>topic</b>: <span title="Codes:{http://terminology.hl7.org/CodeSystem/communication-topic progress-update}">Progress Update</span></p><p><b>encounter</b>: <a href="Encounter-example.html">Encounter: status = in-progress; class = inpatient encounter (ActCode#IMP); type = Initial hospital inpatient or observation care, per day, for the evaluation and management of a patient, which requires a medically appropriate history and/or examination and high level of medical decision making. When using total time on the date of the encounter for code selection, 75 minutes must be met or exceeded.</a></p><p><b>sent</b>: 2014-12-12 18:01:10-0800</p><p><b>received</b>: 2014-12-12 18:01:11-0800</p><p><b>recipient</b>: <a href="Practitioner-example.html">Practitioner Adam Careful </a></p><p><b>sender</b>: <a href="Device-example.html">Device: identifier = http://goodcare.org/devices/id#345675,Serial Number: AMID-342135-8464; status = active; manufacturer = Acme Devices, Inc; lotNumber = 43453424; modelNumber = AB 45-J; type = Electrocardiographic monitor and recorder; contact = ph: ext 4352; note = QA Checked</a></p><h3>Payloads</h3><table class="grid"><tr><td style="display: none">-</td><td><b>Content[x]</b></td></tr><tr><td style="display: none">*</td><td>Patient example has moved away</td></tr></table></div>
  </text>
  <extension url="http://hl7.org/fhir/StructureDefinition/event-recorded">
    <valueDateTime value="2014-12-12T18:01:10-08:00"/>
  </extension>
  <status value="not-done"/>
  <statusReason>
    <coding>
      <system value="http://snomed.info/sct"/>
      <code value="184081006"/>
      <display value="Patient has moved away (finding)"/>
    </coding>
  </statusReason>
  <category>
    <coding>
      <system
              value="http://terminology.hl7.org/CodeSystem/communication-category"/>
      <code value="alert"/>
    </coding>
    <text value="Alert"/>
  </category>
  <medium>
    <coding>
      <system
              value="http://terminology.hl7.org/CodeSystem/v3-ParticipationMode"/>
      <code value="WRITTEN"/>
      <display value="written"/>
    </coding>
    <text value="written"/>
  </medium>
  <subject>🔗 
    <reference value="Patient/example"/>
  </subject>
  <topic>
    <coding>
      <system
              value="http://terminology.hl7.org/CodeSystem/communication-topic"/>
      <code value="progress-update"/>
      <display value="Progress Update"/>
    </coding>
  </topic>
  <encounter>🔗 
    <reference value="Encounter/example"/>
  </encounter>
  <sent value="2014-12-12T18:01:10-08:00"/>
  <received value="2014-12-12T18:01:11-08:00"/>
  <recipient>🔗 
    <reference value="Practitioner/example"/>
  </recipient>
  <sender>🔗 
    <reference value="Device/example"/>
  </sender>
  <payload>
    <contentString value="Patient example has moved away"/>
  </payload>
</Communication>