Stream: implementers
Topic: Capture Inpatient Location Change
Akeem Leighton Foster Spencer (Oct 17 2017 at 15:45):
Greetings Everyone,
I'm looking to capture a patient's room assignment being changed. Does that capture fall under the Encounter resource or the Location resource for a patient?
Jose Costa Teixeira (Oct 17 2017 at 15:48):
I don't understand what you mean with "location resource for a patient".
Jose Costa Teixeira (Oct 17 2017 at 15:48):
seems that encounter.location points to a Location resource, so would that work?
Jose Costa Teixeira (Oct 17 2017 at 15:50):
Encounter.location = "List of locations where the patient has been during this encounter." It's 0..*, so i'd say when patient's room changes, you add one location there...
Akeem Leighton Foster Spencer (Oct 17 2017 at 15:53):
Okay so would this be an entirely new Encounter Resource if the patient's location is changing or would this update an older Encounter instance tied to the patient?
Jose Costa Teixeira (Oct 17 2017 at 15:55):
I guess it depends on what you consider encounter - is it to the hospital or to each location. From my experience, most places consider an encounter "one visit to the hospital", not "one visit to room A"
Jose Costa Teixeira (Oct 17 2017 at 15:57):
With this, if patient goes from room A to room B, you have an encounter for the hospital, and you start with location=[{roomA}] and when you update you have location=[{roomA}, {roomB}]
Akeem Leighton Foster Spencer (Oct 17 2017 at 16:01):
It would have to be each room, if a user has to temporarily go to a different room for a procedure request, as an example
Jose Costa Teixeira (Oct 17 2017 at 16:40):
you can still support many rooms with the example I showed
Lloyd McKenzie (Oct 17 2017 at 16:58):
Sometimes a separate encounter gets created when you go from one department to another, but generally the encounter would remain the same and you'd just end the previous location and add a new one.
Last updated: Apr 12 2022 at 19:14 UTC
