Qualified Clinical Data Registry (QCDR): What it is and How it Supports MIPS Reporting
August 24, 2026
10 min. read
A qualified clinical data registry, commonly called a QCDR, gives healthcare organizations a structured way to collect clinical data, assess performance, and submit information to the Centers for Medicare & Medicaid Services (CMS). Unlike a general reporting vendor, a QCDR may offer specialty-specific quality measures that reflect the conditions, procedures, and outcomes most relevant to its participants.
For clinicians eligible for the Merit-based Incentive Payment System (MIPS), physician group practices, virtual groups, and some Accountable Care Organizations (ACOs), selecting the right reporting pathway can affect administrative workload, performance visibility, and future Medicare payment adjustments. A QCDR can serve as both a CMS submission intermediary and a source of clinical benchmarking data.
What is a qualified clinical data registry?
CMS defines a QCDR as a CMS-approved entity with expertise in medicine and quality-measure development that collects clinical data on behalf of MIPS-eligible clinicians. The data may be used for patient and disease tracking, quality measurement, and improvement in care delivery.1
QCDRs are often operated by specialty societies, professional associations, regional collaboratives, health systems, or organizations with experience managing clinical registries. CMS evaluates applicants through a qualification process, and approved entities are listed in the Quality Payment Program resource library for each performance year.2
A qualified clinical data registry may perform several functions:
Collect data from electronic health records, practice management systems, claims, or other approved sources
Calculate performance rates for applicable quality measures
Give participants reports or dashboards showing their performance
Compare results with registry participants or other benchmarks
Identify gaps in documentation or measure performance
Submit MIPS data to CMS on behalf of participating clinicians or organizations
Beginning with the 2025 performance year, QCDRs and qualified registries became the only third-party intermediaries approved to submit MIPS data on behalf of clinicians, groups, Alternative Payment Model (APM) entities, and Medicare Shared Savings Program participants.3
Participation in a QCDR does not automatically satisfy every MIPS requirement. Organizations remain responsible for confirming eligibility, selecting the correct reporting option, reviewing submitted information, and maintaining supporting records.
QCDR vs. qualified registry: what is the difference?
A qualified registry and a QCDR can both collect MIPS data and submit it to CMS. The primary distinction involves the measures they are permitted to offer.
A qualified registry generally submits MIPS quality measures established within the Quality Payment Program. A QCDR can submit those measures and may also offer CMS-approved QCDR measures. These additional measures are often designed around a specialty, procedure, condition, patient population, or clinical outcome that is not fully represented in the standard MIPS measure inventory.4
For example, a gastroenterology QCDR might track colonoscopy completion, adenoma detection, withdrawal time, or follow-up recommendations. A surgical registry might measure postoperative complications, procedure-specific outcomes, or adherence to specialty guidelines.
This matters when standard MIPS measures do not closely match the services an organization provides. A more clinically aligned measure set can capture aspects of care that broader measures miss.
The distinction is still important even when both options can handle CMS submission:
Qualified registry | Qualified clinical data registry |
Collects and submits approved MIPS data | Collects and submits approved MIPS data |
Primarily reports standard MIPS measures | May report MIPS measures and QCDR measures |
May serve a broad range of specialties | Often focuses on a specialty or clinical area |
Commonly centered on reporting support | May combine reporting, benchmarking, and clinical improvement tools |
CMS approves QCDR measures individually. A measure available through one QCDR may not be offered by another, and measure availability can change between performance years. Organizations should review the current-year measure specifications rather than relying on a prior reporting plan.
How a QCDR supports MIPS reporting
The Merit-based Incentive Payment System is one participation track within the CMS Quality Payment Program. Under MIPS, CMS scores performance data and applies resulting payment adjustments to Medicare Part B reimbursements in a later payment year.5
A QCDR can help with several parts of that process.
Data aggregation
A group may need to combine information from several clinicians, facilities, or EHR instances. A QCDR may accept data through direct integrations, file uploads, manual abstraction tools, or other methods supported by the registry.
Before enrollment, organizations should verify which data sources the QCDR accepts. CMS allows third-party intermediaries to submit data through approved file formats or the Quality Payment Program Submission API, but third parties cannot manually type performance data into the CMS submission system.6
Measure selection and calculation
Measure selection can affect both reporting feasibility and scoring potential. A QCDR may help identify measures that match the organization's patient population, available data, reporting option, and clinical focus.
The organization should still review:
Measure eligibility and denominator criteria
Data-completeness requirements
Case minimums
Benchmark availability
Measure type, such as process, outcome, or patient-reported outcome
Applicable specialty or clinical setting
Collection type and reporting pathway
Choosing a measure solely because it appears easy to document can produce a weak reporting strategy. A better approach is to compare clinical relevance, data availability, scoring potential, and the organization's ability to improve performance during the year.
Performance monitoring
Some QCDRs provide reports throughout the performance period rather than waiting until submission. These reports may show current performance rates, missing data, measure-level trends, or comparisons with other registry participants.
Earlier visibility gives a practice time to investigate documentation problems. For instance, a low performance rate may reflect missed care, but it could also result from incomplete coding, mapping errors, missing exclusions, or data that did not transfer correctly.
CMS submission
After data collection and validation, the QCDR can submit the selected information to CMS. Most MIPS data is submitted during the first quarter following the performance year. For example, data for the 2025 performance year was generally submitted from January 2 through March 31, 2026.7
The submitting organization should request a final submission report, verify the clinicians and measures included, and retain documentation supporting the reported data. A contract with a registry does not shift accountability for inaccurate or incomplete submissions away from the participating organization.
How to choose a qualified clinical data registry
The current CMS list is the starting point for identifying approved QCDRs. Qualification applies to a particular performance year, so an organization should confirm that the registry is approved for the year being reported.2
After verifying CMS status, consider the following factors.
Measure alignment
Review the complete measure catalog and determine how many measures apply to the organization's actual patient population and services. Ask which measures have benchmarks and which can be used under traditional MIPS, a MIPS Value Pathway, or another applicable reporting option.
An extensive measure list has limited value when only a small portion fits the organization's care model.
EHR and workflow compatibility
Ask how information moves from the clinical record into the QCDR. A direct integration may reduce manual work, but the organization should still learn which fields are mapped, how often data is transferred, and how errors are corrected.
Questions to ask include:
Does the QCDR connect with the current EHR?
Is data sent automatically or uploaded periodically?
Are supplemental files required?
How are patient matching and clinician attribution handled?
Can users review rejected or incomplete records?
Who is responsible for correcting mapping problems?
Reporting levels
Confirm that the registry supports the intended reporting level. Needs may differ for an individual clinician, a group reporting under one tax identification number (TIN), a virtual group, or an APM entity.
ACOs and larger physician organizations should also assess how the QCDR handles multiple TINs, clinician rosters, organizational hierarchies, and data from several clinical systems.
Feedback and benchmarking
A QCDR is more useful when its reporting tools support ongoing review. Look for measure-level dashboards, drill-down capabilities, peer comparisons, patient lists, and downloadable reports.
Benchmarking should be interpreted carefully. Differences in case mix, specialty, patient complexity, and data-collection practices can affect comparisons between organizations.
Fees and support
Pricing may include enrollment fees, clinician fees, integration charges, data-abstraction costs, or submission fees. Request a written description of what is included.
Support matters as well. Confirm who can answer measure questions, troubleshoot data issues, review submission readiness, and assist when CMS feedback indicates a problem.
Practical example: using a QCDR across a physician group
Consider a multispecialty physician group preparing for MIPS reporting. Its clinicians document care in two EHR platforms, and several standard MIPS quality measures do not closely match the procedures performed by its largest specialty division.
The organization selects a CMS-approved QCDR that supports both EHR systems and offers specialty-specific QCDR measures. At the beginning of the performance year, the group maps the required data fields, validates clinician identifiers, and confirms which measures have applicable benchmarks.
During the year, the QCDR dashboard shows that one measure has a lower-than-expected performance rate. A record-level review finds that completed services are being documented in a free-text field rather than the structured field used in the measure calculation.
The group updates its documentation workflow and trains the affected teams. Subsequent data feeds show a higher documented performance rate, giving the organization more confidence that its registry results match the care delivered.
At the end of the performance period, the group reviews its final clinician roster, measure results, data completeness, and submission confirmation. Here, the registry did more than transmit data—it surfaced a documentation problem in time to fix it before the CMS submission deadline.
A QCDR can connect MIPS reporting with specialty-specific measurement and ongoing performance review, but its value depends on measure fit, data quality, system compatibility, and how well the organization acts on what the data shows.
Before enrolling, review the current CMS-approved QCDR list, compare measure specifications, confirm reporting-level support, and document each party's responsibilities. The right registry should give you a clear path from data collection through submission, plus useful insight into performance along the way.
Where PRO data connects to QCDR reporting
For organizations already collecting patient-reported outcomes (PROs) on Medbridge, QCDR submission for MIPS is a built-in feature with our partnership with Patient360. PRO collection lives in the same HEP, Pathways, and RTM workflows clinicians already use, so outcomes captured during normal care can also support MIPS submission through a qualified clinical data registry without adding a parallel data-collection step for staff.
Medbridge supports the QCDR submission piece; the choice of reporting pathway and measures remains the organization's own MIPS strategy.
Learn more about Medbridge's patient-reported outcomes tool.
References
Centers for Medicare & Medicaid Services. "Quality: Traditional MIPS Requirements."
https://qpp.cms.gov/reporting-requirements/ways-to-report/traditional-mips/qualityCenters for Medicare & Medicaid Services. "Quality Payment Program Resource Library."
https://qpp.cms.gov/resources/resource-libraryCenters for Medicare & Medicaid Services. "Third Party Intermediaries."
https://qpp.cms.gov/data-management/third-partiesCenters for Medicare & Medicaid Services. "A Brief Overview of Qualified Clinical Data Registries."
https://www.cms.gov/medicare/quality-initiatives-patient-assessment-instruments/mms/downloads/a-brief-overview-of-qualified-clinical-data-registries.pdfCenters for Medicare & Medicaid Services. "About MIPS."
https://qpp.cms.gov/get-started/what-is-mips/about-mipsCenters for Medicare & Medicaid Services. "Submitting Data."
https://qpp.cms.gov/data-management/submitting-dataCenters for Medicare & Medicaid Services. "Collect and Submit Data."
https://qpp.cms.gov/get-started/what-is-mips/data-collection-and-submission
Meet the Authors
