Date
Participants
Goals
Aim of the meeting was to talk about the various possibilities that presented themselves based on the roadmap already shared the previous time and that you can find here: 2019-02-27 Call to Action
Discussion topics
Time | Item | Presenter | Notes |
|---|---|---|---|
21:00 | Introduction | Partecipants | All partecipants introduced themselves |
| Roadmap | Roadmap presentation from now up to June2019, December 2019 and the future | |
TBC | TBC | TBC | To Be Completed by re-playing the recording (task for a secretary assistant?): we again gave an overview of what goes around the development of OpenHospital, discussing the future roadmap of the project, listing and explaining the technological choices made and also imagining the new look that version 2.0 will have, also making a nod to the first practical application that could take place in Ethiopia for the CUAMM electronic partogram project. Unfortunately there was no time to show installation, build and use as desired but it is definitely something you should practice to contribute to. |
Action items
- soon we will publish a third component (repository) on GitHub "openhospital-api" which will initially contain an example of REST services built around the "org.isf.patient" module and documented with OpenAPI (ex Swagger) which will be the track we will all follow for then cover all the other modules
- there is absolute freedom in self-assigning tasks, creating new ones if necessary, dividing them into smaller sub-tasks and discussing them directly on Jira (in English) to ask for opinions or share choices and activities with the whole community, do not be shy!
- to contribute to the code one always proceeds according to the fork & pull-request scheme on GitHub and is documented through the Wiki (which also has tasks on Jira that can be taken over by someone, see OP-7 - Getting issue details... STATUS , OP-8 - Getting issue details... STATUS and OP-9 - Getting issue details... STATUS )
- at Paolo Viotti suggestion we will try to "label" Jira's tasks with specific labels so that they can be reorganized or searched by type and degree of difficulty
Decisions
- once the patient module is exposed as REST and using React as shown by Intesys, we can already carry out the electronic partogram required by CUAMM, for which the specifications are quite defined (unlike the future openhospital-ux which is still in progress) and those interested in contributing can subscribe to the #ePartogram channel we created on #Slack (just provide an email)
- we will organise an ad hoc call on the future layout of OH, the so called UX, where we will talk about functionalities and layout of the screens; for the moment those interested in the work group can link to the thread on Confluence on this page UX - First steps and related subpages, that will be updated in the coming days with what emerged from the call, if you start whatching it (by clicking on the “eye” in the upper-right corner) you will receive updates.