Release 5 Preview #1

This page is part of the FHIR Specification (v4.2.0: R5 Preview #1). 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.json

Patient Care Work GroupMaturity Level: N/AStandards Status: Informative

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

Definition for Code System EventStatus

{
  "resourceType" : "CodeSystem",
  "id" : "event-status",
  "meta" : {
    "lastUpdated" : "2019-12-31T21:03:40.621+11:00"
  },
  "text" : {
    "status" : "generated",
    "div" : "<div>!-- Snipped for Brevity --></div>"
  },
  "extension" : [{
    "url" : "http://hl7.org/fhir/StructureDefinition/structuredefinition-wg",
    "valueCode" : "pc"
  },
  {
    "url" : "http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status",
    "valueCode" : "trial-use"
  },
  {
    "url" : "http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm",
    "valueInteger" : 3
  }],
  "url" : "http://hl7.org/fhir/event-status",
  "identifier" : [{
    "system" : "urn:ietf:rfc:3986",
    "value" : "urn:oid:2.16.840.1.113883.4.642.1.110"
  }],
  "version" : "4.2.0",
  "name" : "EventStatus",
  "title" : "EventStatus",
  "status" : "draft",
  "experimental" : false,
  "date" : "2019-12-31T21:03:40+11:00",
  "publisher" : "HL7 (FHIR Project)",
  "contact" : [{
    "telecom" : [{
      "system" : "url",
      "value" : "http://hl7.org/fhir"
    },
    {
      "system" : "email",
      "value" : "fhir@lists.hl7.org"
    }]
  }],
  "description" : "Codes identifying the lifecycle stage of an event.",
  "caseSensitive" : true,
  "valueSet" : "http://hl7.org/fhir/ValueSet/event-status",
  "content" : "complete",
  "concept" : [{
    "code" : "preparation",
    "display" : "Preparation",
    "definition" : "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."
  },
  {
    "code" : "in-progress",
    "display" : "In Progress",
    "definition" : "The event is currently occurring."
  },
  {
    "code" : "not-done",
    "display" : "Not Done",
    "definition" : "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."
  },
  {
    "code" : "on-hold",
    "display" : "On Hold",
    "definition" : "The event has been temporarily stopped but is expected to resume in the future."
  },
  {
    "code" : "stopped",
    "display" : "Stopped",
    "definition" : "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."
  },
  {
    "code" : "completed",
    "display" : "Completed",
    "definition" : "The event has now concluded."
  },
  {
    "code" : "entered-in-error",
    "display" : "Entered in Error",
    "definition" : "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 \"stopped\" rather than \"entered-in-error\".)."
  },
  {
    "code" : "unknown",
    "display" : "Unknown",
    "definition" : "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 \"other\" - one of the listed statuses is presumed to apply,  but the authoring/source system does not know which."
  }]
}

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.