Generate and submit a QRDA Category III aggregate eCQM report for CMS MIPS quality reporting
domain: healthcare · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Confirm QRDA III is an accepted submission method for the current MIPS performance year and obtain the CMS-published QRDA III Implementation Guide, schematron, and sample files for that specific year, since requirements are updated annually.
Aggregate patient-level quality data across the MIPS-eligible population into a single QRDA III document per eCQM/Promoting Interoperability measure/Improvement Activity, unlike QRDA I which is one file per patient.
Populate required QRDA III header elements (reporting program, performance period, submitter and provider identifiers) per the current-year CMS IG.
Validate the generated XML against the current-year CMS-published schematron before submission to catch structural and value-set errors.
Submit via the CMS Quality Payment Program submission channel appropriate to your reporting entity, noting CMS also supports other collection types (e.g., QPP API/JSON, Part B claims, CMS Web Interface for certain APM entities).
Reconcile submitted numerator/denominator counts against source EHR data before the deadline, since QRDA III files do not always need to include pre-computed performance rates.
Known gotchas
QRDA III (aggregate, one file per provider/TIN) is easily confused with QRDA I (patient-level, one file per patient per measure) used for hospital IQR — they are structurally different documents for different programs.
The CMS QRDA III IG, value sets, and program name codes change every performance year (recent revisions removed retired program codes) — reusing a prior year's template without checking the current IG risks schematron failures.
Passing schematron validation does not guarantee CMS scoring acceptance — mismatches between your EHR's CQL execution and the CMS-published eCQM specification for that performance year are a separate common failure mode.
Give your agent this knowledge — and 15,500+ 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?