Require Consistency with Disabling Condition & Disability Type Fields in Order to Save Screen
This request comes from Customer:
This feature enhancement would require that there be no inconsistencies between the field "Disabling Condition" and the disability types (Physical Disability, Developmental Disability, Chronic Health Condition, HIV/AIDS, Mental Health Problem, and Substance Abuse Problem) in order to save the screen.
When a client advises that s/he has a disabling condition, the response to the Disabling Condition field should be "Yes". You then must select the type of condition from one or more of the following: Physical Disability, Developmental Disability, Chronic Health Condition, HIV/AIDS, Mental Health Problem, and Substance Abuse Problem. Once you have selected the condition, you then indicate that it is a disabling condition by selecting "Yes" in response to either Long Term (in the case of a physical disability, chronic health condition, mental health problem, and substance abuse problem) or Substantially Impairs Independence (in the case of developmental disability and HIV/AIDS). If none of the conditions have been identified as a disability, but Disabling Condition is set to "Yes", the user would not be able to save the screen.
When a client advises that s/he does not have a disabling condition, the response to the Disabling Condition field should be "No". You then must review the list of conditions with the client and determine whether the client has one or more of them. If so, you would select the appropriate condition, then indicate that it is not a disabling condition by selecting "No" in response to either Long Term or Substantially Impairs Independence. If one of the conditions is identified as a disabling condition, and the Disabling Condition field is set to "No", the user would not be able to save the screen.
In cases where the response to Disabling Condition is either "Client doesn't know," "Client refused," or "Data Not Collected," we should not see any of the conditions identified as either a disabling condition or not a disabling condition. Instead, what we should see is that either (1) the client doesn't know if the condition is a disabling condition (select "Client doesn't know"; (2) the client refuses to advise whether the condition is a disabling condition ("select "Client refused"); or (3) information to determine whether a condition is a disabling condition or not has not been collected (select Data Not Collected). If one or more of the conditions is identified as a disabling condition, or none of the conditions is identified as a disabling condition, but the response to the Disabling Condition field is "Client doesn't know", "Client refused", or "Data Not Collected", the user would be unable to save the screen.
As part of our ongoing efforts to build the best feedback platform for you, ideas that have not received a vote or comment in the past year have been set as “Archived.” Please feel free to resubmit this idea using this submission guide.