475 results found
-
The Calendar needs to be more functional
We have received feedback from CoC partner agencies about using the calendar:
"When scheduling appointments, first the report of appointments has to be run to see if there's any conflicting appointments.
It takes FOREVER (feels like it) for a report to be run. Then you have to go put in the appointment after the report shows up.
Then you have to rerun the report to make sure the appointment you scheduled is on the guests schedule and wait for FOREVER again....
If there's anyway we could have a quicker way to access each guest's schedule that would be great.
It…
3 votesThank you for your feedback. We are currently reviewing this request.
-
More control over Sharing for Notes
Having finer control over Sharing for Notes would be very helpful. Customers wishing to grant "read-only" Clarity access to community members don't necessarily want them reading everything about clients.
It would be helpful to have the ability to control Sharing for specific Notes-type, not only at the Agency level, but also at the Program level.
3 votesThank you for your feedback. We are currently reviewing this request.
-
Update how the page refreshes when checking in clients for reservations/bed nights
When recording attendance for clients in large sites, the sections on the lower part of the page require the user to scroll to the bottom of the page, click the reservation slot, go back to the top of the screen to record the attendance, and then scroll all the way back down to click on the next reservation. The need to scroll the page is cumbersome for providers with large sites with numerous reservation slots; a change in how the page refreshes would reduce check-in time.
4 votesThank you for your feedback. We are currently reviewing this request.
-
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.
-
Improve workflow for entering services after program exit has already been entered
When a user has to update Services after a Program Exit has already been entered, they have to re-open the entire enrollment and make the changes and then close it back down again. This design seems like a means to make sure services are not outside of the range of the program start and end dates, but it doesn't actually work because you can put in a service outside of the program start and end dates.
4 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.
-
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.
-
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.
-
Quality Assurance: Chronological Date Entry Logic
Users at times enter in start dates that occur after the exit date or vise versa. Similarly, users enter Housing Move-in date that may be outside the enrollment (before start date or after exit date).
While there are canned reports ([DQXX-121] Project Start Date > Project Exit Date, [GNRL-106] Program Roster), a pro-active approach would be better.
Also, include logic that detects if enrollment dates are future dated and either generate an alert or possibly and this as "On/Off" switch for system admins to manage.
27 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 votesThank you for your feedback. We are currently reviewing this request.
-
Allow users to receive Assessment Due Warnings for program status updates in addition to HUD-required Annual Assessments
Currently Assessment Due Warnings only populate for HUD-required Annual Assessments. We would like to see the option to set Assessment Due Warnings for status update screens, so that users can receive reminders to complete status updates on a more frequent basis. For example, if the Case Status field in the program template is set to "Every Month", the user would receive an Assessment Due Warning each month a client is active in a program.
In addition, we would like to see the "Assessment Due" date on the "Status Due" tab of the Caseload tab to reset each time a status…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.
-
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.
-
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.
12 votesThank you for your feedback. We are currently reviewing this request.
- Don't see your idea?