Issue a GET to Patient/{id}/$everything to request all resources in the patient's compartment
Apply _since, _type, and _count parameters to scope the request and support pagination for patients with large record volumes
Handle the paginated response by following the Bundle.link 'next' relation URLs until no next link is present
Aggregate all returned resource types from the Bundle entries into a local store or display layer
Respect server-imposed limits on $everything result size and implement retry with narrower _type filters if the server returns a CapabilityStatement-advertised error for oversized requests
Known gotchas
$everything is a defined operation but servers may not support all parameters; check the server's CapabilityStatement OperationDefinition to confirm which parameters are supported before relying on _type or _since filtering
The returned Bundle uses type 'searchset'; processing logic designed for 'transaction-response' Bundles will misparse the entries
Some servers return a 202 Accepted with a polling URL for large $everything requests rather than a synchronous Bundle; handle both synchronous and asynchronous response patterns
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp