Surescripts API

[elixiraddons]

Per the documentation of the Challenge guidelines, Screening locations will be provided from two sources:

1. A directory of participating pharmacies will be provided by Surescripts. This directory will be accessible to developers via an API, and will remain available for free to the winning app throughout the campaign period. 

This directory will be updated frequently, and the developer should accommodate these updates by accessing the directory in real time or caching periodically.

Currently the script ONLY provides locations in the state of MN. Will this change? Or, this is all we get except the winners who will be given access to the production site?

2.A directory of participating healthcare providers may be provided by HHS and/or participating launch cities (see below). 

This Community Healthcare Provider directory will be provided as a flat file, which the developers will receive from participating cities and/or HHS. 

These files may be updated periodically by HHS.  HHS and Health 2.0 will follow-up with developers that register on the website about any updates or additions to this directory. 

Appendix C, Table 2.2.2.1 shows the format of the files that will be sent to the winner.

Is there any way to get this flat file? Or, will this also be ONLY provided to the winner?

Providing real values is essential for testing and building good apps and I suggest the co-ordinators do the necessary to help developer community which will enable better participation.

[Joseph Athman]

I am a developer at Surescripts and I can help answer question #1 for you.  The data returned via the Surescripts API is meant to just simulate the format of the data that will be returned and is not intended to portray actual pharmacies that may or may not participate in the final campaign.  Since we are still working with pharmacies to participate in the final product we don't have a way of giving anyone what the final data will actual look like.

Might I suggest instead of making an actual call to the Surescripts API, it may work better for you to simply mock the call out and provide your own set of JSON data to use with your interface?  This way you can model any scenario you'd like without being dependent on the Surescripts data.  

Basically I would use the Surescripts API in testing to just verify that your application can functionally interact with our API, but not use it as the basis for your UI testing.  Hope this helps.

Joe

[Eric Wu]

Hi Joe,

Thanks for your note.

Do you anticipate that Surescripts will be fully functional sometime before October 31st so that we may conduct more rigorous user testing, or should we just phase Surescripts out of our user testing plans completely?

Warm regards,
Eric A. Wu

--
You received this message because you are subscribed to the Google Groups "Million Hearts Challenge" group.
To unsubscribe from this group, send email to million-hearts-cha...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Joseph Athman]

The data will stay the same for the entire testing period.  Only the challenge winners will have access to non-test data.  If you need additional data to do your UI testing then you should plan to mock out the data returned by the API to fit your needs.

Joe

To unsubscribe from this group, send email to million-hearts-challenge+unsub...@googlegroups.com.