advertisement
advertisement
advertisement

Walgreens Refill API Isn’t Very Interesting, But It Will Be

Written by Frank Hayes
February 6th, 2013

Chains are still inching toward making their mobile apps genuinely useful to customers, but at least they’re doing it in more technically useful ways. On Monday (Feb. 4), Walgreens (NYSE:WAG) announced a new application programming interface (API) that should make it easier for mobile app developers to deliver all sorts of prescription refill information to users, at least if Walgreens is willing to provide it.

Unfortunately, what this API currently does is pretty primitive: It accepts a prescription number and then reports back to the app that it has (or hasn’t) successfully requested a refill. Just the fact that there’s an API is a big step forward, because it means Walgreens can extend that API without breaking any apps that use it.

For example, using the API, Walgreens could cleanly add the ability for apps to get more useful information, such as: an estimated time the refill will be ready; the price; whether there’s a brand name that could be substituted if the pharmacy is out of the generic; or whether there’s another nearby store that could refill it sooner if the original store is currently out of the medication.

Those are all things the chain could easily provide in the future, and it doesn’t need an API to provide them. The advantage to an API is that the chain doesn’t have to commit to those features now. That not-especially-interesting architecture could make some much more interesting features available going forward, and with a minimum of extra effort on Walgreens’ end.

An API like this isn’t remotely a new idea—which is actually an advantage, because no drug chain should be risking the use of yet another untried technical architecture in the face of endless privacy and regulatory concerns. There’s already too much shakiness in the link between smartphones and corporate pharmacy systems.

And there’s a real risk for Walgreens in setting up an API. The chain is requiring developers to register with the chain before it can use the API, and the apps will have to pass authentication information to do even a simple refill via prescription number. But, at a certain point, it will become possible for third-party developers to create apps that do the same thing with similar APIs from Walgreens’ competitors, offering the prescription equivalent of a mobile wallet. For the moment, Walgreens is alone.

If a customer shows that list of prescriptions to a competing pharmacist to make sure there are no problematic drug interactions, might that pharmacy try to steal the customer for the prescription Walgreens currently fills? Maybe. On the other hand, it’s probably a lot safer for any customer who is making trips to multiple pharmacies to bargain hunt.

At the risk of sounding snide, we’re glad to see a drug chain’s app whose architecture has finally made it all the way to the 1990s. Now, we’re just waiting for the rest of the features to catch up.


advertisement

Comments are closed.

Newsletters

StorefrontBacktalk delivers the latest retail technology news & analysis. Join more than 60,000 retail IT leaders who subscribe to our free weekly email. Sign up today!
advertisement

Most Recent Comments

Why Did Gonzales Hackers Like European Cards So Much Better?

I am still unclear about the core point here-- why higher value of European cards. Supply and demand, yes, makes sense. But the fact that the cards were chip and pin (EMV) should make them less valuable because that demonstrably reduces the ability to use them fraudulently. Did the author mean that the chip and pin cards could be used in a country where EMV is not implemented--the US--and this mis-match make it easier to us them since the issuing banks may not have as robust anti-fraud controls as non-EMV banks because they assumed EMV would do the fraud prevention for them Read more...
Two possible reasons that I can think of and have seen in the past - 1) Cards issued by European banks when used online cross border don't usually support AVS checks. So, when a European card is used with a billing address that's in the US, an ecom merchant wouldn't necessarily know that the shipping zip code doesn't match the billing code. 2) Also, in offline chip countries the card determines whether or not a transaction is approved, not the issuer. In my experience, European issuers haven't developed the same checks on authorization requests as US issuers. So, these cards might be more valuable because they are more likely to get approved. Read more...
A smart card slot in terminals doesn't mean there is a reader or that the reader is activated. Then, activated reader or not, the U.S. processors don't have apps certified or ready to load into those terminals to accept and process smart card transactions just yet. Don't get your card(t) before the terminal (horse). Read more...
The marketplace does speak. More fraud capacity translates to higher value for the stolen data. Because nearly 100% of all US transactions are authorized online in real time, we have less fraud regardless of whether the card is Magstripe only or chip and PIn. Hence, $10 prices for US cards vs $25 for the European counterparts. Read more...
@David True. The European cards have both an EMV chip AND a mag stripe. Europeans may generally use the chip for their transactions, but the insecure stripe remains vulnerable to skimming, whether it be from a false front on an ATM or a dishonest waiter with a handheld skimmer. If their stripe is skimmed, the track data can still be cloned and used fraudulently in the United States. If European banks only detect fraud from 9-5 GMT, that might explain why American criminals prefer them over American bank issued cards, who have fraud detection in place 24x7. Read more...

StorefrontBacktalk
Our apologies. Due to legal and security copyright issues, we can't facilitate the printing of Premium Content. If you absolutely need a hard copy, please contact customer service.