Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Page Properties

Status

Status
colourYellowGreen
titleIn progressDONE

Impact

Status
colourYellow
titleMedium

Driver

Alessandro Domanico

Approver

Claudio Rosazza

Contributors

Alessandro Domanico miz

Informed

Ilario Gavioli Alberto Mandelli

Due date

Resources

https://docs.google.com/document/d/1scNMAkKK9gLFbswDtkJr0bUiv2IPr7g9dakElBInvEs/edit?usp=sharing document

https://github.com/informatici/openhospital-ui

...

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.

...

SMALL

Option 1

Option 2

Option 3

Description

Replicate Open Hospital structure
(Spring + React + Material UI)

Use a different JS library
(e.g. Devias Kit, Creative Tim, Tabler, etc…)

Use existing softwares
(e.g. Grafana, Jasper, etc…)

Pros and cons

(plus) Same as Open Hospital, in the future the two projects could be easily merged

(plus) Homogeneity, same community can contribute to the project

(minus) The current material UI could be poor in terms of widgets and layout managers

(plus) Leverage special features

(minus) It may need specific knowledge

(plus) Some features granted by the software itself

(plus) Levering high quality features

(plus) In case of Jasper, it could be useful for porting the current reporting system in the “gui”

(minus) It could include several unwanted features making the application heavier than needed

(minus) Strong binding to an existing software can be risky

Estimated cost

Status
colourGreen
title

/

Status
colourYellow
titleMEDIUM
/

Status
Status
colourRed
titleLarge
Status
colourGreen
titleSMALL
/
colourYellow
titleMEDIUM
/

Status
Large
colourRedtitle
Status
colourGreen
titleSMALL
/
Status
colourYellow
titleMEDIUM
/
Status
colourRed
titleLarge

✅ 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
serverSystem JIRA
serverIdf0d90336-9135-337c-8387-a97c21b1155f
keyOP-934