Stream: implementers
Topic: effective[x]
Dongtu (Sep 04 2019 at 01:24):
How can I present both effectiveDateTime and effectivePeriod? My HAPI Fhir server only received one option
pasted image
Grahame Grieve (Sep 04 2019 at 01:26):
that's a choice - you can't have both
Dongtu (Sep 04 2019 at 01:27):
I know but why? I want both. How can I do that?
Jean Duteau (Sep 04 2019 at 01:28):
why would you want both in a given instance? How would you have both a period and a specific date-in-time?
Dongtu (Sep 04 2019 at 01:32):
I would like to present a specific date for the health examination and the start and end time
Lloyd McKenzie (Sep 04 2019 at 01:32):
Then specify the effectivePeriod. The date would be the same for both start and end.
Lloyd McKenzie (Sep 04 2019 at 01:33):
You can't use period to just specify times - you always have to specify the date too.
Lloyd McKenzie (Sep 04 2019 at 01:33):
So sending the effectiveDateTime as well would be redundant.
Armin Griebler (Apr 14 2020 at 12:47):
Is there an observation example with effectiveTiming? Because every time I validate my resource with hapi r4, the server asks for an effectiveDateTime or an effectivePeriod. My effectiveTiming is not recognized.
Lloyd McKenzie (Apr 14 2020 at 16:21):
What version of FHIR are you validating against?
Eric Haas (Apr 14 2020 at 16:31):
@Armin I don't think there is. It would be great if you could submit one as a FHIR tracker.
Armin Griebler (Apr 14 2020 at 16:38):
@Lloyd McKenzie against r4.
Armin Griebler (Apr 14 2020 at 17:05):
That would be my example-code:
"effectiveTiming": {
"repeat": {
"durationUnit": "h",
"frequency": "1",
"period": "5",
"periodUnit": "h"
}
}
So this in combination with a valueQuantity should measure one value every five hours. Shouldn't that be enough information to fulfill the requirements?
Lloyd McKenzie (Apr 14 2020 at 17:38):
How will you specify the multiple values in valueQuantity?
Lloyd McKenzie (Apr 14 2020 at 17:38):
This sounds like something for an order (ServiceRequest) not a result...
Armin Griebler (Apr 14 2020 at 17:43):
@Lloyd McKenzie I would use valueSampledData not valueQuantity. Sorry, my mistake.
Lloyd McKenzie (Apr 14 2020 at 18:35):
@Eric Haas do we have guidance on doing this? valueSampledData already has a period, which is redundant with effectiveTiming.frequency. Why not just have effectivePeriod and convey the frequency via valueSampledData.period?
Eric Haas (Apr 14 2020 at 19:45):
Timing is used for irregularly timed observations.
valueSampledData already has a period, which is redundant with effectiveTiming.frequency.
is an unintended conflict that we did not consider. Will need to add a comment to instruct to use effectivePeriod and convey the frequency via valueSampledData.period?
Tracker FHIR#26848
Lloyd McKenzie (Apr 14 2020 at 20:55):
If you have irregularly timed, how would you populate value? SampledData doesn't permit irregular timing
Eric Haas (Apr 14 2020 at 22:04):
I meant, we added timing for irregularly timed observations in general but did not consider SampledData. for sampled data that is not regular there are a couple of options, but I imagine the simplest it to use good ole resurrected valueAttachment.
Armin Griebler (Aug 27 2020 at 06:36):
Hello everybody, I've got a question about effectiveTiming in Observation. Due to the fact that the cardinality of every element in Timing is 0..1 or 0..*, there would be no required starting point of the Observation right? So how do I figure out the start of this event/Observation when such an information is not required? Could this be related to lastUpdated or another element in the resource?
Lloyd McKenzie (Aug 27 2020 at 14:44):
Some observations simply won't have timing information - and don't need it. For example, you could have an Observation that asserts the patient's blood type and not really care about the effectiveTime. More constrained profiles on Observation can mandate inclusion of effectiveTime (and other elements) where there's an expectation that these values must be known. In the general case, you simply have to be able to deal with Observations where it's not known when the Observed value is asserted to have held.
Last updated: Apr 12 2022 at 19:14 UTC
