Timing Repeat

$10 / year

Timing Repeat indicates a set of rules that describe when the event is to occur or should occur again. Many timing schedules are determined by regular repetitions.

Complexity

Timing Repeat have Length/Range of lengths, or (Start and/or end) limits which indicates either a duration for the length of the timing schedule, a range of possible length, or outer bounds for start and/or end limits of the timing schedule. Timing.repeat.duration indicates How long this thing happens for when it happens. If durationMax is present, this element indicates the lower bound of the allowed range of the duration. For some events the duration is part of the definition of the event (e.g. Intravenous (IV) infusions, where the duration is implicit in the specified quantity and rate). For others, it’s part of the timing specification (e.g. exercise). Some activities are not instantaneous and need to be maintained for a period of time.

Note, though, that some systems include timing details in something like ‘Dosage instructions’ which is wider than just Timing; those systems do not use the Timing data type. Other systems use a set of ‘common’ codes – including, but usually not limited to, widely understood acronyms such as “bis in die (BID)” which means in Latin, twice a day. If a Timing.code is provided, the code is understood to be a complete statement of whatever is specified in the structured timing data (except for Timing.repeat.bounds, which applies to the code), and either the code or the data may be used to interpret the Timing. A structured timing specification should be provided whenever possible, unless the code is BID, ter in die (TID) which in Latin means three times a day, quater in die (QID) which in Latin means four times a day, ante meridiem (AM) which in Latin means Before Midday or Post Meridiem (PM) which in Latin means After Midday, which have a ubiquitous meaning.

These codes shall be understood as having the formal meanings. Note that BID, etc. are defined as ‘at institutionally specified times’. For example, an institution may choose that BID is “always at 7am and 6pm”. If it is inappropriate for this choice to be made, the code BID should not be used. Instead, a distinct organization-specific code should be used in place of the HL7-defined BID code and/or a structured representation should be used (in this case, timeOfDay).

Date Created

2018-09-20

Last Modified

2019-11-01

Version

4.0.1

Update Frequency

Annual

Temporal Coverage

N/A

Spatial Coverage

United States

Source

John Snow Labs; Health Level Seven International;

Source License URL

Source License Requirements

N/A

Source Citation

N/A

Keywords

FHIR, HL7, Medical Terminology, Processes Data, Processes Information, Processes Documentation, Health Information Exchange, Electronic Health Records, FHIR Smart, Smart on FHIR

Other Titles

FHIR Timing Repeat Datatype, Electronic Health Records Exchange Through FHIR

NameDescriptionTypeConstraints
Concept_NameName of the concept in the FHIR structure.stringrequired : 1
Computer_Ready_NameA Computer-ready name (e.g. a token) that identifies the structure - suitable for code generation. Note that this name (and other names relevant for code generation, including element & slice names, codes etc) may collide with reserved words in the relevant target language, and code generators will need to handle this.string-
TypeThe type the structure describes.string-
Dollar_RefThe "$ref" string value contains a Uniform Resource Identifier (URI) which identifies the location of the JSON value being referenced.string-
DescriptionA free text natural language description of the structure and its use.string-
ItemsThe value of the keyword should be an object or an array of objects. If the keyword value is an object, then for the data array to be valid each item of the array should be valid according to the schema in this value.string-
EnumThe enum is used to restrict a value to a fixed set of values. It must be an array with at least one element, where each element is unique.string-
Concept NameComputer Ready NameTypeDollar RefDescriptionItemsEnum
Timing_Repeatid#/definitions/stringUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
Timing_RepeatextensionarrayMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension there is a set of requirements that SHALL be met as part of the definition of the extension.{'$ref': '#/definitions/Extension'}
Timing_RepeatmodifierExtensionarrayMay be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).{'$ref': '#/definitions/Extension'}
Timing_RepeatboundsDuration#/definitions/DurationEither a duration for the length of the timing schedule a range of possible length or outer bounds for start and/or end limits of the timing schedule.
Timing_RepeatboundsRange#/definitions/RangeEither a duration for the length of the timing schedule a range of possible length or outer bounds for start and/or end limits of the timing schedule.
Timing_RepeatboundsPeriod#/definitions/PeriodEither a duration for the length of the timing schedule a range of possible length or outer bounds for start and/or end limits of the timing schedule.
Timing_Repeatcount#/definitions/positiveIntA total count of the desired number of repetitions across the duration of the entire timing specification. If countMax is present this element indicates the lower bound of the allowed range of count values.
Timing_Repeat_count#/definitions/ElementExtensions for count
Timing_RepeatcountMax#/definitions/positiveIntIf present indicates that the count is a range - so to perform the action between [count] and [countMax] times.
Timing_Repeat_countMax#/definitions/ElementExtensions for countMax
Related Data Packages