March round up

Add care seekers/enquiries to waiting lists.

March was a productive month on the development front with waiting lists, real-time duplicate detection and a PHP SDK for the API released.

Waiting lists

Locations now feature waiting lists. Any care seeker/enquiry can be added to a location's waiting list (or later removed) and waiting lists can easily be reviewed when a service or home has availability. Watch a short video guide on how waiting lists work.

Detect duplicates

We've added duplicate record detection to care enquiries. Now when adding or updating a care enquiry CareHQ will search for duplicate records in real-time while you type and alert you if a possible match is found. Watch a short video guide on how duplicate detection helps you eliminate duplicate care enquiries.

Other updates & fixes

  • We've released a PHP SDK for our API making it easier to integrate PHP based websites and applications (such as WordPress) with CareHQ.
  • There is now a Don't know option for the Has dementia and Respite required fields against care enquiries.
  • Added tag to home visit and assessment events on the calendar to indicate if they are in-person or virtual.
  • Reassigning a care enquiry to another user now moves related actions, assessments and home visits to the newly assigned user.
  • Regional managers can now be granted account owner privileges allowing them to manage users and account settings.
  • Care enquiries against locations can now be filtered by closed reason.
  • Account level (global) items of literature now appear under the literature tab for locations (previously only local literature for the location would be displayed).
  • Respite tally is now correct on the admissions, deaths and discharges report.
  • Discharging a resident on a date in the past now immediately sets them as inactive, previously they were only set as inactive at the end of the day.
  • Fixed issue wherein some scenarios the room and resident names were not recorded when updating a booking (details were retained for auditing but were not presented in the human friendly description of the change).
  • Fixed issue where residents in some scenarios wouldn't have the correct discharge reason recorded for them (the correct reason was still retained against the booking but the reason displayed on the view resident page would be based on a previous booking for the user).