Uploaded image for project: 'FHIR Specification Feedback'
  1. FHIR Specification Feedback
  2. FHIR-13702

Encounter needs staus code "waiting"

    XMLWordPrintableJSON

    Details

    • Type: Change Request
    • Status: Resolved - change required (View Workflow)
    • Priority: Medium
    • Resolution: Persuasive with Modification
    • Specification:
      FHIR Core (FHIR)
    • Raised in Version:
      STU3
    • Work Group:
      Patient Administration
    • Related Artifact(s):
      Encounter
    • Resolution Description:
      Hide

      The following changes will be made to the Encounter resource:

      Encounter.status code 1..1 required (planned, in-progress, on-hold, completed, cancelled, entered-in-error, unknown) "The current state of the Encounter"

      Encounter.subjectStatus CodeableConcept 0..1 extensible (arrived, triaged, on-leave, departed)
      "The status of the subject in regards to the Encounter"
      (The definition of arrived in this valueset will include details that this applies for Emergency)

      The status management section will be updated to include the new subjectStatus, specifically the 2nd paragraph which starts to talk about this concept.

      The 3rd paragraph describing leave will be updated to consider both status properties, and how local systems may have multiple types of leave or hold reasons.

      Another paragraph will be added to this section to describe how waiting list status(es) coud be added to the subjectStatus for local usage.

      Note: There is no change to the statusHistory elements at this stage, however this will be revisited as a part of tracker #14157

      Show
      The following changes will be made to the Encounter resource: Encounter.status code 1..1 required (planned, in-progress, on-hold, completed, cancelled, entered-in-error, unknown) "The current state of the Encounter" Encounter.subjectStatus CodeableConcept 0..1 extensible (arrived, triaged, on-leave, departed) "The status of the subject in regards to the Encounter" (The definition of arrived in this valueset will include details that this applies for Emergency) The status management section will be updated to include the new subjectStatus, specifically the 2nd paragraph which starts to talk about this concept. The 3rd paragraph describing leave will be updated to consider both status properties, and how local systems may have multiple types of leave or hold reasons. Another paragraph will be added to this section to describe how waiting list status(es) coud be added to the subjectStatus for local usage. Note: There is no change to the statusHistory elements at this stage, however this will be revisited as a part of tracker #14157
    • Resolution Vote:
      Simone Heckmann/Brian Postlethwaite: 12-0-2
    • Change Category:
      Enhancement
    • Change Impact:
      Non-compatible

      Description

      Please consider the introduction of the status "waiting" to Encounter.status (http://build.fhir.org/valueset-encounter-status.html) to enable tracking of the total time a patient spent waiting during an (outpatient) encounter

      e.g. arrived -> waiting -> triaged -> waiting -> in-progress (in treatment) -> waiting (for X-rays) -> in-progress (getting Xray) -> waiting (for labwork) -> in progress (in treatment) -> finished

        Attachments

          Activity

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            Simone Heckmann Simone Heckmann
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:
              Vote Date: