John Kieti is a Database Specialist at Kenya’s National AIDS Control Council as well as a technology blogger at www.gmeltdown.com.
Last week, I had this great opportunity to be a participant at the fifth annual OpenMRS implementers meeting in Cape Town. The meeting brought together implementers, developers, and the leadership of OpenMRS. The meeting was of the “unconference” style and being relatively less experienced with OpenMRS, I found myself simply following through the intense sessions, soaking up a lot of knowledge and insights. There were many lessons and great experiences including ideas on how to actualize the dream in my earlier blog post on adopting OpenMRS in Kenya. I shall try and describe three of them in this post – based on my personal synthesis.
Lesson 1: Clinical Systems Not Reporting Systems
During one of the evening discussions with Dr. Alvin Marcelo and a few others round a dinner table, I had this bulb light somewhere in my mind that “Really, medical record systems need not be seen as reporting tools”. In fact, to some health care practitioners, all that should be expected of the medical records system is that it assists in retrieving a patient’s medical history, and perhaps assists in diagnosis. To those who think that way, other information management issues including aggregation of patient and treatment statistics for what we know as monitoring and evaluation (reporting) is almost out of scope for a electronic medical records system (EMR). The idea that an EMR system needs to primarily address the health care givers’ information requirements at their points of care implies that national Monitoring and Evaluation (M&E) and reporting needs become secondary.
Lesson 2: Symbiotic Relationships Paramount
It is fairly easy for health experts to say that the field of health information systems (e.g., medical record systems) is their exclusive domain. Such a perspective can be legitimized by many valid arguments to the extent that the relevance of input from other professions can be seriously downplayed. Conversely, from a different perspective, information systems experts can easily justify why health information systems is their domain. When these perspectives are not adequately reconciled, there is a high probability that in an health information systems implementation, either health aspects or technology aspects will not be optimized. During the meeting, several participants emphasized that the development and implementation of successful medical records system calls for a symbiotic relationship between health care professionals and IT professionals. Moreover, health information systems implementation require meaningful engagement of all would-be beneficiaries. This was well summarized in by the observation of Chris Bailey from WHO: “If you want the truth about an EHR system implementation, talk to the nurse.”
Lesson 3: Who and What really is OpenMRS?
I am sure this is a lingering question in some readers’ minds. To me the question was answered better during the meeting. A plenary session with Dr. Paul Biondich helped me to understand the idea that OpenMRS is both a global community and a software platform. It is a non-profit, multi-institution collaborative. Its mission is to improve health care delivery in resource-constrained environments by coordinating a global community that creates a robust, scalable, user driven, open source medical records system platform. From a technology perspective, OpenMRS is also a software platform and a reference application which enables design of a customized medical records system. One more related learning point was that there is an on-going work to incorporate a non-profit organization that would facilitate a more proactive pursuit of the community’s mission.
In general, there was a sense that for a health information systems initiative like OpenMRS, maintaining a balance between meeting health care delivery and software evolution objectives is paramount.
Some nice photos of the 2010 OpenMRS Implementers Meeting are available courtesy of John Wesonga.