At a recent implementation we are seeing a variety of performance issues with Bahmni Connect.
The issues stem from the way the data is laid out at the implementation.
Implementation has large number of patients and encounters.
Also , considering the rise in the need to have remote clinical services in the current times we think we need to redesign the way we synchronise the PWA with the backend.

Currently, after the user enters the credentials and clicks login on the Bahmni connect web app, it synchronises in broadly two steps:
   i. Does a 'push' to send out calls to the backend APIs in OpenMRS to send out any pending events on the PWA.
  ii. Does a 'pull' to update all metadata, offline-concepts , patients, encounters from the backend to the PWA.

When we trigger the pull or "Initial sync"
i. Synchronisation takes hours and is rarely successful.
ii.The devices where the PWA runs become sluggish soon

We want to propose a redesign of the connect syncing strategy(both ways) so we can let the user specify the data they would want to sync for use.

With the above context can you please take a couple of minutes and help us with this survey to understand your cases for Connect PWA and if you need such a feature.