FHIR Chat · Current vs permanent residence · implementers

Stream: implementers

Topic: Current vs permanent residence


view this post on Zulip Jose Costa Teixeira (Dec 22 2020 at 19:30):

I need to capture Current vs Permanent residence.
Patient.address.use only has - home | work | temp | old | billing.
I'm a bit uncomfortable to say "current" = "temp". Thoughts?

view this post on Zulip Lloyd McKenzie (Dec 22 2020 at 20:00):

What does 'current' mean if not temporary? In general, 'current' is either temp, if there is one, or home, if there isn't a temporary.

view this post on Zulip Peter Jordan (Dec 22 2020 at 20:50):

In the 'Shaky Isles' anyway, who can say that an address is permanent, and my interpretation is that any use other than 'old' is current (i.e. in active use). If the aim is to distinguish between a primary home and vacation home, then 'temp' looks to be the best fit, although that does assume that this value set does not intend to cover temporary work or temporary billing addresses.

view this post on Zulip Jose Costa Teixeira (Dec 22 2020 at 20:57):

Right. If a person has one home only, "current" and "permanent" actually mean the same - so in that case, we use one address only - what is the code?
a) current (because it is current)
b) home (because it is home)
?

view this post on Zulip Jose Costa Teixeira (Dec 22 2020 at 21:02):

(Perhaps this is less confusing than I make it - I think this gets interesting when the person has an official address outsideof their home country, but then they spend some time in their home country due to some pandemic. that person may no longer know what's home and what's current. But that is a phylosophical /administrative problem, I guess.)

view this post on Zulip Lloyd McKenzie (Dec 22 2020 at 21:10):

You would send 'home'. FHIR has no notion of 'current'. The implication is that 'home' is 'current home' if there's no temporary.

view this post on Zulip Peter Jordan (Dec 22 2020 at 22:02):

Certain assumptions have to be made because the concepts in this value set are not mutually-exclusive. My assumptions (please correct me if they are incorrect)...
a. home = the primary active home address
b. work = an active work address
c. temp = a secondary active home address
d. old = a non-active work, home or billing address
e. billing = an active billing address

view this post on Zulip Jose Costa Teixeira (Dec 22 2020 at 22:04):

I'd not always assume temp to be secondary or home

view this post on Zulip Jose Costa Teixeira (Dec 22 2020 at 22:05):

The issue is that this is a required binding, so we should not leave much space for assumptions, right?

view this post on Zulip Peter Jordan (Dec 22 2020 at 22:19):

It's hard to see how the use cases of temporary work or temporary billing addresses are served by this value set. In those cases, I'd select work or billing. The primary/secondary distinction for home addresses is still essential for many purposes both medical (e.g. funding in NZ ) and legal (e.g. electoral rolls).

view this post on Zulip Brian Postlethwaite (Jan 11 2021 at 00:47):

There is also the period that comes into place.
I would expect that temp would be their home address at a period to over-ride their usual home address.
(The inclusion of this into FHIR was before my time)

view this post on Zulip Frank Oemig (Jan 11 2021 at 08:25):

That are different aspects:

  • type: home, work, vacation
  • priority: 1st, 2nd,..
  • time: period, current is open till now

Last updated: Apr 12 2022 at 19:14 UTC