-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
🐛 Dictionary migration doesn't check program or entity level exceptions #991
Comments
@hknahal Question: what is the expected behaviour when an exception is removed? It's possible we need the system to re-evaluate all the data at that point instead of waiting for new submission or migration. |
@joneubank If an exception is deleted, the submitted data should be re-validated. For example, after Step #3 above (when exceptions for |
I agree. To my knowledge, this is not done today? I think we need to track two desired features:
|
No, it's not done yet. I agree, the two features you mention would resolve this issue. |
@joneubank @hknahal Do we want to release exceptions now or wait until we implement these two features? |
I would release and give us the ability to accept data with exceptions. Removing exceptions is a use case we don't have immediate expectation to need. |
I think we should go ahead and release exceptions instead of waiting. This won't block any of the programs. |
Same thoughts here! I will make a plan to track these two issues, and we shall be able to prepare for the release! |
Describe the bug
If program or entity level exceptions are deleted, and then migrate to new dictionary, it does not trigger system to check program or entity level exceptions.
Steps To Reproduce
tumour_grading_system
andtumour_grade
fields to beUnknown
.tumour_grading_system
=Unknown
andtumour_grade
=Unknown
. Validated and signed-off on clinical data.tumour_grading_system
andtumour_grade
to beUnknown
).Submitted Data
view for previously submittedtumour_grading_system
andtumour_grade
fields if they are submitted asUnknown
.It appears dictionary migration doesn't trigger the system to check the program/entity level exceptions when re-validating.
Expected behaviour
After dictionary migration, expected error to be reported in
Submitted Data
view for fields that are submitted asUnknown
but have no exceptions applied anymore.The text was updated successfully, but these errors were encountered: