HIFIS 4

Winnipeg is having an issue testing 4.0.60.2.1 on their training database. They're getting a database table error when they load the Client List = All but not when they load the Client List = Active (and they say it takes a really long time).

Here’s a big pain point: when you have a client with expired consent, but they’re in the middle of receiving services. Like, they’re booked into a shelter, or they have an open case file. I get that with no consent, the principle of you can’t modify the client’s information is good and valid, but there’s a problem I think where HIFIS is conflating modifying information and ending a service. So for example to close a case file, you need permission to Edit the case file, and you have to click the Edit button, which also lets you, say, change the caseworker or otherwise modify information. I think globally it would be helpful to have a separate right and button to simply close services. Like there’s a separate right and button to close bulletins. In Admissions, Book-Out is already a separate right. But there should probably be a separate right for CM and other modules like storage, subsidies, HPs, and any other ongoing service. Not saying that you couldn’t close a case file by editing it (in this proposed future), but to have a separate button that JUST closes it. Like with bulletins. Obviously, since this describes lots of different modules and cases, I’m putting it as a longer-term fix. Anyways, we need the ability to close services for clients with expired consent. Right now people tell me they are doing workarounds like: disabling Enforce Consent for an hour and then turning it back on, or editing the Consent Expiry Date to tomorrow then changing it back, just so they can close these services. Option 1: grant the Admin a permanent exemption to the Enforce Consent rule. The Admin can do whatever they like to client files, regardless of whether the consent is valid or not. Forever. Option 2: create a Database Maintenance option that’s something like “bulk expire all services for clients with expired consent” Option 3: just add these close buttons throughout the software Option 4: create an automatic process of when consent expires, also automatically close all services (this could be problematic if, say, a client's consent expires for a few days before getting reactivated, thought) Option 5: have a button or something on a client file, that says, bulk expire all services for this client. Maybe this can be like the Client Service Delete option.

I would like to see a specific button on the consent screen that just says “Withdraw consent” or “Expire” or “end” or “close” I don’t know what it should be called but all it lets you do is add an end date. In an ideal world, the user can choose the end date and add an optional note about it. (That note can just be the existing Comments field) This should be governed by a separate, new right. Separate from Edit. Why? We probably want most staff to be able to end a consent, but not edit the other fields. Furthermore, there’s an issue since consents are “owned by” a SP. If I consent at SP A and then I go to SP B and say that I withdraw my consent, the staff at SP B cannot end the consent created by SP A. So the ability to end a consent overrules who owns the consent record. I’ve noticed that some consent date fields are un-editable. It’s a bit weird. Like, if I added a CA + Explicit consent, it creates two records, and I can edit the Start Date for Explicit but not for CA. Now I’m assuming that this probably has to do with an accountability trail. We can let people add comments to a consent when they edit it, but they can’t change the start date. However, this does have problems like what if they signed the consent form yesterday but I only added the record today? I think adding the close consent button, which is separate from editing the consent, would be helpful. Then those un-editable fields can be editable again, but only by people with the right permission, which would probably be just admins at this point.

I'd like to please put in a request for a dynamic report parameter (like was recently created for GeoRegion) for Waiting List? It's another area where all of the waiting lists would be unique for each community. It should probably be filtered to only show waiting lists the current service provider has access to.

After updating to version 60, service providers may have randomly become unsubscribed from some look-up values. This is particularly present in Waiting Lists, although it's unclear if the issue is present elsewhere. For example, at Service Provider #1, when I look at Waiting Request Reason, I see that everybody is now unsubscribed from all values. The issue is also present for Waiting List Status. If you want to add a client to a waiting list, there's no options in the drop-downs: And for an existing client, it would remember their previous value but you can't select a different one.

This is another version of https://acreconsulting.canny.io/hifis-4/p/housing-status-duplicated-statuses but it's distinct enough that I'm giving it its own ticket. I have a total of 36 clients. I found the issue for 7 clients including Anonymous, Anonymous, that's around 20% of clients affected. I tested the demo site and the issue is present for over 1200 clients. Here are some examples of affected clients: all clients between 2,881 and 2,895 inclusive; 2,723; 800; 259.... there's lots. It's always duplicated Unknown status. Every time. I haven't found a duplicated status that wasn't Unknown. It's always the same client becoming unknown a bunch of times at the exact same timestamp. The timestamp is the same timestamp as the client created date. There are always 77 copies of the duplicated unknown status. The number 77 probably has to do with something in my database. I tested on demo.hifis.ca and the number was 615. I don't know what I have 77 of and demo.hifis.ca has 615 of, but there's probably something.

In my opinion, it should work like the Service Restrictions All | Current filter, where records show as Current if the End Date and Time are in the future. However, the way the Storage List works right now is that records only show as Current if the End Date and Time is left blank. If End Date and Time is filled in, even with a future date, a record won’t show with the filter toggled to Current.

We are currently testing version 4.0.60.2.1. I’m having a problem with saving changes to user accounts. The steps I took: Administration menu > Users Go to an existing user (Active or Inactive), click User Account (under Action). Replace Service Providers currently connected to user account with other Service Providers (and make Default one of the new Service Providers) The green ‘Data Saved’ pop-up doesn’t come up but the page appears to have stopped loading and then the Rights tab still contains the old list of Service Providers to add rights templates to (it didn’t update based on the information that was changed in the User Profile tab). Unfortunately, it doesn’t happen every time. But in trying different things, I can’t find a trend. Sometimes it simply works, shows ‘Data Saved’ and everything is as it should be. And some of the time, the error in the below screenshot appears. When I hit OK, it pushes through and the data are saved.

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.