-
Notifications
You must be signed in to change notification settings - Fork 174
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
[Candidate_parameters] Consent status - Add NA option #8732
[Candidate_parameters] Consent status - Add NA option #8732
Conversation
What is the use case for consent being not applicable? |
@driusan I believe on CCNA this was requested when the consent was not asked or was not relevant for the participant in question. On CCNA we have consent on brain donation, but there is a shortened version of the protocol where candidates are not eligible for autopsies, so they wanted to enter N/A in this case. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This works as expected
…opt_consent_status
)" This reverts commit efe0439.
Adding a N/A option for consent status. This is the expected behaviour: - Updating the consent status from Not Applicable to Yes/No is allowed - Updating the consent status from Yes/No to Not Applicable is NOT allowed - If Not Applicable is selected, no dates are required Removes CCNA override aces/CCNA#3822
Brief summary of changes
Adding a N/A option for consent status. This is the expected behaviour:
Not Applicable
toYes
/No
is allowedYes
/No
toNot Applicable
is NOT allowedNot Applicable
is selected, no dates are requiredTesting instructions (if applicable)
See test plan
Note
This is a CCNA override - https://github.com/aces/CCNA/pull/3822