FHIR Chat · populating Encounter.location · implementers

Stream: implementers

Topic: populating Encounter.location

Craig Newman (Sep 09 2019 at 14:41):

I'm wondering how people are populating Encounter.location when multiple "levels" of locations are known. If a patient is in a bed which is in a room which is in a ward (I'll cut off the example at this level, but it could extend further upwards), are all of those Location resources expected to be listed in Encounter.location or is only the most granular location populated and then the hierarchy determined based on Location.partOf (assuming that Location.partOf for the bed points to the Location resource for the room and that Location.partOf for the room points to the Location resource for the ward, etc)? We are trying to figure out how to translate PV1-3 of a v2 message into Encounter.location. Thanks.

Angus Millar (Sep 11 2019 at 04:47):

I'm currently struggling with the very same dilemma. I did note that the last Encounter example in R4 has a location which wraps Ward, Room, and Bed all into the same Location Resource (Correction: Location element, the reference is only used for the display and there is no external resource) .

{
      "location": {
        "display": "Ward 1, Room 42, Bed 1"
      },
      "status": "active",
      "period": {
        "start": "2017-02-01T09:27:00+10:00",
        "end": "2017-02-01T12:15:00+10:00"
      }
    }

Lloyd McKenzie (Sep 11 2019 at 12:49):

Typically only the most granular is captured. The hierarchy is reflected in the location definition and doesn't need to be communicated in the instance.

Lloyd McKenzie (Sep 11 2019 at 12:50):

The hierarchy can be searched using the part-of search parameter.

Lloyd McKenzie (Sep 11 2019 at 12:51):

@Brian Postlethwaite is part-of recursive? I.e. if A is part of B is part of C is part of D, will a search for part-of=D include locations A, B and C?

Lloyd McKenzie (Sep 11 2019 at 12:51):

(if not, is it reasonable to make it so?)

Brian Postlethwaite (Sep 14 2019 at 03:18):

This has not been defined, but something that I would like to discuss with Fhir I
For org, loc and encounter.
As I'm sure there are other resources that fit this pattern.
Is very similar to Hierarchy terminologies

Last updated: Apr 12 2022 at 19:14 UTC