Stream: implementers
Topic: Timing Datatype
Mounika (Sep 25 2017 at 13:08):
Hello all, I am creating a profile for capturing Alcohol History using Observation resource. I want to capture the frequency of Alcohol use in years or months or days. In Observation resource there is no "Timing" datatype. So please add the datatype in Observation.value[x]
Michel Rutten (Sep 25 2017 at 13:41):
Hi @Mounika K, Observation.value[x] does support the Ratio datatype, maybe you can use that to express consumed amount per unit of time?
Eric Haas (Sep 25 2017 at 14:35):
You can create also create an extension for your observation value if feel this is need in your use case. The timing of an observation can also be expressed using effective time which does support timing.
Rajeev Jagadeesh (Sep 26 2017 at 00:12):
Need to implement recurrence pattern in CarePlan using Timing datatype, However didn't find properties to implement particular pattern (eg: Yearly, The second WeekDay on April Please see the attached image). Please let us know best possible way to implement the same in DSTU2. recurrence.PNG
Lloyd McKenzie (Sep 26 2017 at 03:29):
Second weekday of April and "Every year on Jan. 1" would require extensions. The remainder is doable within the scope of the existing resource. You're welcome to propose either or both as core elements to the data type if you wish...
Rajeev Jagadeesh (Sep 26 2017 at 03:40):
Is there any exisiting extensions we can use?
Lloyd McKenzie (Sep 26 2017 at 03:48):
Not that have been defined by HL7 International and not any others I'm aware of.
Grahame Grieve (Apr 30 2018 at 00:09):
@Thomas Beale asked me about the use of Timing, specifically, how actually useable is it? This is a good question, because it's certainly messy. But all the things in there are real requirements. So I'm interested in 3 things:
- a good user interface for inputting a general timing (I know that in some cirumstances, the options for a particular use will be more limited, but let's say, prescription, it's not going to be)
- a good rendering routine for displaying general timing
- a good routine for determining the next time that a Timing will be 'on' (or if it is presently on)
(Psuedo code preferred for the latter 2)
Grahame Grieve (Apr 30 2018 at 00:10):
has anyone got anything like this? I think these would be good additions to the reference implementations as well as useful for documentation purposes
Brian Postlethwaite (Apr 30 2018 at 05:26):
Rendering would be good in 2 modes, patient friendly and clinician shorthand
Last updated: Apr 12 2022 at 19:14 UTC
