R4 Draft for Comment

This page is part of the FHIR Specification (v3.2.0: R4 Ballot 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

Vocabulary Work GroupMaturity Level: N/ABallot Status: Informative

Raw JSON (canonical form)

Definition for Code System EventStatus

{
  "resourceType": "CodeSystem",
  "id": "event-status",
  "meta": {
    "lastUpdated": "2017-12-20T15:52:34.818+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-ballot-status",
      "valueString": "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": "3.2.0",
  "name": "EventStatus",
  "status": "draft",
  "experimental": false,
  "date": "2017-12-20T15:52:34+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 stage lifecycle stage of a 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 impact on the subject (though preparatory actions may have been taken)"
    },
    {
      "code": "suspended",
      "display": "Suspended",
      "definition": "The event has been temporarily stopped but is expected to resume in the future"
    },
    {
      "code": "aborted",
      "display": "Aborted",
      "definition": "The event was  terminated prior to the full completion of the intended actions but after having at least some impact on the subject."
    },
    {
      "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 \"cancelled\" rather than \"entered-in-error\".)"
    },
    {
      "code": "unknown",
      "display": "Unknown",
      "definition": "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 \"other\" - one of the listed statuses is presumed to apply, it's just not known which one."
    }
  ]
}

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.