[QRDA-1055] Clarification on QRDA APP Identifier and PI Submissions Created: 03/17/22 Updated: 03/25/22 Resolved: 03/25/22 |
|
| Status: | Resolved |
| Project: | QRDA Issue Tracker |
| Component/s: | QRDA-III Standard, Reporting/Attestation |
| Type: | Question/Guidance | Priority: | Moderate |
| Reporter: | Brian Ray | Assignee: | Yan Heras |
| Resolution: | Resolved | Votes: | 0 |
| Labels: | None | ||
| Description |
|
The QPP portal for submission of RY 2021 data appears to be requiring the APP identifier for ACO participants that are only logging in to submit PI data. However, per the QPP website: "Reminder: If your APM Entity is reporting your quality and improvement activities data, you will still need to submit your Promoting Interoperability data at the individual or group level for traditional MIPS." Which would seem to imply organizations in this bucket should still submit PI via QRDA III using the MIPS individual or MIPS group identifier. Can you clarify whether entities that are solely submitting PI data should be using the APP identifier if they're submitting as part of an ACO? |
| Comments |
| Comment by Brian Ray [ 03/24/22 ] |
|
That answered my question - thanks! |
| Comment by QRDA-ICF [ 03/24/22 ] |
|
Hi bray, Does this solution answer your question? If you have no follow up questions, this ticket will be considered resolved and closed on Monday, March 28. Thank you. |
| Comment by Yan Heras [ 03/22/22 ] |
|
Hi bray, Here is the guidance from QPP: You can submit PI data either using MIPS individual or group or using APP individual or group. As long as there is submission data for PI, QPP will use it. QPP will take the highest scoring between program and reporting level for PI Roll Up Scoring. |
| Comment by Yan Heras [ 03/21/22 ] |
|
Thank you for your patience. We are awaiting guidance from the QPP team. |
| Comment by QRDA-ICF [ 03/18/22 ] |
|
Thank you for submitting a ticket to the QRDA JIRA Issue Tracker. Our experts are reviewing your ticket and will provide feedback as soon as possible. Thank you for your patience. |