Nearest hospitals

nearby_hospitals14 fields5 of these fields open in the demo

Source: Enhetsregisteret specialist-health units, geocoded against Kartverket (poi-hospitals)
Geography: Around the address
Reported stale after: 120 days
Access: Requires an API key granted this section
Contract version: 2

Available with: trial key (open fields) · bundle or agreed plan, subject to field policy and source grants · Pricing

What this does not say

Quoted verbatim from the section’s warnings field, exactly as the API returns it. They are not translated: a translation would show something other than what your response actually contains.

Five nearest registered hospital units by straight-line UTM33 distance, not driving time and not the hospital a patient would be taken to: that is decided by the health trust and the emergency medical communication centre.
has_emergency is read from the unit's registered activity and can be wrong; a unit without it may still receive emergencies. Units whose address could not be geocoded are left out.
Routes follow the car profile, from the address to the feature; ranking remains straight-line. Static modelled travel time excludes live traffic and emergency response. Road snapping is limited to 250 m at each end. Ferries may be included without timetable/wait guarantees. Graph source date is unverified unless supplied. © OpenStreetMap contributors, ODbL: https://www.openstreetmap.org/copyright
walk_route and cycle_route follow OSRM's foot and bicycle profiles on the same OpenStreetMap data: paths and stairs allowed on foot, road rules for bicycles; modelled times at profile default speeds, not measured.

Provider-contract fields

2 of 14 fields are value fields — the ones that decide whether a record actually says anything. The rest are context: identifiers, codes and timestamps. Fields marked “open” also occur in the demo projection, which may have different field definitions. Other fields require the appropriate field policy and source access, not just a key.

Field	Type	Role	Demo
id	integer \| null	context	—
hospital_name	string \| null	value	open
health_trust	string \| null	context	—
hospital_type	string \| null	context	open
has_emergency	boolean \| null	context	open
address	string \| null	context	—
municipality_code	string \| null	context	open
lat	number \| null	context	—
lon	number \| null	context	—
straight_line_distance_m	number \| null (m)	value	open
updated_at	string \| null	context	—
route	object	context	—
walk_route	object	context	—
cycle_route	object	context	—

Fetch this section

Send the key in the X-API-Key header. The section can be fetched with the rest of the address, or on its own with pagination.

curl --disable --fail-with-body --silent --show-error --connect-timeout 10 --max-time 30 \
  -H "X-API-Key: ${APPROACH_API_KEY:?APPROACH_API_KEY is not set}" \
  'https://api.approach.no/api/v1/addresses/285717643?include=nearby_hospitals'

# paginated, one section at a time
curl --disable --fail-with-body --silent --show-error --connect-timeout 10 --max-time 30 \
  -H "X-API-Key: ${APPROACH_API_KEY:?APPROACH_API_KEY is not set}" \
  'https://api.approach.no/api/v1/addresses/285717643/sections/nearby_hospitals?limit=25'

Try it now

This is a real call against the public demo, from here. What appears below is what the API returned — not a sample.