FHIR Chat · Meaning of 'period' in Observation.effective[x] · implementers

Stream: implementers

Topic: Meaning of 'period' in Observation.effective[x]


view this post on Zulip Brian Reinhold (Apr 20 2017 at 12:44):

I am a little confused on the intended use of the period option in effective[x]. The statement is "The time or time-period the observed value is asserted as being true". If I have a situation where the measurement was taken over a certain period (such as an average heart rate; say a 60 second average) would the period be the proper way to report it OR do I give the time stamp of the measurement and indicate by some other means (such as an Observation.component) that it was computed over 60 seconds?

view this post on Zulip Lloyd McKenzie (Apr 20 2017 at 14:50):

Period would be the correct way. If you just wanted to capture a duration, I'd use an extension rather than a component

view this post on Zulip Eric Haas (Apr 20 2017 at 17:55):

Agree with Lloyd on using period. if you want to do duration. Extensions makes sense. Can you submit a tracker for consideration as a FHR core extension? We talked about adding a Timing data type to the resource to ber able to represent more complex patterns of observations but Timing is problematic since its designed for recording future events and not event that occurred in the past. We may need to knock on MNMs door and ask about whether we can get a twin datatype for past events.

view this post on Zulip Eric Haas (Apr 20 2017 at 17:55):

Components work as well.

view this post on Zulip Eric Haas (Apr 20 2017 at 17:57):

see GF#12896 re the whole timing in Observation thing

view this post on Zulip Brian Reinhold (Apr 20 2017 at 18:39):

Lloyd,
In the PHD case a component would have the advantage that all could understand it based upon the component.code element without requiring special coding efforts to handle the extension. PHDs have an attribute specifically meaning 'duration' and as long as one understood the 11073-10101 code, there would be no question about what the component means and how it affects the 'primary' observation.

view this post on Zulip Lloyd McKenzie (Apr 20 2017 at 19:53):

Contained observation vs. extension is 6 of one, half a dozen of the other. They're both name-value pairs. Systems are going to have to be able to handle both styles - extensions are going to be quite prevalent. So the decision of one approach vs. the other should be driven by whether you're truly talking about a separate "observed thing" or you're talking about a characteristic of the Observation. "How long did the observation take" is definitely a characteristic of the observing, not a thing observed.


Last updated: Apr 12 2022 at 19:14 UTC