Stream: IG creation
Topic: Binding: (unbound) (example)
Becky Angeles (Aug 27 2020 at 20:22):
I'm a new IG creator and I apologize in advance for my lack of technical knowledge / verbiage. We are seeing "Binding: (unbound) (example)" on an element that is not profiled in our IG. The same element is not labeled "Binding: (unbound) (example)" in the base spec. For example, please see RiskAssessment.prediction.outcome [here] (http://build.fhir.org/ig/HL7/eLTSS/RiskAssessment-eltss.html). It also occurs on RiskAssessment.method. Does anyone know what is causing this and how to fix it? It was suggested that this may be an error in the IG publisher since we have not profiled this element.
Jean Duteau (Aug 27 2020 at 20:24):
there is no way to fix this without specifying the element and binding it to a value set in your profile. The base resource doesn't have a binding on that element, so it is left up to profiles to do a proper binding. The core spec doesn't list "(unbound) (example)" but it is in essence unbound since there is no binding specified.
Becky Angeles (Aug 27 2020 at 20:33):
Thanks, @Jean Duteau. So if we don't want that element profiled, do we really have to specify a value set? I have no idea what value set we should use? Or should I tell the Jira tracker submitter that this is not an error and just a "feature" of the publisher?
Jean Duteau (Aug 27 2020 at 20:36):
that's a good question. in a proper world, the resource in the spec would have a binding, even if it was just an example binding. then you wouldn't see the error. so I'm not sure what you can do in the meantime. I suspect that the best you can do is respond that the error is not an error in your profile but an error in the underlying resource.
Lloyd McKenzie (Aug 27 2020 at 20:44):
It's more of a rendering issue. We've talked about having multiple views of the 'binding' list just as we have multiple views of the profile elements. The 'snapshot' view would list all bindings (including ones your IG hasn't constrained and doesn't care about). The differential view would only list bindings for elements you've constrained somehow and the 'must support' view would list bindings for all required, modifier and must-support elements (i.e. the ones implementers absolutely need to pay attention to). However, we're not there yet. I wouldn't recommend declaring bindings just because you don't like seeing 'unbound'. That's not an error and not something you need to fix.
Becky Angeles (Aug 27 2020 at 20:48):
Thank you both - @Jean Duteau and @Lloyd McKenzie ! We will change our tracker resolution accordingly.
Last updated: Apr 12 2022 at 19:14 UTC
