Content Comparison

...

•  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

  Jira Legacy
  server System JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId f0d90336-9135-337c-8387-a97c21b1155f key OP-7

  ,

  Jira Legacy
  server System JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId f0d90336-9135-337c-8387-a97c21b1155f key OP-8

  and

  Jira Legacy
  server System JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId f0d90336-9135-337c-8387-a97c21b1155f key OP-9

  )
•  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
•  We meet in about a month to discuss the progress of the work (around the end of April).

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.