Our Group of Biomedical Informatics (IBIME) at the Technical University of Valencia, Spain, has been working during the last years in the field of integration and standardization of clinical data for the construction of EHR systems. Our main project has been called LinkEHR, which is a prototype system for managing clinical data in the form of EHR Extracts, following a dual model approach.
This system is part of a coordinated project, together with the University of Murcia (Spain), called “Semantic Web Technologies-Based Platform for the Management of Standardized Electronic Health Records”.
The main component of LinkEHR will be LinkEHR-Ed, an archetype editor with integration and standardization capabilities. Its objectives are:
to develop archetypes trough a visual interface independent from any particular reference model and direct edition of ADL. It includes the capability of importing a new Reference Model expressed as an XML Schema in order to use it as the guide for development of new archetypes. It also includes the capability of semantic validation of the designed archetypes.
to provide tools for the standardization of legacy clinical data by mapping an archetype structure to data sources containing non-standardized clinical data and automatically generation of queries to extract and transform that data in the form of XML EHR extracts compatible with the Reference Model XML-Schema.
Although our work is not yet finished, we have decided to announce the existence of a beta version of LinkEHR-Ed. It just covers point 1 of the objectives (the edition and validation of archetypes), since point 2 (mapping archetypes to clinical data sources) is now under visual interface development and testing and we have decided to hide its interface by the moment.
Some remarks:
LinkEHR-Ed differs of current available archetype tools since it is a technical oriented editor and not a clinical point of view archetype editor.
LinkEHR-Ed has already been tested with the OpenEHR reference model and the European CEN EN13606 reference model.
LinkEHR-Ed is being developed in Java under the Eclipse Framework and it uses many components developed by ACode people. We expect to make its source code public by the end of the project, the last quarter of this year.
It is very impressive work you presented here. I am looking forward to hearing more from your project. Hopefully we will meet in Medinfo. =)
By the way, which ACODE components that you are still using in your project? Most of them have been donated to the openEHR Foundation and all recent developments are hosted by the openEHR Java project ( http://svn.openehr.org/ref_impl_java/TRUNK/project_page.htm).
If you need any help with migrating dependencies of ACODE components or wish to release your Java components through the openEHR Java project, please let me know.
By the way, which ACODE components that you are still using in your project? Most of them have been donated to the openEHR Foundation and all recent developments are hosted by the openEHR Java project ( http://svn.openehr.org/ref_impl_java/TRUNK/project_page.htm).
Dear Rong,
We always get the updated code through the OpenEHR SVN
We have only used the ADL parser/serializer and the AOM implementation, since we do not need to work with any particular RM implementation. We have modified the AOM mainly and added many utility methods in order to meet the needs of our editor. The code has not been done public yet because it can still have some modifications until the end of the project, but if you or anybody else is interested please let us know.
In Medinfo you can meet José Alberto and Diego, unfortunately I will stay at home
Your announcement outlines some very interesting and potentially very valuable work.
Thank you for letting us know about it, and we look forward to your sharing more of it with us in the months ahead.
This is still a small family, globally, and it is lovely to learn about new work that we might all find useful.
We’re working, with the National Centre for Classification in Health (Australia) on Emergency Department TermSets and across the domain of interface terminology and reference terminology (SNOMED-CT) and the following is of great interest
standardization of legacy clinical data by mapping an archetype structure to data sources containing non-standardized clinical data and automatically generation of queries to extract and transform that data . .
to us and likewise I hope we can catch up at MedInfo.
Gordon Tomes
Acute Care Division
Department of Health and Ageing (MDP 63)
PO Box 9848, Canberra ACT 2601
Ph 612 6289 5081 | Mobile 0423 024 922 | Fax 612 6289 7630
**"Rong Chen" <rong.acode@gmail.com>**
Sent by: openehr-technical-bounces@openehr.org
11/07/2007 01:35 AM
Please respond to
For openEHR technical discussions <openehr-technical@openehr.org>
Re: New contribution to Dual Model EHR architectures and archetype development [No Protective Marking]
|
| - |
Dear David,
It is very impressive work you presented here. I am looking forward to hearing more from your project. Hopefully we will meet in Medinfo. =)
By the way, which ACODE components that you are still using in your project? Most of them have been donated to the openEHR Foundation and all recent developments are hosted by the openEHR Java project ( http://svn.openehr.org/ref_impl_java/TRUNK/project_page.htm).
If you need any help with migrating dependencies of ACODE components or wish to release your Java components through the openEHR Java project, please let me know.
