Stream: IG creation
Topic: Expectations for definition resources
Keith Boone (Jul 30 2020 at 16:34):
Definition resources provide constrains on the resources for which they are a definition, but no explicit way to define certain other requirements (e.g., optional/recommended/required as MAY/SHOULD/SHALL). The capabilitystatement-expectation extension seems to be almost perfectly defined to address this, but will not validate (even if I try to define a profile that says it can be present).
Eric Haas (Jul 30 2020 at 16:55):
I have logged trackers to expand this extension's context more broadly in Capabilitystatement and for SearchParameters. What other contexts does it need?
Eric Haas (Jul 30 2020 at 16:56):
We use Must Support as way to define other definitional element how is this different?
Keith Boone (Jul 30 2020 at 18:00):
mustSupport is for profiles. It does not appear in a Resource. So, while Measure defines conformance requirements for MeasureReport resources which reference it, it does not have a way to say: SHOULD have this part, SHALL have that part.
Eric Haas (Jul 30 2020 at 18:27):
@Bryn Rhodes ?
Eric Haas (Jul 30 2020 at 18:29):
I lobbied for expectation-extension to be used everywhere like DAR but that was met with resistance. I think your use case makes a lot of sense.
Lloyd McKenzie (Jul 30 2020 at 20:09):
Perhaps discuss it with the CDS folks - they're responsible for most of the definition resources
Bryn Rhodes (Jul 31 2020 at 17:35):
Yes, this use case makes sense, so a conformanceExpectation extension, we have run into other similar use cases, but haven't done anything with it so far. Submit a tracker?
Last updated: Apr 12 2022 at 19:14 UTC
