Stream: questionnaire
Topic: Constraint for unitOption.valueCoding?
Paul Lynch (Feb 14 2019 at 17:38):
Would it be possible to add a constraint that the Coding in unitOption.valueCoding must contain either a code, a display value, or both? Right now both are optional.
Lloyd McKenzie (Feb 14 2019 at 19:10):
Not in general, though we could do that within SDC. Change proposal please :)
Paul Lynch (Feb 14 2019 at 19:20):
Why "not in general"? Wasn't unitOption originally added for SDC? I am not sure it helps to a constraint just for SDC, because in that case unless code processing a questionnaire only wants to accept SDC questionnaires, it will still have to handle the case where the constraint does not exist.
Lloyd McKenzie (Feb 14 2019 at 20:03):
Coding, in the general case, might have extensions - e.g. just a french translation of a display that doesn't have french. Or some other extension that eliminates the need for a code or a display or something else weird. We need to be pretty cautious when we define capabilities to not nail them down so much that implementers can't do what they need to do. In the SDC IG we impose additional constraints in the interest of maximizing interoperability, but that's not something we should rush to do outside the IG (e.g. when defining extensions).
Last updated: Apr 12 2022 at 19:14 UTC
