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

Many things create encounters from Admission Discharge Scenarios

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Highest Highest
    • US Da Vinci Alerts (FHIR)
    • 0.2.0 [deprecated]
    • Infrastructure & Messaging
    • Home (index)
    • Hide

      Agree with the submitter that the sentence is broader than just typical admission/discharge scenarios, though this nomenclature is easier to use than "begin encounter" and "end encounter" notifications and the main focus is on more severe encounters (inpatient, ER, surgery etc.); implementers may consider the use this IG for other types of encounters, where appropriate.

      we will clarify :

      The intent of this use case is to focus on the beginning and end of following
      types of Encounters. Note that this is not a complete list (it is based on admit reason (
      http://build.fhir.org/v3/ActEncounterCode/vs.html) / discharge disposition value set (
      http://build.fhir.org/valueset-encounter-discharge-disposition.html))

      admission to the emergency department
      admission to a hospital or equivalent facility as an inpatient
      admission to to a health care facility for a predetermined length of time, usually less than 24 hours
      admission to a hospital or equivalent facility for observation
      admission to a healthcare facility on a nonresident basis for example, for an outpatient medical procedure or surgery
      notification about a discharge to the patient's home environment
      notification about a discharge to a long-term care facility
      notification about a discharge to a post-acute care rehabilitation facility
      notification that the patient expired during the encounter

      Show
      Agree with the submitter that the sentence is broader than just typical admission/discharge scenarios, though this nomenclature is easier to use than "begin encounter" and "end encounter" notifications and the main focus is on more severe encounters (inpatient, ER, surgery etc.); implementers may consider the use this IG for other types of encounters, where appropriate. we will clarify : The intent of this use case is to focus on the beginning and end of following types of Encounters. Note that this is not a complete list (it is based on admit reason ( http://build.fhir.org/v3/ActEncounterCode/vs.html ) / discharge disposition value set ( http://build.fhir.org/valueset-encounter-discharge-disposition.html )) admission to the emergency department admission to a hospital or equivalent facility as an inpatient admission to to a health care facility for a predetermined length of time, usually less than 24 hours admission to a hospital or equivalent facility for observation admission to a healthcare facility on a nonresident basis for example, for an outpatient medical procedure or surgery notification about a discharge to the patient's home environment notification about a discharge to a long-term care facility notification about a discharge to a post-acute care rehabilitation facility notification that the patient expired during the encounter
    • Eric Haas/Paul Knapp: 3-0-1
    • Clarification
    • Non-substantive

    Description

      This seems far broader than just Admission and Discharge scenarios – wouldn’t other things create a patient encounter (e.g., ambulatory visits)?

      Existing Wording:

      The initial version of this Implementation Guide will focus on Admission and Discharge Scenarios, in other words, anything that would create an encounter in a patient care record. 

      Attachments

        Activity

          People

            Unassigned Unassigned
            celine_lefebvre Celine Lefebvre
            Celine Lefebvre
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: