13 results found
-
Prevent pop-up warning when following guidelines for missing/partial SSN
Even if users follow the updated guidance for SSN data entry when a SSN is missing or they only have the last four (i.e. xxx-xx-xxxx or xxx-xx-####), the "The SSN entered does not conform to Social Security Administration guidelines" pop-up warning still appears. This is confusing to users given that the guidance has changed and especially given that only having the last four is not a DQ issue under the FY24 data standards. Ideally this pop-up would only appear for SSNs listed on the August feature updates page that the SSA considers invalid:
- The last four digits of the…7 votes -
Add an option to identify pets as a “Household Member"
User Story:
As an outreach worker who works with unhoused individuals and their pets, I want an option to be added that identifies a pet in the “Household Members” section so that we can link the pet to the owner, have an accurate representation of family size, track safety and liability, and know who the client will be taking with them if they were to receive housing. We provide services to clients AND their animals, and we propose a comprehensive set of criteria to be included such as:
- Photo Entry
- Breed
- Age
- Name
- Color
- Microchip status
- Vaccination records
- Size
- Temperament
- …
30 votes -
Multi-CoC Projects: Allow a Primary Site for Each CoC
When reviewing and reporting on data for projects that serve more than one CoC, currently primary site needs to be inferred when the CoC != the Selected CoC as there can only be one primary site in the Clarity UI. This impacts the LSA, HIC, and CSV Export.
The Data Dictionary states that "There must be a one-to-one relationship to 2.02 Project Information if the project only serves one CoC (most common). … It must be possible to associate a project with the CoC code for every geographic area in which the project operates and for which it will be…13 votes -
Assessment Processor - Save Points to the Nearest Hundredth
When assigning points to a Subtotal in an Assessment Processor, the logic rounds point values to the nearest tenth (ie: if a point value of 3.75 is assigned, the system rounds the value up to 3.8 when the screen is saved).
There are 2 HUD CoCs in our implementation that are creating new Coordinated Entry Assessments, both of which are assigning a percentage of points based on clients' responses to the assessment questions. This results in point values that need to be rounded to the nearest hundredth.
Without the ability to assign point values to the nearest hundredth, our implementation…
11 votes -
Tag users in referral notes / messages - or be able to have more than two people on a message thread
It would be great if in the body messages, such as the referral notes, you could tag other users so they could be brought in to the conversation easily to discuss the client in a thread - or be able to have communications with more than one other user on a single thread.
17 votes -
CSV/XML Export - include Unique ID instead of Personal ID
HUD's new EVA data quality tool, provides a powerful resource for identifying data quality issues. However, EVA flags clients with errors and identifies them using the Personal ID. I assume this is because the Unique ID is not available in the export. I'm curious why this is. Is it possible to make the Personal ID searchable in Clarity or to replace it in the export with the Unique ID? I'm trying to find an easy way for our partner agencies to use EVA to find and correct errors, but as of now, it is not easy for them to navigate…
5 votes -
Clarity Looker and SQL Analytics Documentation
It would be useful to have the following updated and pushed to "Data Analysis" section in the Help Center of the Bitfocus website, every time Looker or SQL Access has been updated:
- A "Clarity to Looker Data Dictionary" showing all the fields available in all of the Looker models
- A diagram of how the tables relate in Looker
- SQL Access fields list showing all the fields available
- A diagram of how the tables relate in SQL Access
It would also be helpful to include field descriptions, HMIS metadata, table name, and name.
42 votes -
Report: Which clients don't have release of information (ROI) on file and/or who have ROI renewals coming up.
With the requirement to upload ROIs for every client, it would be extremely helpful to be able to run a report and see which clients in a given program are due for a renewal or need an initial ROI uploaded. Checking each client individually is a huge waste of staff time when you have thousands of people to check.
3 votesThank you for your feedback. We are in the planning phase of a feature or update related to this item.
-
Allow for manual removal of clients from encampments.
Users have expressed scenarios when automations will not prompt the removal of a client from the outreach map when appropriate. Allowing users this ability will account for the scenarios in which automations are applicable.
22 votesThank you for your feedback. We are in the planning phase of a feature or update related to this item.
-
user caseload dashboard
User Dashboard that summarizes their caseload.
For example: How many and what HUD required fields are not entered correctly/missing, clients without services, notes, CLSAs, missing Annual Assessments, Housing dates not entered within enrollment timeframe, client just turned 18 and needs updating, etc... Any data points where logic is being violated this dashboard would provide a summary of where their caseload stands and has quick links to jump to make those corrections/updates.
9 votes -
Allow Search for Client by Personal ID
Personal ID (as opposed to Unique ID) is included in the data extracts for Federal HMIS Partner submissions. Errors in those submissions will identify offending records by Personal ID, however, there's no easy way to search for a record.
Allowing search by Personal ID would be a huge help to the users who are troubleshooting the Federal HMIS Partner uploads.
26 votes -
Multi-select fields should be available on system/agency level
Currently, multi-select fields are only available to be set up by BitFocus. Instead, system admins need to use multiple checkbox fields for each option. Typically, select-all-that-apply questions have many, many choices (even when those questions are designed well and thoughtfully). This quickly eats into custom field limits and custom field publishing to data analysis (both of which are very bad design elements themselves). Please improve this.
28 votesThank you for your feedback. We are in the planning phase of a feature or update related to this item.
-
Audit Log Enhancements
Here are some of the things we would like to see in an audit log:
Audit log similar to client audit log (full history) for user accounts (last edits, values changed, additional agency access added/removed, email changed, photo changed, etc)
Agency audit log for changes to address, active status, creation date.
Program audit log in the same vein with history (who changed what and when on a program - the name, the funding, the beds, basically every PDDE change/edit/creation)
Service audit logs (who created them, edited them, changed available dates, active/inactive, etc.)
Sharing settings - audit history on sharing settings.…11 votesThank you for your feedback. We are in the planning phase of a feature or update related to this item.
- Don't see your idea?