Hey Alberto, I know three approaches which can be used for editing and creating archetype based data. Maybe there are even more.
First of all, of course, the openEHR Opereffa ( http://opereffa.chime.ucl.ac.uk/MainContainer2.jsf ). As fars as I can see it is possible to capture data, but it isn't possible to edit data yet. For me it is also not obvious how a user can import own archetypes and archetype based data into the system. As fars as I understood, there is implementation work to do for supporting archetypes, which are not allready integrated the system. In this point an opereffa developer could bring more information! ;) The second approach can be found inside the CKM (http://openehr.org/knowledge/) . At least the general idea could be used for this purpose. With the template extension of CKM it is now possible to create OTM based forms. Yet it is only used to visualise a form without the functionality to save data, but with some implementation work it could be extended for your purpose. Unfortunatelly it isn't OpenSource so I don't know how much work it could be. The third approach is "EHRflex" (https://sourceforge.net/projects/ehrflex/). It is based on a diploma thesis and allows you to import archetypes (ISO 13606) and use them to actually create data by using dynamically build forms. The editing possiblity will be added in the next three months, since the method is already developed and need only be implemented. The source code is free available and there is also a pre-Alpha vesion running, which can be tested. I don't want to publish the url officially, because my research center doesn't allow me to publicate our testserver, but I can send you the URL in private. EHRflex could be easily extended for openEHR and HL 7 , since it uses an own data model for the interaction part, which only need to be mapped. I hope I could help you Anton Am 16.03.2010 13:57, schrieb Alberto Moreno Conde: > Thanks for your answer Anton > I am interested in what you said about interact with the information, > what are the approaches that you have identified?, because I suppose > that you could handle the information in the same way as when your > archetype has become obsolete or a new version has been created. > > Kind Regards > Alberto > > *Alberto Moreno Conde* > GIT-Grupo de Innovaci?n Tecnol?gica > Hospitales Universitarios Virgen del Roc?o > Edif. Centro de Documentaci?n Cl?nica Avanzada > Av. Manuel Siurot, s/n. > C.P.: 41013 SEVILLA > > > 2010/3/16 Anton Brass <anton.brass at helmholtz-muenchen.de > <mailto:anton.brass at helmholtz-muenchen.de>> > > Dear Alberto, > > well if it is just showing the extract, which is an instance of > the reference model and normally transported in XML, I would use a > XSLT transformation into HTML and CSS. > > If you want interact with the information, there are several > approaches for different standards in development. > > Kind regards > > Anton > > > > Alberto Moreno Conde schrieb: >> Dear all, >> >> I understand that templates are only local constrains that are >> useful in our local implementation to display the information, >> but how would be the best way to display on a screen the >> information that we have received in an EHR_EXTRACT, if we don't >> have a template to show the information that comes within the >> archetype structure? >> >> Kind Regards >> >> Alberto >> >> *Alberto Moreno Conde* >> GIT-Grupo de Innovaci?n Tecnol?gica >> Hospitales Universitarios Virgen del Roc?o >> Edif. Centro de Documentaci?n Cl?nica Avanzada >> Av. Manuel Siurot, s/n. >> C.P.: 41013 SEVILLA >> > > > -- > > Anton Brass > > Institute for Biological and Medical Imaging - MEDIS > Phone: +49 89-3187-4181 > > *Helmholtz Zentrum M?nchen > German Research Center for Environmental Health (GmbH)* > Ingolstaedter Landstr. 1 > D-85764 Neuherberg, Germany > _www.helmholtz-muenchen.de <http://www.helmholtz-muenchen.de/>_ > Chairman of Supervisory Board: MinDir Dr. Peter Lange > Board of Directors: Prof. Dr. G?nther Wess and Dr. Nikolaus Blum > Registergericht: Register of Societies: Amtsgericht M?nchen HRB 6466 > > > _______________________________________________ > openEHR-technical mailing list > openEHR-technical at openehr.org <mailto:openEHR-technical at openehr.org> > http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-technical > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20100316/e0919048/attachment.html>
