I am currently merging the Timing daily and non-daily archetypes into a single unified archetype. This effort aims to align closer with the FHIR Timing backbone element and enhance functionality for machine-to-machine communication, adhering to IETF standards. The goal of this refactoring is to ass…

Hi Lucas! I’m looking forward to seeing the results of your work. The original reasoning behind modelling timing as a set of archetypes was to enable every use case from the simplest to the most complex, without making each archetype too complex to understand (or model!). This set includes not only…

Thank you so much, for your input, Silje. You spared me from an unsurmountable amount of work. I am so happy, that I can now include the missing units.

I’ll also be interested in your conclusions @lukas.eksteen . The current archetypes are complex but the have been well road-tested by both GP community prescribing use and by inpatient use, which have slightly different requirements. I’ve had a look at the current FHIR Timings datatype and I think…

Hi Ian. I look at the current requirements in our EHR and what RFC5545 specifies, and based on that, I model the archetype. In a second step, I align it to FHIR to allow an easier mapping onto FHIR, which will represent a subset of the modeled archetype.

Really interested in how you get on Please keep us posted with examples of your reworked archetype. I suspect you will find that RFC5545 drives you crazy in this context. This was something that was looked at many years ago. We came up with the dose and timing model, based on a lot of prior work …

[image] ian.mcnicoll: more complex timings or be just as confusing. e.g. “4 times a day, 3 times per week”. Yep, as well as things like “2 tablets in the morning and 3 at night, on Mondays, Wednesdays and Saturdays” or “apply on affected skin until it glistens in the morning for two weeks, th…

Hi Ian I have read RFC5545 and it is actually straightforward, but highly boring - reading more than 150 pages may drive you crazy. Moreover, there exist additional RFCs, which should be accounted for (RFC5546, RFC6868, RFC7529, RFC7986, RFC7265) and I have not read it — yet. I hope to finish these…

Merging Daily and Non-Daily Timing Archetypes: Defining Units like 1/wk, 1/mo, 1/yr

Clinical

heather.leslie (Heather Leslie) 6 May 2024 00:18 3

Hi @Lucas Have you see seen this recent thread? - "Times of the day" vocabulary? - #9 by heather.leslie

@thomas.beale @ian.mcnicoll @joostholslag It would be good to have the clinical modellers and specs teams working together on this .

Topic		Replies	Views
"Times of the day" vocabulary? Ask IEB	14	441	2 July 2024
Specs about ACTIVITY.timing still unclear Technical (archive)	4	13	13 July 2016
"Administration rate" constraints are quite strict for rate therapy medication order Ask IEB	7	91	7 April 2026
Timing in the real world, openEHR and FHIR Clinical fhir , time	23	1486	27 May 2020
Feedback request from clinicians and modellers: Archetypes with time dimension Clinical	10	330	15 September 2023
Does the data_types in Better's Archetype Designer include the 'time_specification'? Archetype Designer datatypes	15	699	8 August 2023
UCUM dependence - governance? General Discussion ucum	40	284	15 January 2025
ACTIVITY and timing Technical (archive)	15	7	18 August 2013
Suitable data type to record frequency of something happening Technical (archive)	5	6	29 September 2017
ECG archetype advice required Clinical (archive)	12	18	7 September 2018

Merging Daily and Non-Daily Timing Archetypes: Defining Units like 1/wk, 1/mo, 1/yr

Related topics