Most of the time when we have a repeating CodeableConcept with a binding, the intention is that all repetitions should be drawn from the specified value set (e.g. 'jurisdiction').  However, in some cases, the actual intent is that one of the repetitions ought to come from the value set, but other repetitions might come from something completely different.  I.e. the real desire is to bind a single slice (which might be 0..1 or 0..*), but not all repetitions.  This is done easily enough in a profile - where we have access to slicing.  However, there's no way to do this in resources.

As an example, the extensible binding declared on the Condition.category (and AdverseEvent.category, Condition.category, Consent.category, Substance.category and probably others) element applies to all repetitions of the category element, not only one.  Which means that all category elements are going to spit out a warning if they're not drawn from that value set - even if one of them does.  The usage notes for Condition.category make clear that the intention is definitely to allow orthogonal categories to also be used.  We need to figure out some way to make this clear - and we need to do it before Condition goes normative...