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

History of Encounter.class

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive
    • Icon: Medium Medium
    • FHIR Core (FHIR)
    • DSTU1 [deprecated]
    • Patient Administration
    • STU
    • Encounter
    • Hide

      Include a new backbone element after the class property covering the history (as described, and similar to the status and location histories)

      Show
      Include a new backbone element after the class property covering the history (as described, and similar to the status and location histories)
    • Michelle Miller/Sam Rubenstein: 9-0-0
    • Enhancement
    • Compatible, substantive
    • DSTU1 [deprecated]

    Description

      I would propose a change to encounter that allows us to track the encounter.class for each period of time (similar to what is done with accommodations/beds).

      For example, if a patient shows up in the emergency department, then encounter.class begins as emergency. However, if that patient ends up getting admitted as an inpatient, then the encounter.class changes to inpatient. Just as the patient's location (bed) over time is modeled, same should be done for encounter.class as well.

      Attachments

        Activity

          People

            Unassigned Unassigned
            michelle.m.miller Michelle Miller
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: