Comment:

Early designs of observation included a component element that had code + value. In an early ballot, this was removed because OO did not believe that there were genuninely observations where multiple values share the same metadata (perforner, reliability, method, reference range), but have component values. But increasingly, these are cropiing up. The most significant is blood pressure, which is an early thing for people to encounter. Another is the genetic observation profile - a whole heap of derived values.

It's possible to treat these as related component observations, but this creates multiple observations, with multiple metadata (what's the implications of that?) and incurs processing overhead which has generated comment within the implementation community. I would like to bring back Observation.component, with the possible corollary that we limit it's use to some well described cases