HIFIS Feedback

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

When adding an address record, Country is pre-selected as "Canada" but Province and City are left blank. Can we not just assume that, by default, addresses in the same Province as the one we are currently in (i.e. application Registration knows what province we are in, or you could look up the current Service Provider and see what province it is in)? The reason for this is because when you have to select Province first, the software has to then process and load the list of Cities based on the Province, leading to a delay for staff.

This problem was first reported in 4.0.57.30 under ticket 9954 We have a custom table attached to client details which we have configured to allow only one record. The table has a single field. Both copies of the client had the same value set for the field prior to merging. As a result, the field / value is linked twice to the merged client, even though the table only allows one record. I am able to remove one of the values under the admin account by temporarily changing the Custom Table to allow multiple records, which then gave me the individual edit and delete options for each record. As of 4.0.60.3, we are now seeing multiple records in a single value table that is attached to the Admissions module. We have no idea how these are being created, it’s likely not from a merge as it was in the previous case with the client details custom table. We have seen this happen twice recently, and it breaks our custom report since it should be impossible to have multiple values in these fields due to the custom table configuration. When you try to edit, it picks the top one and the other one has no way to edit or delete. The workaround is to change the Allow Multiple Values setting to Yes, which changes the interface to have the edit / delete button on every row, instead of a single edit button that only allows you to bring up one of them for editing, and no delete button.

In previous versions of HIFIS (e.g., 4.0.59.7.1) the browser was redirected to the Custom Reports tab after uploading a custom report. This is no longer occurring in HIFIS 4.0.60.4. Instead, when uploading a custom report in 4.0.60.4, the following occurs: • After pressing the Save button, a green ‘Data Saved’ balloon is shown in the top right corner of the screen. • The browser remains on the ‘Add Report Form’, but the title of the ‘Add Report’ form is changed to ‘Report Generator | [Report Name]. • Clicking the Cancel button on the Add Report form OR clicking the Reports > Report Manager menu item redirects to an empty version of the ‘Add Report’ form. ticket 15148 - identified as a bug to be fixed in a future version.

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.

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.

Currently, can't make the attachments field in Consent module mandatory or disabled.

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.

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.

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.

We are currently running build 4.0.59.5. I have an consent related enhancement request to submit for a future HIFIS patch. We would like to be able to disable the “Explicit” consent type option in the consent drop down when creating a client or a consent record. When we upgraded our HIFIS instance from 58 to the 59 version, we selected the option to convert all our Explicit consent records into Coordinated Access + Explicit consent, since our consent form already included consent for entry into the Coordinated Access system. We are running into a process issue where we can not stop users from selecting the “Explicit” option when creating new consent records, when really they should be selecting Explicit + Coordinated Access consent. This results in clients being created with only the Explicit record (just like they used to be prior to v59) and thus are missing from the CA list, even if they meet all the other criteria. We have tried to train workers not to use the “Explicit” option, but unfortunately we have a lot of users who are not understanding this requirement to get their clients into the CA system, even after multiple reminders. The only way we can fix this currently is our HIFIS coordinator reviewing a custom report and adding the missing CA consent. If we had some other way to prevent “Explicit Only” clients from being created, it would increase our data quality for the ESDC export as well as save our coordinator a lot of time manually reviewing the files that have explicit consent but are missing CA consent. This would affect the add client screen (with enforce consent) where we would like the ability to remove “Explicit” as an option. This would also affect the Client Management -> Consent screen As well as the Enforce Consent popup when that setting is enabled.