Hi Alberto, we are working on this subject:

http://code.google.com/p/open-ehr-gen-framework/
http://code.google.com/p/open-ehr-gen-framework/wiki/Optimizacion
http://code.google.com/p/open-ehr-gen-framework/wiki/EstructurasDeDatos
http://www.openehr.org/wiki/display/impl/Playing+with+Pablo%27s+Open+EHR-Gen+Framework

-- 
Kind regards,
Ing. Pablo Pazos Guti?rrez
LinkedIn: http://uy.linkedin.com/in/pablopazosgutierrez
Blog: http://informatica-medica.blogspot.com/
Twitter: http://twitter.com/ppazos



Date: Fri, 3 Jun 2011 14:27:55 +0200
Subject: Dual Model EHR implementation
From: [email protected]
To: openehr-technical at chime.ucl.ac.uk

Dear all,

Within the Virgen del Rocio University Hospital we are analysing how to 
implement a EHR based on Dual Model Approach.  When we analysed direct 
implementation a database based on of either OpenEHR Reference Model  or ISO 
13606, we have detected that it could have slow performance . Given that we are 
concerned about this problem, we would like to know possible strategies have 
been identified by implementers in order to fasten the performance of storage 
and query.


Also the granularity level is one open issue that impacts on the performance, I 
would like to know if the level of granularity of the archetypes contained 
within the OpenEHR CKM is able to satisfy the requirements of  an EHR with more 
than 1 million records.


Kind Regards 

Alberto



Alberto 
Moreno Conde
GIT-Grupo 
de Innovaci?n Tecnol?gica
Hospital 
Universitario Virgen del Roc?o
Edif. 
Centro de Documentaci?n Cl?nica Avanzada
Av. 
Manuel Siurot, s/n.
C.P.: 
41013    SEVILLA
 
 

_______________________________________________
openEHR-technical mailing list
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/20110603/836a5915/attachment.html>

Reply via email to