Comment:

Instead of unbounding Observation.referenceRange.meaning to allow for specifying the reference range type and the population it applies to, can we split it into two separate elements? Something like "type" (0.1) and "appliesTo" (0.*)?

It feels cumbersome to unbound something with the intent of adding two separate concepts to the same element when we have the ability to just make new elements. If we don't, we are forcing consumers who differentiate the two concepts to interpret the meaning from the source coding system, which is often more difficult.

Summary:

Do not unbound referenceRange.meaning - use two elements instead.