Good to hear you appreciate our effort. While developing Archie we found issues in both the ADL-antlr grammar and the Marand ADL-designer. We¹re very happy to see how soon after we reported them the issues were fixed - Often even within a matter of minutes after reporting. So it already has helped the compatibility of different tools - we can now parse the ADL2 output of the adl-designer.
About our motivation: we develop and sell software for the Dutch care market. Our current EHR-implementation works great for many organizations, but is not flexible enough for some others. That is why we are looking at openEHR and developing prototypes for the next version of our EHR. When we realised the improvements in ADL 2 and the limitations of the java reference implementation we decided we needed to switch to ADL2. We found out there was no open source tool available we could use. So we developed Archie and released it under the Apache license - so others will more easily be able to develop their own tools, whether open or closed source. And because we think that for a platform like openEHR - the more people using it, the more benefit there is to anyone using or developing openEHR-based software. o. Regards, Pieter Bos Nedap Healthcare > >---------------------------------------------------------------------- > >Date: Fri, 30 Oct 2015 07:57:24 +0100 >From: Erik Sundvall <erik.sundv...@liu.se> >To: For openEHR implementation discussions > <openehr-implementers@lists.openehr.org> >Cc: ?ystein Nytr? <nyt...@idi.ntnu.no> >Subject: Re: New open source ADL2-Library >Message-ID: > <caehpwgf0lce_6kdggjubsphzdv1g9v2jjf+fue-9wyf9gaw...@mail.gmail.com> >Content-Type: text/plain; charset="utf-8" > >Great news! > >Apache 2 is a good licensing choice, that is what we recommend for openEHR >open source projects, although some contributors have felt reasons to use >other licences. > >Apache 2 for example makes it easier for some companies to allow staff to >spend paid working time on improving industry/community-shared open source >components that they use in their closed or open platforms. Nowadays I'd >guess more openEHR software implementation work is done by business >employees during paid time than by volunteers using their spare time. > >Having more ADL2 parsers does bring some extra benefits: >- compatibility tests and discussions can clarify the specification if >needed >- more of the possible design space is explored by more teams that can >learn from each other > >However having a dozen of open source ADL2 parsers would probably be a >waste of developer effort. > >I think the same goes for archetype/template editing tools, having a >handful of tools explores more options and brings up more good discussions >than having a single one, but having too many would potentially be a waste >of developer effort. > >If you want to, then please to tell us a little bit more about the >context/product that you will be using the parser in. > >Best regards, >Erik Sundvall >Ph.D. Medical Informatics. Information Architect. Tel: +46-72-524 54 55 >(or >010-1036252 in Sweden) >Region ?sterg?tland: erik.sundv...@regionostergotland.se (previously >lio.se) >http://www.regionostergotland.se/cmit/ >Link?ping University: erik.sundv...@liu.se, http://www.imt.liu.se/~erisu/ > >On Wed, Oct 28, 2015 at 7:34 PM, Bert Verhees <bert.verh...@rosa.nl> >wrote: > >> Thanks very much, Pieter, great job! >> >> Bert >> Op 28 okt. 2015 18:20 schreef "Pieter Bos" <pieter....@nedap.com>: >> >> I would like to announce a new open source ADL2 library, written in >>Java. >>> It is based on the ANTLR-grammar released very recently by Thomas >>>Beale. >>> >>> You can find it at https://github.com/nedap/archie >>> >>> It is still very much in development, but it is now at a state where it >>> could be of use to people. It currently features: >>> >>> - an ADL2-parser that parses the full definition, specialises, >>> terminology, value sets and (a subset of) rules sections >>> - an archetype object model implementation >>> - a flattener that can also make operational templates - still needs >>> testing and work! >>> - basic path queries with node ids and node meanings. >>> - an experimental Archetype treewalker for openEHR reference models ? >>>it >>> can save you many instanceof calls. >>> >>> It parses most valid ADL2 files i?ve tested it with into an archetype >>> object model. That includes most of the content of the clinical >>>knowledge >>> manager. We?re currently using this same library for an openEHR >>> implementation and we will add features, fixes and tests to it as we >>> progress. >>> >>> You might ask, why a new library? Don?t we have adl2-core already? The >>> answer is quite simple: licensing. >>> We could not use the adl2-core library for our projects, because it >>>would >>> require us to release the entire project under the (A)GPL. So we >>>ignored >>> the existing library and built our own. And now we release Archie under >>> the Apache license. This means you should be able to use it in any >>>project >>> you like. >>> >>> Want to help? Great! There?s a list of missing functionality on the >>>github >>> page. Just fork and create a pull request. Or just report any issues >>>you >>> find on the github issue tracker. >>> >>> Regards, >>> >>> Pieter Bos >>> Nedap Healthcare >>> >>> >>> _______________________________________________ >>> openEHR-implementers mailing list >>> openEHR-implementers@lists.openehr.org >>> >>> >>>http://lists.openehr.org/mailman/listinfo/openehr-implementers_lists.ope >>>nehr.org >>> >> >> _______________________________________________ >> openEHR-implementers mailing list >> openEHR-implementers@lists.openehr.org >> >> >>http://lists.openehr.org/mailman/listinfo/openehr-implementers_lists.open >>ehr.org >> _______________________________________________ openEHR-implementers mailing list openEHR-implementers@lists.openehr.org http://lists.openehr.org/mailman/listinfo/openehr-implementers_lists.openehr.org
