Stream: implementers
Topic: Encounter discharge estimation
Luud Slagter (Feb 11 2022 at 09:35):
Hi! In our source system an encounter also contains some data related to the discharge estimation. In http://community.fhir.org/t/estimated-discharge-date-in-encounter-resource/198 already a question was posted w.r.t. how the estimated discharge date should be represented in FHIR (short answer: Encounter.period.end). In our case however there is some additional data present, such as the type of discharge estimation, a boolean to indicate whether the discharge estimation is still active and some elements related to the confirmation of the discharge estimation. Therefore we aren't able to represent all this information within the Encounter resource itself (at least without using extensions), and currently we're thinking about modelling this information as a separate Observation instead. Does someone already have some experience with such a usecase?
@Chris Royle , @Michelle (Moseman) Miller Since you were involved in the question I've linked, any insight from your side would be appreciated!
Michelle (Moseman) Miller (Feb 11 2022 at 17:40):
For what it's worth, I noticed that PA (Patient Admin) thinking has evolved over time. Previously, per J#7873 and R4, there was a single period element, but now in the emerging R5 build, I see that period has been renamed to actualPeriod and new elements added for plannedStartDate and plannedEndDate.
In my past implementation experience, we were focused on estimated dates and used status to guide the interpretation of the period dates being planned or actual.
I would recommend cross-posting this question to the "patient administration WG" stream to get their input as well.
Luud Slagter (Feb 23 2022 at 14:51):
We have also considered pre-adopting the plannedEndDate element within Encounter. However this turned out to be insufficient to support all data elements related to the discharge estimation, hence we've decided to use an Observation instead. Thanks for the help!
Lloyd McKenzie (Feb 23 2022 at 15:43):
Feel free to submit change requests if you think the resource is missing elements that will be used by a wide number of systems...
Last updated: Apr 12 2022 at 19:14 UTC
