Lookups - Analytics API v1.4.13

(Last updated: 2026-10-12, Created: 2026-09-30)

The Lookups endpoint, /lookups/graphql, lists the values used for filtering in EWA Insight, such as organizations, stations and mission types. It is built for EWA Insight, and is not meant for your own integrations, see Configuration. To find ids and names in your own integrations, use the Clean layer.

All lookups read from the Clean layer, and leave out values that are deleted in EWA. The sk_* fields are the id or value itself, not the keys used in the Core layer.

Lists without paging

These return the whole list, and take no arguments.

Field	Returns	Lists
organizations	sk_organization, organization_id, organization_name	Organizations
urgency_levels	sk_urgency_level, urgency_id, urgency_level_name	Urgency levels
mission_types	sk_mission_type, mission_type_id, mission_type_name	Mission types
resource_types	sk_resource_type, resource_type_name	Resource types
location_types	sk_location_type, location_type	Location types used in completed records
retts_priority_levels	sk_retts_priority_level, id, color	RETTS priority levels
sats_priority_levels	sk_sats_priority_level, id, color	SATS priority levels
transferred_locations	sk_transferred_location, transferred_location_name	Locations patients were transferred from or to
circumstances	sk_circumstance, circumstance	Circumstances registered in records
assistance	sk_assistance, assistance	Assistance registered in records
accompanying_personnel	sk_accompanying_personnel, accompanying_personnel	Accompanying personnel registered in records
personnel_roles	sk_personnel_role, personnel_role, sk_resource_type, resource_type_id, resource_type_name	Personnel roles, per resource type

Paged lists

These are paged by page number and sorted by name, see Filtering and paging. keywords searches in the name.

Field	Arguments	Returns
stations	keywords, organization_ids, station_ids, page, page_size	sk_station, organization_id, station_id, station_name
personnel	keywords, user_ids, page, page_size	sk_personnel, user_id, full_name
resources	paging, filters: { keywords, station_id, sk_resource_type }	sk_resource, sk_resource_type, resource_id, resource_name, station_id, station_name
interventions	paging, filters: { keywords, sk_intervention_group }	sk_intervention, sk_intervention_group, intervention, intervention_group
intervention_groups	paging, filters: { keywords }	sk_intervention_group, intervention_group
chief_complaints	paging, filters: { keywords, sk_chief_complaint_group }	sk_chief_complaint, sk_chief_complaint_group, chief_complaint, chief_complaint_group
chief_complaint_groups	paging, filters: { keywords }	sk_chief_complaint_group, chief_complaint_group
location_counties	paging, filters: { keywords }	county_id, county_name
location_municipalities	paging, filters: { keywords, county_id }	county_id, county_name, municipality_id, municipality_name
location_groups	paging, filters: { keywords, county_id, municipality_id }	county_id, county_name, municipality_id, municipality_name, location_group_id, location_group_name

• stations and personnel take page and page_size directly, and return page, page_size, total_pages, total_records and items.
• The others take paging: { page, page_size }, and return paging_info { page page_size total_pages total_records } and items.
• page defaults to 1 and page_size to 100.
• personnel, interventions and chief_complaints also include values found in completed records.

Example: the first 20 stations in organization 1.

{
  stations(organization_ids: [1], page: 1, page_size: 20) {
    total_records
    items { station_id station_name }
  }
}