Votereport.in uses this technology to report voting frauds in the ongoing general elections in India. A minor plug – Voterport.in is a sister site of WiseVoter.org, which I helped establish.

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:

• FOAF – http://en.wikipedia.org/wiki/FOAF_(software) : This ontology describes a persons social network
• FAO – http://en.wikipedia.org/wiki/Geopolitical_ontology: This ontology describes a geopolitical unit.

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.

Related articles by Zemanta

• Semantic Web Glossary (semanticalley.com)
• Semantic web – The foundations (digital-constructions.com)
• A conference comes of age: a review of the 7th International Semantic Web Conference (ISWC2008) (blogs.talis.com)

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.

What this 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.