FHIR Chat · R4 IG diff has "unbound" with valueset strength constraint

Stream: IG creation

Topic: R4 IG diff has "unbound" with valueset strength constraint

Rob Eastwood (Feb 06 2020 at 01:03):

We are working on a profile of the R4 DiagnosticReport (I don't think this issue is limited to this resource though) to change an codeableconcept element's binding strength from example to preferred. Specifically the element DiagnosticReport.category with its binding to Diagnostic Service Section Codes.

Using Forge R4 to change the binding strength from 'example' to 'preferred' results in the StructureDedfinition xml as

<element id="DiagnosticReport.category">
      <path value="DiagnosticReport.category" />
      <binding>
        <strength value="preferred" />
      </binding>
</element>

When built using latest IG Publisher (v1.0.61), the resultant rendering in the diff table shows "(unbound)" in place of where the valueset should be:
pasted image

The snapshot and detailed descriptions pages do show the valueset name with hyperlink as expected.

And with the xml hand-edited to include the associated valueset element, the build diff table then renders correctly with the hyperlink to the valueset. However, subsequent Forge saves removes this valueset element (presumably as technically there has been no change to it and therefore has no place in the differential).

Any suggestions? Thank you

Note that this profile is not as yet published but I believe that this would be easily reproduced (just add a binding strength tightening to an existing binding from the spec) and build with the publisher.

Rob Eastwood (Feb 16 2020 at 23:02):

Confirming still present with IGP v1.0.64

Grahame Grieve (Feb 17 2020 at 00:58):

ok how do I reproduce it?

Rob Eastwood (Feb 17 2020 at 04:41):

Reproduce with:

with HL7 AU R4 AU Base Condition profile
for element Condition.bodySite, remove binding to https://healthterminologies.gov.au/fhir/ValueSet/body-site-1 ie remove this line; leaving this

<element id="Condition.bodySite">
    <path value="Condition.bodySite" />
    <binding>
        <strength value="preferred" />
    </binding>
</element>

(which in my understanding equates to leaving the existing spec binding for Condition.bodySite to SNOMED CT Body Structures but upgrading the binding strength from 'example' to 'preferred')

build with IGP etc

Last updated: Apr 12 2022 at 19:14 UTC