Import Bahmni Obs Data without setting VisitEndDate

gsluthra · April 28, 2023, 4:53am

(Posting on behalf of a community member, to ensure this gets documented for future)

Hello! I am trying to import observation data and I want the visit to remain open. However, when I import data using the CSV importer it is closing the visit and assigning it an end date. By default if I exclude the non-mandatory ‘Visit End Date’ field, the import assigns the visit a ‘date_stopped’ that is one second after the ‘date_started’/csv field ‘Visit Start Date’ (picture attached) . If I import a blank ‘Visit End Date’ the import still assigns it a ‘date_stopped’, as pictured, and when I import with an ‘NA’ it throws an error for date formatting. Is there a way to ensure the visit remains open for data I’m importing via the csv importer?

gsluthra · April 28, 2023, 5:05am

I spent some time looking at the Bahmni import CSV code. I assume you are using the Encounter import, that allows you to specify Obs/Encounter/Visit in CSV for patients as documented in Wiki here: https://bahmni.atlassian.net/wiki/spaces/BAH/pages/13697066/Migrate+Patient+and+Encounter+Data#MigratePatientandEncounterData-2.Encounters

The import code triggered by the UI, in the backend seems to come here:

github.com

Bahmni/bahmni-core/blob/e687cc5b0685c3820b6815b10e79ee7f03a5e4ae/admin/src/main/java/org/bahmni/module/admin/csv/persister/EncounterPersister.java#L99


      
          
          
    List<BahmniEncounterTransaction> bahmniEncounterTransactions = bahmniEncounterTransactionImportService.getBahmniEncounterTransaction(multipleEncounterRow, patient, shouldPerformForm2Validations);
          
          
    for (BahmniEncounterTransaction bahmniEncounterTransaction : bahmniEncounterTransactions) {
                  bahmniEncounterTransaction.setLocationUuid(loginUuid);
                  bahmniEncounterTransaction.setProviders(providers);
                  duplicateObservationService.filter(bahmniEncounterTransaction, patient, multipleEncounterRow.getVisitStartDate(), multipleEncounterRow.getVisitEndDate());
              }
              Boolean isAuditLogEnabled = Boolean.valueOf(Context.getAdministrationService().getGlobalProperty("bahmni.enableAuditLog"));
              for (BahmniEncounterTransaction bahmniEncounterTransaction : bahmniEncounterTransactions) {
                  BahmniEncounterTransaction updatedBahmniEncounterTransaction = bahmniEncounterTransactionService.save(bahmniEncounterTransaction, patient, multipleEncounterRow.getVisitStartDate(), multipleEncounterRow.getVisitEndDate());
                  if (isAuditLogEnabled) {
                      Map<String, String> params = new HashMap<>();
                      params.put("encounterUuid", updatedBahmniEncounterTransaction.getEncounterUuid());
                      params.put("encounterType", updatedBahmniEncounterTransaction.getEncounterType());
                      auditLogService.createAuditLog(patient.getUuid(), "EDIT_ENCOUNTER", "EDIT_ENCOUNTER_MESSAGE", params, "MODULE_LABEL_ADMIN_KEY");
                  }
              }
          
          
    return new Messages();
          } catch (Exception e) {

From there, while searching for an existing visit in DB for this patient, it tries to associate the Obs/Encounter to that visit. If an existing Visit is not found, it seems to create a new one. See this: bahmni-core/VisitIdentificationHelper.java at e1db1777a0abda728b54f1746c3dad489c248b93 · Bahmni/bahmni-core · GitHub

Here, it sets the END Date to midnight-1sec (end of visit start date), as the visitEnd Date.

I think this is what you also show in your screenshot. The Visit End Date is set to END of the day when the visit is started.

In summary, I think since it isn’t finding an existing Visit in the system to associate this data with, it is creating a new visit for that same date/time you mentioned in VisitStartDate column, and marking Visit as closed as midnight same day (11:59pm). I don’t think it will let you currently leave Visit as open in this scenario.

The integration tests for this functionality are here (although there isn’t any test for validating what happens when VisitEndDate is null and existing Visit doesn’t exisit): bahmni-core/EncounterPersisterIT.java at 60cd85ca9881ac0623327a300979f2ca3413e7d2 · Bahmni/bahmni-core · GitHub

cc: @sivareddy @binduak @angshuonline – Cc’ing others who may know this code better than me.

sivareddy · April 28, 2023, 7:45am

@gsluthra if we set encounter date to current date, then visit end date set to null. bahmni-core/VisitIdentificationHelper.java at master · Bahmni/bahmni-core · GitHub

gsluthra · April 28, 2023, 8:52am

Thanks @sivareddy – so if encounter date is today, then it is assumed that visit is still open (since visit end date is in future… which is tonight at 11:59), which therefore the system doesn’t not automatically set. right?

sivareddy · April 28, 2023, 9:07am

yes @gsluthra .