Page Properties | ||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
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.
...
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 | ||||
Status | ||||
colour | Green | title | SMALL/
|
|
|
✅ Action items
...
✅ Action items
- To decide the final Option
- To create Jira issues with analysis' outcome Alessandro Domanico and to group them under an Epic issue
\uD83C\uDF1F 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 →
Jira Legacy | ||||||
---|---|---|---|---|---|---|
|