Hi Jasna, 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. Ian On 16 October 2013 15:51, Jasna Dugali? <jasna.dugalic at gmail.com> wrote: > 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? > > The other obscurity is how are data exchanged? Do I have to exchange TDD, > filled with data, and generated from composition (according to TDS) or I'll > have to make some ehr_extract equivalent? If using ehr_extract is needed, > is there any example on how to use it? I read some parts of the > documentation and found > https://github.com/openEHR/adl-archetypes/blob/master/Example/openEHR/ehr_extract_template/Working/Templates/ehr_extract/openEHR-EHR_EXTRACT-EXTRACT.t_basic_acute.v1.adls > but I need explanation of its using. > > 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. > > > Thanks, > > Jasna > > > > On 15 October 2013 13:13, Mate Be?tek <mate.bestek at gmail.com> wrote: >> >> Hi from Slovenia! >> >> 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. >> >> Kind regards >> Mate >> >> >> 2013/10/15 Mate Be?tek <mate.bestek at gmail.com> >>> >>> Pozdrav i iz Slovenije! >>> >>> 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. >>> >>> LP,Mate >>> >>> >>> >>> >>> 2013/10/15 Miroslav Koncar <miroslav_koncar at yahoo.com> >>>> >>>> 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 meto >>> >>> >>> >> >> >> _______________________________________________ >> openEHR-technical mailing list >> openEHR-technical at lists.openehr.org >> >> http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org > > > > _______________________________________________ > openEHR-technical mailing list > openEHR-technical at lists.openehr.org > http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org -- Dr Ian McNicoll office +44 (0)1536 414 994 fax +44 (0)1536 516317 mobile +44 (0)775 209 7859 skype ianmcnicoll ian.mcnicoll at oceaninformatics.com Clinical Modelling Consultant, Ocean Informatics, UK Director openEHR Foundation www.openehr.org/knowledge Honorary Senior Research Associate, CHIME, UCL SCIMP Working Group, NHS Scotland BCS Primary Health Care www.phcsg.org
