Changes to the Submissions API for PY 2019 - What is currently included in the Developer Preview Environment Aug 15th, 2019

[Sarah White]

The Quality Payment Program (QPP) Developer Preview environment is now open for testing QPP submissions for performance year 2019. 

As this is a testing environment it is updated when new functionality is released or changes are made to existing functionality. We will provide more information about what is included in future releases in follow up Google Group posts. 

Changes to the QPP Submissions API for PY 2019 that are in the Developer Preview environment as of August 15, 2019:

1. Removing QPP XML support - Beginning with the submission period for PY 2019, the QPP Submissions API will no longer accept QPP XML. Requests should be sent in QPP JSON. If you are submitting a QRDA III XML via direct API submission, please use the converter endpoint to convert to QPP JSON as has been the standard practice for the Submissions API. 
2. CEHRT ID for PI measurement sets - Beginning with the 2019 performance period, MIPS eligible clinicians must use EHR technology certified to the 2015 Edition certification criteria to report the 2019 Promoting Interoperability Objectives and Measures. This CEHRT ID must be submitted to QPP as a part of the submitted PI category measurement set data. It will be submitted on the measurement set level. 
3. New field "observationInstances" for nonproportion metric type - We updated the nonproportion metricType to include a new field called “observationInstances”. Observation Instances are defined as the number of denominator eligible instances that are used as input in the calculation to derive the numerator (i.e. average, ratio). We will provide a separate post detailing how this relates to reporting nonproportion measures. 

Changes to the QPP Submissions API for PY 2019 that are not complete or available in the Developer Preview environment as of August 15, 2019:

1. Deprecating submitting eCQMs and MIPS CQMs in the same quality measurement set -  Starting with PY 2019, you will need to submit these as separate measurement sets. This requires making TWO POST /measurement-sets requests with different submissionMethods if you are calling the API directly or uploading a file as a registry user on qpp.cms.gov. If providing a file for your client to upload themselves, you can include TWO quality measurement sets within ONE POST /submission (the format for sending all three categories at once). At this time we have removed "registry" as a valid submission method for measures that are eCQM-only. Error messaging will be added in a later release. We will provide more information about how to submit these in a separate follow up post.
2. Low Volume Threshold Opt In process - This is still under development and is not live in the Developer Preview yet. We will provide more information about how this will be handled via direct API calls for those that submit directly to the API in a separate follow up post. You will be able to test this functionality using the new Test Data Services. Details on how to test that will be provided once the functionality is released in Developer Preview.
3. Score endpoints are currently not available - The POST /score-preview and GET /score endpoints are not currently available in the Developer Preview environment. We are making changes to the score response based on the new PY 2019 aggregate measure scoring rule. We will turn these endpoints back on when that functionality is complete and documentation is made public.

[abhijeet mahajan]

Hi Sarah,

For the highlighted sentence in the email below (assuming that there will be two POST requests one for MIPS CQM and one for eCQM) will it create two submissions or just one ?

And also, how the scores will be returned, separately for each submission or collective for that TIN-NPI Combination like previous years ?

Thanks,

Abhijeet

[Sarah White]

Hi Abhijeet,

It will be two measurement sets for one submission object. Scores are based off the entire submission object. In Year 3 measures will be aggregated across measurement sets to choose the highest performing 6 measures. This is why those score endpoints are not currently related. We're still working on the changes to the API response for the new scoring rules.

[Brett Thom]

Hello,

Do we know when the score endpoints will be available or designed?

Thanks

Brett

[Brad Buchanan]

Any estimate on when the /score-preview and score endpoints will be available in the Developer Preview environment?

Thanks,

Brad B

On Thursday, August 15, 2019 at 6:26:26 PM UTC-4, Sarah White wrote:

[Allison Johnson]

Hi Brad,

Thanks for your question. We expect to have those endpoints up by the end of this month or early November. We'll post an update here in the group as we get closer to having a firm date. 

Thanks!

Allison

[Allison Johnson]

Hi Brett,

Thanks for your question. We expect to have those endpoints up by the end of this month or early November. We'll post an update here in the group as we get closer to having a firm date. 

Thanks!

Allison

[Nick Mamich]

Hi Sarah:

During the 10/19/2019 QCDR call for 'tech talk', Chris Szeluga ( Product Team)   mentioned you posted a message requested feedback for research on NPI and eligibility  verification via API .

Is there a message from you that would start the thread on this topic?

Thanks,

nick

[Sarah White]

Hi Nick,

I think this is the thread you're looking for - https://groups.google.com/d/msg/qpp-apis/KCHGp2PVSHU/4y1xfjApDgAJ

--
You received this message because you are subscribed to the Google Groups "Developer Group for QPP APIs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to qpp-apis+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/qpp-apis/6d5150f7-96c1-45f1-81e8-e51c2d1afa98%40googlegroups.com.

[akhtar nawaz]

I am new and working on QPP  Api. when I send a request on https://qpp.cms.gov/api/eligibility/graphql with post method it show error. 

Access to XMLHttpRequest at 'https://qpp.cms.gov/api/eligibility/graphql' from origin 'http://52.9.235.242' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: It does not have HTTP ok status.

I am new can you guide me .

Thanks

[Priti Singh]

Hi,

We are a Qualified Registry and will be doing MIPS submissions on behalf of our clients using the QPP file upload via the QPP portal. Is there any change to the file format other than the addition of CEHRT ID to the for 2019. Please advise.

Regards,

Priti Singh

On Thursday, August 15, 2019 at 6:26:26 PM UTC-4, Sarah White wrote:

[Priti Singh]

[prit...@gmail.com]

Hi,

Can you please elaborate on the below? Is this applicable to submitting via file upload on the QPP portal?

New field "observationInstances" for nonproportion metric type - We updated the nonproportion metricType to include a new field called “observationInstances”. Observation Instances are defined as the number of denominator eligible instances that are used as input in the calculation to derive the numerator (i.e. average, ratio). We will provide a separate post detailing how this relates to reporting nonproportion measures    

Thanks,

Priti

--
You received this message because you are subscribed to a topic in the Google Groups "Developer Group for QPP APIs" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/qpp-apis/5yO2CFdvW8k/unsubscribe.
To unsubscribe from this group and all its topics, send an email to qpp-apis+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/qpp-apis/ab593727-09b3-4e12-9d1b-dec7f0643d67%40googlegroups.com.

[Sarah White]

Hi Priti, 

The summary of Submissions API changes are here: https://groups.google.com/forum/#!topic/qpp-apis/OsAyX660CC0 This includes a link to another post on how to submit the new field for nonproportion measures. Anything that changes the Submissions API changes the file format for how you submit to the UI too, so for example, the UI will also no longer take QPP XML files. We accept QPP JSON and QRDA III XML.

You received this message because you are subscribed to the Google Groups "Developer Group for QPP APIs" group.

To unsubscribe from this group and stop receiving emails from it, send an email to qpp-apis+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/qpp-apis/CAH6cDrjD7Yf_H2ZwiZOTPH1O9JNuZ3%2B3BLU%3D53nNvJo3b5afXw%40mail.gmail.com.