Innovation and Openness - Is There Room for Both

322 views

Published on

Koray Atalag
Department of Computer Science, University of Auckland
www.cs.auckland.ac.nz
(P34, 1/10/09, Opus Room, 11.13)

Published in: Health & Medicine
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
322
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
0
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Innovation and Openness - Is There Room for Both

  1. 1. Innovation & Openness - is there room for both? Koray Atalag, MD, Ph.D
  2. 2. Why B other? <ul><li>Health IT is not delivering its full potential </li></ul> Systems are expensive to build and maintain  Frustrated users/buyers  Low penetration into practice  Limited/no interoperability  etc. etc. etc.
  3. 3. An Important “bottleneck” “ handover” <ul><li>Cognitive friction / limits to </li></ul><ul><li>human communication </li></ul><ul><li>Unknown requirements </li></ul><ul><li>Wrong requirements </li></ul><ul><li> Changing requirements? </li></ul>
  4. 4. The “handover”... <ul><li>Not only the body of knowledge can only partially be “handed” over, </li></ul><ul><li>but also it might just be “ too much to handle ”: </li></ul><ul><li>Techies : breadth/depth/complexity & changeability in Medicine </li></ul><ul><li>Clinicians : the physical limitations of IT can also be hard for a clinician to understand (the &quot;if it can be done on Star Trek, why not here&quot; syndrome) </li></ul>So far so good... Isn’t this the reality in health IT?
  5. 5. Getting “IT” r ight ... <ul><li>Room for improvement  tackling “handover” </li></ul><ul><li>Solid software r equirements </li></ul><ul><li>Future-proof systems? </li></ul>
  6. 6. - T he I nnovation <ul><li> Complete set of specifications (not formal std) </li></ul><ul><li> Focus on content & architecture –not messaging </li></ul><ul><li> Open Access – not for profit Foundation </li></ul><ul><li> Adopted by ISO & CEN (13606) </li></ul><ul><li> Joint work programme with IHTSDO </li></ul><ul><li> HL7 ??  not an “either..or” decision </li></ul><ul><li>and it works! </li></ul>
  7. 7. How it Works? <ul><li>Separate domain knowledge from software code </li></ul><ul><li>Separate tasks of developers & domain experts </li></ul>© The openEHR Foundation
  8. 8. Doctors in the d river’s s eat! <ul><li>Empowers domain experts /users </li></ul><ul><li>Active in whole software lifecycle </li></ul><ul><li>Minimal “handover” to techies </li></ul><ul><li>Confidence vs. alienation </li></ul>
  9. 9. Clinical Models
  10. 10. Why Openness is Essential? <ul><li> Because no single group, company, academic institution or government can overcome the wickedness of health IT – ALONE ! </li></ul><ul><li> F oundation for global collaboration </li></ul><ul><li>– “ wisdom of the crowds ” </li></ul>
  11. 11. What is Needed? <ul><li>At a minimum  </li></ul><ul><li>- o pen standards </li></ul><ul><li>- open service descriptions </li></ul><ul><li>- g ood documentation </li></ul><ul><li>Better if  </li></ul><ul><li>- open “data” descriptions </li></ul><ul><li>- open source reference implementations </li></ul><ul><li>- open source tools & libraries </li></ul>
  12. 12. O pen S tandards <ul><li>Most common features: </li></ul><ul><ul><li>Available to all – no/minimal cost </li></ul></ul><ul><ul><li>Governed by n ot-for-profit organisation </li></ul></ul><ul><ul><li>O pen decision-making procedure </li></ul></ul><ul><ul><li>Royalty-free in implementing (no patents etc.) </li></ul></ul>
  13. 13. Open d ata <ul><li>Open descriptions for data: </li></ul><ul><ul><li>f ormat & content </li></ul></ul>
  14. 14. More on “Open Data” Format Content ???
  15. 15. Bottomline... www.openehr.org “ Openness is a neccesity for innovation ” ...and there is room for both
  16. 16. Thanks F urther I nformation [email_address] To view this presentation and others from HINZ go to the hive

×