HIFIS Feedback

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.

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.

This was recently introduced in HIFIS version 60. There is value in being able to specify the location a service occurred in, but that exists because of the service mapping feature. But having both a Geographic Region field and also a service location field is firstly redundant and can also lead to conflicting data.

In order to let a user complete the "Diversion Workflow" they need to have the user right "Add Diversion Records." If that right is not given, users get an error after clicking the "Add Diversion Workflow" button saying they don't have rights.

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.

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.

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.

Can't remove a service provider from a user profile. Steps to reproduce: Open user profileDelete one of the service providers from the "User Profile" tabGreen data saved notification appearsReload page, and the removed service provider is back. Here's a recording of it: https://www.loom.com/share/30de5ba2cb6f4b908bc86c1245ee33a5?sid=4f39f16e-8965-463e-954c-2f98a14b5566

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