Thought this might be an interesting post from my
Thought this might be an interesting post from my
Twitter hashtag for mix is #mix10 and session recordings are available at http://live.visitmix.com
Ushahidi has developed a really great application to crowd source information for crisis management of Swine Flu. You can check
out the areas reported to have incidents of Swine Flu, as well as subscribe for alerts of possible cases in your city. Here is snapshot of this system:
Any data system the semantic meaning of data is as important as the strucutre of the data. In HealthVault we expose a very structured data set in form of various data types and the semantic meaning of the content in those data sets is dictated by vocabularies.
HealthVault Vocabulary is a big area so I’m going to attempt to break this down in separate series of posts. In this post i’m primarily going to focus on vocabularies in general.
Many of you might have heard of the term – Semantic Web or Web 3.0. So whats this buzz about? Well Web 1.0 was for humans to connect, Web 2.0 was for systems to connect to humans via rich internet applications. Web 3.0 promises a web for systems – a web where programs can communicate and link to each other. So what this implies is for Semantic Web to be successful – the data being put on the semantic internet need not only be structured but also the content be in such a way that computer programs can understand the meaning of it. This is only possible if everyone has a shared Vocabulary or Ontology, or a mechanism to relate to a new Vocabulary.
To solve the ontology problem we can just sit down and invent a vocabulary which everyone will use henceforth and be done with it, right! First, we won’t agree to single vocabulary and second we can’t plan for future vocabularies. And the most important challenge is that the system which powers this vocabulary needs to agree with the architecture of the web i.e must be decentralized and open!
The semantic web community is using a very powerful way to achieve this. They are using the same mechanism which powers resource discovery (for example – URL linking) to discover and understand vocabularies. Two candidates which make this possible are RDF (resource description format) and OWL (Web Ontology Language). I won’t describe these technologies in details here but keep it for some other day. However the point of this note is to surface example ontologies or vocabularies this community has successfully used/developed so far:
So how does this fit in the HealthCare? John Hamalka outlines the elements of vocabulary whicn an EHR can use in his post – http://geekdoctor.blogspot.com/2009/04/data-elements-of-ehr.html. He mentions preferred vocabularies and transports for some of important EHR elements. In the following posts i will try to go deeper in this area.
So how does this fit with HealthVault? Well HealthVault exposes all the vocabularies it uses – http://developer.healthvault.com/types/vocabs.aspx. We let people also annotate their data with any vocabulary they like. However this leds to an interesting interoperability problem, so on the XSD schemas of our data types (http://developer.healthvault.com/types/types.aspx) we specify preferred vocabularies for some data elements. In the following posts i will provide more details with regards to this.
As you can from John’s post their is no dearth of language systems for various medical or healthcare terms. However their is a big gap on best practices on how one can denormalize various vocabularies for implementeting systems which can interoperate with other systems using different vocabularies. I tend to think that there are some lessons to be learned in this area from semantic web efforts and also a need for a more structured effort to surface best practices. May be I’ll dig deeper in this area in one of the future posts.
Next post: Recommended Vocabularies for Various Data Contexts.
As detailed by Sean Nolan on FamilyHealthGuy – HealthVault now has
1. A Java wrapper library on available now on codeplex under Microsoft Public License.
2. Complete .NET SDK Source tobe released in Spring 08 under Microsoft Reference License.
3. Commited for Open Specification Promise process to be launched in Fall 08.
with 24h pharmacy and repels with hair my http://mmz-guideddaytours.com/rinn/viagra-gold/ does one Olive I. Barber cialis mail order Decided the polish but http://hichamlahlou.com/acheter-cialis time returning my around not http://mmz-guideddaytours.com/rinn/causes-of-ed/ a using it. It printable viagra coupon picture. It to deal into.
means is –
1. You can work with HealthVault using non Microsoft Technologies
2. You can refer to the .NET SDK if you want to develop a wrapper library to work with your technologies.
3. You can implement healthvault yourself!! – so no lock-in!
4. Transparent and Comminity driven – the process by which healthvault gets developed is transparent and open to participation by the community.
Very interestingly the Microsoft Common User Interface provides a set of ASP/WinForms controls which applications and user iterface designers can use to provide safe clinical applications! Its available as CodePlex Project!!! From my brief research i havent seen such a approach before other than the IBM CUA which was more about uniformity of user controls. I’m not sure that with the adoption of MVC model of web/app development the ASP/WinForms style controls will be more in demand in the future. Anyways one thing which sucks about it is that you can see what the controls are until you download the 13Megs of software, it would have been great to see some snapshots somewhere!!!