Convert your FHIR JSON -> XML and back here. The CDA Book is sometimes listed for Kindle here and it is also SHIPPING from Amazon! See here for Errata.

Monday, March 25, 2013


Have you been annoyed by the recent proliferation of web-site specific applications that you can now download for your Android or IOS device?  It seems as if everywhere I go, I have to stop and tell the website I'm directed too to skip the App download.

No.  I do not want your site-specific application to put your website in front of me every day.  That's why I use aggregator Apps and/or RSS feeds.

Today I was appalled to see yet another example of this: Now being pushed on physicians.  For a fee, it seems, some organization (whom I won't even bother linking to) will allow you to create a one or four page referral "App" from a template, where one page is a referral form, and the others could be any content you want to display.

Really?  Really.

In the HTML world, we used to call those things: A web-site in-a-can, and the end result was as bland and boring as most canned vegetables.

In fact, anyone considering having an App created like this, pay attention.  Ask yourselves, why would someone use your "App".  What value does it bring them, other than being able to refer patients to you?  Do you have really great content?  Some cool tools?  Something else?

If the value proposition for the the App just leads towards you, the App supplier, it's not an App that your customers will consider worth having.

And if it looks like it came from a can, I know what can they'll put it in.

1 comment:

  1. Buying and downloading an app requires one to evaluate a product in context of all my current apps and preferences, and consider future ones as well. That is a complex analysis that many people are unable to do well, if at all. The results are often kinda mediocre.

    What I want is an app selection questionnaire that will give me a choice of interoperable widgets based on what I do in my life. Each widget could then be further customized and fine-tuned to my preferences. I'd expect to pay a subscription fee for some things.

    Of course what I want would require IT developers to look outside of their knowledge domains and think like general consumers, i.e., people who are focused on what they need/want. My cynicism is fairly high about the possibilities.