Identify the Measure resource canonical URL on the FHIR server and confirm it exists via GET /Measure?url={canonical}
POST /Measure/{id}/$evaluate-measure with query parameters reportType=individual, subject=Patient/{id}, periodStart=YYYY-MM-DD, periodEnd=YYYY-MM-DD
Receive a MeasureReport resource of type 'individual' in the synchronous response; check measureReport.status is 'complete'
Inspect measureReport.group[].population[] entries for numerator, denominator, and initial-population counts, and measureReport.group[].measureScore for the computed ratio
If the operation runs long, check whether the server supports async via Prefer: respond-async and poll Content-Location accordingly
Validate the returned MeasureReport against the DEQM Individual MeasureReport profile using $validate before downstream use
Known gotchas
reportType=individual requires a single subject parameter pointing to a specific Patient; omitting subject or supplying a Group reference will cause a 400 or silently shift to population semantics on some servers
The measure evaluation period must align with the measure's defined improvement notation and measurement period extension; mismatched dates produce a technically valid but clinically meaningless MeasureReport
Some clinical reasoning engines (e.g., cqf-ruler) require pre-loaded CQL Library dependencies referenced by the Measure before $evaluate-measure will succeed; missing Library content returns a vague 500
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