There is a concern with Consent.except.code

If this code is found in an instance, then the exception applies. TODO: where do you not have to look? This is a problematic element.

This concern seems to indicate a data identification vector like this would be computationally difficult.

The need is real, so I think we must find a way to make this determinstic and yet useful. I don't have specific method of resolving.

It is clear to me that an organization that accepts these kind of exceptions must have figured out how to enforce them; where other organizations would not accept these kind of exceptions in the Consents they capture. This is a worst case, leaving the element defined but without specific enforcement guidance. If this is the conclusion, it needs to be identified as a concern with this element.