Definition for Code System EventStatus SystemEventStatus

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


  
  
    
  
  
    
    
      
      
        

      
      
      
        
          
            
          
          
            
          
          
            
          
        
        
          preparation
            
          
          
          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.
        
        
          in-progress
            
          
          
          
        
        
          not-done
            
          
          
          The event was terminated prior to any activity beyond preparation.  I.e. The 'main' activity
             has not yet begun.  The boundary between preparatory and the 'main' activity is context-specific.
        
        
          on-hold
            
          
          
          
        
        
          stopped
            
          
          
          The event was terminated prior to the full completion of the intended activity but after
             at least some of the 'main' activity (beyond preparation) has occurred.
        
        
          completed
            
          
          
          
        
        
          entered-in-error
            
          
          

<CodeSystem xmlns="http://hl7.org/fhir">
  <id value="event-status"/> 
  <meta> 
    <lastUpdated value="2025-11-10T15:17:08.817+00:00"/> 
  </meta> 
  <text> 
    <status value="generated"/> 
    <div xmlns="http://www.w3.org/1999/xhtml">
      <p class="res-header-id">
        <b> Generated Narrative: CodeSystem event-status</b> 
      </p> 
      <a name="event-status"> </a> 
      <a name="hcevent-status"> </a> 
      <p> This case-sensitive code system 
        <code> http://hl7.org/fhir/event-status</code>  defines the following codes:
      </p> 
      <table class="codes">
        <tr> 
          <td style="white-space:nowrap">
            <b> Code</b> 
          </td> 
          <td> 
            <b> Display</b> 
          </td> 
          <td> 
            <b> Definition</b> 
          </td> 
        </tr> 
        <tr> 
          <td style="white-space:nowrap">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 style="white-space:nowrap">in-progress            <a name="event-status-in-progress"> </a>           </td>           <td> In Progress</td>           <td> The event is currently occurring.</td>         </tr>         <tr>           <td style="white-space:nowrap">not-done            <a name="event-status-not-done"> </a>           </td>           <td> Not Done</td>           <td> The event was terminated prior to any activity beyond preparation.  I.e. The 'main'

             activity has not yet begun.  The boundary between preparatory and the 'main' activity
             is context-specific.</td> 
        </tr>         <tr>           <td style="white-space:nowrap">on-hold            <a name="event-status-on-hold"> </a>           </td>           <td> On Hold</td>           <td> The event has been temporarily stopped but is expected to resume in the future.</td>         </tr>         <tr>           <td style="white-space:nowrap">stopped            <a name="event-status-stopped"> </a>           </td>           <td> Stopped</td>           <td> The event was terminated prior to the full completion of the intended activity

             but after at least some of the 'main' activity (beyond preparation) has occurred.</td> 
        </tr>         <tr>           <td style="white-space:nowrap">completed            <a name="event-status-completed"> </a>           </td>           <td> Completed</td>           <td> The event has now concluded.</td>         </tr>         <tr>           <td style="white-space:nowrap">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;stopped&quot; rather than &quot;entered-in-error&quot;.).
        
        
          unknown
            
          
          
          The authoring/source system does not know which of the status values currently applies
             for this event.  Note: This concept is not to be used for &quot;other&quot; - one of the
             listed statuses is presumed to apply,  but the authoring/source system does not know which.
        
      
    
  
  
    
  
  
    
  
  
    
  
  
  
    
    
  
  
  
  
  
  
  
  
  
    
      
      
    
    
      
      
    
  
  
  
  
  
  
    
    
    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.
  
  
    
    
    
  
  
    
    
    The event was terminated prior to any activity beyond preparation.  I.e. The 'main' activity
     has not yet begun.  The boundary between preparatory and the 'main' activity is context-specific.
  
  
    
    
    
  
  
    
    
    The event was terminated prior to the full completion of the intended activity but after
     at least some of the 'main' activity (beyond preparation) has occurred.
  
  
    
    
    
  
  
    
    

             decisions were based on it.  (If real-world activity has occurred, the status should
             be &quot;stopped&quot; rather than &quot;entered-in-error&quot;.).</td> 
        </tr>         <tr>           <td style="white-space:nowrap">unknown            <a name="event-status-unknown"> </a>           </td>           <td> Unknown</td>           <td> The authoring/source system does not know which of the status values currently

             applies for this event.  Note: This concept is not to be used for &quot;other&quot;
             - one of the listed statuses is presumed to apply,  but the authoring/source system
             does not know which.</td> 
        </tr>       </table>     </div>   </text>   <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-wg">    <valueCode value="pc"/>   </extension>   <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status">    <valueCode value="trial-use"/>   </extension>   <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">    <valueInteger value="4"/>   </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.4.110"/>   </identifier>   <version value="6.0.0-ballot3"/>   <name value="EventStatus"/>   <title value="EventStatus"/>   <status value="draft"/>   <experimental value="false"/>   <date value="2025-11-10T15:17:08+00:00"/>   <publisher value="HL7 International / Patient Care"/>   <contact>     <telecom>       <system value="url"/>       <value value="http://hl7.org/fhir"/>     </telecom>     <telecom>       <system value="email"/>       <value value="fhir@lists.hl7.org"/>     </telecom>   </contact>   <contact>     <telecom>       <system value="url"/>       <value value="http://www.hl7.org/Special/committees/fiwg"/>     </telecom>   </contact>   <contact>     <telecom>       <system value="url"/>       <value value="http://www.hl7.org/Special/committees/patientcare"/>     </telecom>   </contact>   <description value="Codes identifying the lifecycle stage of an event."/>   <jurisdiction>     <coding>       <system value="http://unstats.un.org/unsd/methods/m49/m49.htm"/>       <code value="001"/>       <display value="World"/>     </coding>   </jurisdiction>   <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="not-done"/>     <display value="Not Done"/>     <definition value="The event was terminated prior to any activity beyond preparation.  I.e. The 'main'

     activity has not yet begun.  The boundary between preparatory and the 'main' activity
     is context-specific."/> 
  </concept>   <concept>     <code value="on-hold"/>     <display value="On Hold"/>     <definition value="The event has been temporarily stopped but is expected to resume in the future."/>   </concept>   <concept>     <code value="stopped"/>     <display value="Stopped"/>     <definition value="The event was terminated prior to the full completion of the intended activity

     but after at least some of the 'main' activity (beyond preparation) has occurred."/> 
  </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;stopped&quot; rather than &quot;entered-in-error&quot;.).
  
  
    
    
    The authoring/source system does not know which of the status values currently applies
     for this event.  Note: This concept is not to be used for &quot;other&quot; - one of the
     listed statuses is presumed to apply,  but the authoring/source system does not know which.
  

     decisions were based on it.  (If real-world activity has occurred, the status should
     be &quot;stopped&quot; rather than &quot;entered-in-error&quot;.)."/> 
  </concept>   <concept>     <code value="unknown"/>     <display value="Unknown"/>     <definition value="The authoring/source system does not know which of the status values currently

     applies for this event.  Note: This concept is not to be used for &quot;other&quot;
     - one of the listed statuses is presumed to apply,  but the authoring/source system
     does not know which."/> 
  </concept> 


</

CodeSystem

>