Help define the short-term Bahmni Roadmap

Software Bahmni
21

@darius and all, those would be the low hanging fruits. Or at least a starter to do list while awaiting a more structured roadmap.

(I wasn’t sure if the issue about the Reporting Module limited integration into Bahmni Apps should be part of it? Just let me know.)

Cc: @ningosi @mjsanish @ekirapa @ajeenckya

22

@arjun, @vinay, @ramashish, we have created tickets for issues that you all suggested (ICD codes for diagnoses, backup/restore locations, manage beds UI). You can find the links in Dimitri’s post that I’m replying to.

Can you please comment on our update these tickets with more details (e.g. full user stories), very soon, because work is starting now.

23

For further information and the detailed requirement document please refer here

24

@ramashish would it be possible to share this doc as a Google Doc? This would make it interactive with others able to comment/edit… etc.

25
26

Hello everyone, am really not so technical in the bahmni implementations, but one of the things that I would suggest the bahmni team to consider in the next release is probably the “OWA”

27

@ejustine this is happening to a certain extent. Two tickets that bring in UI components are doing so through using OWAs, see:

  • BAH-378: Design and integrate bed management admin UI
  • BAH-314: Enable Bahmni Apps Reports app to handle ‘date range’ reports from the Reporting module

They are both ‘in development’.

28

See PR #24

  • BAH-317: I18N support when searching by identifiers and address fields values.

@angshuonline @darius @binduak @shruthipitta