Snapshot 3: Connectathon 32 Base

This is Snapshot #3 for FHIR R5, released to support Connectathon 32. For a full list of available versions, see the Directory of published versions.

Example Procedure/example (XML)

Patient Care Work GroupMaturity Level: N/AStandards Status: InformativeCompartments: Encounter, Patient, Practitioner, RelatedPerson

Raw XML (canonical form + also see XML Format Specification)

Jump past Narrative

General Procedure Example (id = "example")

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

<Procedure xmlns="http://hl7.org/fhir">
  <id value="example"/> 
  <meta> 
    <versionId value="1"/> 
  </meta>   
  <text> 
    <status value="generated"/> 
    <div xmlns="http://www.w3.org/1999/xhtml">Routine Appendectomy</div> 
  </text> 
  <status value="completed"/> 
  <code> 
    <coding> 
      <system value="http://snomed.info/sct"/> 
      <code value="80146002"/> 
      <display value="Appendectomy (Procedure)"/> 
    </coding> 
    <text value="Appendectomy"/> 
  </code> 
  <subject> 
    <reference value="Patient/example"/> 
  </subject> 
  <occurrenceDateTime value="2013-04-05"/> 
  <recorder> 
    <reference value="Practitioner/example"/> 
    <display value="Dr Cecil Surgeon"/> 
  </recorder> 
  <reportedReference> 
    <reference value="Practitioner/example"/> 
    <display value="Dr Cecil Surgeon"/> 
  </reportedReference> 
  <performer> 
    <actor> 
      <reference value="Practitioner/example"/> 
      <display value="Dr Cecil Surgeon"/> 
    </actor> 
  </performer>   
  <reason> 
       <concept> 
         <text value="Generalized abdominal pain 24 hours. Localized in RIF with rebound and guarding"/> 
       </concept> 
  </reason> 
  <followUp> 
    <text value="ROS 5 days  - 2013-04-10"/> 
  </followUp> 
  <note> 
    <text value="Routine Appendectomy. Appendix was inflamed and in retro-caecal position"/> 
  </note> 
  <supportingInfo> 
    <reference value="ImagingStudy/example"/> 
  </supportingInfo> 
</Procedure> 

Usage note: every effort has been made to ensure that the examples are correct and useful, but they are not a normative part of the specification.