Dear all, the initial release of a java reference kernel for openEHR is available. The project page is at http://www.openehr.org/repositories/kernel_java-dev/latest/project_page.htm. This work has been carried out by the Swedish company a-code, led by Rong Chen and G?ran Pestana. See http://www.openehr.org/projects/t_projects.htm for further information & links on a-code. We are indebted to the team for donating their work as open source to the openEHR Foundation, which really means of course, to the openEHR community.
The idea of a "kernel" in openEHR is a small but sophisticated component which implements the reference model (RM) and archetype model (AM) in order to actually use archetypes at runtime to build and validate data. It is the key component in many openEHR services, and central to the archetype method. We are aiming for this implementation to become the openEHR reference implementation of the kernel for the Java language. The work is continuing jointly between a-code and the CHIME team at UCL, including Nathan Lea, Yin Su Lim, with some project management provided by me. Other developers are invited to express interest. The project is run according to the openEHR Technical CM Plan (http://www.openehr.org/repositories/spec-dev/latest/publishing/CM/CM_plan.pdf). Community feedback can be in the form of discussion or Problem Reports, to report bugs or suggested enhancements (http://coruscant.chime.ucl.ac.uk:8200/openEHR_Collector/projects/reference_implementations/javakernel/PR/folder_contents). The development team itself uses Change Requests (http://coruscant.chime.ucl.ac.uk:8200/openEHR_Collector/projects/reference_implementations/javakernel/CR/folder_contents) to document the changes it makes on the software base; these can be viewed by anyone in the community. We are working on various PR and CR reports. We believe this forms an important initial step toward the reliable health computing platform of the future, and we encourage Java developers to work with the software and provide feedback. Technical note: developers should consider using BitKeeper to access and synchronise the code. See the openEHR BitKeeper pages (http://www.openehr.org/developer/t_bk_um_top.htm). BK is free for open source use. For discussion of this software, PLEASE use the openehr-implementers at openehr.org list. - thomas beale -- ___________________________________________________________________________________ Research Fellow, University College London (http://www.chime.ucl.ac.uk) Chair Architectural Review Board, openEHR (http://www.openEHR.org) CTO Ocean Informatics (http://www.OceanInformatics.biz) - If you have any questions about using this list, please send a message to d.lloyd at openehr.org
