FHIR Chat · Encounter AdmitDisposition · implementers

Stream: implementers

Topic: Encounter AdmitDisposition


view this post on Zulip Ardon Toonstra (Feb 21 2022 at 12:33):

For our Encounters we are looking to best model "AdmitDisposition".

The concept is similar to Encounter.hospitalization.dischargeDisposition but for admittance. It relates to Encounter.hospitalization.admitSourcebut has less to do with specific referrals. It is for example about if someone comes from Dementia Level Care or Hospital Level Care, or from a Hospice. The Encounter model itself haven't named the .admitSource using the same terminology as the . discharge**Disposition**... so we are thinking of creating a AdmitDisposition extension.

Do others have experiences with this?

view this post on Zulip Lloyd McKenzie (Feb 21 2022 at 16:52):

@Brian Postlethwaite

view this post on Zulip René Spronk (Feb 21 2022 at 17:47):

Encounter.admitSource ? This has a preferred binding so could be easily extended. If it's not that you may have to come up with a more elaborate definition of what it is you're looking for (to distinguish it from admitSource).

view this post on Zulip Vassil Peytchev (Feb 21 2022 at 22:26):

admitSource seems to be more of an administrative concept, while admitDisposition would be more of a clinical concept. I would hesitate mixing them together.

view this post on Zulip Brian Postlethwaite (Feb 24 2022 at 22:36):

@Cooper Thompson can you summarize the R4 story here and a little on the new changes coming in R5?


Last updated: Apr 12 2022 at 19:14 UTC