I’m new to this list and in openEHR. I studied openEHR pdfs about adl, aom, em etc., watched Tomas Beal’s adl tutorial on youtube. I partial understand openEHR but I have big holes between those parts, so I hope someone will answer my questions because I am not sure that I am going the right way.
I managed to get the TDD, but I am not sure if the purpose of TDD is exchanging or something else.
How to exchange data between two OpenEHR systems and between systems in which one of them is not an openEHR?
pozdrav, vidim da ste na listi, dobrodosli Nisam znao da In2 gleda u openEHR metodologiju, pozdravljam, mislim da je to nesto sto ce bitno promijeniti trziste u slijedecih 3-5 godina.
Pravi odgovor na vase pitanje je - stylesheet transformation. Sustav koji ne podrzava openEHR archetypes and reference model, ako zeli slati podatke u openEHR enabled system, treba imati izmedju sebe transformaciju podataka iz cega god radi u openEHR, ADL. Ako pak imate dva sustava koji su openEHR kompatibilni, onda je stvar puno laksa, jer formalizam osigurava verzioniranje archetypes, odnosno oba kroz templates metodologiju samo rade constraining of existing archetypes. U oba slucaja, jednom kada imate templates and forms u XML-u, nacin na koji cete komunicirati podatke je kroz IHE infrastrukturu, odnosno CDA external references.
Kljucni benefit zapravo sjedi na openEHR clinical data repositoriju, koji ce onda osigurati semanticku interoperabilnost, ontologiju i technology neutral repozitorij podataka.
Svakako dodjite na ISHEP - www.ishep.org. Imat cemo posebnu radionicu oko ovoga, u sklopu PARENT project workshop-a.
Kod nas je OpenEHR prilično daleko dogurao. Osobno sam ga upotrijebljivao
na nacionalnom eZdravje projektu te nekoliko ostalih projekata (znam da se
PARENT isto tako pokušava osloniti na OpenEHR). Kako je več bilo rečeno,
potreban je OpenEHR server u koji se pohranivaju podatci zajedno za
arhetipima. Sa upotrebom nekog query jezika (npr. AQL ili XPATH/XQUERY)
dobiva se podatke, koje se može onda upotrijebiti npr. za CDA dokumente.
Isto tako u kontra smijeru, radi se transformacija iz npr. CDA u OpenEHR
pomoču XSLT. Postoje več nekoliko open source projekata, koji služe kao
OpenEHR repozitorij i kao framework za izgradnju aplikacija iznad tog
repozitorija.
We’ve been able to use OpenEHR on many levels. This includes the national eHealth project, a research project (eCare) where an OpenEHR based platform for development of new behavior change interventions was developed and used for a year in controlled clinical trials (the interventions were tested), also while working for the epSOS project and for defining our national EHR “content modules”, we used OpenEHR archetypes and templates.
To use OpenEHR you need an OpenEHR repository where both the archetypes and data are stored (e.g. in a form of xml documents that are controlled by the OpenEHR xml schema). To use the data one can use a query languege (AQL or XPATH/XQUERY) to get the data which can then be used for different purposes (like creating CDA document ). If working directly with xml documents, you can use XSLT for performing transformations between OpenEHR xml schema and CDA schema. In the other direction, you can also use XSLT, obviously. Anyhow, there are a few open source OpenEHR repositories which come with frameworks for developing new OpenEHR based applications that run on top of OpenEHR repositories.
In Slovenia, we have a national EHR (IHE based) where CDA is used for the documents. While I worked on the national eHealth project we defined OpenERH as the way to model clinical content and we are currently (the Slovenian MoH is) in the process of establishing the national process of OpenEHR governance. And plenty more on this topic is happening in Slovenia. The latest PARENT project is also something to note - the register of registers is probably going to use OpenEHR as the basis.
Thank you all for your answers. I know theoretically how thing work but I’m not sure I’m doing the right thing.
For example if one system is openEHR compatible and the other isn’t who needs to make XSLT transformation? Reading Miroslav’s answer I would say that the openEHR makes xml for exchange according to openEHR rules and the other system needs to send that xml, the other system is responsible for XSLT transformation if they don’t support openEHR. Is this true?
After reading the openEHR.Net documentation I would say that TDD is the one that needs to be exchanged between systems but as I said I’m not sure. After reading Mate’s comment I would say CDA must be exchanged between systems.
Hi Mate – and also mate as people often greet each other in New Zealand J
Well done with all the great work – which sounds very impressive.
I’m particularly interested in the “Register of registers” concept – can you please elaborate on this?
A PhD candidate of mine is planning to establish some ‘decision support’ tool for modellers by looking at a number of model sources, including other CKMs and some relevant ontologies, DCMs, CDA etc. Do you see a match?
All of these are valid choices. There is a 'canonical' XML format
whose schema are on the openEHR website. It is possible to exchange
data in this format in a number of ways via the openEHR EHR-Extract,
inside a CDA document as native openEHR data, inside a CDA document,
transformed to equivalent CDA templates where they exist.
The choice will largely depend on the environment you are working in.
TDD is a simplified version of openEHR XML which is easier to work
with, since the XML tags reflect more directly the business names of
the parent openEHR template from which the TDD is derived. Any TDD
document can be transformed to the canonical format via a standard
transform.
In current projects in the UK we have used
1. Native 'proprietary' xml transformed to TDD then transformed to
canonical openEHR XML then persisted.
2. Native proprietary system populates a TDD then the TDD is carried
as an attachment within a CDA Level 1 wrapper. The openEHR TDD is then
stripped out on receipt, transformed ot canonical format and
persisted.
I would also expect to be working with situations where the openEHR
data needs to be transformed to/from full CDA level 3 templates. This
is considerably more complex since it requires more fine-grained
mapping.
It all depends what the customer wants and to a large extent the
degree of CDA adoption by the host country.
Nisam znao da In2 gleda u openEHR metodologiju, pozdravljam, mislim da je to nesto sto ce bitno promijeniti trziste u slijedecih 3-5 godina.