« Using the discussion tools | Main | Content profiles »



Feed You can follow this conversation by subscribing to the comment feed for this post.

Cindy Throop

We've made a lot of progress in the last year. When I first started participating in conversations about health information exchange, people weren't even differentiating between structure and content (hence, some cyclical and confusing dialogs!). This is a significant step forward, and an easy one to take for granted.

Arien, I look forward to meeting you and getting involved in supporting NHIN Direct!

Heather Leslie

Hi Arien,

Thanks for this. Totally agree with the separation of content from transport, but suggest that the ideal for interoperability is that content that is both exchanged, persisted, aggregated and queried is in the same non-proprietary structure - it is only then that our health data will really start to flow.


Arien Malec

Heather - very much agreed. The use of common profiles to lock down the content rules will be critical.

Heather Leslie

Agreed. Locking down content definitions at even finer granularity such as individual clinical concepts will enable us to be able to use and re-use health information more flexibly and organically. Part of my work is facilitating development and publication of archetypes, with a collaborative community of international clinicians/informaticians - www.openEHR.org/knowledge. It is relatively new, but gathering some momentum and worth watching.

Phill Lowe

The current internet design has shown the value of separating layers. Combining content and transport would have ruled out the transition to wireless that is so active today. By limiting the interaction between transport and content, we are free to change either with only minimal impact on the other!

Puma Outlet

thank goodness for rule breaking! I love your page.Thank you for another great article.so you are allowed to change them whenever you want.

The comments to this entry are closed.