POST /Measure/{id}/$evaluate-measure with reportType=population (or reportType=summary depending on server terminology), periodStart, and periodEnd; omit the subject parameter to evaluate across all patients the server can access
Receive a MeasureReport of type 'summary'; inspect group[].population[] for aggregate counts (initial-population, denominator, numerator, exclusions) across the full cohort
Review group[].measureScore for the population-level performance rate as a decimal or Quantity
Include supplementalData definitions in the Measure if stratification by demographics (age, sex, race/ethnicity) is required; parse MeasureReport.group[].stratifier[] for stratified counts
Submit the summary MeasureReport to the receiving organization (payer, registry) using $submit-data or direct REST POST to the receiver's MeasureReport endpoint
Known gotchas
Population-level $evaluate-measure runs across all accessible patients and is computationally expensive; most servers restrict this to system-level tokens with broad patient access and may impose time limits
The reportType parameter value varies across DEQM IG versions and server implementations (population vs. summary vs. data-collection); consult the server's OperationDefinition for the exact supported values
Supplemental data and stratifiers in the MeasureReport reflect only patients included in the initial population; do not interpret stratifier counts as representative of the full server patient population
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