ARCHETYPE Timing - non-daily (openEHR-EHR-CLUSTER.timing_nondaily_local.v0)

ARCHETYPE IDopenEHR-EHR-CLUSTER.timing_nondaily_local.v0
ConceptTiming - non-daily
DescriptionStructured information about the intended timing pattern for a therapeutic or diagnostic activity occurring over days, weeks, months or years.
UseUse to record structured information about the intended timing pattern for a therapeutic or diagnostic activity occurring over days, weeks, months or years. This archetype is designed to be used within the 'Direction repetition' SLOT within the CLUSTER.therapeutic_direction archetype, but can also be used in other CLUSTER and ENTRY class archetypes where clinically appropriate. In use cases where it's necessary to specify explicitly that an activity is to take place every day, the "Repetition interval" element can be set to "1 day".
MisuseNot to be used to record timing details within a single 24 hour time period. Use the CLUSTER.timing_daily archetype for this purpose. In use cases where it can be safely assumed that an activity should be carried out every single day, this archetype is redundant.
PurposeTo record structured information about the intended timing pattern for a therapeutic or diagnostic activity occurring over days, weeks, months or years.
ReferencesDerived from: Derived from: Timing - non-daily, Published Archetype [Internet]. openEHR, openEHR Clinical Knowledge Manager [cited: 2019-12-17]. Available from: https://www.openehr.org/ckm/archetypes/1013.1.2246
Copyright© openEHR Foundation, HiGHmed
AuthorsAuthor name: Ian McNicoll
Organisation: freshEHR Clinical Informatics Ltd.
Email: ian@freshehr.com
Date originally authored: 2015-09-11
Other Details LanguageAuthor name: Ian McNicoll
Organisation: freshEHR Clinical Informatics Ltd.
Email: ian@freshehr.com
Date originally authored: 2015-09-11
Other Details (Language Independent)
  • Licence: This work is licensed under the Creative Commons Attribution-ShareAlike 3.0 License. To view a copy of this license, visit http://creativecommons.org/licenses/by-sa/3.0/.
  • Custodian Organisation: HiGHmed
  • References: Derived from: Derived from: Timing - non-daily, Published Archetype [Internet]. openEHR, openEHR Clinical Knowledge Manager [cited: 2019-12-17]. Available from: https://www.openehr.org/ckm/archetypes/1013.1.2246
  • Original Namespace: org.highmed
  • Original Publisher: HiGHmed
  • Custodian Namespace: org.highmed
  • MD5-CAM-1.0.1: E5D0A90B38BC3A8F824BC65141448CB3
  • Build Uid: d021cf42-9cff-4494-8613-0a29e9884aa1
  • Revision: 0.0.1
Keywordstiming, administration, dosing, frequency, interval, order, recommendation, schedule, plan, repetition
Lifecyclerejected
UID724335d0-c720-4276-9cc5-182315d9e67d
Language useden
Citeable Identifier1246.145.937
Revision Number0.0.1
items
Repetition intervalRepetition interval: The interval between repetitions of the activity.
For example: 'Every 3 weeks'. If necessary, this element can be used to explicity specify that an activity is to take place every single day, by setting it to "1 day".
Allowed values: years, months, weeks, days
>0 days
FrequencyFrequency: The number of days per time period on which the activity is to take place.
For example: '3 times per week', '2-4 times per month'.
Choice of:
  •  Quantity
    Property: Frequency
    Units:
    • 1.0..7.0 1/wk
      Limit decimal places: 0
    • 1.0..31.0 1/mo
      Limit decimal places: 0
    • 1.0..366.0 1/a
      Limit decimal places: 0
  •  Interval of Quantity
    Lower: Property: Frequency
    Units:
    • 1.0..7.0 1/wk
      Limit decimal places: 0
    • 1.0..31.0 1/mo
      Limit decimal places: 0
    • 1.0..366.0 1/a
      Limit decimal places: 0

    Upper: Property: Frequency
    Units:
    • 1.0..7.0 1/wk
      Limit decimal places: 0
    • 1.0..31.0 1/mo
      Limit decimal places: 0
    • 1.0..366.0 1/a
      Limit decimal places: 0

Specific dateSpecific date: The activity should take place on a specific date or a specific range of dates.
For example: 'on 12 Jan 2017' or 'on 30 Oct 2017 to 6 Nov 2017'.
Choice of:
  •  Date
  •  Interval of Date

Specific day of weekSpecific day of week: The activity should take place on a specific day of the week.
For example: 'On Monday, Wednesday and Friday'.
  • Monday [The activity should take place on Monday.]
  • Tuesday [The activity should take place on Tuesday.]
  • Wednesday [The activity should take place on Wednesday.]
  • Thursday [The activity should take place on Thursday.]
  • Friday [The activity should take place on Friday.]
  • Saturday [The activity should take place on Saturday.]
  • Sunday [The activity should take place on Sunday.]
Specific day of monthSpecific day of month: The activity should take place on a specific day or interval of days of the month.
For example: 'on the 3rd, 13th and 23rd of each month' or 'on the 1st to the 10th of each month'.
Choice of:
  •  Count
    min: >=1; max: <=31

  •  Interval of Count
    Lower: min: >=1; max: <=31

    Upper: min: >=1; max: <=31

Timing descriptionTiming description: Text description of the timing.
For example: 'Use for one week, then stop for two weeks, then repeat'. This element is intended to allow implementers to use the structures for daily timings without necessarily specifying the non-daily timings in a structured way.
Specific eventSpecific event: The activity should take place in relation to a specific named event.
Event nameEvent name: The name of the event that triggers the activity to take place.
This element is intended for events that can occur at variable dates, such as onset of menstruation, and not for doses or activities that are conditional on a different varable. If required, the event name can be coded using a terminology, which could potentially be used to trigger an application to set a concrete date for the activity.
Time offsetTime offset: The period of time before or after the named event when the activity should take place. Negative durations can be used to signify that the activity should be taken before a known event.
For example: '3 days after onset of menstruation = menstrual onset + 3 days', '2 weeks prior to admission= admission -2 weeks'.
Allowed values: years, months, weeks, days

On / off cycleOn / off cycle: A cycle of activity where an on-off pattern is required.
For example: 'take for 1 week, omit 2 weeks, repeat 4 times'
OnOn: The period of time for which the activity should take place.
Allowed values: years, months, weeks, days
>0 days
OffOff: The period of time for which the activity should NOT take place.
Allowed values: years, months, weeks, days
>0 days
RepetitionsRepetitions: The number of repetitions of the on/off cycle.
min: >=0

Other contributorsSyed Ajaz, Alberta Health Services, Canada
Vebjørn Arntzen, Oslo University Hospital, Norway (openEHR Editor)
Silje Ljosland Bakke, Nasjonal IKT HF, Norway (openEHR Editor)
SB Bhattacharyya, Sudisa Consultancy Services, India
Laila Bruun, Oslo universitetssykehus HF, Norway
Lisbeth Dahlhaug, Helse Midt - Norge IT, Norway
Hildegard Franke, freshEHR Clinical Informatics Ltd., United Kingdom
Heather Grain, Llewelyn Grain Informatics, Australia
Kristian Heldal, Telemark Hospital Trust, Norway
Annette Hole Sjøborg, DIPS ASA, Norway
Hilde Hollås, DIPS AS, Norway
Evelyn Hovenga, EJSH Consulting, Australia
Tom Jarl Jakobsen, Helse Bergen, Norway
Nils Kolstrup, Skansen Legekontor og Nasjonalt Senter for samhandling og telemedisin, Norway
Heather Leslie, Ocean Health Systems, Australia (openEHR Editor)
Ian McNicoll, freshEHR Clinical Informatics, United Kingdom (openEHR Editor)
Lars Morgan Karlsen, Nordlandssykehuset Bodø, Norway
Isaiah Nyabuto, GIZ, Kenya
Andrej Orel, Marand d.o.o., Slovenia
Anne Pauline Anderssen, Helse Nord RHF, Norway
Vladimir Pizzo, Hospital Sírio Libanês, Brazil
Anoop Shah, University College London, United Kingdom
Norwegian Review Summary, Nasjonal IKT HF, Norway
Nyree Taylor, Ocean Informatics, Australia
Rowan Thomas, St. Vincent's Hospital Melbourne, Australia
Anders Thurin, SU, Sweden
Stian Torleif Varpe, Helse Bergen, Norway
Karl Trygve Kalleberg, Oslo Universitetssykehus, Norway
Gro-Hilde Ulriksen, Norwegian center for ehealthresearch, Norway
John Tore Valand, Helse Bergen, Norway (openEHR Editor)
Lars Ivar Mehlum, Nasjonal IKT HF, Norway
Translators
  • German: Caroline Bönisch, UMG, Caroline.Thoms@med.uni-goettingen.de, Caroline Bönisch
  • Norwegian Bokmål: Silje Ljosland Bakke, Nasjonal IKT HF
  • Portuguese (Brazil): Osmeire Chamelette Sanzovo, Hospital Sírio Libanês - SP, osmeire.acsanzovo@hsl.org.br