FHIR © HL7.org  |  FHIRsmith 4.0.1  |  Server Home  |  XIG Home  |  XIG Stats  | 

FHIR IG analytics

Packagehl7.fhir.uv.xver-r4.r4b
Resource TypeCodeSystem
IdCodeSystem-event-status.json
FHIR VersionR4B
Sourcehttp://hl7.org/fhir/uv/xver-r4.r4b/0.1.0/CodeSystem-event-status.html
URLhttp://hl7.org/fhir/event-status
Version4.0.1
Statusdraft
Date2019-10-31T17:29:23-05:00
NameEventStatus
TitleEventStatus
Realmuv
Authorityhl7
DescriptionCodes identifying the lifecycle stage of an event.
Contentcomplete

Resources that use this resource

CodeSystem
de.fhir.terminologie#0.0.1-alpha2eventstatus-supplementSupplement EventStatus
ConceptMap
hl7.fhir.us.ccda#currentCF-ImmunizationStatusC-CDA to FHIR Immunization Status
hl7.fhir.us.ccda#currentCF-ProcedureStatusC-CDA to FHIR Procedure Status
hl7.fhir.us.ccda#currentFC-ImmunizationStatusFHIR to C-CDA Immunization Status
hl7.fhir.us.ccda#currentFC-ProcedureStatusFHIR to C-CDA Procedure Status
hl7.fhir.uv.v2mappings#currenttable-hl70322-to-event-statusTable HL70322 to Event Status Map
smart.who.int.immunizations#currentIMMZ.D.ConceptMapConceptMap to and from IMMZ.D DataElements
hl7.fhir.uv.genomics-reporting#currentGenomicStudyStatusMapGenomic Study Status Map
kbv.basis.terminology#1.8.0KBV_CM_Base_Terminology_Complete_GermanKBV_CM_Base_Terminology_Complete_German
hl7.fhir.uv.xver-r2.r4b#0.1.0R2-procedure-status-for-R4B-event-statusCross-version ConceptMap for ValueSet R2-procedure-status-for-R4B-event-status from FHIR DSTU2 to FHIR R4B
hl7.fhir.uv.xver-r4.r3#0.1.0R4-event-status-for-R3Cross-version ConceptMap for ValueSet R4-event-status-for-R3 from FHIR R4 to FHIR STU3
hl7.fhir.uv.xver-r4.r3#0.1.0R4-immunization-status-for-R3Cross-version ConceptMap for ValueSet R4-immunization-status-for-R3 from FHIR R4 to FHIR STU3
hl7.fhir.uv.xver-r5.r3#0.1.0R5-event-status-for-R3-clinical-impression-statusCross-version ConceptMap for ValueSet R5-event-status-for-R3-clinical-impression-status from FHIR R5 to FHIR STU3
hl7.fhir.uv.xver-r5.r3#0.1.0R5-event-status-for-R3Cross-version ConceptMap for ValueSet R5-event-status-for-R3 from FHIR R5 to FHIR STU3
hl7.fhir.uv.xver-r2.r5#0.1.0R2-procedure-status-for-R5-event-statusCross-version ConceptMap for ValueSet R2-procedure-status-for-R5-event-status from FHIR DSTU2 to FHIR R5
hl7.fhir.uv.xver-r2.r4#0.1.0R2-procedure-status-for-R4-event-statusCross-version ConceptMap for ValueSet R2-procedure-status-for-R4-event-status from FHIR DSTU2 to FHIR R4
hl7.fhir.uv.xver-r4b.r3#0.1.0R4B-event-status-for-R3Cross-version ConceptMap for ValueSet R4B-event-status-for-R3 from FHIR R4B to FHIR STU3
ValueSet
hl7.fhir.uv.ae-research-backport-ig#currentadverse-event-status-vsAdverse Event Status
fhir.astp.us-quality-core#currentus-quality-core-non-negative-event-statusNon-Negative Event Status
fhir.astp.us-quality-core#currentus-quality-core-non-negative-immunization-statusNon-Negative Immunization Status
silfhirprofileig#currentprocedure-statusSGHI Procedure status value set
hl7.fhir.us.qicore#currentqicore-positive-event-statusPositive Event Status
hl7.fhir.uv.xver-r3.r4b.r4#0.0.1-snapshot-2R3-event-status-for-R4BCross-version VS for R3.EventStatus for use in FHIR R4B
hl7.fhir.uv.xver-r4.r3#0.1.0R4-event-status-for-R3Cross-version ValueSet R4.EventStatus for use in FHIR STU3
hl7.fhir.uv.xver-r4.r3#0.1.0R4-immunization-status-for-R3Cross-version ValueSet R4.ImmunizationStatusCodes for use in FHIR STU3
hl7.fhir.uv.xver-r5.r4.r4#0.0.1-snapshot-2R5-adverse-event-status-for-R4Cross-version VS for R5.AdverseEventStatus for use in FHIR R4
signal.core.r4#0.2.10event-statusEventStatus
hl7.fhir.uv.xver-r3.r4.r4b#0.0.1-snapshot-2R3-event-status-for-R4Cross-version VS for R3.EventStatus for use in FHIR R4
hl7.fhir.uv.xver-r5.r4#0.1.0R5-adverse-event-status-for-R4Cross-version ValueSet R5.AdverseEventStatus for use in FHIR R4
hl7.fhir.uv.xver-r5.r3#0.1.0R5-adverse-event-status-for-R3Cross-version ValueSet R5.AdverseEventStatus for use in FHIR STU3
hl7.fhir.uv.xver-r5.r3#0.1.0R5-event-status-for-R3-clinical-impression-statusCross-version ValueSet R5.EventStatus for use in FHIR STU3
hl7.fhir.uv.xver-r5.r3#0.1.0R5-event-status-for-R3Cross-version ValueSet R5.EventStatus for use in FHIR STU3
hl7.fhir.uv.xver-r4.r4b.r4b#0.0.1-snapshot-2R4-clinicalimpression-status-for-R4BCross-version VS for R4.ClinicalImpressionStatus for use in FHIR R4B
hl7.fhir.uv.xver-r4.r4b.r4b#0.0.1-snapshot-2R4-event-status-for-R4BCross-version VS for R4.EventStatus for use in FHIR R4B
hl7.fhir.uv.xver-r5.r4b#0.1.0R5-adverse-event-status-for-R4BCross-version ValueSet R5.AdverseEventStatus for use in FHIR R4B
de.medizininformatikinitiative.kerndatensatz.mtb#2026.0.0mii-vs-mtb-systemische-therapie-statusMII VS MTB Systemtherapie Status
hl7.fhir.uv.xver-r4b.r3#0.1.0R4B-event-status-for-R3Cross-version ValueSet R4B.EventStatus for use in FHIR STU3

Resources that this resource uses

No resources found


Narrative

Note: links and images are rebased to the (stated) source

Generated Narrative: CodeSystem event-status

This case-sensitive code system http://hl7.org/fhir/event-status defines the following codes:

CodeDisplayDefinition
preparation PreparationThe 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 In ProgressThe event is currently occurring.
not-done Not DoneThe 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 On HoldThe event has been temporarily stopped but is expected to resume in the future.
stopped StoppedThe 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 CompletedThe event has now concluded.
entered-in-error Entered in ErrorThis 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".).
unknown UnknownThe 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.

Source1

{
  "resourceType": "CodeSystem",
  "id": "event-status",
  "text": {
    "status": "generated",
    "div": "<!-- snip (see above) -->"
  },
  "extension": [
    {
      "url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status",
      "valueCode": "trial-use"
    },
    {
      "url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm",
      "valueInteger": 3
    },
    {
      "extension": [
        {
          "url": "packageId",
          "valueId": "hl7.fhir.uv.xver-r4.r4b"
        },
        {
          "url": "version",
          "valueString": "0.1.0"
        },
        {
          "url": "uri",
          "valueUri": "http://hl7.org/fhir/uv/xver/ImplementationGuide/hl7.fhir.uv.xver-r4.r4b"
        }
      ],
      "url": "http://hl7.org/fhir/StructureDefinition/package-source"
    },
    {
      "url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-wg",
      "valueCode": "pc"
    }
  ],
  "url": "http://hl7.org/fhir/event-status",
  "version": "4.0.1",
  "name": "EventStatus",
  "title": "EventStatus",
  "status": "draft",
  "experimental": false,
  "date": "2019-10-31T17:29:23-05:00",
  "publisher": "Patient Care",
  "contact": [
    {
      "name": "Patient Care",
      "telecom": [
        {
          "system": "url",
          "value": "http://www.hl7.org/Special/committees/patientcare"
        }
      ]
    }
  ],
  "description": "Codes identifying the lifecycle stage of an event.",
  "jurisdiction": [
    {
      "coding": [
        {
          "system": "http://unstats.un.org/unsd/methods/m49/m49.htm",
          "code": "001",
          "display": "World"
        }
      ]
    }
  ],
  "caseSensitive": true,
  "valueSet": "http://hl7.org/fhir/ValueSet/event-status|4.3.0",
  "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."
    }
  ]
}