HIFIS Feedback
Submit feedbackOur log of things that can be improved with HIFIS. Here's the official issues log.
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
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
Remove "Reason for Service" on Group Activities
It’s a mandatory field but users must select one Reason for Service that applies to all participants. Typically the selected answer is “Seeking Specific Services,” in other words they’re at the Group Activity because they need to receive the services offered by the Group Activity. Because it applies to all participants, there's no useful information that can be collected in this field.
#347Ali Ryder0
Remove "Referred To" and "Referred From" from Group Activities
This makes very little sense and could only logically be used if the same referral was made to each of the dozens of participants in a Group Activity were given the same referral.
#346Ali Ryder0
Remove the Agency Involved / Referral field from Sessions
This will be replaced by a Referrals tab
#345Ali Ryder0
Remove the "Referred To" field on Case Management
This was recently added with no apparent rationale and is leading to confusion for users
#344Ali Ryder0
Remove the "Referred By" free-text field
Remove the free text "Referred By" field that appears alongside the "Referred From" field on the following screens: Book InAdd Food Bank TransactionAdd Goods and Services TransactionAdd Turn Away (and Add Anonymous Turn Away)
#343Ali Ryder0
Reconfigure Case Manager field to make it more consistent across modules
Currently, when a module includes a caseworker, the information about the caseworker is stored in a module-specific table, such as HIFIS_Cases, instead of the more generic HIFIS_Services. Specifically, it is present in HIFIS_Diversion, HIFIS_SPDAT_Intake, HIFIS_VAT_Intake, HIFIS_Cases, HIFIS_HousePlacements, and it's possible that I'm missing one or two. In contrast, the Reason for Service field is present in the HIFIS_Services table instead of the module-specific tables, despite the fact that Reason For Service is, like Caseworker, not present in all modules. Specifically, it's not present in Case Management, or Housing Placements, or Storage or SPDAT or VAT, and there may be more. It would be beneficial if information about the Caseworker was stored consistently, in the field HIFIS_Services.CaseworkerID, and have it be null in the modules that don't contain a caseworker field, similar to Reason for Service. This would allow higher level analysis in particular - create a report showing all services, broken down by type, by reason for service, by program, by service provider, and now by caseworker too.
#342Ali Ryder0
Assessments in Case Management
In Case Management, add a new tab called "Assessments." In that tab, you're going to have sub-tabs (like how if you have multiple Custom Tables, you have a Custom Tables tab and then each Custom Table is it's own sub-tab underneath) for SPDAT, VI-SPDAT, and VAT. If more assessments get added to HIFIS, they would be added here too. From the Assessments tab, you can add an applicable assessment directly, assuming you have rights. If you add an assessment from the Front Desk or Client Management, have an extra field (optional) that's, like, "Case File" and it will allow you to associate an assessment with a case. The Case file should list all Assessments that are associated with the Case.
#340Ali Ryder0
Option to view all Case Comments in one screen
Just make it easier to review your Case Comments!
#339Ali Ryder0