Warning | ||
---|---|---|
| ||
This page has been Archived, and is obsolete. It is available on the Bahmni wiki only for reference and historical purposes. Instead of deleting a page, we prefer to "archive" it, so that it is still available to people who have bookmarked the page. |
Warning |
---|
This page is In-Progress and will be drafted over the next couple of months. If you have any suggestions or would like to add pages which talk about the functionality of Bahmni, please feel free to add them. |
...
Purpose and Benefits
An address hierarchy is maintained in the application to ensure that addresses are codified and human errors can be prevented during entry of patient addresses.
Steps
1) Upload CSV with address mappings:
Address Hierarchy needs to be configured in OpenMRS to display in Bahmni UI. It is best set up by uploading a Comma Separated Values (CSV) file of address hierarchy that represents the hierarchy you want in your implementation. If you have a hierarchy of State > District > Taluka / Block > Village / City then the CSV should have the format of State, District, Taluka , Village.
...
Now, once you have such CSV in place, go to OpenMRS > Administration > Manage Address Hierarchy
In "Upload Address Hierarchy" section, select this CSV file to upload
Set "Delimiter (regex format):" to ',' (without quotes)
...
Click upload to complete the upload process.
2) Map Address Fields:
Once the Address CSV is successfully uploaded, you would see a list of fields in the "Address Hierarchy Levels"
Click on the Edit link next to the field to specify the "Name", "Address Field" and "Required" flag.
...
To ensure that these address fields get synced to correct Labels in OpenELIS, refer to steps in Address Mapping between OpenELIS and Bahmni / OpenMRS
Master Data Setup
Master data for address hierarchy is done by creating a CSV file containing the address mappings to be uploaded. The CSV file's format is as per the sample file provided below :
https://bahmni.atlassian.net/wiki/display/BAH/Address+Hierarchy