News for hackers. Stuff that matters.
Re:Walgreens Developer APIs by rnovak on Friday August 22, 2014 @07:10PM (#8214357)
As both a developer and someone who takes medicine, I'd just like to say: NO

I shred my Prescription labels, and now they're basically going to be opened up to the world for some stupid developer to expose because he/she didn't think it through?

Apple's location data was secure until 3rd party apps leaked it. No thanks. The convenience is not worth the loss in security/privacy

Re:Walgreens Developer APIs by ZoF on Friday August 22, 2014 @09:45PM (#8214735)
Read the docs.

All they give out is the store location/pickup time for an RX# request, no identification info, no medication info.

Re:Walgreens Developer APIs by rnovak on Sunday August 24, 2014 @05:19PM (#8219714)
If it's implemented correctly. How many top tech companies implement their API's perfectly the first, second, or even hundredth time around? Walgreens isn't a tech company.

As the patient, the person who's information is being stored, I should have the ONLY say so over what happens to that information EVER, and if they don't get that, I have no problem taking my business elsewhere, which it looks like I'll have to do.

Re:Walgreens Developer APIs by joerago on Sunday August 24, 2014 @05:59PM (#8219806)
To clarify, our Rx Refill API is "inbound" in nature only. If the patient initiates a refill, one can be completed. This is not an API around "outbound" information from Walgreens systems. Hope that helps to clarify.