HIFIS FAQ

In HIFIS, there is one user that has the username Admin and anyone logged in as this user can do everything in the software. You can create additional users, and check off all the rights boxes, and they can do almost everything the admin can do, but there are occasional differences, where only the admin can do something specific. In addition, when you install a HIFIS update, then there could be new rights that get added (not in every release). If there are new rights, then only the Admin has those rights by default and therefore only the Admin can grant them to other users. So for example, if there's a new module in the latest version that you want to enable, only the Admin can enable it. Aside from having all the new rights, here are a list of known actions that only the Admin can take: Registration - only the Admin can register your HIFIS instance Admin view Non-Admin view Look-Up Tables: Manage Subscriptions - the Admin can manage the subscriptions for all service providers at the same time Admin view Non-Admin view Look-Up Tables: Placeable - in the House Types look-up table, there is an extra field controlling whether the value is visible in the Housing Placement module (Placeable) Admin view Non-Admin view Bulletins: Send To All Providers - when creating a bulletin, the admin has access to a button labelled "Send To All Providers" Admin view Non-Admin view Reports - Before version 4.0.60.1, only the Admin could deploy official HIFIS reports from what they call the "Report Marketplace." Admin view

In HIFIS, when any user takes certain actions for a client file, this updates the client's Date of Last Activity. If the client's Date of Last Activity is at least 90 of days ago, the client automatically becomes inactive at some point overnight. If a client who is inactive has one of the actions taken on their file, they immediately become active once more. Here is a list of actions that result in the client becoming or remaining active: 4.0.59.1 4.0.59.6 4.0.60.3 4.0.60.4 Admissions: Booking into a shelter (so, if the client is booked in on January 1) Admissions: Each day a client is in shelter (so, if today is January 10th and the client is still booked in, this would be January 10th) Admissions: Each day a client is in shelter Admissions: Each day a client is in shelter Adding a new Appointment record Add a Calls and Visits Log Add a Calls and Visits Log Add a Calls and Visits Log Add a Calls and Visits Log Case Management: Add a Case Case Management: Add a Session Case Management: Add a Case Case Management: Add a Session Case Management: Add a Case Case Management: Add a Session Case Management: Every day between the Case Opened date and the Case Closed date Adding a new Consent record Add a Diversion Add a Diversion Add a Food Bank transaction Add a Food Bank transaction Add a Food Bank transaction Add a Food Bank transaction Add a Goods or Services transaction Add an Express Good Add an Express Service Add a Goods or Services transaction Add an Express Good Add an Express Service Add a Goods or Services transaction Add an Express Good Add an Express Service Add a Goods or Services transaction Add an Express Good Add an Express Service Client is identified as an Attendee in a Group Activity Client is identified as an Attendee in a Group Activity Client is identified as an Attendee in a Group Activity Client is identified as an Attendee in a Group Activity Housing Placement: Add a Housing Placement Housing Placement: Add a Housing Placement Attempt Housing Placement: Add a Follow Up Housing Placement: Add a Housing Placement Housing Placement: Add a Housing Placement Attempt Housing Placement: Add a Follow Up Housing Placement: Add a Housing Placement Housing Placement: Add a Housing Placement Attempt Housing Placement: Add a Follow Up Housing Placement: Every day between the Date Search Started and the Final Follow-up date Add Housing Loss Prevention interaction Add Housing Loss Prevention interaction Add Housing Loss Prevention interaction Housing Loss Prevention: Every day between the Date Search Started and the Final Follow-up date Client is provided medication through Medication Dispensing Client is provided medication through Medication Dispensing Client is provided medication through Medication Dispensing Client is provided medication through Medication Dispensing Add a Service Restriction Add a Service Restriction Add a Service Restriction Add a Service Restriction Add a Storage Item Add a Storage Item Add a Storage Item Add a Storage Item Client takes a Survey Client takes a Survey Client takes a Survey Client takes a Survey Adding a new Turn Away record Add any VI-SPDAT or SPDAT assessment Add any VI-SPDAT or SPDAT assessment Add any VI-SPDAT or SPDAT assessment Add any VI-SPDAT or SPDAT assessment Add any VAT assessment Add any VAT assessment Add any VAT assessment Add any VAT assessment

ELMAH stands for Error Logging Modules and Handlers and is an error-logging tool that HIFIS uses. Whenever an error occurs within HIFIS - ranging from really minor inconveniences you might not realize were errors, to catastrophic failures - a record of that error is generated and stored in something called the ELMAH log. The ELMAH log is not intended for communities to use themselves. Instead, a copy of the log file should be shared with the HIFIS development team, in the event that an issue is discovered that requires further investigation. The HIFIS development team will ask you for a copy of your ELMAH log in those cases. Since each log is date- and timestamped, and there are probably more logs being generated than you would think, when you are troubleshooting, it is helpful to note the exact date and time that the error occurred, which can help to identify WHICH log, or which section of the log, is the relevant portion. Generally speaking, you can access your ELMAH logs from your web browser, by adding /elmah to the end of your domain. For example, for the site https://demo.hifis.ca, the ELMAH log is found at https://demo.hifis.ca/elmah (you need to be logged in to access it). Here is a guide on how to access your ELMAH logs, via the HIFIS development team.