> c'était une blague... I see that, sorry for that.
Please understand my situation. I was in the urge to solve a problem in the ADL1. 4 environment and I was not waiting for someone to tell me that that problem is already solved because ADL2 will come real soon. Maybe it is maybe it is not, but that discussion did not help me. But in the end my problem is solved so everything is oké now. Best regards Bert Op wo 1 mrt. 2017 15:55 schreef Bert Verhees <bert.verh...@rosa.nl>: > Lots of good things happening. We will see when major shifts will occur. I > keep my finger in the wind and expect another year to wait. > > I hope sooner. There will be a migration period in which both versions > will be used. > > Bert > > Op wo 1 mrt. 2017 15:41 schreef Ian McNicoll <i...@freshehr.com>: > > Hi Pieter, > > Thanks for the update. This kind of innovation is why I am so keen to make > the jump to this brave new world. > > I'd love to hear more about your main project but will contact you > separately. > > 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 1 March 2017 at 13:04, Pieter Bos <pieter....@nedap.com> wrote: > > We’re looking forward to the new ADL-designer. We’re currently building an > ADL-2 based openEHR implementation and currently doing parts of the > archetype design by hand until we have better tools. > > If you want to use ADL-2 and you’re looking for a java library for your > EHR or authoring tools, Archie implements ADL-2 and the reference model, > plus a lot of tools for working with them. > Important for specialization: It include a flattener and operational > template creator that converts specialized archetypes and templates to an > operational template. Those make working with specialized archetypes much > easier. They combine the archetypes, templates, templates overlays and > specialized archetypes into one flat archetype that you can use in your > tools and user interfaces. > > See http://github.com/nedap/archie . It now also has experimental but > usable support for rule evaluation. > > Licensed under the Apache license, so it should be usable in any kind of > project you like – open source or proprietary. > > Regards, > > Pieter Bos > Nedap Healthcare > > From: openEHR-technical <openehr-technical-boun...@lists.openehr.org> on > behalf of Ian McNicoll <i...@freshehr.com> > Reply-To: For openEHR technical discussions < > openehr-technical@lists.openehr.org> > Date: Wednesday, 1 March 2017 at 13:20 > To: For openEHR technical discussions <openehr-technical@lists.openehr.org > > > Subject: Re: inheritance of archetypes > > Hi Bert, > > Marand are about to release a major interim update to their ADL-2 > Archetype tooling. I am told sometime in March). > > One of the major design criteria is to be able to create ADL1.4 artefacts > and, critically, ADL 1.4 .opts so we can use the new tools with existing > systems, but take advantage of better handling of specialisations etc. > @Birger - This will also help with transition in tooling like CKM, where we > should be able to create ADL 1.4 flat forms for review purposes. > > We expect this first release to need a bit of work and user-feedback. We > (freshEHR) have committed to give it a good workout on real-world project > so that we can rapidly iterate and get it ready for proper release. > > This is the year we make the jump, at least in the design space!! I expect > back-end CDRs and other tooling to be working with ADL1.4 artefacts for > some time. The impact on CDRs is not actually very significant if we mange > the transition carefully. > > I would be delighted to hear from any developers or companies who might be > prepared to make a contribution to this project (open-source of course). We > have had a couple of interesting offers of support already. Good tooling is > essential to openEHR, and if we get a good set of baseline tools, there are > all sorts of interesting extensions that could be developed. > > > Ian > > Dr Ian McNicoll > mobile +44 (0)775 209 7859 > office +44 (0)1536 414994 > skype: ianmcnicoll > email: i...@freshehr.com<mailto:i...@freshehr.com> > twitter: @ianmcnicoll > > [ > https://docs.google.com/uc?export=download&id=0BzLo3mNUvbAjUmNWaFZYZlZ5djg&revid=0BzLo3mNUvbAjRzZKc0JpUXl2SkRtMDJ0bkdUcUQxM2dqSVdrPQ > ] > Co-Chair, openEHR Foundation ian.mcnic...@openehr.org<mailto: > ian.mcnic...@openehr.org> > Director, freshEHR Clinical Informatics Ltd. > Director, HANDIHealth CIC > Hon. Senior Research Associate, CHIME, UCL > > On 1 March 2017 at 10:00, Bert Verhees <bert.verh...@rosa.nl<mailto: > bert.verh...@rosa.nl>> wrote: > Op 1-3-2017 om 10:44 schreef Thomas Beale: > Good news Thomas, but don't bring it with disdain. > > I don't know what the words means ;) > > I got it from google translate, in French it is dedain. > that appears to be a PR about GDL? > > I meant a current list of Open Issues, I don't know why the 168 is on top, > it seems to have the highest priority, I don't understand why. > That is not my discussion point. > So it's not perfect, but it's far from non-existent. I'd say your best bet > is to use the new version of ADL-designer. > As said, institutions will want a stable release. I will never advise an > organization to move to ADL2 as long as it is not stable. > Also one of the selling points of OpenEHR is CKM, it is fully ADL 1.4. > There must be many archetype, and many data-storages based on ADL 1.4 > > And there is another point, companies don't tend to change when they do > not feel the pain. > I had my first IP6 course in 1998, I worked for DEC (Digital) at that > time, and still the computer I work on is configured using IP4, so is my > Internet-router. > > But the discussion on this technical list can be closed as the point I > wanted to make is planned to be solved (and maybe soon). > > Best regard > > Bert > > > > _______________________________________________ > openEHR-technical mailing list > openEHR-technical@lists.openehr.org<mailto: > 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
