Stream: implementers
Topic: Observation value components
natus (Aug 29 2018 at 12:57):
Hello,
In Observation resource I am wondering why single-observation value are stored out of the component results ?
There is value and component, in cases where we have 0 or 1 value we could store it in components, so can you explain to me the reason of the existence of value out of components ?
Thank you!
Lloyd McKenzie (Aug 29 2018 at 15:39):
Most observations just have a single value. Imposing component on them would make them more complex for no reason. There'd also be a question of what to put in the Observation.code vs. Observation.component.code.
natus (Sep 03 2018 at 15:31):
Thank you for your answer :) Another question related to this : why observation.components cannot store valueBoolean like it can in the root value of observation ?
Thanks,
Lloyd McKenzie (Sep 03 2018 at 15:54):
valueBoolean was a late addition. The guidance prior to that was to use valueCode. It's possible that adding it to component got missed. @Eric Haas ?
Eric Haas (Sep 04 2018 at 00:15):
was missed in STU3 but corrected in R4
Last updated: Apr 12 2022 at 19:14 UTC
