-
Type:
Change Request
-
Resolution: Persuasive
-
Priority:
Medium
-
FHIR Core (FHIR)
-
STU3
-
Modeling & Methodology
-
Datatypes
-
2.23.2.14
-
-
Grahame Grieve/Ron Shapiro: 2-0-0
-
Compatible, substantive
-
STU3
Existing Wording: Timing.repeat.count
Definition: A total count of the desired number of repetitions across the duration of the entire timing specification.
Timing.repeat.countMax
Definition: A maximum value for the count of the desired repetitions (e.g. do something 6-8 times).
Timing.repeat.duration
Definition: How long this thing happens for when it happens.
Timing.repeat.durationMax
Definition: The upper limit of how long this thing happens for when it happens.
Timing.repeat.frequency
Definition: The number of times to repeat the action within the specified period / period range (i.e. both period and periodMax provided).
Timing.repeat.frequencyMax
Definition: If present, indicates that the frequency is a range - so to repeat between [frequency] and [frequencyMax] times within the period or period range.
Timing.repeat.period
Definition: Indicates the duration of time over which repetitions are to occur; e.g. to express "3 times per day", 3 would be the frequency and "1 day" would be the period.
Timing.repeat.periodMax
Definition: If present, indicates that the period is a range from [period] to [periodMax], allowing expressing concepts such as "do this once every 3-5 days.
Comment:
Each of count, duration, frequency, period should indicate that if xMax is present, x becomes the lower bound/mimimum value. Each of xMax should indicate that they are the upper bound and x that is the lower bound.
Is is unclear how you differentiate "exactly X" from "at least X" without also imposing an upper limit? Similarly, it is unclear how to indicate "up to X" without a lower limit (I suspect the answer to this latter issue is a lower limit of 0).
Summary:
Clarify use of ranges in Timing
- is voted on by
-
BALLOT-4926 Affirmative - Elliot Silver : 2018-May-FHIR R4 INFRASRUCTURE R1
- Closed