Stream: implementers
Topic: ServiceRequest.occurrenceTiming
Craig Newman (Mar 07 2019 at 15:23):
I'm looking at the ServiceRequest example at http://hl7.org/implement/standards/fhir/servicerequest-example2.xml.html and either I'm not understanding how to implement ServiceRequest.occurrenceTiming or there is an error in the example .
Within the text element it says: occurrence : Duration 15 days, Do 1-1 per 1 days
And a comment in the resource gives an example of: Chest therapy 1-4 times per day as needed to clear mucus
But the resource itself says:
<occurrenceTiming>
<repeat>
<duration value="15"/>
<durationMax value="25"/>
<durationUnit value="min"/>
<frequency value="1"/>
<frequencyMax value="4"/>
<period value="1"/>
<periodUnit value="d"/>
</repeat>
</occurrenceTiming>
I'm assuming frequencyMax came from the comment (1-4 times per day) but do the duration elements indicate that each therapy session (which can happen 1-4 times per day) should last from 15-25 minutes (which is nowhere else in the resource "text")? Should the "15 days" be represented as occurrenceTiming.repreat.boundsDuration?
Lloyd McKenzie (Mar 07 2019 at 15:43):
The text doesn't actually reflect the duration at all, which is legitimate. The text doesn't have to reflect all of the discrete data, only what's considered "essential" information. If the 15-25 is for automated billing but the human would just "know" (and be somewhat annoyed to be told), then not including it in the text is fine.
Craig Newman (Mar 07 2019 at 15:54):
I'm less worried about the text matching the discrete elements, I am more concerned with my own understanding that the "duration" elements are related to the duration of a given instance of a service while bounds or count should be used to indicate the "for 15 days" part of the instructions. bounds seems like the easier way to go in this case but it seems like count and countMax could be populated with values of 15 and 60 respectively. Are these the correct interpretations of duration, count and bounds?
Lloyd McKenzie (Mar 07 2019 at 16:06):
Duration is definitely about an individual instance. Bounds covers the outer bounds of all repetitions.
Craig Newman (Mar 07 2019 at 16:35):
Does anyone know why ServiceRequest.occurrence has a choice of data types? While more complex, the Timing data type would seem to offer a way to indicate just a single date/time (as opposed to occurrenceDateTime) or a period (as opposed to occurrencePeriod). Is it just a way to keep things simply when the ServiceRequest is only for a single instance of a service?
○ A specific date/time - occurrenceDateTime
§ This implies that the ServiceRequest is only for a single instance of the service
§ Why is this needed when occurrenceTiming.event is available?
○ A specific period of date/times - occurrencePeriod
§ Does this implies that the ServiceRequest is only for a single instance of the service given there is no "count" element in the Period data type?
§ Why is this needed when occurrenceTiming.repeat.boundsPeriod is available?
○ A complex timing definition - occurrenceTiming
Are my assumptions about occurrenceDateTime and occurrencePeriod only being used for a single instance ServiceRequest right?
Lloyd McKenzie (Mar 07 2019 at 16:41):
There are lots of use-cases where timing is overkill and there's a need/desire to constrain to the type that's actually needed.
Last updated: Apr 12 2022 at 19:14 UTC
