How does TanStack Query help UK GDPR right to erasure in NHS applications?

TanStack Query and UK GDPR erasure for NHS: when a patient exercises their right to erasure (Article 17) and the NHS application has cached patient data in TanStack Query cache: (1) erasure request received (DELETE /patients/{nhs_number}), (2) server-side erasure (PostgreSQL cascade delete -- all patient records deleted), (3) cache invalidation (queryClient.removeQueries({predicate: q => q.queryKey.includes(nhsNumber)}) -- removes all cached queries containing that NHS number), (4) active session (if patient is currently viewing their record -- React state cleared, redirect to homepage), (5) audit log (erasure request recorded -- UK GDPR right to erasure fulfilled timestamp). ClickMasters NHS erasure pattern: every NHS application has a dedicated erasure webhook that triggers both PostgreSQL cascade delete and TanStack Query cache invalidation -- UK GDPR Article 17 compliance.

Should UK NHS HealthTech use Apollo Client with FHIR?

Apollo Client with FHIR R4: Apollo Client is designed for GraphQL APIs. NHS FHIR R4 UK Core is a REST API (not GraphQL). Combining Apollo Client with FHIR: (1) Apollo Client can fetch REST via @apollo/client link (REST to Apollo cache adapter) -- adds significant complexity, (2) FHIR servers provide GraphQL endpoint (HAPI FHIR has experimental GraphQL -- but not FHIR standard, not UK Core validated), (3) ClickMasters recommendation: do not use Apollo Client for NHS FHIR R4. Use TanStack Query (REST) for FHIR API calls. TanStack Query handles FHIR pagination (FHIR bundle next page links), FHIR caching (per-resource stale time), and FHIR cache invalidation (invalidate on patient update). Apollo Client adds no benefit over TanStack Query for REST FHIR -- it adds bundle size and complexity.

React Query Vs Swr Vs Apollo Uk Data Fetching

TanStack Query vs SWR vs Apollo Client -- UK Data Fetching (2026)

Updated: June 20269 min read

UKGBPComparisonUK GDPRUK Law

Direct Answer

TanStack Query (formerly React Query) is ClickMasters default for all UK REST API data fetching: best cache management, mutation handling, and infinite query support. SWR is right for simple read-heavy applications where TanStack Query is overkill. Apollo Client is right when a GraphQL API is mandated -- but since ClickMasters defaults to REST + tRPC (not GraphQL), Apollo is rarely needed. Data fetching library choice affects NHS clinical UI loading performance, FCA IBS UI availability, and UK GDPR cache invalidation (right to erasure -- cached patient data must be invalidated on deletion).

Factor	TanStack Query v5	SWR v2	Apollo Client v3
NHS patient data cache invalidation	BEST -- queryClient.invalidateQueries() on UK GDPR erasure	SWR mutate() -- adequate	Apollo cache eviction -- good
FCA payment mutation with optimistic UI	BEST -- useMutation with rollback on failure	No mutation support	Good -- Apollo useMutation
NHS FHIR R4 REST API fetching	BEST -- stale-while-revalidate, deduplication, prefetch	Good -- simpler API	Not designed for REST
tRPC integration (ClickMasters default)	BEST -- @tanstack/react-query used internally by tRPC	tRPC can use SWR adapter	Not applicable (tRPC uses React Query)
NHS clinical UI offline support	Good -- query persister (IndexedDB cache)	Limited offline support	Apollo cache persistence -- good
Background data refresh (NHS live data)	BEST -- refetchInterval, refetchOnWindowFocus	Good -- revalidateOnFocus	Polling -- good
UK GDPR right to erasure (cache clear)	BEST -- queryClient.clear() clears all cached patient data	SWR cache.clear() -- available	Apollo cache.reset() -- available
Bundle size	Medium (47KB gzipped)	BEST -- 4KB gzipped	Large (93KB gzipped)
ClickMasters default	All UK REST and tRPC data fetching	Simple read-only dashboards	GraphQL APIs only