Date
Participants
Corrado Costa
Luigi Enrico Maccolini
Henrique Almeida
Goals
purpose of the meeting was to resume work after the release of version 1.9, in details:
To finish the merge of the features tagged "Uni2grow"
To continue Antonio Verni's work on openhospital-api
To continue the work of Intesys on openhospital-ui
To start drafting a roadmap of integration with FHIR
To make some changes to the OpenHospital website
Discussion topics
Time | Item | Presenter | Notes |
|---|---|---|---|
21:00 | Presentation | Welcome to old and new participants | |
21:30 | Roadmap | Brief roadmap's presentation with the news about the release process and Jira’s tasks workflow | |
22:00 | openhospital-ui | Alessandro showed the state of the art about the new User Interface (scaffold) in React created by Intesys and early refactored by Henrique Almeida. They have been also able to link it to the DB with the WIP of Antonio Verni on the REST-API component which, in this way, has been tested as functioning for the full-stack application wrapup. The way forward for the coming months is to publish the WIP of Antonio and to finalize the full-stack on the ‘patient’ module first, which will be a reference for the other modules. Niccolò Pasquetto Alessandro Falezza Riccardo Costa and Henrique, will prepare an short how-to about the UI and the connection with the API. Nicolò De Uffici from Intesys, will share his WIP about the UI Design. Moreover, a solution has to be found for the User’s permissions schema and for Transifex translations | |
22:30 | FHIR and Privacy | Alessandro Domanico Luigi Enrico Maccolini | We discussed the possibility to provide in OpenHospital a FHIR service in parallel to the new REST-API, with the idea that in the future they could converge in the same unified service; in other words OpenHospital would handle FHIR calls for both external and internal requests. For this topic Alessandro will create a dedicated Jira Task helped by Luigi. We discussed also the topic of data security and we separated into 3 different topics: 1. Data Breach by Intrusion 2. Data Breach by Wrong Design 3. Data Breach by non-compliance with the law. While the 1st should be granted by the API design, the 2nd is more related to how the software is designed and we have to think about. The 3rd point requires more in-depth analysis with specific skills, so it will further investigated within ISF experts and Alessandro will report to the OH’s group. |
23:00 | OpenHospital website | - | There was no time to discuss this topic |
Action items
- To publish the openhospital-api component Antonio Verni
- To prepare a short how-to about the UI and the connection with the API Niccolò Pasquetto
- To share the WIP about the UI Design Niccolò Pasquetto and Nicolò De Uffici
- To create a Jira Task about FHIR service component Alessandro Domanico
- To investigate further about Privacy Alessandro Domanico
Decisions
- To discuss how to implement the user’s permission schema
- To discuss how to include Transifex translations