search

abtassociates / eva

Eva is a HUD application to aid HMIS Leads with data analysis. It is an open-source project intended for local use by HMIS Administrators in Continuums of Care (CoCs) around the U.S. and its territories.
GNU Affero General Public License v3.0
14 stars 4 forks source link

Missing Fields Not Accurate #564

Open fbradford7 opened 1 week ago

fbradford7 commented 1 week ago

Is your feature request related to a problem? Please describe. Eva flags fields answered as "client doesn't know" and "client prefers not to answer" as missing but these are valid answers per the data standards.

Describe the solution you'd like I would like Eva to be able to decipher if a field has been answered "doesn't know" or "prefers not to answer" rather than information actually missing or "data not collected"

Describe alternatives you've considered I manually check each answer for these missing fields

Additional context Add any other context or screenshots about the feature request here.

zabalad commented 4 days ago

Hi @fbradford7,

Thank you for reaching out. We want to ensure we're on the same page in terms of how we define "missingness" in the context of Eva.

Currently, there are four possibilities for missingness in Eva: (1) Blank, (2) doesn't know, or 8 (3) prefers not to answer, or 9 (4) Data not collected, or 99.

Currently, blank values and "data not collected" are flagged as errors by Eva. "Doesn't know" and "prefers not to answer" are flagged as warnings by Eva, meaning that the system makes a note of it but does not treat the values as needing to be corrected.

It's worth noting that we are currently in the process of recategorizing "data not collected" as a warning rather than an error. Once we make this change, the only type of missingness that will be treated as an error moving forward will be blank entries. However, this change has not been made yet - we are still working on this.

But to address your request, which was to differentiate between doesn't know/prefer not to answer and true missing/data not collected - Eva currently does this already by differentiating between warnings and errors in the data quality checks. Below is a screenshot with the definitions of High Priority/Error/Warning (found in the Instructions on Eva): image

Please let us know if this clarification helps to resolve your issue. If not, please follow up with additional details and/or a screenshot of your Eva validation output (please DO NOT include screenshots of your input data).