Stream: implementers
Topic: Age extension to observation
Lauri Karppinen (Jan 04 2019 at 08:40):
Hi! What would be the most simple way to put age to observation. I tried to find extensions from simplifier but didn't find exactly appropriate for my use. I need to store age at the moment of examination. I have patients age in patient resource but i would need this extra one for observation. Feels like common thing You need but didn't find examples. Any help would be very much appreciated.
Mikael Rinnetmäki (Jan 04 2019 at 12:18):
I believe the most common scenario for this is that you have the patient's birth date in Patient resource and you derive the age at the time of the observation from that, based on the effective time of the observation. Does that scenario not suit you?
Mikael Rinnetmäki (Jan 04 2019 at 12:21):
Do you specifically need the age to be stored within the Observation resource, for consumers of that resource not to require access to the patient resource, for instance?
Lauri Karppinen (Jan 04 2019 at 12:34):
Calculating age from birthdate and effectiveDateTime is my second choice. Actually 1st version from screening study makes that already. Now I'm expanding our software to support serial monitoring studies and age in observation itself would be more useful in that. 1st I thought this would be common thing to make. But it seems not...
Lloyd McKenzie (Jan 04 2019 at 14:44):
Storing age with observations is pretty uncommon as you typically have the birth date available (along with gender) as part of the demographic information. If there's a particular subtype of observation where capturing age as part of the observation is typical, it could go as a component. Other than that, an extension is an option. But certainly the preferred approach is to just calculate it based on effectiveTime and date of birth.
Last updated: Apr 12 2022 at 19:14 UTC
