Hi Pablo, I think it is fair to say that ACtivity.timing not used much (if at all). The various timing syntax options are far from standardised around the world.
.timing is also difficult since real-world timings are often nested and need to be associated with specific parts of the archetype. The approach we have taken with Medication is to develop two timing Cluster archetypes. Timing - daily, Draft Archetype [Internet]. openEHR Foundation, openEHR Clinical Knowledge Manager [cited: 2016-06-18]. Available from: http://openehr.org/ckm/#showArchetype_1013.1.2245 and Timing - repetition, Draft Archetype [Internet]. openEHR Foundation, openEHR Clinical Knowledge Manager [cited: 2016-06-18]. Available from: http://openehr.org/ckm/#showArchetype_1013.1.2246 and have also allowed for a parseable dose string in the Medication order archetype. Medication order, Draft Archetype [Internet]. openEHR Foundation, openEHR Clinical Knowledge Manager [cited: 2016-06-18]. Available from: http://openehr.org/ckm/#showArchetype_1013.1.1445 I have an outstanding task to show some examples of use in more complex medication orders. Personally, I advise implementers to avoid ACTIVITY.timing. I would be interested to know if/how others use it. Ian Dr Ian McNicoll mobile +44 (0)775 209 7859 office +44 (0)1536 414994 skype: ianmcnicoll email: [email protected] twitter: @ianmcnicoll Co-Chair, openEHR Foundation [email protected] Director, freshEHR Clinical Informatics Ltd. Director, HANDIHealth CIC Hon. Senior Research Associate, CHIME, UCL On 18 June 2016 at 03:26, pablo pazos <[email protected]> wrote: > Hi, > > I was reviewing the latest specs and, compared with 1.0.2 where > ACTIVITY.timing usage is not so clear, I think we still need to improve > that specific point. > > *1. timing description is too focused on medication* > > "Many Instructions will have only one Activity, usually describing a > medication to be administered and its timing..." > > A treatment or procedure instruction can also be repeated, like do > physiotherapy 3 times a week, ultrasound application daily for 10 > repetitions, etc. (you can notice I sprained an ankle not so long ago). > > > *2. specific codes / syntax to be used* > > I think for the sake of completeness we need to include this in the specs. > I reviewed the time specification from the data_types spec v1.0.2 and I'm > not sure we are defining the syntax we need for ACTIVITY.timing. > > On HL7 specs I've seen a lot of commonly used codes that I don't know if > those are defined in any standard or if those are just common medical > vocabulary, I mean: ac, pc, bid, tid, qid, qhs, q4h, q8h, q12h, prn, .... > > Maybe we can include those as part of the specs > > > *3. the timing field description references HL7 GTS and ISO 8601* > > From HL7 v3 specs, the XML form is clear enough and it has a XSD that > defines the GTS, but the literal expression (the string code) is not so > obvious (AFAIK the rules to create it are not formally defined). What I'm > not sure of is if we can use the XML form (*might* complicate XSD > validation or the literal form). From v3: > > Table 46: Examples for Literal Expressions for Generic Timing > Specifications > Literal ExpressionMeaning > M09 D15 H16 N30 S34.12 September 15 at 4:30:34.12 PM as the intersection > of multiple periodic intervals of times (calendar patterns) > M0915163034.12 September 15 at 4:30:34.12 PM as one simple periodic > interval of time (calendar pattern) > M01; M03; M07 January, March, and July (a union of three periodic > intervals of time) > M04..09 M/2 Every second month from April to September (April, June, > August) > J1; J2; J4 Monday, Tuesday, Thursday > W/2 J2 every other Tuesday (intersection of every other week and every > Tuesday) > 1999 WY15 the 15th calendar week in 1999 (period code is optional for the > highest calendar unit) > WM2 J6 Saturday of the 2nd week of the month > M05 WM2 J6 Saturday of the 2nd week of May > M05 DM08..14 J7 Mother's day (second Sunday in May.) > J1..5 H0800..1600 Monday to Friday from 8 AM to 4 PM > J1..4 H0800..1600; > J5 H0800..1200 Monday to Thursday 8 AM to 4 PM and Friday 8 AM to 12 noon. > [10 d] H/8 Three times a day over 10 days (each time a 60 minutes > interval). > H0800..1600 \J3 Every day from 8 AM to 4 PM, except Wednesday. > (M0825..31 J1)..M0831 The last calendar week of August. > JHNUSMEM..JHNUSLBR The season from the U.S. holidays Memorial Day to > Labor Day > > And about ISO, I think we are talking about the "repeating intervals" form > (https://en.wikipedia.org/wiki/ISO_8601#Repeating_intervals). If that is > corrent, we should say that on the spec (the referenc to ISO 8601 is > vague). On the other hand, the ISO specification is not publicly available, > so we are referencing a closed spec from an open spec. That's why I think > we should define the syntax in our specs to avoid referencing closed specs. > > -- > Kind regards, > Eng. Pablo Pazos Gutiérrez > http://cabolabs.com <http://cabolabs.com/es/home> > <http://twitter.com/ppazos> > > _______________________________________________ > openEHR-technical mailing list > [email protected] > > http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org >
_______________________________________________ openEHR-technical mailing list [email protected] http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
