It is definitely on the openEHR Specifications Roadmap. That was a clear decision at the Oslo meeting a year ago. There are at least 3 implementations that I know of and more back-end vendors are intending to implement but I know what you mean 'technically';)
I agree that AQL is RM agnostic but am not aware of any non-openEHR implementations @Diego/ Gerard?? Ian Dr Ian McNicoll mobile +44 (0)775 209 7859 office +44 (0)1536 414994 skype: ianmcnicoll email: i...@freshehr.com twitter: @ianmcnicoll Co-Chair, openEHR Foundation ian.mcnic...@openehr.org Director, freshEHR Clinical Informatics Ltd. Director, HANDIHealth CIC Hon. Senior Research Associate, CHIME, UCL On 26 August 2015 at 13:12, Seref Arikan <serefari...@kurumsalteknoloji.com> wrote: > Well, technically, it is not part of the openEHR scope either. Happy to be > corrected :) > > On Wed, Aug 26, 2015 at 1:09 PM, Ian McNicoll <i...@freshehr.com> wrote: > >> Hi Diego, >> >> I was not aware of any 13606 implementations that support AQL , although >> I am sure there is some sort of path-based querying. AFAIK AQL is not part >> of the 13606 scope. >> >> Happy to be corrected. >> >> Ian >> >> Dr Ian McNicoll >> mobile +44 (0)775 209 7859 >> office +44 (0)1536 414994 >> skype: ianmcnicoll >> email: i...@freshehr.com >> twitter: @ianmcnicoll >> >> Co-Chair, openEHR Foundation ian.mcnic...@openehr.org >> Director, freshEHR Clinical Informatics Ltd. >> Director, HANDIHealth CIC >> Hon. Senior Research Associate, CHIME, UCL >> >> On 26 August 2015 at 13:03, Diego Boscá <yamp...@gmail.com> wrote: >> >>> I agree with most of the points, but I'm curious why you say that 13606 >>> does not support AQL (and in any case wouldn't be "AQL does not support >>> 13606"?) >>> >>> 2015-08-26 12:32 GMT+02:00 Ian McNicoll <i...@freshehr.com>: >>> >>>> This might help a little >>>> >>>> >>>> http://www.slideshare.net/atalagk/implementation-and-use-of-iso-en-13606-and-openehr >>>> >>>> Similarities: >>>> >>>> Both use archetypes and ADL and two-level information modelling. >>>> Both share the EHR, FOLDERS,COMPOSITIONS, ENTRY, ELEMENT classes. >>>> Some archetype tools can work with both styles of archetype e.g LinkEHR >>>> and Archetype Workbench. >>>> The just announced ADL2 Archetype editor/ template designer tools >>>> (beware!!! Early developer versions!!) >>>> >>>> http://ehrscape.marand.si/designer/template-editor.html >>>> >>>> http://ehrscape.marand.si/designer/archetype-editor.html >>>> >>>> should be relatively easy to adapt to 13606 or other archetype-based >>>> reference models such as CIMI. They will be open sourced very soon. >>>> >>>> Differences: >>>> >>>> The EHR reference models are different >>>> In spite of sharing the classes above, the attributes within those >>>> classes differ >>>> openEHR sub-classes ENTRY into ADMIN_ENTRY, OBSERVATION, EVALUATION, >>>> INSTRUCTION and ACTION >>>> The datatypes are different >>>> >>>> The demographic models are different >>>> The EHR Extract formats are different >>>> >>>> 13606 is intended primarily for the communication of EHR extracts >>>> across systems but some persistence repositories exist. >>>> openEHR is intended primarily for data persistence and querying within >>>> systems but it is possible to message openEHR data. >>>> >>>> 13606 does not (currently) support templates but ADL/AOM2 is being >>>> considered >>>> 13606 does not support AQL Archetype Query Language >>>> >>>> 13606 is formal ISO standard but is closed source i.e. behind a >>>> paywall, as in normal for ISO published material >>>> openEHR is open source and freely available >>>> >>>> There is a great deal of cross-communication between the two >>>> communities and a number of people work with both formalisms. It is >>>> possible to transform data between the two formalisms but they are not >>>> directly compatible. >>>> >>>> I hope that is accurate and non-contentious! >>>> >>>> Ian >>>> >>>> >>>> >>>> >>>> >>>> Dr Ian McNicoll >>>> mobile +44 (0)775 209 7859 >>>> office +44 (0)1536 414994 >>>> skype: ianmcnicoll >>>> email: i...@freshehr.com >>>> twitter: @ianmcnicoll >>>> >>>> Co-Chair, openEHR Foundation ian.mcnic...@openehr.org >>>> Director, freshEHR Clinical Informatics Ltd. >>>> Director, HANDIHealth CIC >>>> Hon. Senior Research Associate, CHIME, UCL >>>> >>>> On 26 August 2015 at 10:14, 王海生 <edwin_ue...@163.com> wrote: >>>> >>>>> dear all , >>>>> how could i explain to someone difference and relationship >>>>> between openEHR and EN13606 >>>>> thx >>>>> -- >>>>> 王海生 >>>>> 15901958021 >>>>> >>>>> >>>>> >>>>> 夏日畅销榜大牌美妆只要1元 >>>>> <http://r.mail.163.com/r.jsp?url=http%3A%2F%2F1.163.com%2Fhd%2Foneact%2Fhdframe.do%3Fid%3D21%26from%3Dfooter_beauty&sign=817593681&_r_ignore_statId=7_13_79_48&_r_ignore_uid=n...@163.com> >>>>> >>>>> _______________________________________________ >>>>> openEHR-technical mailing list >>>>> openEHR-technical@lists.openehr.org >>>>> >>>>> http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org >>>>> >>>> >>>> >>>> _______________________________________________ >>>> openEHR-technical mailing list >>>> openEHR-technical@lists.openehr.org >>>> >>>> http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org >>>> >>> >>> >>> _______________________________________________ >>> openEHR-technical mailing list >>> openEHR-technical@lists.openehr.org >>> >>> http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org >>> >> >> >> _______________________________________________ >> openEHR-technical mailing list >> openEHR-technical@lists.openehr.org >> >> http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org >> > > > _______________________________________________ > openEHR-technical mailing list > openEHR-technical@lists.openehr.org > > http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org >
_______________________________________________ openEHR-technical mailing list openEHR-technical@lists.openehr.org http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
