Stream: implementers
Topic: Redundancy in Observation codes and units
Craig McClendon (Nov 07 2018 at 20:53):
If I have an Observation for "Calories burned in 24 hour Calculated" - LOINC 41979-6.
The Observation.code expresses that it is for 24 hours.
Also the Observation.effectivePeriod would likely encompass the 24 hours.
For the valueQuantity - is it preferred to also denote the timing with a UCUM code like: kcal/(24.h), or just specify the unit as kcal and avoid the triple-redundancy?
Lloyd McKenzie (Nov 07 2018 at 21:00):
The example units in LOINC are kcal/(24.h), so I guess that's what they expect and what will commonly be used.
Morten Ernebjerg (Nov 08 2018 at 08:49):
@Lloyd McKenzie Looks like you posted an answer in this other thread?
Lloyd McKenzie (Nov 08 2018 at 12:31):
I had. Now moved. Thanks for pointing out the issue @Morten Ernebjerg
Last updated: Apr 12 2022 at 19:14 UTC
