Bahmni Connect: how to setup the LocationBasedSyncStrategy?

mksrom · January 5, 2018, 5:55pm

Thanks @shruthipitta for spending the time to debug this with me .

We have found that the problem is likely coming from the fact that too many calls are made when the address set on the Login location is a high level in the address hierarchy.

Indeed, there is as many calls made as there is filter values (ie, address entries):

github.com

Bahmni/bahmni-connect/blob/2cd8e6800f9d7b3bff480ec7a6b0f2e1bbbaac68/ui/app/common/offline/services/offlineSyncService.js#L80


      
          
          
var savePatientDataFromFile = function () {
              var eventLogUuid;
              var defer = $q.defer();
              offlineDbService.getMarker('patient').then(function (marker) {
                  if (marker.lastReadEventUuid) {
                      return defer.resolve();
                  }
          
          
        return getDbName().then(function (dbName) {
                      var promises = marker.filters.map(function (filter) {
                          var syncedInfo = offlineService.getItem("synced") || {};
                          var synced = syncedInfo[dbName] || [];
                          return $http.get(Bahmni.Common.Constants.preprocessedPatientFilesUrl + filter).then(function (response) {
                              return getPatientDataForFiles(getRemainingFileNames(response.data, synced), 0, null, dbName).then(function (uuid) {
                                  eventLogUuid = uuid;
                              });
                          }).catch(function () {
                              endSync(-1);
                              return defer.reject();
                          });

In my use case, there is only one possible login location named ‘Health Center’ because the clinic is a mobile clinic and provides care across 3 provinces. So I would have to set the level to the highest one, “country”. That is 16,459 address entries.

This means that in the code below, promises will contain 16,459 promises.

And as many HTTP calls will be made. This seems to freeze the Chrome window.

If one sets a lower address level to the Login location, such as a District or Village, the number of child entries is much smaller and all works. For instance, with few trials I can say that around 500~700 entries max, the page works and loads fine.

Conclusion: I believe the LocationBasedSyncStrategy was not created to load such a big number of entries and may just not fit for me here.

I am thinking I should create a “AllPatientsSyncStrategy” instead to simply retrieve all patients.