Stream: hapi
Topic: Discharge Planning
dsh (May 15 2020 at 20:38):
We have a use case of Case Managers who start patient discharge planning from the moment they are admitted. This process includes identifying anticipated/planned discharge dates, locations to discharge to, barriers to discharge, Coverage (insurance), social status (homelessness / poverty), transportation etc. As you can see this can involve multiple parties and is a constantly evolving case.
Any idea on what is the best Resource or resources that can be leveraged to implement this use case?
Vibin_chander (May 18 2020 at 05:40):
In this situation isn't it we have to leverage the existing the existing encounter resource?
Vibin_chander (May 18 2020 at 05:41):
If ending up creating the new resource is a solution then it becomes more like V2
Frank Oemig (May 18 2020 at 06:57):
Interesting questions, but:
- This is the hapi stream, the question belongs to implementers
- Seeing the huge amount of implementing questions, would it make sense to divide into domain specific substreams, eg. Implementers/adt?
- Looking at v2 and v3 is a good idea
- It must be realized by a combibation of resource updates, eg patient, encounter,...
- Not sure, whether the encounter resource definition is correct/appropriate?! It should be more like in c3...
dsh (May 18 2020 at 07:31):
Thanks @Frank Oemig I just moved this conversation to Implementers stream
Keerthivasan Ramanathan (May 18 2020 at 15:50):
May be you can checkout the CarePlan resource? Just see if you can leverage it
Mareike Przysucha (May 18 2020 at 17:10):
As I don't think it is wise to discuss the same issue in two streams, please see discussion here: https://chat.fhir.org/#narrow/stream/179166-implementers/topic/Discharge.20Planning. As this is not HAPI-specific, I'd prefer to lead the discussion there. Thanks.
Last updated: Apr 12 2022 at 19:14 UTC
