Performance issue with authoring local extension concepts due to the integrity check

[alex-ha-github]

Hi,

We are facing a performance issue with authoring local extension concepts in our system due to the integrity check.

Our local extension contains approximately 22k concepts which users modify through our system.
In a transaction involving concept modification, our system calls several APIs to update the concept and a few reference sets.
We've observed that it takes an extensive amount of time to perform an integrity check before committing a change to a concept or reference set.
This means that multiple integrity checks are executed for a single transaction.

We've noticed that the 'integrityIssue' flag in our branch is set to 'true', causing Snowstorm to trigger an integrity check for each data commit.
However, it appears the results of these integrity checks are not being utilized.

Would it be possible to skip the integrity check?

Thanks,
Alex

[kaicode]

The component integrity report is run automatically during codesystem upgrade (new dependent codesystem version, for example depending on a new International or National release). If an issue is found the flag is added to the codesystem branch. When any child branch is created or rebased that branch also gets the flag.
Any commit on a branch with the flag will run the report again, if the report is clean then the flag is removed from that branch automatically. When the fix is promoted if the parent branch has the flag the report is run again to clear the flag.

At Snomed International the strategy is to deal with any integrity issues straight after upgrade. The flag is used to notify the user that there is an issue. The integrity report is run again and the results used to identify which active axioms point to inactive concepts. Someone manually fixes the axioms on a child branch, classifies, and promotes the fix to the codesystem branch to clear the issue. This happens right at the start of the authoring cycle, before work begins.

Right now it's not possible to disable the integrity checks.

[alex-ha-github]

Thank you for the elaboration.

Our system now regularly generates integrity reports for user review.
Therefore, in our case, it isn't necessary to update the flag to notify the user immediately after changes to a concept or a reference set.

Would it be possible to add flexibility in the later release to allow local extensions to skip the integrity check before commit?
In other words, could we have an option to switch the integrity check on or off?

Given that it takes tens of seconds for each transaction to undergo an integrity check, skipping it could significantly improve performance.

Thanks.