FlowsBook a callSign inCreate free accountSign up
Population and demographics

Hospital catchment population: how many residents, and how old, around a site

Before a new hospital or clinic wing is planned, count the residents within a drive of the site, then split them into seniors and children. A practical method.

Part of the guide Location intelligence automation

By the xMap team · · 5 min read

A hospital catchment population is the number of people who live close enough to a site to use it as their usual hospital, usually defined by travel time rather than a straight line. Count the residents inside that area, then look at who they are: the over-60s and the over-80s drive admissions and bed days, children drive paediatric and maternity demand. Those three numbers, set against the hospitals already serving the same streets, tell a planner whether a site is worth a deeper study.

This guide is for health system planners, private hospital groups weighing a new campus, consultants writing a feasibility note and charities placing a community hospital. It covers how to draw the area, which age groups to read for which service, a made-up comparison of two sites near Lyon, the traps that inflate or shrink the count, and a flow that produces the same table for every candidate site.

Draw the area the way patients travel

Most people choose a hospital by how long it takes to get there, not by the distance on a map. A ring road or a bridge can put a district 20 minutes away while a closer one across a river takes longer. So begin with a drive area and fall back to a circle only when you need a wider reach.

  • A drive area. Travel area draws what can be reached by car from the site, up to 15 minutes for now, on usual traffic. It suits emergency departments and day surgery, where nearness decides the choice.
  • A circle. Demographics can count everyone within 500 m to 8 km of the site. Useful as a second, wider ring for planned care, where patients accept a longer trip.
  • A drawn area. For a regional hospital, draw the district or health region on the Area of interest map. Demographics adds up the small hexagons inside it.

Running two rings side by side, a 15-minute drive and an 8 km circle, gives a near catchment and an outer one. The gap between them is often the most useful number in the whole study: it shows how much demand the site depends on from people who also live near somebody else's hospital.

Which residents to count for which service

Demographics gives every area its residents, men and women, and nine age groups from 0 to 9 up to 80 and over, plus three summary groups: 0 to 19, 20 to 59 and 60 and over. Read them against the service you plan.

ServiceRead firstWhy
Emergency and general medicineTotal residents, people per km2Everyone uses it; density shows how busy a small area can get.
Elderly care, cardiology, orthopaedicsseniors_60_plus, age_70_79, age_80_plusThe oldest groups use beds the longest.
Paediatricsage_0_9, age_10_19, children_pctA young district fills a children's ward faster than its total suggests.
Maternityage_20_29, age_30_39, population_femaleRead with care: the grid gives women in total, not women by age.
Outpatient clinicsadults_20_59Working-age adults book most routine appointments.

Fields that Demographics adds to each area or site. The grid does not split age groups by sex.

A made-up comparison near Lyon

The figures in this example are invented to show the reading, not measured. A private hospital group has two candidate plots on the edge of Lyon and wants a first answer in an afternoon.

Plot A (east)Plot B (south-west)
Residents within 15 minutes by car310,000245,000
Aged 60 and over21%29%
Aged 80 and over4%7%
Aged 0 to 913%9%
Hospitals already within 8 km62
Residents per existing hospitalabout 52,000about 122,000

Invented figures for illustration only.

Plot A has more people in reach, but they are younger and already well served. Plot B has fewer residents, almost twice the share of over-80s and far fewer hospitals sharing them. For a group that wants to build a geriatric and orthopaedic centre, Plot B is the stronger lead; for a children's unit, Plot A is. The total alone would have pointed to the wrong plot for the first plan.

Mistakes that distort the count

  • Counting overlapping rings twice. If you compare five sites, their catchments overlap. Sum them and you count some residents two or three times. Compare sites one by one, never add their totals.
  • Forgetting who comes in by day. The grid counts where people live. A business district can have few residents and many daytime workers. For the daytime picture, Mobility Footfall measures presence around the site, in people-hours rather than residents.
  • Using one ring for every service. Emergency care lives on a short drive; a cancer centre draws from much further. Match the area to the service.
  • Ignoring the hospitals on the edge. A hospital just outside the drive area still pulls patients from inside it. Count providers in the wider ring too.

Let an AI employee build the table for every site

Writing this table by hand for one plot takes an afternoon. A flow does it for twenty plots, in the same way each time, and can repeat it when the list changes.

  1. Put the candidate plots in a table on My data, with their addresses or positions, and start the flow with My data.
  2. Add Demographics set to each incoming place, within 8 km. Every plot gets its residents, its age groups and people per km2.
  3. Add Nearby places set to pass on each incoming place with counts, for hospitals within the same distance.
  4. Add a Calculated field for residents per existing hospital, and one for the number of residents aged 80 and over.
  5. Ask xMap LLM to rank the plots for the service you plan, quoting only the figures it was given.
  6. End with Make a report, so the board receives a PDF with the table, the ranking and a map.

For a near ring by drive time, start instead from the plots, add Travel area at 15 minutes by car, and set Demographics to totals for each area. The rest of the flow stays the same. It is one example of location intelligence automation: the counting runs on its own, and the planner reads the conclusion.

Questions

How far should a hospital catchment reach?

It depends on the service. Emergency care is often read within a short drive, while specialist centres draw from a region. Run a near ring and a wider one and compare them.

Can I count residents by age and sex together?

Not from this grid. It gives men and women in total and nine age groups in total, but not age groups split by sex.

Why does my site in London show no residents?

The population grid does not cover the United Kingdom or the United States yet. The step says there is no data rather than returning zero people.

Does the drive area use today's traffic?

No. Travel area uses usual traffic, which is the right basis for a catchment that should hold on an ordinary day.

Templates that do this

Read next

More on population and demographics · Every article · Templates

Put it to work

An AI employee in xMap Flows does this on live data, on its own timetable. Start from a template or describe it in plain words.