Chronic Homelessness mismatch
We updated our production environment to build 60.3 on Wednesday and have noticed some inconsistencies between the “Chronic Homelessness Y/N” field from the CA module and what is reported under the new “Chronically Homeless” Yes/No field available on the client profile. We use the CA module in order to run our local prioritization, so it’s important that we understand how it’s working and why the Y/N fields aren’t matching with what HIFIS is saying for the client on their profile. This example client shows “Yes” for the new Chronically Homeless field on the client profile. Please see the relevant housing history for this client below as well. From the CA Module, looking for this same client, he is reporting “N” under Chronic Homelessness Y/N. Here is a query demonstrating the relevant fields: SELECT CA.ClientID ,CA.HomelessIn365Days ,CA.HomelessIn1095Days ,CA.ChronicallyHomelessYN FROM vw_CoordinatedAccess as CA WHERE ClientID = 125 I am attempting to troubleshoot to trace the issue back to the source, but I thought I would start by reporting it and provide a sample query to the devs to demonstrate the issue. SELECT CA.ClientID ,CA.HomelessIn365Days ,CA.HomelessIn1095Days ,CA.ChronicallyHomelessYN as CAChronicallyHomelessYN ,HIFIS_Clients.IsChronicallyHomelessYN as ClientProfileChronicallyHomelessYN FROM vw_CoordinatedAccess as CA INNER JOIN HIFIS_Clients on CA.ClientID = HIFIS_Clients.clientID WHERE CA.ChronicallyHomelessYN <> HIFIS_Clients.IsChronicallyHomelessYN The following query is currently giving us 126 results (with 1376 total results from vw_CoordinatedAccess). 69 of the 126 are showing Y for Chronic in the CA Module, and N for Chronic on the client profile. The remaining 57 are showing N for Chronic in the CA Module, and Y for Chronic on the client profile.
Christie S#Bug🐛#Housing Status#Coordinated Access4
Editing Client Vitals sets Chronically Homeless Status to 'No'
When editing a client’s vitals in HIFIS 4.0.60.3 and 60.4, the HIFIS application sets the client’s Chronically Homeless status to ‘No’, regardless of the client's current Chronically Homeless status. This may cause the Chronically Homeless status of some clients to be reported incorrectly by the application. Ticket 14971.
Ryan B#Bug🐛#Housing Status2
Being booked at a shelter no longer refreshes activity daily - 60.4
Clients currently in shelter appear to not have their activity status reset every day if they are actively booked into shelter. So instead of 0 days, all clients who have been booked in shelter are showing last activity day as the day of the update instead of 0 days.
Kat L#Bug🐛#Activity Status0
Reactivated Clients - 60.4
In 60.4 Clients are active way past the 90 day threshold (and are reactivated during the update) some of these clients have never had a service and are active despite being created years ago- causing the numbers of active clients to Spike. HICC is aware of this and is currently working on the issue
Kat L#Bug🐛#Activity Status0
60.4 Deceased Clients are inactive
in updating to 60.4 - all of our Clients that were previously deceased were marked as inactive. HICC is aware and is currently working on a solution 🤞
Kat L#Bug🐛#Activity Status3
Housing Status: Incorrectly displaying as "Unknown"
Known bug that happens a LOT! Clients show up as “Unknown” housing status even when there is data that should give them a different status! More detail in the comments.
Ali Ryder#Bug🐛#Housing Status#Major🚨6
Housing Placement dates
There's incorrect behaviour when you try to modify some dates in Housing Placements. You can Move In and specify the move-in date, but if you make an error, it's difficult to change. Yes you can modify the Start Date in the corresponding Housing History record, but the Move In Date on the HP record does not update.When you Secure a Unit, you can specify the Housing Secured date. When you Add and Secure a Unit, you can't specify the Housing Secured DateYou can't modify the Housing Secured Date after the Housing Has been secured, in the case that a staff makes an error
Ali Ryder#Housing Placements🏠0
Update custom report file
Instead of having to upload a new report and delete the old one, can we replace the attachment for an existing report? That way we don't have to go remember what Report Categories and Service Providers to attach it to, and it would help to keep things clean.
Ali Ryder#Reporting📊0
Add user account actions to Audit Log
It would be great if login attempts were stored in the Audit Log. When a user logs in or logs out that is logged, but it would be great to see the following: User "aryder" unsuccessfully attempted to login 2024-04-30 at 11:28 amUser "aryder" unsuccessfully attempted to login 2024-04-30 at 11:29 amUser "aryder" unsuccessfully attempted to login 2024-04-30 at 11:30 amUser "aryder" account locked at 2024-04-30 at 11:30 amUser "aryder" account unlocked by user "Admin" at 2024-05-03 at 8:47 amTemporary password for user "aryder" generated by user "Admin" at 2024-05-03 at 10:10 amPassword request email sent to user "aryder" at 2024-05-03 at 10:42 amUser "aryder" password reset by email at 2024-05-03 at 10:43 amUser "aryder" account deactivated by user "Admin" at 2024-05-17 at 2:11 pm All of this would be helpful for helpdesk roles to know.
Ali Ryder#User Accounts👤#Audit Log1
Change username
Sometimes a user account might get added with a typo, or in contravention of a naming policy. It would be great if we could be able to modify user accounts.
Ali Ryder#User Accounts👤1
Make consent uploads mandatory
Currently, can't make the attachments field in Consent module mandatory or disabled.
Laura S#Consent📝0
Book-Out leads to Add Housing History
When a client does a book-out, the Reason for Discharge field is mandatory. If the user selects one of the housed options, like "Housed - Independent" for example, HIFIS should automatically be adding a Housing History record. Here's what I'd like to see: A user does a book-out and on the Book Out screen, selects a housed option in reason for dischargeThe user clicks saveHIFIS detects that one of the "housed" options has been selected, and redirects the client to the Add Housing History screenThe Add Housing History screen should automatically enter the start date = the date of the book-outThe Add Housing History screen should automatically select the Housing Type (looked up from the Reason for Discharge)The user can then add the rest of the details and hit save. This would go a long way to ensuring that housing status and housing transitions are being calculated correctly, and make the CHR have better data, and result in less work for shelter staff.
Ali Ryder#Admissions🛌#Housing History🏠2
Financial Profile records duplicating
In testing 60.3 we have found an issue with records duplicating under the Financial Profile area. This appears to be affecting all 4 tabs within the Financial Profile section. Whenever you add a record under Income, Expenses, Assets or Debts when there is already a record, the new record is added multiple times. For example, I added a “Employment - Casual" record under Incomes on client # 5624 on the demo site. Adding the first record seems to work properly.I then added a new income record for “OW” and two were createdI then added another new record for “Panhandling” which was created 3 times.Adding a fourth record for “Disability Benefits” resulted in 4 records being created
Christie S#Bug🐛#Income💵#Expenses💵1
Case Management > View All Session Details Blank
In testing 60.3 we have found an issue with the “View All Session Details” button in the Case Management area. To see this, create a new case management record, or open a client that already has an open case management record, either from Front Desk > Case Management, or from Client Management > Case Management. Then Click on the Display button to view the details. What we expect to see here is a summary of all sessions attached to the case management record. In our production environment (v4.0.59.7.1) we see a summary of all sessions attached to the case management record.
Christie S#Bug🐛#Case Management🧙♂️1
Duplicate Clients in CA module (Consent)
The Coordinated Access module shows duplicated clients when clients have multiple open Coordinated Access consents. (Which could occur when you merge two client files.) Workaround: close one of the open Coordinated Access consent records.
Ali Ryder#Consent📝#Coordinated Access1