NHS API - Final calling!

[Will Tinsdeall]

Hi,

Thanks for all the help so far. It looks like I'll be heading down to the DoH this Thursday, so I just want to make sure I am covering all of the main points. Looking through the feedback (and adding some of my own in) I get to this:

Current suggestions:

• Site specific hash to protect API access better, and also allow AJAX requests (rather than username and password as GET params)
• JSON encoding as well as XML
• Hospital performance data
• 2.0 interactive approach? - Commenting/Rating feature for care facilities?
• Better procedure for getting API user/pass (online rather than paper)
• Link in with hmg.gov.uk/data - SPARQL
• "urls should be 'cool' i.e. they don't change. If you have things like .asp in the url then when / if you change from using asp pages your urls will change too and break applications."
• SOAP as well as REST

Does anyone else have anything they can add to this list? I have re-attached the API documentation.

Will

--------

Check out my portfolio and online computing guides at http://www.iexpand.co.uk

Follow The Engage Project News Feed on Twitter '@EngageProject'