Archetype relational mapping - a practical openEHR persistence solution

BackgroundOne of the primary obstacles to the widespread adoption of openEHR methodology is the lack of practical persistence solutions for future-proof electronic health record (EHR) systems as described by the openEHR specifications. This paper presents an archetype relational mapping (ARM) persistence solution for the archetype-based EHR systems to support healthcare delivery in the clinical environment.MethodsFirst, the data requirements of the EHR systems are analysed and organized into archetype-friendly concepts. The Clinical Knowledge Manager (CKM) is queried for matching archetypes; when necessary, new archetypes are developed to reflect concepts that are not encompassed by existing archetypes. Next, a template is designed for each archetype to apply constraints related to the local EHR context. Finally, a set of rules is designed to map the archetypes to data tables and provide data persistence based on the relational database.ResultsA comparison study was conducted to investigate the differences among the conventional database of an EHR system from a tertiary Class A hospital in China, the generated ARM database, and the Node + Path database. Five data-retrieving tests were designed based on clinical workflow to retrieve exams and laboratory tests. Additionally, two patient-searching tests were designed to identify patients who satisfy certain criteria. The ARM database achieved better performance than the conventional database in three of the five data-retrieving tests, but was less efficient in the remaining two tests. The time difference of query executions conducted by the ARM database and the conventional database is less than 130 %. The ARM database was approximately 6–50 times more efficient than the conventional database in the patient-searching tests, while the Node + Path database requires far more time than the other two databases to execute both the data-retrieving and the patient-searching tests.ConclusionsThe ARM approach is capable of generating relational databases using archetypes and templates for archetype-based EHR systems, thus successfully adapting to changes in data requirements. ARM performance is similar to that of conventionally-designed EHR systems, and can be applied in a practical clinical environment. System components such as ARM can greatly facilitate the adoption of openEHR architecture within EHR systems.

[1]  D Kalra,et al.  ISO 13606 Electronic Health Record Communication Part 1: Reference Model [99 pages] , 2008 .

[2]  Thomas J. Eggebraaten,et al.  A health-care data model based on the HL7 Reference Information Model , 2007, IBM Syst. J..

[3]  I. Kohane,et al.  Escaping the EHR trap--the future of health IT. , 2012, The New England journal of medicine.

[4]  Ewan Tempero,et al.  Model driven development of clinical information sytems using openEHR. , 2011, Studies in health technology and informatics.

[5]  Tony Austin,et al.  Generic screen representations for future-proof systems, is it possible?: There is more to a GUI than meets the eye , 2009, Comput. Methods Programs Biomed..

[6]  Erik Sundvall,et al.  Performance of XML Databases for Epidemiological Queries in Archetype-Based EHRs , 2012 .

[7]  Jon Patrick,et al.  Evaluation of a Persistent Store for OpenEHR , 2006 .

[8]  Sebastian Garde,et al.  Towards Semantic Interoperability for Electronic Health Records , 2007, Methods of Information in Medicine.

[9]  Knut Bernstein,et al.  Modelling and implementing Electronic Health Records in Denmark , 2003, MIE.

[10]  Rong Chen,et al.  Julius – a template based supplementary electronic health record system , 2007, BMC Medical Informatics Decis. Mak..

[11]  Dipak Kalra,et al.  The openEHR Foundation. , 2005, Studies in health technology and informatics.

[12]  T Beale,et al.  Archetypes: Constraint-based Domain Models for Future-proof Information Systems , 2000, OOPSLA 2000.

[13]  G W Beeler,et al.  HL7 version 3--an object-oriented methodology for collaborative standards development. , 1998, International journal of medical informatics.

[14]  Evelyn J. S. Hovenga,et al.  Expressing clinical data sets with openEHR archetypes: A solid basis for ubiquitous computing , 2007, Int. J. Medical Informatics.

[15]  Jane Grimson,et al.  Applying the archetype approach to the database of a biobank information management system , 2011, Int. J. Medical Informatics.

[16]  Adolfo Muñoz Carrero,et al.  Model Formulation: Proof-of-concept Design and Development of an EN13606-based Electronic Health Care Record Service , 2007, J. Am. Medical Informatics Assoc..

[17]  Sebastian Garde,et al.  Towards a comprehensive electronic patient record to support an innovative individual care concept for premature infants using the openEHR approach , 2009, Int. J. Medical Informatics.

[18]  D. Kalra,et al.  EN 13606 Health informatics - Electronic health record communication - Part 1: Reference model , 2007 .

[19]  Georg Duftschmid,et al.  Towards plug-and-play integration of archetypes into legacy electronic health record systems: the ArchiMed experience , 2013, BMC Medical Informatics and Decision Making.

[20]  Catalina Martínez-Costa,et al.  A model-driven approach for representing clinical archetypes for Semantic Web environments , 2009, J. Biomed. Informatics.

[21]  Tipster Se Cm.  Architecture Overview , 1996, TIPSTER.

[22]  Sam Heard,et al.  Archetype Definitions and Principles , 2003 .

[23]  Kevin Waugh,et al.  Understanding object-relational mapping: A framework based approach , 2009 .

[24]  J EggebraatenThomas,et al.  A health-care data model based on the HL7 reference information model , 2007 .

[25]  Perry L. Miller,et al.  Research Paper: Exploring Performance Issues for a Clinical Database Organized Using an Entity-Attribute-Value Representation , 2000, J. Am. Medical Informatics Assoc..