ARCHETYPE Timing ahs (openEHR-EHR-CLUSTER.timing_ahs.v1)

ARCHETYPE IDopenEHR-EHR-CLUSTER.timing_ahs.v1
ConceptTiming ahs
DescriptionStructured information about the intended timing of a therapeutic or diagnostic activity
UseUse to record structured information about the intended timing of a therapeutic or diagnostic activity. This archetype is designed to be used within the 'Timing' SLOT within any clinically appropriate archetype, or any slot where timing is required.
PurposeTo record structured information about the intended timing of a therapeutic or diagnostic activity.
References
Copyright© openEHR Foundation
AuthorsAuthor name:
Other Details LanguageAuthor name:
Other Details (Language Independent)
  • Licence: This work is licensed under the Creative Commons Attribution-ShareAlike 4.0 License. To view a copy of this license, visit http://creativecommons.org/licenses/by-sa/4.0/.
  • Custodian Organisation: Ocean Informatics
  • Original Namespace: com.oceaninformatics
  • Original Publisher: Ocean Informatics
  • Custodian Namespace: com.oceaninformatics
  • MD5-CAM-1.0.1: 87B5D179CB60010214671E213D31EE37
  • Build Uid: ac9aec87-c843-40e0-b4a3-74644b3454b3
  • Revision: 1.0.0
Keywords
Lifecyclepublished
UID37d7bd8a-306a-4d4a-b527-e00de9316883
Language useden
Citeable Identifier1013.1.1959
Revision Number1.0.0
items
FrequencyFrequency: The frequency as how often, either by number of times per time period or interval between each scheduled activity, that the activity is to take place.
or example: "q4h", "every 4 hours", "weekly", "every 2 days".
Timing descriptionTiming description: Text description of the daily timing. This element is intended to allow implementers to use the structures for different timings without necessarily specifying the timings in a structured way.
For example: "Take morning and evening".
Specific timeSpecific time: A specific time or interval of time when the activity should occur.
For example: "08:00" or "15:00-16:00".
Choice of:
  •  Time
  •  Interval of Time

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

    Upper:  Date/Time
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

Exact timing critical?Exact timing critical?: Is exact timing of the activity critical to effectiveness, or patient safety or wellbeing?
For example when administering antiparkinson medications.
As requiredAs required: Record as True if the activity should only occur when the "'As required' criterion" is met.
Termed 'PRN' ("pro re nata", latin: "as the situation arises") or 'PN' ("per necessare", latin: "when required") in some cultures.
'As required' criterion'As required' criterion: The condition which triggers an 'As required' activity.
For example: "for pain".
Specific eventSpecific event: A specific, named time event that the activity should occur in relation to.
Event nameEvent name: The name of the event that triggers the activity to take place.
For example: "Before each meal", "at bedtime", "in the morning". It is understood that these event names may not equate to the same exact times in different cultures. Coding with a terminology, for example HL7 FHIR Named events, is recommended where appropriate.
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:For example: '30 minutes after meal = meal + 30 minutes', '2 hours before bedtime = bedtime -2 hours'. '3 days after onset of menstruation = menstrual onset + 3 days', '2 weeks prior to admission= admission -2 weeks'.
On / off cycleOn / off cycle: A cycle of activity where an on-off pattern is required.
For example: "Apply an ice pack on for 20 minutes, off for an hour, repeat" or For example: 'take for 1 week, omit 2 weeks, repeat 4 times'
OnOn: The period of time for which the activity should take place.
OffOff: The period of time for which the activity should NOT take place.
RepetitionsRepetitions: The number of repetitions of the on/off cycle.
Other contributors
Translators