iMedicalApps.com published an article detailing Apple’s ‘new’ development policy which will reject any app that includes dosing information for a medicine. Normally I wouldn’t comment on an article from another site in this much depth, but given the way headlines suddenly become ‘insights’ in this business, I thought it would be helpful to clarify a few things.
The article starts with an ominous headline “Apple is now rejecting new medical apps that include drug dosages.” Apple is not doing this across the board. One or two devs got rejected. Which by the way, happens all the time, for all kinds of reasons. The article goes on from there, “It appears that a number of developers have struggled recently to get medical applications into the App Store.” It doesn’t say how many developers or how wide spread the problem is. And, without any kind of context as to what the app was, or any insight into it’s functionality, it’s impossible to draw any conclusion as to why it was rejected. Given the amount of apps currently in the app store that reference dosing information (mostly by manufacturers) I seriously doubt this is a widespread issue.
A simple reading of the actual rejection sent by Apple illustrates where the developer(s?) went wrong.
“We found that the Seller and/or Artist names associated with your app do not reflect the name of the manufacturer of the medicine referenced in your app or its metadata, as required by the iOS Developer Program License Agreement.
“You” and “Your” means and refers to the person(s) or legal entity (whether the company, organization, educational institution, or governmental agency, instrumentality, or department) using the Apple Software or otherwise exercising rights under this Agreement. For the sake of clarity, You may authorize contractors to develop Applications on Your behalf, but any such Applications must be submitted under Your developer account.
We can only accept medical dosage information submitted by the medicine’s manufacturer.
If you have published these apps on behalf of a client, it would be appropriate for your client to enroll in the iOS Developer Program, then add you to their development team so you can develop an app for them to submit under their developer account.”
I actually see this as a good thing for users. First, the developer in the article clearly didn’t follow the metadata practices of Apple’s guidelines, which is a no-no. Apple has been very consistent on making sure apps are what they say they are and aren’t playing games with metadata to boost rankings. Already I’m suspicious of the developer(s?), since they seem to be unwilling to follow or correct this issue now that Apple has pointed out it’s a problem. Second, if you are publishing dosing information and aren’t doing it on behalf of the manufacturer, you may be publishing the wrong information. Since pharma has so many checks and balances on it’s content, Apple can be assured that anything with a manufacturer’s name on it would have the content verified for accuracy.
As part of gathering the info for the Mobile App Wiki, I spent quite a bit of time in the Android store. Let me tell you, it’s hard to know who’s published what. The requirements are very flimsy for publishing an Android app, and I couldn’t tell if an app was legit or not (see the Bob in IT example). To be clear, Apple is not asking for the content to be verified, but does have some controls to ensure the veracity of content. Given the importance Apple has placed on medical content and audiences, this seems like a logical restriction to ensure quality for it’s users. So if you are developing an app for a pharma client, or doing it in house, you should be fine.