As *open*EHR moves forward with ADL 1.5, UCL CHIME has been working on tooling to deliver more capability to the *open*EHR users community, providing new and open source assets to leverage in systems development.
The *open*EHR Eiffel repository developed by Ocean Informatics has been providing a very mature, capable and tested open source code base for quite some time. In the context of the UCL Opereffa project, a major work item has been to provide support for the new features of ADL 1.5. Following the principle of making use of open source assets in the *open*EHR ecosystem, and contributing back to it, we have decided to leverage the capabilities of the Eiffel code base by developing a Java layer around it. Our work, named Project Bosphorus will enable users of Java to make use of this Eiffel code base. Bosphorus has been under development at CHIME by a team led by Seref Arikan and supervised by Professor David Ingram, with kind help from Thomas Beale of Ocean Informatics. We believe that by providing a Java wrapper around the Eiffel code base, we will add a significant new option to the already available open source projects in the *open*EHR ecosystem. As the Eiffel code moves forward, Bosphorus will be updated to provide access to newly introduced features. We will build on Bosphorus in the Opereffa project, to manage the new features of ADL 1.5. Opereffa?s developing Java code base and Eclipse tooling will support the new capabilities via this layer. In the short term, we also have set ourselves the goal of providing a JSON and XML based web service, hosted by UCL, to deliver ADL parsing and template processing functionality in a service oriented manner. This service is planned to be connected to the CKM archetype repository hosted at UCL. We hope that by opening up this work, we will be able to help implementers make the transition to upcoming changes in the *open*EHR specifications. In compliance with our commitment to open source solutions, Bosphorus has been made available in the *open*EHR SVN server from the outset, and it will remain so in the future. We hope that the *open*EHR community will make use of this project to add more to the evolving *open*EHR tooling ecosystem. As always we are open to collaboration with all parties interested in our work, and we are very grateful to those who have contributed their work to make ours possible. Seref Arikan and David Ingram -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20101214/e6053103/attachment.html>
