Setup Teleconsultation Feature

Teleconsultation in Bahmni is a remote way of connecting Patients and Doctors who cannot connect face to face. Bahmni teleconsultation is web-connected with the existing system which supports patients and doctors to join in a video call together. Read more about the feature here.

Bahmni leverages Jitsi as a platform to enable video consultations between patients and doctors. The default setup uses meet.jitsi.si which can be used for testing/demo purposes. For production use-cases we highly recommend self hosting the jitsi service. Read more about setting up Jitsi in the following pages.

Detailed guide - https://jitsi.github.io/handbook/docs/devops-guide/

On Docker - https://jitsi.github.io/handbook/docs/devops-guide/devops-guide-docker

Once you self-host Jitsi, update the URL pattern in OpenMRS → Administration → Settings → Bahmni → Appointment Tele Consultation Server Url Pattern property with your domain name.

Enabling Teleconsultation Appointments

Bahmni Appointment Scheduling module allows marking an appointment as Teleconsultation appointment upon which a teleconsultation link will be generated and the provider and the patient can join.

Enable Teleconsultation Appointments Feature

In your implementation specific configuration, add the allowVirtualConsultation property with value as true in the openmrs/apps/appointments/app.json file.

"config": { "allowVirtualConsultation": true,

Now when scheduling an appointment, one can find the option to mark it as Teleconsultation as shown in the below screenshot.

Once the appointment is scheduled as teleconsultation, the meeting can be joined either from the appointments page and opening the appointment and clicking on the Join Teleconsultation button or from the appointments display control and clicking on the Join Teleconsultation button from there.

 

image-20240908-145926.png
Appointments Details View Pop-Up

 

 

 

Enable Adhoc Teleconsultation

This feature is applicable starting Bahmni Lite v1.0.0 or Bahmni Standard v1.0.0

Bahmni provides the ability for a clinician to start an Adhoc Tele-consultation (on-demand) with a patient. To enable this, one needs to set allowAdhocTeleConsultation to true in /openmrs/apps/clincal/app.json in your implementation specific configuration. Note this config should be in clinical/app.json.

"config": { "allowAdhocTeleConsultation": true,

 

Enabling Email Notifications for Teleconsultation

Bahmni supports sending Email notification to the patient on booking a teleconsultation appointment with the teleconsultation meeting link or when an adhoc teleconsultation is started.

For emails to be sent the patient’s email needs to be captured while registration. Add a person attribute as email and capture it during registration.

To enable email sending, you need to configure SMTP server details in the .env file. Follow this page to setup SMTP information to OpenMRS service in docker compose.

There are few global properties which can be used to configure email subject and content templates. The configure the below properties, navigate to OpenMRS → Administration → Settings → Bahmni

  1. Appointment Tele Consultation Server Url Pattern → The Jitsi Domain URL pattern with which teleconsultation will happen.

  2. Appointment Tele Consultation Send Email → Defines whether or not the send email. Set this to true

  3. Appointment Tele Consultation Patient Email Notification Subject → Subject Line for teleconsultation appointment booking confirmation

  4. Appointment Tele Consultation Patient Email Notification Template → Content template for teleconsultation appointment booking information.

  5. Appointment Adhoc Tele Consultation Patient Email Notification Subject → Subject Line for adhoc teleconsultation meeting started

  6. Appointment Adhoc Tele Consultation Patient Email Notification Template → Content template for adhoc teleconsultation meeting.

  7. Appointment Adhoc Tele Consultation Bcc Emails → Additional Emails to send notification when an adhoc consultation is started.

 

The Bahmni documentation is licensed under Creative Commons Attribution-ShareAlike 4.0 International (CC BY-SA 4.0)