You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
I created a binding with multiple value sets in IGAMT. Pushed to GVT. The value is in one of the value sets but I get an error.
I think one of the value set is not correctly exported in the ValueSetLibrary XML. It shows up in the NoValidation section for some reason.
Investigation shows that value sets with codes over a certain threshold (1000) are added to the list of value sets excluded from validation.
The long term solution, is to use external code sets for large value sets (once feature become available)
If we decide to keep this constraint (which might be necessary) I think we have to indicate that to the users somehow, may be an indicator on the vs binding.
Describe the bug
I created a binding with multiple value sets in IGAMT. Pushed to GVT. The value is in one of the value sets but I get an error.
I think one of the value set is not correctly exported in the ValueSetLibrary XML. It shows up in the NoValidation section for some reason.
User Account
rosinc
URL
https://hl7v2-igamt-2.nist.gov/ig/610841518b87bc0008787276/segment/61094e408b87bc00087884cd/structure
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Should not see an error the SPM-4 error.
Screenshots
Additional context
Profile:
Electronic-Laboratory-Reporting-(ELR)-610841518b87bc0008787276_20240124_184530.zip
The text was updated successfully, but these errors were encountered: