Implement the Da Vinci DEQM (Data Exchange for Quality Measures) individual reporting workflow to submit a patient-level quality measure report from a provider to a payer or registry
domain: hl7.org/fhir/us/davinci-deqm · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Assemble a DEQM Individual MeasureReport Bundle containing the MeasureReport, the patient's clinical supporting resources (Observation, Encounter, Condition), and an Organization resource for the submitter
POST the Bundle to the receiver's FHIR server using the \$submit-data operation on the Measure endpoint: POST /Measure/{id}/\$submit-data
Include the measureReport parameter pointing to the MeasureReport and resource parameters for each supporting clinical resource in the Parameters wrapper
Verify the response is HTTP 200 with an empty body or OperationOutcome with severity information; handle 422 for validation failures
Confirm the MeasureReport status is complete and the measure URL in MeasureReport.measure matches the canonical Measure URL registered with the receiver
Known gotchas
DEQM defines two reporting paradigms — submit-data (push) and collect-data (pull); confirm the receiver supports $submit-data rather than expecting you to expose a $collect-data endpoint
Supporting resources in the $submit-data Parameters must include all resources referenced by the MeasureReport population criteria; missing references cause the receiver's validation to reject the submission
The MeasureReport.subject must reference a Patient resource included in the Bundle; using a logical reference without a matching Bundle entry causes reference resolution failures on the receiver side
Give your agent this knowledge — and 15,600+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?