Stream: implementers
Topic: Encounter Location
William Hartman (Nov 12 2020 at 16:44):
I am using https://r3.smarthealthit.org/ as my base url for testing and trying to find the location in the encounter api call (I'm assuming that the location is the Unit/Department). I see that the location is optional, however none of them seem to have it that I have found. Am I perhaps doing something wrong to search/read the encounters or does this server I am using simply not have any locations in their encounters. If the latter, any recommendations on a different one to use for my tests? Thanks.
Vassil Peytchev (Nov 12 2020 at 16:55):
Unit/Department is an Organization. Location is meant to represent geographical location/physical address.
Michele Mottini (Nov 12 2020 at 17:03):
An hospital department (or even a bed) is a location:
"location": [
{
"location": {
"reference": "Location/16a24a56-fb0f-eb11-8167-0a69c1b3225b",
"display": "Cedars-Sinai - MDRH EMERGENCY DEPT"
}
}
]
Nothing special is required to get the locations when searching for encounters, so I'd say there are no locations in that server.
There is some location data in our test server: https://fhir.careevolution.com/
William Hartman (Nov 13 2020 at 13:16):
Michele Mottini said:
An hospital department (or even a bed) is a location:
"location": [ { "location": { "reference": "Location/16a24a56-fb0f-eb11-8167-0a69c1b3225b", "display": "Cedars-Sinai - MDRH EMERGENCY DEPT" } } ]Nothing special is required to get the locations when searching for encounters, so I'd say there are no locations in that server.
There is some location data in our test server: https://fhir.careevolution.com/
Thanks! Once I figure out how to use the access token with the npm package I'm using I'll let you know how it goes. I appreciate it.
Last updated: Apr 12 2022 at 19:14 UTC
