Teleconsultation Webex Session in HTML5 with patient communication via SMS (No Webex App Required)

This repository is a template that can be used as a base to replicate the teleconsultation service.

The objective of this document is to technically detail the Teleconsultation Application that is based on the Webex video conferencing engine and that is being used at several Hospitals in the Region.

This clientless and hardware-less ubiquitous solution is based on Cisco Webex technology, taking advantage of the capabilities and integration (API) of these platforms to enable voice and video interactions, giving hospital medical staff full control over the schedule and enabling the communication channel in a safe and orderly manner.

With this application communication is achieved in 4 important directions:

  • Doctor - Doctor: internal communication among the medical staff via text messages, calls, videos and file transfers in a safe and easy way
  • Doctor - Family member: Doctors at the hospital can inform the medical status of patients to family members while at home through voice and video communications
  • Patient - Family member: the patient can talk to his/her relatives by voice or video, allowing them to feel safely close.
  • Discharged patients - Doctors: Doctors can follow-up on those patients already discharged from the hospital

Based on HTML5 video calls, the solution offers the following benefits:

  1. From the perspective of medical personnel, the main advantage is that it gives them full control of their schedule, opening a secure communication channel only when necessary, allowing the Physician to focus on caring for his patients
  2. From the patient / family perspective, the main advantage is that the video call is made without the need to install any special application or software, taking maximum care of usability and making it so easy that anyone can access the teleconsultation
  3. And finally, being a hardware less and clientless solution, it allows rapid deployment and scalability in contingency situations

The application aims to:
  • Generate accessibility for people who are not native to the digital age
  • Automate and facilitate the generation of communication channels between doctors, patients and relatives
  • Give full control of these communication channels to Health personnel
  • Integrate technologies such as HTML5, Webex, and SMS to achieve the above objectives

The way in which these objectives are achieved are:

  1. Via a Web page the Health personnel can generate a Webex session.
  2. Then a link is sent via SMS to the relatives and patients. In this link they can access the video conference without installing any application.

This is accomplished using the Webex SDK for HTML5. The user only has to click 2 times to enter the session. In the image below you can see an screenshot of the result once the cliente click on the link.

widget

Architecture

Webex Meetings

Webex Meetings Cloud APIs are being leveraged. Which is a multipoint of audio, video and web presentation conferences with different advanced functions. Due to the context of the document we will delve into the APIs more than other advanced functions.
Since these are used to fulfill the objectives of Automation and control mentioned above; This is achieved through the following functionalities.

  • Generation and sheduling service for the Webex Session
  • Generation of Users both in the application and in Webex
  • Assignment of necessary permissions for each user
  • Physician control to start the session through the virtual lobby

The detail of APIs called is in the next section.

Widget

The Webex Browser SDK generates the ability to make video calls in a browser that supports HMTL5 and JavaScript; this maintaining the security features for which Webex is known, I have even added new capabilities.

The SDK is in charge of:

  • Join the session
  • Get access to the microphone and camera of the device used by the user
  • Control the Audio and Video codec with which it is transmitted
  • Deliver Audio and video control to the user
All of this is accomplished by using the JS functions that are loaded together with the HTML

Unique Token

Each user and session has a unique token with which it is valid for 1 hour. This in order to generate an extra layer of security in addition to handing over control of the communication channel to the Physician; in order to avoid that the Family members generate an overload of work.
This same unique token is used to generate the guest credentials in the Webex session.

JWT (JSON Web Token)

The SDK requires JWT to authenticate users using HTML5.
Since the objective is that the user can enter easily (NO Logins, NO downloads), Webex's ability to automatically and safely generate guest users is used.

For this, the concept of “Guest Issuers” is used, which are the credentials with which the JWT that the Widget requires is generated.
These can be generated easily and quickly in the following Link:
https://developer.webex.com/docs/guest-issuer

This element could be considered part of the advanced functions but because it is used to fulfill different objectives, Accessibility and security, it was treated independently.

Virtual Lobby

This is a functionality that puts the user on hold while the doctor does not start the session.
This lobby also displays using a. git the next steps you will have to do, give microphone and camera permissions, click the green button to start the call.

It automatically lets the user pass when the Doctor is ready.

SMS provider

An integration with an SMS messaging provider was carried out to be able to have a greater scope due to the ubiquity of this service. The SMS Message is used to send the user a link with which they can Join the Webex Session and to let them know the date and time of the scheduled sessions.

Coviex (Core)

The Core of the application is a development in Python under the Flask Framework; At the same time, JavaScrip is used to give dynamism to HTML files.

This development is based on Python 3.7 and is running on a VM with Ubuntu in the AWS EC2 service.
The Core is in charge of coordinating and communicating the different elements:

  • Webex administration and agenda
  • Lobby waiting for users

Multimedia traffic at no time travels to the Core of the application.

In the next image you can see a model of the Architecture.

architecture

Instructions

You will need next things to be able to use this Code:

  • A Webex with admin access to the control Hub
  • Enough licenses to cover the medical acounts created
  • A Twilio account
  • A webex Teams bot
  • A Webex Guest Issuer

This code is been developed in Pyhton Using th Flask Framework; with a mix of JS for the Frontend.

It is originally deployed in a Ubuntu VM with Python 3.7. the libraries and the version are represented in the requirements.txt file.

Within the file BashRunMe.sh are all the commands needed to set ready an Fresh Ubuntu VM; been an .sh file you can run it directly.

All the needed varibles must exist as environment variables . Either you add them via the CLI or you use the exampleDOTenv to create a .env file so that when run the code this add them automatically.

Once the VM is ready with all the packages installed, python 3.7 and all the libries for python installed yo can just use the command:

 python3 runme.py

This is NOT a recommended way leave it running, but you can use this to check that everything is ready.
Once everything is Ready I recommend that you use aome kind of WSGI service; in this case we will use Gunicorn.

if you run the bashRunMe.sh you should alredy get installed gunicorn; you can use the next command to keep it running:

gunicorn3 --workers=8 --bind 0.0.0.0:xxx run:app --access-logfile gunicorn.log --error-logfile gunicorn-error.log --capture-output -D

Let me explain a little bit datailed this command:

  • Workers: it is recommendes that you use between 2-4 workes per Core
  • Bind: the IP and port for the service(i reccomend that you use other than default 5000 port in flask)
  • run:app make reference to the name of the file (without the .py) and the module to run
  • access-logfile: the name of the to store the logs
  • error-logfile: the name of the file where the errors logs will be stored
  • capture-output: this force all the outputs to be store as error logs
  • D: this make the command to run as a Deamon

To generate the video call the browser will need to ask for acces to the micfofone an the camera; all the most user browser will need a valited Cert for this.

I recommend to use another service like NGNIX as a proxy and to provide the Cert.

Contact Info:

joarriag@cisco.com

More info about the app:

https://www.youtube.com/watch?v=iM9ur4-0TpI

published

View code on GitHub

Code Exchange Community

Get help, share code, and collaborate with other developers in the Code Exchange community.View Community
Disclaimer:
Cisco provides Code Exchange for convenience and informational purposes only, with no support of any kind. This page contains information and links from third-party websites that are governed by their own separate terms. Reference to a project or contributor on this page does not imply any affiliation with or endorsement by Cisco.