FHIR Release 3 (STU)

This page is part of the FHIR Specification (v3.0.2: STU 3). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions . Page versions: R5 R4B R4 R3

Codesystem-event-status.xml

Vocabulary Work GroupMaturity Level: N/ABallot Status: Informative

Raw XML (canonical form)

Definition for Code System EventStatus

<CodeSystem xmlns="http://hl7.org/fhir">
  <id value="event-status"/> 
  <meta> 
    <lastUpdated value="2019-10-24T11:53:00+11:00"/> 
  </meta> 
  <text> 
    <status value="generated"/> 
    <div xmlns="http://www.w3.org/1999/xhtml">
      <h2> EventStatus</h2> 
      <div> 
        <p> Codes identifying the stage lifecycle stage of a event</p> 

      </div> 
      <p> This code system http://hl7.org/fhir/event-status defines the following codes:</p> 
      <table class="codes">
        <tr> 
          <td> 
            <b> Code</b> 
          </td> 
          <td> 
            <b> Display</b> 
          </td> 
          <td> 
            <b> Definition</b> 
          </td> 
        </tr> 
        <tr> 
          <td> preparation
            <a name="event-status-preparation"> </a> 
          </td> 
          <td> Preparation</td> 
          <td> The core event has not started yet, but some staging activities have begun (e.g. surgical
             suite preparation).  Preparation stages may be tracked for billing purposes.</td> 
        </tr> 
        <tr> 
          <td> in-progress
            <a name="event-status-in-progress"> </a> 
          </td> 
          <td> In Progress</td> 
          <td> The event is currently occurring</td> 
        </tr> 
        <tr> 
          <td> suspended
            <a name="event-status-suspended"> </a> 
          </td> 
          <td> Suspended</td> 
          <td> The event has been temporarily stopped but is expected to resume in the future</td> 
        </tr> 
        <tr> 
          <td> aborted
            <a name="event-status-aborted"> </a> 
          </td> 
          <td> Aborted</td> 
          <td> The event was  prior to the full completion of the intended actions</td> 
        </tr> 
        <tr> 
          <td> completed
            <a name="event-status-completed"> </a> 
          </td> 
          <td> Completed</td> 
          <td> The event has now concluded</td> 
        </tr> 
        <tr> 
          <td> entered-in-error
            <a name="event-status-entered-in-error"> </a> 
          </td> 
          <td> Entered in Error</td> 
          <td> This electronic record should never have existed, though it is possible that real-world
             decisions were based on it.  (If real-world activity has occurred, the status should be
             &quot;cancelled&quot; rather than &quot;entered-in-error&quot;.)</td> 
        </tr> 
        <tr> 
          <td> unknown
            <a name="event-status-unknown"> </a> 
          </td> 
          <td> Unknown</td> 
          <td> The authoring system does not know which of the status values currently applies for this
             request.  Note: This concept is not to be used for &quot;other&quot; - one of the listed
             statuses is presumed to apply, it's just not known which one.</td> 
        </tr> 
      </table> 
    </div> 
  </text> 
  <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-ballot-status">
    <valueString value="Informative"/> 
  </extension> 
  <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
    <valueInteger value="3"/> 
  </extension> 
  <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-wg">
    <valueCode value="pc"/> 
  </extension> 
  <url value="http://hl7.org/fhir/event-status"/> 
  <identifier> 
    <system value="urn:ietf:rfc:3986"/> 
    <value value="urn:oid:2.16.840.1.113883.4.642.1.101"/> 
  </identifier> 
  <version value="3.0.2"/> 
  <name value="EventStatus"/> 
  <status value="draft"/> 
  <experimental value="false"/> 
  <date value="2019-10-24T11:53:00+11:00"/> 
  <publisher value="HL7 (FHIR Project)"/> 
  <contact> 
    <telecom> 
      <system value="url"/> 
      <value value="http://hl7.org/fhir"/> 
    </telecom> 
    <telecom> 
      <system value="email"/> 
      <value value="fhir@lists.hl7.org"/> 
    </telecom> 
  </contact> 
  <description value="Codes identifying the stage lifecycle stage of a event"/> 
  <caseSensitive value="true"/> 
  <valueSet value="http://hl7.org/fhir/ValueSet/event-status"/> 
  <content value="complete"/> 
  <concept> 
    <code value="preparation"/> 
    <display value="Preparation"/> 
    <definition value="The core event has not started yet, but some staging activities have begun (e.g. surgical
     suite preparation).  Preparation stages may be tracked for billing purposes."/> 
  </concept> 
  <concept> 
    <code value="in-progress"/> 
    <display value="In Progress"/> 
    <definition value="The event is currently occurring"/> 
  </concept> 
  <concept> 
    <code value="suspended"/> 
    <display value="Suspended"/> 
    <definition value="The event has been temporarily stopped but is expected to resume in the future"/> 
  </concept> 
  <concept> 
    <code value="aborted"/> 
    <display value="Aborted"/> 
    <definition value="The event was  prior to the full completion of the intended actions"/> 
  </concept> 
  <concept> 
    <code value="completed"/> 
    <display value="Completed"/> 
    <definition value="The event has now concluded"/> 
  </concept> 
  <concept> 
    <code value="entered-in-error"/> 
    <display value="Entered in Error"/> 
    <definition value="This electronic record should never have existed, though it is possible that real-world
     decisions were based on it.  (If real-world activity has occurred, the status should be
     &quot;cancelled&quot; rather than &quot;entered-in-error&quot;.)"/> 
  </concept> 
  <concept> 
    <code value="unknown"/> 
    <display value="Unknown"/> 
    <definition value="The authoring system does not know which of the status values currently applies for this
     request.  Note: This concept is not to be used for &quot;other&quot; - one of the listed
     statuses is presumed to apply, it's just not known which one."/> 
  </concept> 
</CodeSystem> 

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.