ihub-pti / boldo-web Goto Github PK

There is a number of issues related to the call feature. They are all based in missing cleanups of the WebRTC connection.

To fix this:

• Read this article: https://developer.mozilla.org/en-US/docs/Web/API/WebRTC_API/Signaling_and_video_calling
  Esp. the section about the "Ending the call".

• Find issues , esp. regarding error handling for unhandled errors, edge cases that might happen (what to call first to avoid glitches and how to end a call correctly to free all resources).

• Refactor our code and fix the issues found above

Add flash messages for success, error and info that can provide user feedback where no form is to validate.

The flash message should appear on the top right and disappear after a short time.

It should also be possible to show multiple messages, they should stack below each other.

This is particularly important for the Call. As there are various things that can go wrong and this is the only location which can show them nicely.

They should be rendered globally inside the App.tsx to keep flash messages appear across pages.

Add Patient Details in the following places:

• Calendar (Events, Modal)
• Waiting Room Sidebar
• Call (Top and Sidebar)

This is available through: iHub-PTI/ihub-core#10

Problem:

1. It is too easy to accidentally leave the page during the call as a doctor. Navigation events and page reloads should require a confirmation during the call.

2. While in a call, on a page reload, the connection should reestablished.

To Implement 1:

We can make use of a confirm() pop-up on page navigation. This should be triggered for native browser navigation as well as the react-navigation plugin.

2. This seems to be tricky. Might be fixed after the call is cleaned up.

The endpoint is not implementing any logic right now.
Also it doesn't deserve to be it's own endpoint. Instead it should be a query param.

It should

• Fetch data
• Fetch events from DB
• Calculate correct status
• return only relevant ones

Buttons are not implemented currently.

It is not clear how to tackle this issue. It might have todo with the MediaDevice. More research is needed.

Before we tackle this, it seems to be a good idea to cleanup the call.

Also: We should show a visible symbol of muted audio or video on the screen, as those buttons are hidden behind a menu button.

Every appointment has a room which handles the "Waiting Room UI" and the "Call".

This room has the following states:

1. No permission - no appointment with given ID for this doctor
2. Closed - Before and after the appointment
3. Waiting Room Open - 15 minutes before appointment until appointment marked as finished
4. Patient is connecting - Establishing Call
5. Call - Call in Progress