The referral analysis allows one to compute the travelling times and/or the distances along the least-cost paths (i.e. path between two locations that minimizes the total travel duration for those travelling along it, see Ray and Ebener, 2008) between two groups of health centers. Such path is different from a straight line as it does take into account the landscape constraints together with the modes and speeds of travel of the population.
For For example, one would want to know the distance and travel time between each primary health care facility and the nearest referral hospital in a given Province, or make sure that the travel time between each Basic Emergency Obstetric Care facilities (BEmOC) and the nearest Comprehensive Emergency Obstetric Care facilities (CEmOC) is below 2 hours in a given country.
Starting Starting with version 5.3.2 of AccessMod, the scaling up Referral module has been improved to run in parallel mode, which means it can take advantage of all CPUs that are allocated to the AccessMod Virtual Machine. This speeds up the referral computation (see details in Appendix 5).
If you are running a referral analysis with a large number of facilities, it is therefore better to first set up your Virtual machine with a maximum of CPUs and memory (see Section 4.2).
...
The sections in the second part of the analysis panel can then be filled as follow:
Facilities selection
...
(5) The "Permute group" option allows one to improve computation time when more facilities are selected in the starting group than in the destination one. But if this option is selected, 'Limit the spatial analysis to the closest pair time-wise' is not possible. We will not use this option for the exercise.
(6) The option "Output the layer of the paths among selected facilities", if checked, will output a polyline shapefile with all least-cost paths among all the start-destination pairs of points. We will not use this option for the exercise.
(7) The "Enable parallelization" option, if checked, allows the referral analysis to be parallelized on all available CPUs/cores that your AccessMod isntance instance has access to, if it is possible, and if it is worth doing it with the available memory. If you are using Virtual box, the numbers of available cores can be changed in the settings of VirtualBox (see section 4.2). Using this option can drastically decrease the overall computation time for this analysis. We will not use this option for the exercise.
...
(9) If "Measure distances from cell center" is checked, the resulting distance will be measured between the center of the cells in which the FROM and TO facilities are located (this corresponds to the shortest path by travel time). If unchecked, this measure of the distance will also include the (small) distance between each facility and the center of the cell in which they are located (this corresponds to an extended path compared to the shortest path by travel time). We will not use can check this option for the exercise.
...
(12) The validation module should indicate that all fields have been correctly filled in (with a green “OK”). If this is the case, you can hit the "Compute" button to launch the analysis. If this is not the case, the "Compute" button will still be in red, and you will have to go through the warning and error message to find out what needs to be adjusted.
A transparent model window with some text and a progress bar will appear in front of the panel while the analysis is being conducted. Please wait until this window disappears to continue using AccessMod. This analysis can take a lot of time to completed especially if the number of health facilities to be processed is high.
...
You can archive these three tables, export them, and open them in Excel to visualize the results. The three tables present the same 6-column structure as presented in the following example (referral nearest by time class):
- from_cat: unique identifier of the "From"health facility, as per the field selected from the attribute table of the health facility layer.
- from_name: name of the "From" health facility, as per the field selected from the attribute table of the health facility layer.
- to_cat: unique identifier of the "To" health facility identified through the analysis, as per the field selected from the attribute table of the health facility layer. In this case, this column contains code of the closest hospital by time from the "From" health facility.
- to_name: name of the "To" health facility identified through the analysis, as per the field selected from the attribute table of the health facility layer. In this case, this column contains the code of the closest hospital, by time, from the "From" health facility.
- distance_km: distance in kilometers between the two health facilities ("From" and "To")
- time_m: travel time in minutes between the two health facilities ("From" and "To")
...
In the above table, for example, you can notice that reaching the Queen Elizabeth Centre Hospital from the Chabvala Health Centre requires about 700 minutes of travel, but these two facilities are separated by only 50 km. If you look at the geographic locations of these two centers in a GIS software, you will see that a river (i.e., a barrier to movement) and the lack of roads in this area leads to require a long travel time before reaching the hospital. If you want to visualize the path between the two facilities, you can re-launch the analysis, but this time by selecting the option "Output the layer of the paths among selected facilities". The resulting shapefile can then be displayed in your GIS software.
This particular pair of health facilities also illustrates the impact that a barrier to movement can have on the output results. This calls for careful considerations when choosing the input layers and defining barriers to movements. For example, it that particular case considering the use of boats to cross the river at some point could have considerably reduced the travel time between the two facilities.
| Note |
|---|
The header for the columns containing the unique identifier and the name of the health facilities will match the label for the field you have selected from the attribute table of the "FROM" and "TO" health facility layers. As mentioned here above, the distance and the travel time columns are included in each of the 3 tables, but their content is only significant for the analysis that each of the resulting file covers (closest by distance, closest by time or all possible combinations). In other words:
AccessMod generates only two tables when checking the "Limit the analysis to the closest destination point in time" option, namely: 1. The one containing the nearest facility within the given time for each "FROM" health facility (referral nearest by time class) 2. The one containing all pair-wise results (referral class) In both tables:
What happens if two facilities are equally "closest by time" ? |
...