Add _include parameters to a search to pull forward-referenced resources (e.g., _include=MedicationRequest:patient to include the Patient from each MedicationRequest)
Add _revinclude parameters to pull resources that reference the search results (e.g., _revinclude=Provenance:target to include Provenance records targeting each result)
Parse the returned Bundle, distinguishing 'match' entries (primary search results) from 'include' entries using entry.search.mode
Handle iterative includes (_include:iterate) when chaining references across multiple hops, and confirm the server supports this capability
Avoid requesting unbounded _revinclude on high-cardinality relationships, as the result set can be extremely large
Known gotchas
_include and _revinclude are optional capabilities; confirm server support via CapabilityStatement.rest.resource.searchInclude before relying on them in production
The search.mode field in Bundle entries distinguishes 'match' from 'include'; processing logic that ignores this field and treats all entries as primary results will incorrectly count or validate included resources
Some servers apply a cap on the number of included resources returned regardless of _count; a silent truncation of includes means the client may not receive all referenced resources
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