Vincenzo Della Mea wrote:

> Dear colleagues,
> in the OpenEHR web site there is written that open source java  
> components will be released during 2003. Apart that we are now in 
> 2004  (happy new year!), is there any possibility that they will be 
> released  in a short time, or is better not to take into account this 
> possibility  to do some OpenEHR experimentation in the near future?

What I think will be realistic in terms of open source code:

- we already have the whole ADL archetype parser/validator in Eiffel 
which already exists. The only delay here is that we have to do some 
cleaning up so that it will compile on a vanilla Eiffel installation - 
currently we had to add some hacks in the ISE libraries to make it work 
(mainly class renames). We also have this same component available as a 
dotNet DLL, and we have tested it with C# and VB.net - and it works 
pretty well.

As for Java, there are other parties who would like this component 
wrapped in Java, and we do have a way of doing this - but it will take 
some time; we hope to get some colleagues at Mayo Clinic to lend a hand 
on this. Maybe there will be something in a couple of months - which I 
can guarantee would be quicker than rewriting this component from 
scratch in Java!

- as for the main EHR server and other related components of an EHR 
system, we are looking at 6 months to have something running from the 
Australian federal government HealthConnect trial. This will most likely 
be in Java as far as I know.

- other Java components are likely to appear from UCL within 12 
months,based on their previous systems (CEN ENV13606-based)


We would like to encourage others to experiment as much as possible. In 
the next few weeks we will have the website working better, so that it 
serves the specifications straight from the configuratoin management 
system (including any release you ask for - known baselines etc); we 
will also be implementing a lot of outstanding change requests. We hope 
that these changes will enable implementors to work more effectively. 
OpenEHR also has the aim of setting up an implementor's page, and 
enabling better communication between open source implementors, so that 
not too much re-invention goes on. This year will be a big one for openEHR!

hope this helps.

- thomas beale

>
> Thank you,
>
> Vincenzo
>
> ------------------------------------------------------------------------ 
> ------------------------
> -----------------------------  Vincenzo Della Mea, PhD  
> ------------------------------
> Dept. of Mathematics and Computer Science - University of Udine, Italy
> -----------------------  http://www.dimi.uniud.it/~dellamea/  
> ------------------------
> ------------------------------------------------------------------------ 
> ------------------------
>
> -
> If you have any questions about using this list,
> please send a message to d.lloyd at openehr.org
>
>


-- 
..............................................................
CTO Ocean Informatics - http://www.OceanInformatics.biz

openEHR - http://www.openEHR.org
Archetypes - http://www.oceaninformatics.biz/adl.html           
Community Informatics - http://www.deepthought.com.au/ci/rii/Output/mainTOC.html
..............................................................


-
If you have any questions about using this list,
please send a message to d.lloyd at openehr.org

Reply via email to