FHIR Chat · Location mapping widget

Stream: implementers

Topic: Location mapping widget

Francis Otieno (Oct 07 2021 at 12:27):

Looking for some help here. I would like to add a location mapping widget that allows one to collect details about a location (name of village, town . city, country, longitude and latitude ) and save it as a location resource with a link to a patient.
Usecase

Fill in a questionnaire - name of the village, town, city, country
Add a widget to get the location details/coordinates - Long/Lat
Save resource Patient + Location
How would I need to structure the questionnaire response or for those in a similar use case how did you go about it ?

Lloyd McKenzie (Oct 07 2021 at 13:30):

What is the intended relationship between the Patient and the Location? Is this for contact/exposure tracing?

Francis Otieno (Oct 07 2021 at 14:02):

Yes, I can see a link of the location to the patient , where they live/reside

Lloyd McKenzie (Oct 07 2021 at 16:27):

Where they live/reside would typically be captured in Patient.address. There's a standard extension to allow capturing GPS coordinates for an address. You generally wouldn't have a Location instance for the patient's address.

Francis Otieno (Oct 07 2021 at 16:50):

Perfect. Thanks a bunch @Lloyd McKenzie. You made my evening :)

Mike Lohmeier (Oct 07 2021 at 17:34):

Out of curiosity, what would have been the preferred solution if the location was not the patient's address? For example, if a patient had an asthma attack or sleep apnea event away from the home? Is adding an address with geo location extension to an extended Observation the preferred route.

Lloyd McKenzie (Oct 07 2021 at 17:53):

The fun bit there, is "location of subject when symptom occurred" and "location where observation was captured" aren't the same. The event-location extension can be used to capture the latter. We don't have a standard extension I'm aware of as-yet for the former.

Mike Lohmeier (Oct 07 2021 at 18:08):

Thanks, yep that makes sense on the differentiating between symptom and capture.

For the geo location values, is there any standard-extension work for accuracy or confidence values for latitude, longitude and altitude values in progress? The mobile devices will report accuracy for these values as well and the distribution of accuracy values is actually pretty ugly especially for poor gps chipsets.

Similarly, is there anything in the works for more than just geopoints in the standard-extensions? We have hotspot tools for both individual patients and population health that allow users to view hotspots that are polygons. We used geojson here for all geo and it worked really well to convey any type of geo data.

Lloyd McKenzie (Oct 07 2021 at 18:36):

Not via anything defined as yet, though you could submit a change request for us to define one.

John Silva (Oct 07 2021 at 19:02):

In the US (and probably Europe GDPR) this is PHI - Protected Health Information; so it would probably need to have patient approval and a particular scope for its use.

Jose Costa Teixeira (Oct 07 2021 at 19:11):

John Silva said:

In the US (and probably Europe GDPR) this is PHI - Protected Health Information; so it would probably need to have patient approval and a particular scope for its use.

it would need to have a valid purpose and scope for sharing, but not patient approval