There is no support to migrate multi-select observations, Add more for a concept and Add more for section in Bahmni encounter CSV upload.
Proposed Approach:
Use of Single Column and values are separated by configurable character(s).
Enclose the entire value in special characters like [], {} etc to identify the column as multi select concept/ Add more concept in a section / concept in Add more for a section.
Eg:
Multi-select for concept
Assume that delimiter for Multi-select for concept = $
Column Value => [CodedValue1$CodedValue2$CodedValue3]
Add more for a concept in a section
Assume that delimiter for Add more for concept = %
Column Value => [Value1%Value2%Value3]
Add more for a section
Assume that delimiter for Add more for section = ^
Comments from @angshuonline in PAT call - Overloading the Value column as above seems error prone, especially for human editing. For programmatic creation of CSV this might be ok, and in that case, probably better to introduce different columns to hold such values.
Suffixing column headings with attributes (AddmoreSection=true, AddmoreConcept=true, MultiSelect=true etc)
Add more concept or multi select concept values are separated by delimiter eg : $ (Configurable property)
Use of Separate row for each Add more section. We will be using Patient Identifier, Visit Start Date, Visit Type and Encounter Date to join such multiple CSV rows
Read Observation properties from form definition (.json)
Provide multiple values separated by delimiter. Global property bahmni.admin.csv.upload.obs.multiSelect.splitter used to define delimiter. Default Value is |