FHIR Chat · new validation error on extensions · IG creation

Stream: IG creation

Topic: new validation error on extensions


view this post on Zulip Eric Haas (Jun 27 2020 at 03:13):

Have 100s of error s in US Core for borrowing the capabilitystatement-expectation extension to provide guidance for expectation on searchparameters and capability statement. We advocated for allowing to be used everywhere in capabilitystatement to no avail - although I had a tracker approved to use it in SP.

Authors of the FHIR core extension simply fail to capture all the possilbe contexts for extensions when they are created. The upshot with this error is duplication and profligation of extensions in igs.

We certainly don't want to expose a duplicate extension in US Core just to provide the infrastructure to express conformance expectations on those elements not covered by core standard extension

The extension http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation is not allowed to be used at this point (allowed = e:CapabilityStatement.rest.resource.interaction, e:CapabilityStatement.rest.resource.searchParam, e:CapabilityStatement.rest.searchParam, e:CapabilityStatement.rest.operation, e:CapabilityStatement.document, e:CapabilityStatement.rest.interaction, e:CapabilityStatement.rest.resource.searchInclude, e:CapabilityStatement.rest.resource.searchRevInclude; this element is [[CapabilityStatement.rest.resource, BackboneElement.resource, BackboneElement])

view this post on Zulip Eric Haas (Jun 27 2020 at 03:22):

@Brett Marquard FYI

view this post on Zulip Grahame Grieve (Jun 27 2020 at 20:05):

I don't recall this discussion, but I can see why we wouldn't allow it to be used absolutely anywhere at all.

view this post on Zulip Grahame Grieve (Jun 27 2020 at 20:06):

But I'm going to assume that the list of places you have used it is reasonable. Still, I'm not sure procedurally how to resolve this

view this post on Zulip Eric Haas (Jun 27 2020 at 21:14):

can we make it a warning instead of an error?

view this post on Zulip Grahame Grieve (Jun 27 2020 at 21:24):

I think we don't want to do that for all extension use anywhere, no

view this post on Zulip Eric Haas (Jul 16 2020 at 20:39):

@Grahame: Any ideas how we can resolve this? CapabilityStatements in three IGs are peppered with it.

view this post on Zulip Grahame Grieve (Jul 17 2020 at 01:27):

I think you have to take it up with FHIR-I

view this post on Zulip Eric Haas (Jul 20 2020 at 20:11):

based on todays FHIR-I Call created : J#28103

view this post on Zulip Eric Haas (Jul 20 2020 at 20:17):

and, for searchparameter already voted on J#20470 will add comments


Last updated: Apr 12 2022 at 19:14 UTC