544 results found
-
Redundant reservation selection options
In the program enrollment for a client, when making a reservation through providing a bed service, there are two times when a dropdown selection for the unit is available, once when providing the service and another time when previewing the reservation, but for the same unit. This can lead to frequent user errors as they believe they have made the unit selection in the first dropdown menu but, after clicking the Previre Reservation button, can inadvertently change that selection when selecting the slot in the next dropdown menu.
1 voteThank you for your feedback. We are currently reviewing this request.
-
HUD field Constraints
Whenever the HUD data standards are updated, we find that we have to replicate Bitfocus's constraints for our custom screens. Instead, adding the option to apply the already made constraint to the screen would be useful...either at the field level (Use current constraint for any screen when field is added) option or screen level (copy constraint to screen when field is added) option...
10 votesThank you for your feedback. We are currently reviewing this request.
-
LSA flags
Longitudinal Systems Analysis Report Clarity integration with HUD LSA validation flags and errors
The key idea is that a user wouldn't need to leave the Clarity app to submit an LSA and receive the LSA report flags. Flags are ingested into Clarity, and the Clarity UI can help resolve the flags.
“It seems like if you’ve got control of the LSA Export compiler, and if you’re hashing (storing a persistent record) of the data going into it, it would be simple to connect the dots backward to the origin of the error.
Right now, everyone in the country is doing…
6 votesThank you for your feedback. We are currently reviewing this request.
-
XML import client matching should have a match on PersonalID option
XML import client matching should have a match on PersonalID option
2 votesThank you for your feedback. We are currently reviewing this request.
-
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 -
Change the [STFF-103] User Active Caseload to include staff assigned through Care Team
Change the [STFF-103] User Active Caseload report to include staff assigned through Care Team
1 voteThank you for your feedback. We are currently reviewing this request.
-
Allow Custom Services to be Deleted with the DIT
If System Admins can upload Custom Services through the XML DIT, they should also be able to delete Custom Services. Our organization recently integrated a new agency into HMIS with a large quantity of custom services, but one of those services is misleading and should be removed from the system. We have no way to do this because "custom services are not supported for deletion using the DIT, only HUD-defined services".
4 votesThank you for your feedback. We are currently reviewing this request.
-
Edit Core Field Tool Tips
Allow System Administrators to edit tool tips for HUD Standard or core fields. This will allow System Administrators to address training or data collection needs in their instance.
1 voteThank you for your feedback. We are currently reviewing this request.
-
Recurring Reports
It would be help to have a recurring schedule options of the reports within the schedule option now. Currently, an user is able to schedule reports for each day they want the report initiated. It would be extremely useful to have an option to run reports daily, weekly, monthly, etc..
10 votesThank you for your feedback. We are currently reviewing this request.
-
Documentation Requirements- Allow for logic/conditions when configuring documentation requirements
Documentation Requirements- Allow for logic/conditions when configuring documentation requirements.
When configuring documentation requirements for a program, you can only list required documents but do not have the ability to indicate AND/OR conditions. The way it works now, you can add multiple documents but the system thinks that all documents are required. This is problematic because, for some programs, we want to indicate that a driver's license OR a passport is required but the system would think both are required.
For example, for housing programs, clients would only need to show one form of ID. Either the driver's license or a…
21 votesThank you for your feedback. We are currently reviewing this request.
-
1 vote
Thank you for your feedback. We are currently reviewing this request.
-
System Notification for Referral Updates and New Notes to the Agency Receiving the Referral
System notifications for Updated Referrals and New Referral Notes are sent only to the staff member who created the referral. This is to request that these automated system notifications also be sent to the Staff Member at the Referred-To Program. Notes are also only visible. This would improve communication between different teams and save referred-to agencies from clicking through each client on the referral list checking for updates.
7 votesThank you for your feedback. We are currently reviewing this request.
-
Create a workflow warning and hard stop for Housing Move-in Dates prior to the Enrollment Date.
Create a warning to notify users when they enter a Housing Move-in Date prior to the Enrollment Date. It should also prevent the user from saving the enrollment. The Housing Move-in Date cannot be prior to the client's enrollment date even if it is a PH to PH transfer. This creates an error on the APR. The APR in Clarity categorizes this as not being housed even though there is a recorded housing move-in date.
This causes problems when trying to troubleshoot the issue.
13 votesThank you for your feedback. We are currently reviewing this request.
-
Screen Field "start" and "end" dates
Objective: The "start" and "end" dates will allow the fields in screens to become active on the "start" date and inactive on the "end" date. Default start and end dates should match that of the screen.
Reason: Currently, system admin need to manually add, hide, delete, fields from screens live. These changes may cause some users to experience error messages. Also, some modification may include adding, hiding, or deleting several fields which might make this time consuming.
Outcome: System will automatically activate or de-activate screen's fields based on the dates entered.
1 voteThank you for your feedback. We are currently reviewing this request.
-
Screen "start" and "end" dates
Objective: The "start" and "end" dates will allow the screens to become active on the "start" date and inactive on the "end" date.
Reason: Currently, system admin need to manually activate or de-activate screens.
Outcome: System will automatically activate or de-activate screens based on the dates entered.
1 voteThank you for your feedback. We are currently reviewing this request.
-
Password expiration warning - specify site
Password expiration warnings are helpful, but they should specify the site they are for. I have a number of different passwords for a training site, a live site, migration site, etc. and all have different passwords. When I get the warning, it just says "Clarity." Would be much more helpful to know which site needs to be updated!
16 votesThank you for your feedback. We are currently reviewing this request.
-
Additional Options for Capturing 'Prioritization Status' for Coordinated Entry Assessments (4.19)
Related to the existing idea advocating for 4.20 Coordinated Entry Events to be Service based Events instead of Inferred Events, (https://ideas.bitfocus.com/forums/930328-clarity-human-services/suggestions/43917810-provide-access-to-data-element-4-20-response-categ), there is an additional need related to how the 'Prioritization Status' associated with 4.19 Coordinated Entry Assessments is captured within Clarity.
Currently, the only way to capture that a client has been 'Placed on prioritization list' (4.19_7.1) is if the Coordinated Entry Assessment associated with the client is placed on a Community Queue. For communities that choose to take advantage of the CQ functionality offered by Clarity, this works well, but for communities who choose not to…
10 votesThank you for your feedback. We are currently reviewing this request.
-
Email sent out to Navigator when assigned in Community Queue
When a Navigator is assigned in the Community Queue, it will help tremendously if the Navigator receives an email to know she/he has been assigned a new client. This will avoid having to do an extra step of having to email the Navigator.
9 votesThank you for your feedback. We are currently reviewing this request.
-
Allow Notes and Public Alerts to be Imported with the DIT
Most agencies that we integrate have client notes and public alerts that should be imported into HMIS, but the DIT doesn't support this. It would be helpful for new agencies and the team doing the integration if notes and public alerts could be imported using the DIT.
3 votesThank you for your feedback. We are currently reviewing this request.
-
Direct Expenses cannot exceed Fund Amount
When Direct Expenses are enabled for a Funding Source, it would be very helpful to add a feature that limits any Service Expenses to be charged in excess of the Fund Amount -ie, Direct Expenses cannot exceed Fund Amount; Total Available > 0. This feature could be added under "Eligibility" or it could be a flag that pops up when a user tries to add a new Service Item. Thanks.
5 votesThank you for your feedback. We are currently reviewing this request.
- Don't see your idea?