FHIR Chat · Forge: Strange handling of must-support in diff · tooling

Stream: tooling

Topic: Forge: Strange handling of must-support in diff

view this post on Zulip Morten Ernebjerg (Jun 04 2021 at 07:51):

I was working on some profiles in Forge and noticed that mustSupport is in some cases not present in the differential though it is present in the snapshot, which seems to lead to some strange behavior. It can be reproduced as follows:

  1. Take the IPS AllergyIntolerance profile StructureDefinition from the IPS 1.0.0 FHIR package.
  2. Manually delete the snapshot element.
  3. Open the profile in Forge and switch on "Save snapshot component"
  4. Make some inconsequential change and save the changes to ensure that the snapshot has been generated.

I then observe the following:

  1. The "mustSupport" flag on AllergyIntolerance.code is now gone in the differential, although it was there in the initial IPS profile in step 1 above. It is, however, still present in the saved snapshot and still displayed in Forge
  2. If I try to remove the mustSupport flag from AllergyIntolerance.code in Forge, I get the following warning: " When an element is marked as 'must be supported' in the resource, this can not be undone in the profile.". Given that IPS profiles the base AllergyIntolerance directly and must-support is never set in the base spec AFAIK, I'm not sure what this could mean.

@Ward Weistra Is there something amiss here?

view this post on Zulip Matthijs van der Wielen (Jun 07 2021 at 07:25):

Hi @Morten Ernebjerg ,

That is indeed not expected behavior. I have asked the Forge team to investigate why this happens. I will create a ticket for you on the Jira Service Desk to keep you informed of the progress.

Kind regards,
Matthijs

view this post on Zulip Morten Ernebjerg (Jun 07 2021 at 07:27):

thanks @Matthijs van der Wielen !

Last updated: Apr 12 2022 at 19:14 UTC


An HL7 Website -