Call for Participation: CMS Web Interface (GPRO) API

[Developer Group for QPP APIs]

We are seeking participants for user research in support of the API we are building for the CMS Web Interface (formerly known as GPRO). Note that this API serves a different purpose from the one that is currently available for testing in the public sandbox and Developer Preview.

To participate, please read the information below, then reply to this message.

What is the purpose of this research?

• We are conducting this research to understand the market needs for a CMS Web Interface API and guide decisions about feature set and implementation timeline.

Who can participate?

• Organizations that have used the Web Interface in the past to report on behalf of a large group or ACO
• Organizations with a development team that would be a likely user of an API

What is the time commitment?

• Research will be conducted over the next 2-3 weeks
• 30 minutes for an initial screening call to talk about your anticipated use case
• 60 minute facilitated research session
  
• 60 minute follow-up session (if necessary)

Please reply to this message to indicate your interest in participating in the user research.

[Michael Murdock]

I would like to participate. I am a senior developer for a EHR and current waiting for our API key so we can the developer preview. I have worked with other API and have implemented them into our product in the past. So look forward to any insight I can provide.

Thanks

Michael Murdock

AllMeds Inc

862-816-4661

[jeffi.ming...@gmail.com]

I'd like participate in user research for a CMS Web Interface API.

Jeff Iasilli

Product Manager

Mingle Analytics

On Tuesday, September 5, 2017 at 10:56:49 AM UTC-4, Developer Group for QPP APIs wrote:

[Aditya Deshpande - Head Product - FIGmd]

FIGmd would like to participate.

[Jonathan Sullivan]

Great, I will ask the research team to reach out to you.

[LewChaney]

I just joined this group today and I'm unsure of the normal participation requirements. I can see from the history of posts in this group that most posts are related to the public sandbox URL. In a nut-shell, I have been successfully posting to the public sandbox URL ( https://qpp-submissions-sandbox.navapbc.com ) for a couple of months now. As of yesterday I have received a "QPP-APIToken" to test posting to the developer preview URL ( https://qpp.cms.gov/api ). I am using the .Net HttpWebRequest class for the communication attempts whether in the public sandbox or the developer preview with the APIToken. I seem to be gaining a successful authorization with the APIToken by adding httpWebRequest.Headers["Authorization"] = "Bearer MYAPITOKEN" to by Headers collection. 

So here is my problem when I attempt to POST to the developer preview URL endpoint ( https://qpp.cms.gov/api/submissions ) in hopes of creating a new submission. 

If I don't add the header authorization with the APIToken I get a "The remote server returned an error: (401) Unauthorized." exception as I would expect. 

If I do add the header authorization with the APIToken I get a "The remote server returned an error: (404) Not Found." exception. I cannot find any combination after many tweaking tests of my HttpWebRequest object to get beyond the "The remote server returned an error: (404) Not Found." exception on the developer preview server.

On the public sandbox server, all of my (POST/GET/etc...) attempts work without any exceptions at all.

Any suggestions will be most appreciated...

Regards,

Lew Chaney

[Jonathan Sullivan]

Hi Lew, this thread is related to a different topic than the one you raise below. The short answer is that you cannot use the /submissions endpoint to create a submission. Instead, use the measurementSet endpoint to create a submission object. Please see this thread for details: https://groups.google.com/forum/#!topic/qpp-apis/m0h-Wvir9HA.