While working with a large scale implementation using Bahmni connect we have come across a situation where we feel we are being restricted by a fundamental way Bahmni connect is designed to work today. We are planning a roadmap around designing a solution to address that.
We are running a very short survey here to understand the implementation that you are working on currently and if the design change is something you would want to use or collaborate on.
Please take the survey here.It will help us immensely in understanding connect’s usage.
Survey Link : https://forms.gle/LQcD2BepVJZRa3cf6
Please let us know if you are having difficulty accessing the survey.
@angshuonline @mksrom @akhilmalhotra1 @mksd @arjun @pkanchankar @krishnanspace @binduak
@kirity @buvaneswariarun @praveenad @tejakancherla @adhliwayo @tawakay @vmalini @pradiptakundu
We have been working on a document to come up with what technical approach we should go with to start devising the solution. Once we are able to come up with a technical approach we will be in a better position to start work on a more low level implementation diagram for that approach.
For now attaching copy of the document in the thread for discussion.
@tejakancherla. @pratibhasagar @angshuonline @buvaneswariarun @pradiptakundu @vmalini
Bahmni-Connect Technical Analysis.docx (1.4 MB)
We are finishing up the work for Bahmni connect where we have implemented the following changes ,
i. Zipped downloads of address hierarchy and offline concepts to make the initial sync quicker
ii.Additional sync strategy to provide the ability to download granular location based data to the PWA device.
More details to be posted in this space in the following days.