Health Care Worker @Home

The whole database structure will be rewritten.

New consultation flow and routing¶

Previously, doctors had to create an Invite so that patients could request a consultation. This workflow proved inadequate.
In the new design, we will remove the Invite model and introduce a dedicated Requests model.

A Request will now be created first, after which one Consultation and optionnaly Appointments will be added. Each appointment will contain its own Participants.

For having the best routing possible, we will introduce Reason of consultation model, which give health service name with routing rules. For me information, look on #8925.

New Messaging module¶

Since HCW@Home will send a lot of messages, a new message table dedicated for messages to send/messages sent will be used. This will provide an easy way for admin to track failures, since message routing can be complex.

Beside Message, a list of templates will be configurable, permitting to admin to update message templates, into multiple languages. A dedicated template validation process will be in place for template that need prior validation before being used (e.g. Whatsapp).

Media server configuration¶

Similar to the current one, the interface will offer ability to add one or more Media server. Despite we will use Livekit, we will keep in mind to have way to define several type of Media Server.

Background tasks.¶

Background tasks are used to achieve various action, like Consultation routing, Messaging delivery, Appointment remoinder etc... We will give complete control of tasks executed to the admin to know if something failes, or was run successfully.