Stream: conformance
Topic: Must supports in derived profiles
Eric Haas (Jul 27 2018 at 16:11):
So once an element is a must support always a must support, but what's not clear is does that that means that a must support could never be profiled to 0..0. It specifically says that it can be optional, so why couldn't a derived profile say that the element doesn't apply?
Lloyd McKenzie (Jul 27 2018 at 16:13):
Setting maxOccurs to 0 should generally be avoided. That says the sender must strip this element out because I'm not willing to ignore it. It's always better for interoperability to ignore rather than reject so long as doing so doesn't raise a safety issue.
Lloyd McKenzie (Jul 27 2018 at 16:13):
If a parent profile says "mustSupport", you must support the element as described in that IG if you want to be compliant with a derived profile.
Lloyd McKenzie (Jul 27 2018 at 16:14):
If you can't/won't support the element as described, then you can't make your profile a child profile.
Eric Haas (Jul 27 2018 at 16:16):
@Bryn Rhodes .... I guess that means no.
Bryn Rhodes (Jul 27 2018 at 16:22):
Yes, I suppose so, because the intent of using mustSupport within QI-Core is that systems can rely on those elements for decision support and quality measurement.
Richard Townley-O'Neill (Jul 30 2018 at 00:15):
This has made me think that mustSupport sits uncomfortably between profiles and implementation guides. The flag is set in a profile, but its meaning may be defined in the profile or in other docco that supports the implementation guide. See Must Support. When a profile is used in more than one implementation guide it will be easy for the flag to be separated from its meaning.
Maybe we should say that the mustSupport flag's meaning must be described in the profile. Any thoughts?
Lloyd McKenzie (Jul 30 2018 at 02:20):
If a profile is published on its own, mustSupport must be defined in that profile. If a profile is published as part of an IG, mustSupport can (and should) be defined once at the IG level for all profiles published in that IG. (Though there could be a few situations where there are distinct mustSupport rules associated with different groups of profiles, you'd still manage this at the IG level.)
Richard Townley-O'Neill (Jul 30 2018 at 02:44):
So profiles can have context, and one must consider this when using a profile outside of its original context.
Makes sens.
Lloyd McKenzie (Jul 30 2018 at 03:06):
Profiles have to have context - you can't make constraints from the base resource unless you have context of some sort.
Last updated: Apr 12 2022 at 19:14 UTC
