On the Getting started page, a new presentation is available explaining the openEHR knowledge development tool chain. It is less than 10 slides, and since quite a few people have requested it after recent presentations, I have made it generally available.
Wow! Very helpful!
Thanks and
greetings from Vienna,
Stefan Sauermann
Acting Program Director
Biomedical Engineering Sciences (Master)
University of Applied Sciences Technikum Wien
Hoechstaedtplatz 5, 1200 Vienna, Austria
P: +43 1 333 40 77 - 988
M: +43 664 6192555
E: stefan.sauermann@technikum-wien.at
I: www.technikum-wien.at/mbe
I: www.healthy-interoperability.at
Thomas Beale schrieb:
Thank you, Tom.
I will add this slides for our congress, JCMI 2010 in Nov 20, which
Dipak will join.
Best regards,
Shinji
Dear openEHR clinical (technical) members,
this is truly a very good presentation of openEHR tools, thanks for sharing it with all of us. It makes me believe this presentation provides answers to the provocative question that has been put forward in the forum,” why is openEHR adoption so slow”. In this email I will try to explain it from my perspective and I hope to get your feedback to become wiser on this.
B2B processing has been established long time ago (e.g. banking sector) but now it is based on open standards. The machine lingua franca of internet is XML (XHMTL) and everything (Processing Standards, Vocabulary Standards and Technology Standards) should be expressed in that form one way or the other. But humans expect everything in a human language readable form. On the opposite, machines are exchanging XML for interoperability purposes. Therefore both worlds have to fit together and have to exist transparently one from the other.
OK let’s get into that health sector. Simply put, If I am a doctor, I want to act (send, receive, create, read, write, sign, etc) on a document (note, email, form, catalogue, report, etc) NOT on a software(application program & system). Why not, because I want globally accepted MEDIA OF EDI (Electronic Data Interchange). This currently means it has to be created with a standard format, PDF or Open Document (Writer/Word , Spreadsheet, Presentation) format or other media format (jpg for images), (mp3 for audio) in order to be ready for processing in every IT system available. The non-IT professional wants to do better everyday business no matter what software tools they will be used in-between, and no matter what will be the exact specifications of the underlying XML format (e.g. CDA embedded on PDF, or CCR embedded on DOCX, HL7, etc).
Depict it with an analogy to human/computer functional structure (i.e. brain/CPU, memory, senses/Input-Output)
There is blood circulating in your veins, there has to be a similar analogy with the IT world and we already experience the blood of IT that is circulating and floating around. These are the computer media (images, documents, audio, etc) we exchange between us.
End to End Human to Human Communication based on EDI with Pairs of
Action - Implementation
Sending Information - User (Human World / Senses)
Representation of information - MEDIA OF EDI (Human Computer Interaction, Machine I/O)
Deconstruction and Processing of information - XML Semantics World, Software Tools, Human Resources (CPU)
Permanent Storage of Information - Central Database (Memory)
Construction and Processing of information - XML Semantics Processing World, Software Tools, Human Resources (CPU)
Representation of information - MEDIA OF EDI (Machine I/O, Human Computer Interaction)
Receiving information - User (Human World / Senses)
Therefore, saying all these I am not sure how exactly openEHR approach will fit on the wider picture I tried to describe to you. The way I see it, regarding the final slide of openEHR tools (9), patients and health professionals are users of EDI. For human to human communication information HAS TO BE ACCURATE and COMPREHENSIBLE using mainly vision, hearing/speech and touch senses. Information HAS TO BE STORED in MEDIA OF EDI that are created and processed by IT systems and other IT-human resources. Depending on the terminology standards (e.g. ICD10), artifact standards (CDA, CCR, openEHR) and other semantics that are hidden underneath the MEDIA OF EDI a central database should keep track of all the different representations of the information so that Babel Tower is eliminated.
This is the end or perhaps the beginning of the story, hope it inspires a few, hope it helps.
Athanassios I. Hatzis, PhD
PS: I will continue, hopefully my constructive criticism, on the openEHR approach that I feel it is going in the right direction but probably with a narrowed perspective on tools that are used for implementation, perhaps due to the fact that you are also trying to do business with the software and that is not bad of course. From that point of view I see machines world of SOA and again I am not sure how openEHR fits into that puzzle (i.e. connecting services not applications). Perhaps you can point me to the right direction with your presentations and material to read on this too 