CSV Upload: No support to migrate multi-select obs in encounter csv upload

Tags: #<Tag:0x00007f302c39aef0>

There is no support to migrate multi-select observations in bahmni encounter CSV upload. Find documentation here

We have two approaches to support this, suppose for the following screenshot

Approach 1: Repeat headers for all the mult-select answers

Eg: CSV headers would look like this (No, of csv headers are equal to the number of answers)

Repeat.1.Obs.MultiSelectTest."FSTG, Specialty determined by MLO", Repeat.1.Obs.MultiSelectTest."FSTG, Specialty determined by MLO"

and values as Plastic,Maxillofacial

Approach 2: Only one header and all multi-select values as a single value separated by some configurable character

Eg: CSV headers would look like this

Repeat.1.Obs.MultiSelectTest."FSTG, Specialty determined by MLO"

and values as Plastic$Maxillofacial if $ is configured(advanced properties) as separator

We are going to do it with approach-2 since approach-1 makes CSV very complex for end-user if possible multi-select answers are more(say 50) i.e. if one patient has all the answers then for rest of the patient’s CSV columns should be handled(a comma) which makes it error-prone and increases complexity to prepare CSV rows.

@angshuonline @mksrom @snehabagri @binduak @praveenad @neha @vinisha @vmalini @mohit

Inputs from @angshuonline,

  • Should consider other entities besides forms
  • Check for type coded and then expect for multi-select type
  • Should handle error scenarios when question is not multi-select but multiple values are given