...
The OpenSRP application also allows one to capture multiple addresses for a person, which are distinguished by the field "addressType". Hence, each person can have only one address for each addressType. For example, Mr. Smith cannot have two addresses for addressType "usual residence"; however, he can have two addresses with addressTypes "usual residence" and "previous residence". The addressing address scheme in OpenSRP is flexible and can be mapped to a number of different address formats across the world.
...
Each field must be mapped to OpenSRP or OpenMRS predefined fields in XLSForm to allow data to be pushed into OpenMRS as person address. The address group is identified by person_address in instance::openmrs_entity column in the XLSForm. Each field is mapped with OpenMRS as specified by table below.
| OpenSRP | OpenMRS | XLSForm Column | XLSForm Value (case insensitive) | XLSForm Value (recommended) |
|---|---|---|---|---|
| addressType | address6 | instance::openmrs_entity_parent | Any unique value identifying address from a list of possible addresses for a person | - |
| startDate | start_date | instance::openmrs_entity_id | startDate / start_date | startDate |
| endDate | end_date | instance::openmrs_entity_id | endDate / end_date | endDate |
| latitude | latitude | instance::openmrs_entity_id | latitude | latitude |
| longitude | longitude | instance::openmrs_entity_id | longitude | longitude |
| postalCode | postal_code | instance::openmrs_entity_id | postalCode / postal_code | postalCode |
| state | state_province | instance::openmrs_entity_id | state / state_province / stateProvince/ province | stateProvince |
| country | country | instance::openmrs_entity_id | country | country |
addressFields (Customizable) | ||||
| HOUSE_NUMBER / HOUSE / HOUSE_NO / UNIT / UNIT_NUMBER / UNIT_NO | address1 | instance::openmrs_entity_id | house_number / house / house_no / unit / unit_number / unit_no / address1 | house / unit |
| STREET / STREET_NUMBER / LANE | address2 | instance::openmrs_entity_id | street / street_number / lane / address2 | street / lane |
| SECTOR / AREA | address3 | instance::openmrs_entity_id | sector / area / address3 | sector / area |
| SUB_DISTRICT / MUNICIPALITY / TOWN / LOCALITY / REGION | address4 | instance::openmrs_entity_id | municipality / town / locality / region / sub_district/ address4 | sub_district / town / municipality |
| COUNTY / DISTRICT | county_district | instance::openmrs_entity_id | county / district / countyDistrict / county_district | countyDistrict |
| CITY / VILLAGE | city_village | instance::openmrs_entity_id | cityVillage / city_village / city / village | cityVillage |
| GEOPOINT** | latitude, longitude, address5 | instance::openmrs_entity_id | geopoint | geopoint |
| Everything else with concatenated key-val pair | address5 | instance::openmrs_entity_id | Any other value for address field not covered elsewhere. Highly unrecommended. | - |
| Note |
|---|
**geopoint datatype in XLSForm is split into latitude, longitude fields above and also stored as it is into address5 field. |
...
| View file | ||||
|---|---|---|---|---|
|