Confirm the FHIR server supports the $summary operation by checking the CapabilityStatement for a Patient-level operation named summary
Invoke the operation with GET [base]/Patient/[id]/$summary; the server returns a FHIR Bundle of type document
The Bundle contains a Composition resource as the first entry; the Composition defines the IPS sections and references the clinical resources
Iterate the Composition.section array; each section has a title, code, and entry array referencing resources in the Bundle by their fullUrl
Extract clinical data from the referenced resources: Medication Statement or MedicationRequest for medications, AllergyIntolerance for allergies, Condition for problems — cross-referenced to the section codes defined by the IPS IG
Validate the Bundle against the IPS FHIR Implementation Guide profiles if conformance checking is required
Known gotchas
The $summary operation returns a document Bundle, not a searchset; do not parse it as a paginated search result
Servers may return a minimal IPS with only required sections populated; optional sections such as Immunizations or Procedures may be absent if no data exists
The IPS Composition.type and section codes are defined by the IPS IG and differ from generic document codes; validate section.code against the IPS value sets when processing
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