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.
New Supportive Housing module, similar to that described in ACRE Consulting's report.
Reference: https://www.acreconsulting.ca/products/178360
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
Lots of clients are having duplicated client housing status change records. For example: clients becoming chronically homeless every day; clients becoming housed 4 times in the same day, etc.
Currently, when most records exist (for example, Turn Aways, Appointments, Incidents, SPDAT, VAT, Waiting List, client in a Waiting List, Income, Education, Contributing Factor, etc.), a user can navigate to the List page for that kind of record and click the Delete button in the Action column.
However, this is not the case for many types of services. Several types of services, including Case Management, Goods and Services, Housing Placements, Housing Loss Prevention, and Food Bank, cannot be del…
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.
Behavioural Risk Factors and Watch Concerns are combined under the label "Behavioural Factor"
Contact Information is labeled as "Additional Information"
Debts are labeled as "Liability"
Modifying custom tables
Recording a custom table record
Modifying a custom table record
Accessing Coordinated Access module
Modifying Express Goods and Services Templates
Modifying Food Bank Items
Modifying Housing Continuum
Modifying Look-Up Tables
Modifying Programs
Modifying Questionnaires
Modifying Service Providers
Sending a Broadcast
Client is an Attendee in a Group Activity
Add Contact Information (need confirmation)
List Contact Information (part of List Vitals)
List Physical Appearance (part of List V…
Turnaways should not be considered a service provided to clients. Instead, they should be treated separately from services, like Appointments, Waiting Lists, or Calls & Visits Logs are not services.
Longer explanation:
When a Turnaway is added, this creates a record in HIFIS_Services. Among other things, this means that most reports that look at how many clients received services in a date range would include clients that were ONLY turned away in those reports. This is a standard reporting method …
Remove the free text "Referred By" field that appears alongside the "Referred From" field on the following screens:
Book In
Add Food Bank Transaction
Add Goods and Services Transaction
Add Turn Away (and Add Anonymous Turn Away)
The Turnaways module asks for Client Name and Family Members, then separately asks for the user to manually enter the number of Adults, which defaults to 1, and the number of Children, which defaults to 0. These fields should be automatically calculated based on the Client Name and Family Members fields. Moreover, on the Add Turnaway screen, these fields could even be hidden to reduce any confusion that may exist (these fields should still be present on the Add Anonymous Turnaway screen).
Either forced or through Service Provider Mandatory settings.
There’s an accountability issue: either staff can globally Edit a thing, or they can’t Edit any of a thing.
What is missing is the ability for a staff to only be able to Edit their own things, or only Edit things that have happened recently.
For example, I add a case note. Then I notice a typo, so I want to fix it. I should be able to edit my own case note within 24/48/72 hours. But 6 months from now I have no reason that I would need to edit this case note. The only possible reason I might have f…
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 Rea…
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, hav…
As you may or may not know, there is a mandatory field called "Reason for Service" that appears on many service types, such as Admissions, and Diversion, and Goods & Services, and Group Activities, and so on.
What you may not know is that the "Reason for Service" field on the Goods & Services module uses an entirely different lookup table, called "Reason for Goods & Services" with an identical initial list of values. However, it's a separate table and it's also stored in the database differently.…
When a client has a Case open, or a Housing Placement open or a Housing Loss Prevention open, there's a designated Caseworker. Can we automatically add that Caseworker, who is a user and who already exists in the system, as a Contact in the Contacts module? Lots of communities would like to manually enter this but they find staff are forgetting to do it so it's never a reliable source of information. Yes, users could look up the Case Management Client List, but they'd also have to look up the Ho…