Skip to content

Clarity Human Services

Thanks for taking the time to suggest improvements to Clarity Human Services! 

If you don't see a category for your idea or don't know what category to choose, you can leave the category blank. We'll sort it out!

View our full feature request policy here.

Clarity Human Services

Categories

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

26 results found

  1. For the CAPER report, please automatically determine an individual enrollment is also the head of household.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Thank you for your submission! 

    To ensure HUD compliance, the [HUDX-228-AD] ESG CAPER report must align with the HUD HMIS programming specifications. Data Element 3.15 Relationship to Head of Household is used to determine heads of household.


    While this item will not be added to our roadmap at this time, we greatly value your feedback and encourage you to continue submitting ideas for future consideration.

  2. Hello,
    Since we work with lots of client data, and case managers often don't know a client's UID off the top of their head, it would be helpful if I'm able to include the client's full name and alias in a report. Once that report or dashboard is created, I would like to be able to schedule delivery by Encrypted Email which would better protect that client's information.

    7 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Declined  ·  0 comments  ·  Sharing  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. Using the data analysis tool, customers want to quantify the shelter-utilization migratory movements of clients with multiple emergency shelter entry-exit within a reporting date range – eg: 2 years. For example, a client has emergency shelter entry-exit history and has moved from zipcode 12345 -> 23456 -> 34567 -> 45678. The goal is to quantify each of these zipcode-to-zipcode records (eg: how many clients went from zipcode 12345 to 23456) and map this migration flow using “connect with lines”.

    11 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Thank you for your submission! While this item will not be added to our roadmap at this time, we greatly value your feedback and encourage you to continue submitting ideas for future consideration.

  4. Requesting the ability to download the table with columns in the same order as in the visualization on the dashboard.

    22 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Declined  ·  1 comment  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. I have many agencies that use the SSOM assessment, this was an assessment created by Bitfocus but there is no report to pull these fields out in a meaningful way and the fields are not available in looker. It would be helpful if these fields were available so reports can be built.

    10 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Declined  ·  0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. The count of adults and children in Looker are a snapshot of the project start. The household counts don't update over time if household members exit or they age into adulthood. Our users would like these fields to update as there are changes in the household.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Declined  ·  1 comment  ·  Sharing  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. Would it be possible to reveal the SPM Report Date Filter and SPM CoC Code Filter fields in the HMIS Performance Model in the same way that [Reporting Period Start Date] and [Reporting Period End Date] have been made available to allow for more intuitive dashboard filters?

    For example, using the Reporting Period Filter on a dashboard with enrollments and Current Living Situation assessments & using the [Reporting Period Start Date] and [Reporting Period End Date] fields to limit to just CLS records that occurred during the reporting period filter dates.

    9 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Thank you for your submission! The SPM filters were built to work with the SPM fields in a specific way. Using them in a different way could lead to inaccurate reporting.

    While this item will not be added to our roadmap at this time, we greatly value your feedback and encourage you to continue submitting ideas for future consideration.

  8. Submitting a request to add custom elements at entry/exit/update to the Data Quality Model.

    5 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. We normally finish our import around noon. Right now the model is updated only at midnight. There are always errors. Having to wait until the next day is frustrating.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Thank you for your submission! Updates take place at night to prevent issues arising during the day when resources are utilized most.

    While this item will not be added to our roadmap at this time, we greatly value your feedback and encourage you to continue submitting ideas for future consideration.

  10. In Looker, there are currently tables for entry data, status update data, and most recent data (labelled "update/exit" but pulls data for all clients regardless whether updates or exits exist). Please add a table for exit data. Yes, one can use the update/exit and filter it down to exited clients but that can't be combined with active clients without a merged look. E.g. Something as simple as:

    ClientID - Entry date - Exit date - Income at entry - Income at exit

    requires a merged look to avoid returning "income at exit" for clients who are not exited.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Thank you for your submission! The current functionality allows for greater flexibility. It should be possible to use a custom dimension to achieve the desired results without a merged look.

    While this item will not be added to our roadmap at this time, we greatly value your feedback and encourage you to continue submitting ideas for future consideration.

  11. When creating a Look, there are fields that aggregate response choices for HMIS Data Elements such as Destination. These can be very useful fields - but it's not possible to verify which response choices are included in each category. For example, under Update/Exit Screen is "Housed on Exit" = Housed or Not Housed.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Hi, Allie! In the ‘Data’ section of the Looker interface, there is an option to select ‘SQL’ to the right of ‘Results’. Once selected, the code for the Look will be revealed and logic/response choices can be verified. 

    For example, when ‘Housed on Exit’ is in a Look, clicking on ‘SQL’ will reveal the related Destination response field #s per the HMIS Data Dictionary in Appendix A (“WHEN last_screen.exit_destination IN ( 3, 10, 11, 19, 20, 21, 22, 23, 26, 28, 31, 33, 34 )“). Permanent Housing exit destinations are included within the logic of this dimension.”

  12. An option in the Reports module that allows customers to host their own reports using external reporting tools (like Microsoft SQL Server Reporting Services) would allow providers to run and schedule those reports as needed within Clarity without requiring them to be built using the default Pentaho report.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We are declining to pursue this capability at this time.

    Our team has a number of concerns that would need to be addressed before we could begin development of such a feature, including data ownership concerns, client privacy concerns and reusability concerns.

    We do generally encourage customers toward using Data Analysis (Looker) to address custom reporting needs. If Data Analysis is not meeting a specific need, we are open to working with customers to address those needs either through additional Data Analysis support or, if Looker really cannot address the needs, support for data interoperability with third-party solutions.

  13. A customer would like to set up a workflow that uses a Look to detect when outreach workers make direct referrals to shelters. Upon referral, the Look will send an email to a "matcher" who ensures the referral is appropriate before the receiving site accepts it.

    This is a time-sensitive process, so the 2-hour delay in Looker refresh rates makes this workflow unfeasible.

    Would it be possible to have an increased refresh rate to facilitate such a workflow?

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Thank you for your submission! While this item will not be added to our roadmap at this time, we greatly value your feedback and encourage you to continue submitting ideas for future consideration.

  14. The Error fields for HMIS Data Elements in the DQ model are a black box for CoCs and end users. No documentation of these fields exists to explain to users what values the fields in this model can take (what errors the fields are looking for) or the conditions that must be met for the field to flag enrollments as an error. Looker oriented end users ask questions about these fields, and would benefit from more thorough database documentation.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Thank you for your submission! While this item will not be added to our roadmap at this time, we greatly value your feedback and encourage you to continue submitting ideas for future consideration.


    Please reference the info bubbles for each field for additional information and the Data Quality Model article. If additional information is needed, please reach out to support@bitfocus.com. 

  15. We need to track historical attendance for our shelter programs, including slot information. We are often asked to report where someone stayed (their slot) longer than 90 days ago, but that is apparently all that is available in the Reservations Model. Not only does this mean that we need to combine data from multiple models just to get total history, it means that we are not able to provide this tracking for all kinds of vital business needs (contact tracing, legal requests, etc.) Please change this!
    https://get.clarityhs.help/hc/en-us/articles/360008990913-Reservations-Model

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Thank you for your submission! While this item will not be added to our roadmap at this time, we greatly value your feedback and encourage you to continue submitting ideas for future consideration.

    We recommend utilizing the Services Model to review reservation data outside the 90-day limit.  

  16. I cannot stress this need enough. The ability to view standard and custom reports/Looks and toggle filters in the reports/Looks should be standard across the board for ALL users, regardless of their access to building reports/data analysis. The data that users enter is only as useful as it is VISABLE to staff and managers. Users should be able to view reports as needed and not have that access unnecessarily bottlenecked at the Agency Manager level. This is not a novel request-- other products do this.

    13 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Looker is the built-in data analysis tool for ad hoc/custom reporting for Clarity. Access to it is controlled by a user's access role. If you do not have access, you should talk to your agency manager or System Administrator for your Clarity instance.

  17. The Program Roster report already has a program list and a date range in a separate tab from the data. So a header isn't really necessary. All this does is add messy steps for cleaning up the format before any filtering can be done. Please remove the header on the first tab. Thanks!

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Declined  ·  0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  18. Currently the Outbound recidivism measures are only accessible to users with aggregate data analysis rights. The Reentry Enrollment ID should continue to only be available to users with 'aggregate data analysis' rights as this Looker dimension would incidentally provide access to potentially restricted data. However, the other Outbound Recidivism measures in Looker that are currently restricted are the only way to effectively show recidivism that most closely meets HUD's definition of recidivism which is an important measure required by most local funders. Currently the only way for users to access correct recidivism data is to request our HMIS team supply…

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Declined  ·  1 comment  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  19. Having to publish custom fields to Looker before being able to analyze those assessments at all is prohibitive and discourages data use. Instead, fields should be immediately available as field/question-answer pairs in Looker, so we can pull the data out, crosstab it, etc.

    6 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    After investigating this functionality, we are unable to implement this idea. The impact of immediate publication of Clarity fields for data analytics would be detrimental to Looker performance which is a shared resource. 

  20. When using the gear icon on fields in embedded Looker fields in the data pane, the tooltip for the field comes up. The tooltip then blocks a lot of the items in the gear menu, such as Remove (sometimes it flashes while hovering over the top item in the list). This prevents you from clicking on the menu item. To improve this, please make the tooltip not come up when you are using the gear icon, only when hovering over the field name itself.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
← Previous 1
  • Don't see your idea?