Skip to content

Settings and activity

48 results found

  1. 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)
    An error occurred while saving the comment
    Jessica Salazar commented  · 

    I was reviewing ideas and there are many top high voted ideas that align with this one. The idea would be to centralize a lot of these ideas since many are caseload based work. So if every user has a "dashboard" providing these sort of flags and quick links to program enrollments, we would ideally see an increase in data integrity.

    Here are a few I wanted to point out:
    ->Was an active client exited as "deceased" elsewhere? Standardize Logic could notify the staff about this client.
    https://ideas.bitfocus.com/forums/930328-clarity-human-services/suggestions/43649772-quality-assurance-deceased-standardized-logic

    ->Ideally Names and IDs would be visible here:
    https://ideas.bitfocus.com/forums/930328-clarity-human-services/suggestions/44924266-client-unique-identifier-should-be-visible-on-all

    ->Date HUD Standards:
    https://ideas.bitfocus.com/forums/930328-clarity-human-services/suggestions/43649706-quality-assurance-chronological-date-entry-logic

    ->Overlapping Enrollment Flags:
    https://ideas.bitfocus.com/forums/930328-clarity-human-services/suggestions/39505756-concurrent-overlapping-enrollment-alert

    ->Move In Date Data Standard:
    https://ideas.bitfocus.com/forums/930328-clarity-human-services/suggestions/44983885-do-not-allow-program-start-date-entries-to-occur-a

    ->Assessment Related Standards:
    https://ideas.bitfocus.com/forums/930328-clarity-human-services/suggestions/43842963-allow-users-to-receive-assessment-due-warnings-for

    ->Documentation Requirements:
    https://ideas.bitfocus.com/forums/930328-clarity-human-services/suggestions/43873521-documentation-requirements-allow-for-logic-condit

    Jessica Salazar shared this idea  · 
  2. 23 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)
    Jessica Salazar supported this idea  · 
  3. 24 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)
    An error occurred while saving the comment
    Jessica Salazar commented  · 

    This is mostly on the Looker end of access rather than on the user interface as the idea suggests, but I feel as though the reason behind the idea align...

    Keeping a small history of page meta data like this would be helpful to review in Looker as well (a few days to no more than a month - whatever is feasible for the system). We've encountered issues where profiles get completely changed or wiped out because of some change someone else makes in the system. But because our staff corrected the changes, we are unable to look back and discover who made the "alarming" change.

    Jessica Salazar supported this idea  · 
  4. 27 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)
    Jessica Salazar supported this idea  · 
  5. 29 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)
    Jessica Salazar supported this idea  · 
    An error occurred while saving the comment
    Jessica Salazar commented  · 

    This aligns with another idea I posted that recommends HUD standards are validated by the system at the point of data entry. Similar to this suggestion would be the Engagement Date for Outreach projects, they should be dated after enrollment start date, and before enrollment exit date. There is the Move in Date, that should also be after enrollment start date and before exit date. Program service dates would be the same. There is currently a check at exit that allows the control of service end dates from going beyond an enrollment exit date, however it is still possible to bypass this. These are just a few examples of how the system could enforce many data standards and hopefully minimize data integrity issues caused by naturally existing human error.

  6. 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)
    An error occurred while saving the comment
    Jessica Salazar commented  · 

    Or instead changing this to their caseload list instead would be more efficient for users since these are the people they are typically searching for the majority of the time. Merging the Search page with the Caseload page would streamline their work. OR a mixture of all 3, the search and notification box on top, page split below this to give full caseload on one side and a longer list of recent searches on the other side....

    Jessica Salazar supported this idea  · 
  7. 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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Jessica Salazar supported this idea  · 
  8. 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)
    An error occurred while saving the comment
    Jessica Salazar commented  · 

    The ability to grant this control to an Agency Admin would be extremely helpful.

    Jessica Salazar supported this idea  · 
  9. 3 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)
    An error occurred while saving the comment
    Jessica Salazar commented  · 

    To add to ideas for UI updates:
    -Visible Unique Identifier next to client name that we are navigating through.
    -Minimize the need for 2 locations of a single piece of information i.e. Client level Notes, Program Level Notes, Client Level Services, Program Level Services, Client Level Assessments, Program Level Assessments. These could be a single page for each focus where we are able to select our program for the data point we wish to create.

    Jessica Salazar supported this idea  · 
  10. 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)
    An error occurred while saving the comment
    Jessica Salazar commented  · 

    A relative idea I provided was incorrectly marked completed which fell under the umbrella of this larger idea, specifically managing agency user accounts on the agency level. I checked with our CoC System Administrator and they confirmed that this is still a function that cannot be granted to an agency, only the CoC System Administrator has this function. Since it falls under this umbrella of providing agency control of our user accounts, here is the link for reference:
    https://ideas.bitfocus.com/forums/930328-clarity-human-services/suggestions/44150403-user-accounts-agency-management

    Jessica Salazar shared this idea  · 
  11. 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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Jessica Salazar supported this idea  · 
  12. 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)
    Jessica Salazar supported this idea  · 
  13. 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)
    An error occurred while saving the comment
    Jessica Salazar commented  · 

    This would be great at service creation as well. Outreach programs have particular services set up to record a geolocation so it can be an automatic process as part of this type of set up. Alternatively, an option (checkbox perhaps) to create a CLSA when any service is being created would allow outreach workers to efficiently record these relative contacts (CLSAs) at that same time.

    Jessica Salazar supported this idea  · 
  14. 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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Jessica Salazar supported this idea  · 
  15. 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)
    Jessica Salazar supported this idea  · 
  16. 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)
    Jessica Salazar supported this idea  · 
  17. 15 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)
    Jessica Salazar supported this idea  · 
  18. 40 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)
    Jessica Salazar supported this idea  · 
  19. 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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Jessica Salazar supported this idea  · 
  20. 33 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)
    An error occurred while saving the comment
    Jessica Salazar commented  · 

    As a provider our documentation requirements continue to increase where packets we are required to upload are well over 40 pages, and quality is important since we (and our funders) must be able to read the documents clearly.

    Jessica Salazar supported this idea  · 
← Previous 1 3