intelehealth / intelehealth-webapp Goto Github PK

I am planning to try this application in my local and was able to get it compiled and deployed locally.
Till this point the instructions are very helpful.
but i would like to know what is the default username/password. admin/Admin123 does not work.
is there a place to configure it?

The user (doctor) should be able to enter the dosage (in mg) of the medications entered. since the dosage will vary according to the medicines

When I tried to update the details of the admin user on the doctor's UI, it wasn't getting updated. The insertion of provider attributes is already done on the server DB.

Once the user has clicked on start visit note, and started the visit note encounter, the cards should remain visible and the "Start Visit Note" button should disappear.

The help text is not sufficient
Possible solutions:

• improving the help text
• placeholders

Medication fragment, Doctor's Advice and Doctor's Notes - most confusing.

A new card has to be added on the web-UI. The details are mentioned below:

1. On the dashboard, there should be a separate section, which shows the list of referred visits/ specialist consultations.
2. Fields on the dashboard:
   Patient ID, Name, Gender, DOB, Location, Referred to (specialist doc/ hospital), Current Status (seen by specialist/ hospital staff or not)

This issue is prominent in Philippines, because several people have the same first and last name, the best differentiators are the middle name, prefix, etc.

All the list of medications need to be added, and it should be visible on the UI in the form of predictive text. The list will be provided by Dr Miriam.

A new card has to be added. The work flow and details are mentioned below.

1. Fields on the dashboard:
   Patient ID, Name, Gender, DOB, Location, Follow-up date, Status (patient has come for follow-up visit or they haven't)
2. Once the visit is complete, patients with scheduled follow-up in descending order (most upcoming dates shown first) should be visible here on the UI.
3. Once the patient has come for the follow-up, it moves to queued visits again, and once the visit is complete, it is removed from the dashboard.
4. The user should be able to see and filter these follow-up visits on a weekly/ daily basis on the UI. 1. Fields on the dashboard:
   Patient ID, Name, Gender, DOB, Location, Follow-up date, Status (patient has come for follow-up visit or they haven't)
5. Once the visit is complete, patients with scheduled follow-up in descending order (most upcoming dates shown first) should be visible here on the UI.
6. Once the patient has come for the follow-up, it moves to queued visits again, and once the visit is complete, it is removed from the dashboard.
7. The user should be able to see and filter these follow-up visits on a weekly/ daily basis on the UI.

if a user enters obs and wants to delete the obs they can not.
they have to refresh the page.

This is because the UUID is not getting stored with the obs while inserting and without the uuid, an obs cannot be deleted.

Features for the Syria release. Some may apply to other deployments as well

admin/Admin123 doesnt work!

Can you please double check & update.

Thank You!

Please let us know the id and password for default or please let us know the flow diagram

In the initial versions we will support video calling via WhatsApp and audio calling via the phone's app.

Proposed solution:

Part 1: Doctor's need a easy way to start a video/audio call with CHW
We will do this by providing click to call links on the Patient Interaction card.
Get the value of the phoneNumber (provider attribute) of the creator for the ADULTINITIAL encounter (this will be the provider uuid for the CHW).
Add a click to chat link for whatsapp. Here's how to do it https://faq.whatsapp.com/en/android/26000030/
https://wa.me/phoneNumber?text=Hello!%20I'm%20calling%20for%20patient%20FirstName%LastName%20openMRSID
Add a click to call link for phone: https://developers.google.com/web/fundamentals/native-hardware/click-to-call/
If the doctor is accessing the webapp from a mobile phone browser then they can simply click on the Whatsapp click to chat link and it will open their Whatsapp to the contact of the CHW with the pre-filled message. The doctor can hit send for the message and start a video or audio call using whatsapp. Similarly if they use the click to call link then it will open the calling app of the phone with the phone number of the health worker.

If the doctor is accessing the webapp from a computer, there should be an option to SMS these links to their phone or send via email. The phoneNumber and email to which this link has to be sent will be taken from the provider attribute of the doctor.

Part 2: CHWs need an easy way to call the doctor
When the doctor clicks on the Start Visit button (and thus creates a visit note encounter), POST an obs of type Medical Advice into the database. This obs will contain the click to chat link for Whatsapp for the doctor and the click to call link for phone for that doctor.

When the CHW downloads the prescription or automatic sync happens, the medical advice card will show these two links.

hello, im sorry but i need know how i do to install it ?
can i install in shared hosting ? or i need a vps ? or a cloud instance ?
any tuto about installation please
thank you

These are patients for which the Vitals and ADULTINITIAL encounter is complete.
However, we do not want to display patients whose visit note has been entered but the visit hasn't been ended.
The Active Visits is sorted by date, this may result in some patients who were missed to be seen remaining

http://pie.med.utoronto.ca/dc/

Update the webui to show all non-voided complaints in the C/O card and recent visits card and not just the most recent complaint

Add a Home button to all screens so that the user can easily navigate back to home

#237 Emergency button and queued visit issue
When health worker clicks on emergency button and uploads the patient details for the first time, the patient is visible on flagged visit on webui. But if the patient data is updated on visit summary screen, and is uploaded keeping the emergency button clicked, the patient is visible on queued visit section on webui

Solution: Change flagged from an encounter to a visit attribute. This will need changes to the android app

Also needed for AFI
If visit_type = 4 (Telemedicine visit), it should be visible to the doctor's UI
On the Android app, we will create a new visit_type for non-teleconsultation visits (visit_type = 5, CHW visit). If the visit is of visit_type 5, then it should not be visible on the doctor's UI

Related to: Intelehealth/Android-Mobile-Client#763

User may dismiss it by mistake, so we need to make sure that the prompt remains until the user has installed the PWA.

There may be cases where the doctor is required to fill in a certain piece of information.

Prompt for the relevant treatment guideline based on the diagnosis entered by the doctor

The PWA syncs with the REST API at regular intervals to see if new data has been posted.
Related to #59

Two ways to do this:

1. This can be done through the PWA - on a mobile device get the notification in the notifications bar
2. SMS notifications

When I do a search for a patient on the search bar of the visit summary page, the previous search items are also displayed on the WebUI. For e.g, if I search using the term "Sahu", I get the first 2 rows as well, which I had searched for earlier using their OpenMRS ID.

We are creating four sections on the home screen:

1. Flagged Visits (where last encounter = flagged)
2. Waiting for doctor's teleconsult (where last encounter = adult initial)
3. Visits in progress (where last encounter = Visit note)
4. Completed visits (where last encounter = Visit complete)

Add a column of Provider Name in all the sections

There is a check to make sure if a visit note is created, another one cannot be created. Add a notification to the doctor that a visit note encounter is already created