POST /Measure/{id}/$collect-data with periodStart, periodEnd, and subject parameters to retrieve the relevant clinical data
Receive a Parameters resource containing a measureReport parameter (data-collection MeasureReport) and one or more resource parameters holding the collected FHIR resources
Inspect the data-collection MeasureReport to confirm evaluatedResource references match the collected resource list
Store or forward the collected resources and the data-collection MeasureReport to an aggregator or payer endpoint using $submit-data
Use $data-requirements first if unsure which resource types and profiles the measure depends on, to avoid collecting unnecessary data
Known gotchas
$collect-data returns raw FHIR resources, not a scored result; do not interpret the data-collection MeasureReport's population counts as a final measure score
Large patient cohorts will produce very large Parameters bundles; consider requesting $collect-data per-patient and batching submissions rather than running against an entire Group
The collected resources may include data from outside the measurement period if they are referenced by in-period resources; validate dates before forwarding to avoid reporting period confusion
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