Inclusion of a Patient Dashboard

[anishaswain]

I would like to propose the idea for a dashboard for patients which is presently absent in the app. There are dashboards for the admin, doctors, labs etc but the inclusion of this feature would make the app more accessible from the patient side.The features would include:

1. Book an appointment from the list of available doctors.
2. Manage appointments, i.e., if there would be a change in the schedule of the doctor, it would be notified to the patients and a new appointment would be fixed.
3. Check-up reminders for patients.
4. Reminders for the refill of medicines.
5. Reports of checkups and imaging lab reports.

These are the basic features that would make the experience for the patients more convenient, however, more ideas and features would be appreciated to be worked upon.

[emadehsan]

Great ideas! What do you think about # feature for Patients? Currently patients are added only through dashboard. But if he/she has to book an appointment for the very first time, he/she must be able to #!

[emadehsan]

I think currently the core team is focused on Release 1.0 since the release date (April 1st) is approaching. These features might get included in next versions of the software.

[aanchan]

I'm currently working on this issue. I approached it by creating a new route called patientrole.index. I'm creating this route so that only a particular logged in patient has access to it. What I am struggling though with is displaying basic patient data. I'm trying to understand enough about the Ember Data store, CouchDB and PouchDB along with the structuring of the abstractIndexRoute and abstractPagedController in order to get the current users login ID from sessionVars, query the document store (CouchDB) and display all of the patient's credentials as a first step. I want to do this so that the current logged in user can view only his/her data. What would be the best way to generate a query? I'm thinking I need to create a new view in pouch-views.js?

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.