OH2022 - Dashboard
Status | DONE |
---|---|
Impact | Medium |
Driver | @Alessandro Domanico |
Approver | @Claudio Rosazza |
Contributors | @Alessandro Domanico @miz |
Informed | @Ilario Gavioli @Alberto Mandelli |
Due date | Jun 30, 2022 |
Resources | https://docs.google.com/document/d/1scNMAkKK9gLFbswDtkJr0bUiv2IPr7g9dakElBInvEs/edit?usp=sharing document |
Relevant data
The goal is to implement an extension of Open Hospital UI with an anonymous data analysis system for monitoring purposes to obtain appropriate metrics on services provided, status of the drug warehouse, epidemiological cases, cases of non-communicable diseases, malnutrition, gestational problems, childbirth and premature deaths.
To design of a new page into Open Hospital UI, with a structure to be customizable by the user and easy to extend in the code.
The page should be optional after the login, only for enabled users.
The dashboard should show only information enabled for the specific logged user roles and permissions (see Use Cases below)
Background
At the moment Open Hospital software (in both its GUI and UI - under development) is missing a landing page after the login in which an administrator, a medical director or any enabled users, can have a grasp of main indicators of the hospital activities.
At the moment the user is only redirected to a basic page “Search / New Patient” regardless his/her roles and permissions (in UI, the permissioned main menu in GUI) . This also should change in order to set as landing page the new Dashboard or any other view.
At the moment in the Open Hospital db one can find informations such as:
Nr. of OPD at date (today, yesterday, last week, last 14 days) divided by Age and Sex
Nr. of ongoing Admissions divided by Ward, Age and Sex
Nr. of discharges at date (today, yesterday, last week, last 14 days) divided by Age and Sex
Average length of stay (admission duration) divided by wards
Bed Occupancy Rate (BOR = number of admission / number of beds) divided by wards and period (today, last week, this month, last month, this year)
List of drugs under critical level order descending
List of most consumed drugs at date (today, yesterday, last week, last 14 days) in descending order
Forecast of drugs consumption (most consumed drugs last year, same period - if available)
List of most frequent diagnosis at date (today, last 3 days, this week) divided by provenance with possibly showing them on a map
Nr. of children under malnutrition control
Nr. of patients under chronic control
Nr. of patients under ANC, delivery and PNC at date
Nr. of deliveries at date (today, yesterday, this week, last week, this month, last month, this year) divided by outcome
Total bills collections and total bills unpaid at date (today and everyday back current week) divided by OPD and IPD
Total bills collections and total bills unpaid this month, last month divided by OPD and IPD
📱 Use cases
The Medical Director logs into Open Hospital and lands on the Dashboard showing the most common diagnosis in the last month and the less used appeared in the current week, so she can discuss them in the next staff meeting. She also gets an overview of the current bed occupancy ratio in the hospital for each ward and general.
The Client’s collection agent logs into Open Hospital and lands on the Dashboard showing the current outstanding balances for each client.
The Chief Accountant logs into Open Hospital and lands on the Dashboard showing the state of billing (income and receivable) as well as the closed and still pending bills.
The Chief Pharmacist logs into Open Hospital and lands on the Dashboard showing the drugs running out of stock as well as a brief forecasting of average consumption in the following months.
👨🏫 Required features
Responsive UX
Customizable layout
Save layout per user
Options considered
| Option 1 | Option 2 | Option 3 |
---|---|---|---|
Description | Replicate Open Hospital structure | Use a different JS library | |
Pros and cons | Same as Open Hospital, in the future the two projects could be easily merged Homogeneity, same community can contribute to the project The current material UI could be poor in terms of widgets and layout managers | Leverage special features It may need specific knowledge | Some features granted by the software itself Levering high quality features In case of Jasper, it could be useful for porting the current reporting system in the “gui” It could include several unwanted features making the application heavier than needed Strong binding to an existing software can be risky |
Estimated cost | MEDIUM | MEDIUM | SMALL |
Action items
Outcome
Option 2: to develop some components from scratch might be overkilling, one library (from Option 2) will be used for the POC.
Jira issue → OH2-145: Monitoring DashboardIn Progress
Open Hospital powered by ISF
2005 - 2016 ISF © Informatici senza frontiere - ONLUS