HIFIS Feedback
Submit feedbackOur log of things that can be improved with HIFIS. Here's the official issues log.
15240: Client State Accuracy Impacted by Gaps in ClientIDs
We've observed inconsistencies in client states within HIFIS, for example, some clients are marked as 'Active' despite not receiving services in over 90 days, while others are marked as 'Inactive' even though they still have open case management goals. In HIFIS, client state is updated by the [dbo].[sp_checkClientState] stored procedure. This procedure can be executed for an individual client or for all clients in the database. When run for all clients, it processes them in sequential batches of 5,000 (e.g., ClientID 1–5,000; 5,001–10,000; etc.). However, gaps in the ClientID sequence can cause the procedure to skip clients. For example, our database contains a gap between ClientIDs 25,000 and 35,000. As a result, the client state for all clients with a ClientID above 25,000 may not be updated. Explanation When processing all clients, the [dbo].[sp_checkClientState] procedure relies on the [dbo].[fn_checkClientStateData] function to retrieve client state data for each batch. If no data is returned for a given batch (e.g., when a gap exists in the ClientID range) the [dbo].[sp_checkClientState] procedure exits early. This prevents the remaining client batches from being evaluated, leading to incomplete or inaccurate client state data.
#294Ryan B1
16034: RecentActivityDateTime is null
In HIFIS_Clients, a bunch of clients are having null values stored for RecentActivityModuleTypeID and RecentActivityDateTime , despite having actions in their file that constitute activity. So far I cannot detect any commonality between the clients who do have a Recent Activity, and those who don't have any. Affected software elements Clients Approaching Inactivity reportRecent Inactivity reportCoordinated Access moduleAny custom report that includes a "days since last activity" calculation
#333Ali Ryder4
Stored procedure sp_CheckClientState not being initiated
Every night, the stored procedure sp_checkClientState is supposed to run, which is supposed to check each client's date of last activity and update their activity/inactivity status accordingly. It appears that this procedure is not always being called when it is supposed to, which is resulting in a number of issues related to activity/inactivity.
#297Ali Ryder1
New Supportive Housing Module
New Supportive Housing module, similar to that described in ACRE Consulting's report. https://www.acreconsulting.ca/products/178360-HIFIS-Improvement-Project-Supportive
#171Ali Ryder1
Client's Recent Activity not Updating
When creating new services (Admissions, Case Management, Housing Placements, Reservations, SPDAT, Storage, Turnaways etc..) for a client in HIFIS 4.0.60.4.2, the 'RecentActivityModuleTypeID' and 'RecentActivityDateTime' fields in the HIFIS_Clients table are not updated to reflect the client's most recent activity. This can result in inaccurate data shown in the 'RecentInteractionDateTime' and 'SinceLastActivityDays' fields in the vw_CoordinatedAccess and vw_CoordinatedAccessExport views.
#243Ryan B2
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.
#156Ali Ryder7
14885: 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.
#219Christie S4
Children out of family
A big gap related to families in HIFIS is the ability to keep track of clients that are part of the family but not currently living together, that would theoretically get reunited when the parents get housed. This could include: children in foster care, children temporarily living with grandparents, or a household that's split up due to shelter capacity issues. This is commonly handled by communities via custom tables, and there isn't a satisfactory way to do it. A simple partial fix may be, on the family membership screen, to indicate whether the client is living in or out of the family during the date range period, and have an easy way to swap, like a new button that temporarily removes the client from the family (like they're "on hold" until a later date).
#357Ali Ryder0
Better way to handle pregnancy
Pregnancy isn't just a health issue or a contributing factor, it also affects family size and housing requirements. Although there are ways to record that someone is pregnant in HIFIS (i.e. create a Contributing Factor) it should be handled differently, in a more obvious and integrated way, and connected to the Family module. For example, having the ability to specify the due date of the baby and having an easy way to convert a pregnancy into a new family member.
#356Ali Ryder0
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.
#215Christie S4
Better way to track Referrals
Introduce new behaviour in HIFIS to allow better tracking of referral completion, recording referrals in more circumstances, and referring clients to other service providers inside HIFIS. Reference: https://www.acreconsulting.ca/products/216596-HIFIS-Improvement-Project-Referrals
#341Ali Ryder0
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.
#213Ali Ryder1
Client Search not working as expected
The Client Search is really different than in our current production version (4.0.59.4). Is it working the way you expect it to? For example, to get to my client John William Test (Alias 1 Jonathan Silly Pants), it no longer works to search jo te or wi pa. john test doesn't work either, you have to type in test, john. But jonathan silly works. Is that by design? Absurdly, han sil works.
#40Kristina N4
Make consent uploads mandatory
Currently, can't make the attachments field in Consent module mandatory or disabled.
#62Laura S1
Case end date is not mandatory
When changing the case status from Open to Closed (any), the End Date appears but is not mandatory. You can save the case status as closed without providing an end date. This causes a disconnect in the data; cases may appear ongoing (no end date) but with a status indicating they are closed.
#33Ali Ryder1