Stream: implementers
Topic: address geocodes
Brian Postlethwaite (Jun 20 2016 at 03:49):
Probing interest in a standard extesion for storing the geocode data for an address
(similar to what is on the location)
Brian Postlethwaite (Jun 20 2016 at 03:49):
Also interested in where extension profiles on datatypes are documented/discoverable.
(There doesn't appear to be a Profiles tab like there is on the all the resources - but there are examples and a mappings section))
David McKillop (Jun 20 2016 at 04:49):
@Brian Postlethwaite if a standard extension for geocodes is being considered, should a standard extension for other location systems also be considered eg http://what3words.com/about/ ?
Erich Schulz (Jun 20 2016 at 04:56):
that looks really cool @David McKillop - especially for developing countries, but a fixed 3m resolution is bit limiting - 3 words seems like an encode designed for humans rather than computer - and given anytime you have coords you can generate the 3 words doesn't seem like something to bounce about in FHIR?? more somthing that a client app would handle?
Brian Postlethwaite (Jun 20 2016 at 05:13):
interesting idea, would also need to extend into regions/shapes and do intersections and unions etc. So for these I would expect that they would be converted into numeric geocodes for processing.
So like Erich suggests, probably a client side conversion would be simple enough, even though that could be lossy.
David McKillop (Jun 20 2016 at 05:13):
@Erich Schulz Thanks for the feedback, I thought it was pretty cool as well. What you say about "3 words" being for humans makes sense and more appropriate for a client app. I'll leave it at that.
Brian Postlethwaite (Jun 20 2016 at 05:14):
I was looking at how we can make the data fit with the existing tools and data that's out there, and that's basically the geocodes as used on Google Maps.
Brian Postlethwaite (Jun 20 2016 at 05:15):
(and we cover with Location, just not the address datatype, hence not on patient, person, relatedperson or - practitioner should be done through the location for work addresses, but home address could have the geocode extension too)
Erich Schulz (Jun 20 2016 at 05:19):
there's a few issues around different projections, 2d/3d and accuracy to consider...
Erich Schulz (Jun 20 2016 at 05:20):
or is that an extension to the extenstion ;-)
Brian Postlethwaite (Jun 20 2016 at 05:23):
Would propose to use the same as defined in the location resource, the WGS84 datum, which is the same projection as defined here: http://www.opengeospatial.org/standards/kml
Erich Schulz (Jun 20 2016 at 05:28):
i'm not an expert but there seem to be a few standards in this space...
Erich Schulz (Jun 20 2016 at 05:30):
probably not material I guess
Grahame Grieve (Jun 20 2016 at 06:12):
Brian - I think there should be a profile page for data types - can you make a task for that
Grahame Grieve (Jun 20 2016 at 06:12):
I don't see why we'd add geocode to address - surely it should be on locatoin
Grahame Grieve (Jun 20 2016 at 06:12):
given where what3words is, it would definitely be an extension.
Brian Postlethwaite (Jun 20 2016 at 06:23):
Patients don't have a location, only an address
Brian Postlethwaite (Jun 20 2016 at 06:23):
(otherwise wouldn't be proposing it)
Brian Postlethwaite (Jun 20 2016 at 06:23):
(And it is on location already)
Grahame Grieve (Jun 20 2016 at 06:24):
I would have thought an extension from address to location
Brian Postlethwaite (Jun 20 2016 at 06:25):
just to put the geocode in? Then all the address properties are potentially duplicated, and org and...
Erich Schulz (Jun 20 2016 at 07:40):
but it isn't a simple issue because the Earth is in motion...
Erich Schulz (Jun 20 2016 at 07:40):
"How will 'continental drift' affect GDA?
The Australian plate is moving in a north easterly direction at a rate of about 7 cm per year, but there is little known distortion within the plate. That means the latitude and longitude of points in Australia, measured in a world-wide system, are changing slowly but constantly.
The definition of the GDA94 datum includes fixed values for certain geodetic reference points in Australia. The values of these will remain fixed. GDA94 position values, therefore, are NOT affected by continental drift. The RELATIONSHIP of positions to each other, such as between 2 seismic shots, or of an object relative to the Trigonometric beacon used to locate that object, will NOT change.
However, ABSOLUTE positions in Australia, measured in a world-wide system, will change over the long term. WGS84 is such a world-wide system. This is one of the reasons why the exact relationship between GDA94 and WGS84 coordinates for points is not constant.
In the future, GPS systems which measure absolute positions to centimetre precision, may become commonly available. This will necessitate new rules for dealing with the gradual change of absolute positions."
Erich Schulz (Jun 20 2016 at 07:41):
from here
Erich Schulz (Jun 20 2016 at 07:42):
so in 30 years time your "3 word location" maybe different... or not
Erich Schulz (Jun 20 2016 at 07:42):
depending on your reference
Grahame Grieve (Jun 20 2016 at 11:01):
we're going up in the world ;-)
Erich Schulz (Jun 20 2016 at 11:01):
heh
Grahame Grieve (Jun 20 2016 at 11:01):
Mt Everest, watch out
Brian Postlethwaite (Jun 22 2016 at 00:48):
Anyone else have anything to add here?
(Interested in adding geocodes as extension on address - other suggested approach is to add an extension to link to location)
Reason to want this is to be able to map patient addresses (or practitioners, relatedperson etc)
Brian Postlethwaite (Jun 22 2016 at 00:48):
And likely to suggest search parameters too
Brian Postlethwaite (Jun 22 2016 at 00:50):
Another suggestion would be to move the position backbone element in location into the address datatype. (removing it from location, and making it available on any address - much cleaner I think)
Jeremy Walton (Jun 22 2016 at 02:31):
@Brian Postlethwaite I would think that geographic location is closely tied to an address, so it would fit there. Do you have an extension definition built? What about an optional elevation parameter (ala Z)?
Brian Postlethwaite (Jun 22 2016 at 02:52):
Haven't built it yet, but was considering a complex extention that was the same as the location.position backbone element that has lat,long,alt
Brian Postlethwaite (Jun 22 2016 at 02:52):
But while making the change, suggesting making the change to the datatype for address and remove from location.
Last updated: Apr 12 2022 at 19:14 UTC
