Stream: implementers
Topic: observation.valueaddress
AbdulMalik Shakir (Nov 28 2018 at 01:48):
I am creating an IG based upon STU-3. I am struggling with how to represent an observation whose value is an address (58332-8 death location and 69447-1 Injury Location). There is no observation.valueAddress element and there is no way to point a Location resource to a subject. Any suggested workarounds?
Michele Mottini (Nov 28 2018 at 03:42):
Put the address as a single string in valueString and the as an Address data type in an extension of value ? So general-purpose client would have ta decent value and clients that know about the special extension can get better details
AbdulMalik Shakir (Nov 28 2018 at 14:26):
It looks like an extension is my only option. I am considering adding a "location" extension to Observation that would function similar to the location element of Adverse Event. Any opinions pro or con with this approach?
Michele Mottini (Nov 28 2018 at 14:30):
I'd make it an extension of Observation.value maybe - because it is the value of the observation after all
René Spronk (Dec 07 2018 at 09:29):
@AbdulMalik Shakir Would it always be an address, or could it extend to GPS coordinates ? We just ahd a discussion in another thread about real time location tracking (e.g. of patients), whereby we'd need an extension on Observation to a Location resource (which has address, coordinates as well as other descriptions). Location may be too complex in your use case if it's really just (and always) an address.
AbdulMalik Shakir (Dec 07 2018 at 09:46):
@AbdulMalik Shakir Would it always be an address, or could it extend to GPS coordinates ? We just ahd a discussion in another thread about real time location tracking (e.g. of patients), whereby we'd need an extension on Observation to a Location resource (which has address, coordinates as well as other descriptions). Location may be too complex in your use case if it's really just (and always) an address.
@René Spronk My requirement is not always a postal address. It is any location that a decedent's remains might be found. GPS would be useful in some cases but sometimes it could simply be a landmark such as 'the 59th street entrance to Central Park' or 'Aboard United flight 167 from DC to LAX). The Location resource would meet all of my needs.
René Spronk (Dec 07 2018 at 10:45):
In which case you could propose such an extension (valueLocation, a reference to a Location resource) to Observation. (I won't be proposing it myself, my real-time-location question [the other thread] was raised on behalf of a participant in a FHIR training course)
Lloyd McKenzie (Dec 11 2018 at 01:49):
valueReference would probably be the appropriate extension. You'd constrain it to be a Reference to a Location in your particular profile
Last updated: Apr 12 2022 at 19:14 UTC
