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

Encounter.period should talk about estimated end date

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Medium Medium
    • FHIR Core (FHIR)
    • R4
    • Patient Administration
    • Encounter
    • Hide

      It's not clear whether it's legitimate to specify a "forecast" end date for an encounter as the Encounter.period.end or not, nor is it clear how to distinguish an estimated end date from an actual end date given that there's no date on the Encounter that says when it was last changed.  (_lastUpdated is a technical date and wouldn't necessarily imply that 'estimated' end had been replaced with 'actual' end.)

       

       

      FHIR-22766 added extensions for plannedStartDate  and plannedDischargeDate.  We will abandon that change, and instead create two (non-extension) properties:

       

      plannedStartDate  0..1 dateTime

      Definition:  The planned start date/time (or admission date) of the encounter.

      plannedEndDate  0..1 dateTime

      Definition:  The planned end date/time (or discharge date) of the encounter.

       

      We will also update the existing Encounter.period to be Encounter.actualPeriod, with an update to the definition:

      Definition: The actual start and end time of the encounter.

      Show
      It's not clear whether it's legitimate to specify a "forecast" end date for an encounter as the Encounter.period.end or not, nor is it clear how to distinguish an estimated end date from an actual end date given that there's no date on the Encounter that says when it was last changed.  (_lastUpdated is a technical date and wouldn't necessarily imply that 'estimated' end had been replaced with 'actual' end.)   –   FHIR-22766 added extensions for plannedStartDate  and plannedDischargeDate.  We will abandon that change, and instead create two (non-extension) properties:   plannedStartDate  0..1 dateTime Definition:  The planned start date/time (or admission date) of the encounter. plannedEndDate  0..1 dateTime Definition:  The planned end date/time (or discharge date) of the encounter.   We will also update the existing Encounter.period to be Encounter.actualPeriod, with an update to the definition: Definition : The actual start and end time of the encounter.
    • Brian Postlethwaite / Reinhard Egelkraut : 7-0-0
    • Enhancement
    • Non-compatible
    • R5

    Description

      It's not clear whether it's legitimate to specify a "forecast" end date for an encounter as the Encounter.period.end or not, nor is it clear how to distinguish an estimated end date from an actual end date given that there's no date on the Encounter that says when it was last changed.  (_lastUpdated is a technical date and wouldn't necessarily imply that 'estimated' end had been replaced with 'actual' end.)

      Attachments

        Activity

          People

            brian.postlethwaite Brian Postlethwaite
            lloyd Lloyd McKenzie
            Lloyd McKenzie
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: