Regenstrief Institute, Partners in Health
OpenMRS (Open Medical Record Solution) is a medical record management software.
Open Medical Record System (OpenMRS) consists of a software platform and a reference application that enables customized design of electronic medical records systems.
Proprietary medical record systems, paper records
Goal 3: Good health and well-being
The main users of the software will be healthcare workers, such as nurses, doctors or administrative staff
OpenMRS relies on the assistance of developers from the OpenMRS community to improve the system.
Experts note that OpenMRS has been used by humanitarian organizations such as Save the Children for health-related situations such as West African Ebola outbreak.
OpenMRS has been downloaded 324,801 times in 212 countries from July 27, 2010 to May 24, 2019. There are 1,845 reported implementation sites with over 6.3 million active patients as of December 2016.
Connectivity requirement for the product/service to work (mobile internet, SMS, voice, fixed internet, Wi-Fi, other [specify]).
Coverage required for the product/service to work (2G, 3G, 4G, LTE, broadband, dial-up, other [specify]).
Device features required for the product/service to work (bluetooth, Wi-Fi, camera, IVR, GPS, accelerometers/motion sensors, physiologic biosensors, biometric identifiers, SIM, memory card (e.g microSD), other [specify]).
Device(s) type required for the product/service to work (smartphone, feature phone, computer, tablet, other [specify]).
- 100 patients: 1 GHz processor, 256 MB, 40 GB hard drive
- 10,000 patients: 1.5 GHz processor, 2GB, 150 GB hard drive with RAID and appropiate backup facilities
- 250,000 patients: 2.26 GHz processor, 16 GB, 500 GB hard drive
- Examples here
Connectivity requirement for the product/service to work. Some apps/services can work offline. If no, specify if network connectivity is needed at any point (e.g connectivity needed for download).
Is the product/service able to receive and send back information to the user?
Rates of user vs downloads/subscriptions – Compliance rate for the eHealth service
Support according to the literacy level required from the user. If yes, specify type of literacy support. If no, the user is intended to be literate.
Operating system required and software version (Android, IOs, Windows, other [specify])
Power supply required for the product/service to work (uninterrupted prower supply (UPS), ocassional power supply [minimum time required], other).
Education and behavior change, human resource management, decision support, data collection & analytics, electronic medical records, Healthcare provider- CHW training, telemedicine/remote diagnostic, stock management, disease surveillance and reporting
– Central concept dictionary: Definitions of all data (both questions and answers) are defined in a centralized dictionary, allowing for robust, coded data
– Security: User authentication
– Privilege-based access: User roles and permission system
– Patient repository: Creation and maintenance of patient data, including demographics, clinical observations, encounter data, orders, etc.
– Multiple identifiers per patient: A single patient may have multiple medical record numbers
– Data entry: With the FormEntry module, clients with InfoPath (included in Microsoft Office 2003 and later) can design and enter data using flexible, electronic forms. With the HTML FormEntry module, forms can be created with customized HTML and run directly within the web application.
– Data export: Data can be exported into a spreadsheet format for use in other tools (Excel, Access, etc.)
– Modular architecture: An OpenMRS Module can extend and add any type of functionality to the existing API and webapp.
– Patient workflows: An embedded patient workflow service allows patient to be put into programs (studies, treatment programs, etc.) and tracked through various states.
– Cohort management: The cohort builder allows you to create groups of patients for data exports, reporting, etc.
– Relationships: Relationships between any two people (patients, relatives, caretakers, etc.)
– Patient merging: Merging duplicate patients
– Localization / internationalization: Multiple language support and the possibility to extend to other languages with full UTF-8 support.
– Support for complex data: Radiology images, sound files, etc. can be stored as “complex” observations
– Reporting tools: Flexible reporting tools
– Person attributes: The attributes of a person can be extended to meet local needs
– Integrated applications : EHR(Electronic health record) ,PMS (Practice management software) , ERP (Enterprise resource planning)
– Configurable reports
– Interoperability: Hl7 (Health level 7)
– Coding system: ICD-9/10 SNOMED, CPT, HCPCS,
– Access control model: ACL (Access control list)
Basic infrastructure requirements to implement OpenMRS include a reliable power source, connectivity to the Internet and/or a local area network (for implementations with multiple locations), computers, virus protection, basic computer maintenance, and a server. The storage space required depends on the size of the project, but most installations require a minimum of 2GB RAM and 250GB hard disk.
OpenMRS University holds an online “office hours” session every week to teach developers and implementers about OpenMRS and answer questions. Support materials for developers and implementers are available on the OpenMRS Wiki page. OpenMRS also hosts a discussion forum, OpenMRS Talk, as a channel for communication and support.
An on-site IT professional is needed for the first 2-3 months of implementation. It is recommended that implementers develop a maintenance plan to ensure long term operation of OpenMRS. Experts also note that deployment will require a knowledgeable and dedicated team to procure resources for hosting and maintenance.
The OpenMRS framework was used to develop an EMR system at a University Hospital in Haiti and was used to register 8,700 unique patients within the first month of use. OpenMRS has been used to develop an electronic medical record system in Kenya that has stored over 720,000 patient records, 4.9 millions encounters, and 178 millions observations as of February 2014.
Allen, C., Jazayeri, D., Miranda, J., Biondich, P.G., Mamlin, B.W., Wolfe, B.A., Seebregts, C., Lesh, N., Tierney, W.M. and Fraser, H.S., 2007, Experience in Implementing the OpenMRS Medical Record System to Support HIV Treatment in Rwanda, Studies in Health Technology and Informatics, pp. 382-386.
Manders, E.J., José, E., Solis, M., Burlison, J., Nhampossa, J.L. and Moon, T., 2010, Implementing OpenMRS for Patient Monitoring in an HIV/AIDS Care and Treatment Program in Rural Mozambique, Studies in Health Technology and Informatics, pp. 411-415.
Naressa, A., Mohammed-Rajput, Smith, D.C., Mamlin, B., Biondich, P., Doebbeling, B.M., 2011, OpenMRS, A Global Medical Records System Collaborative: Factors Influencinf Succesful Implementation, Regenstrief Institute, Inc., Indianoapolis, IN, Indiana University School of Medicine, Inidianapolis, IN, Center for Implementing Evidence-based Practice, Roudebush VA, Medical Center, Indianapolis IN.
Thompson, A., Castle, E., Lubeck, P. and Makarfi, P.S., 2010, Experience Implementing OpenMRS to Support Maternal and Reproductive Health in Northern Nigeria, Studies in Health Technology and Informatics, pp. 332-336.
Tierney W.M., et. al., 2010, Experience Implementing Electronic Health Records in Three East African Countries, Studies in Health Technology and Informatics, pp. 371-375.
Tierney W.M., et. al., 2007, The AMPATH Medical Record System: Creating, Implementing, and Sustaining an Electronic Medical Record System to Support HIV/AIDS Care in Western Kenya, Studies in Health Technology and Informatics, pp. 372-376.
Syzdykova, A., Malta, A., Zolfo, M., Diro, E. and Oliveira, JL., 2017, Open-Source Electronic Health Record Systems for Low-Resource Settings: Systematic Review; Department of Electronics, Telecommunications and Informatics (DETI), Institute of Electronics and Informatics Engineering of Aveiro (IEETA), 5(4), p.1.
The OpenMRS platform is compliant with HL7 standards and can be configured to meet local standards and requirements.
Pilot studies that used surveys to evaluate perceived benefits of the platform: OpenMRS, A Global Medical Records System Collaborative: Factors Influencing Successful Implementation
There is a demo for users to test the platform interface
In context photographs (0)
You can use the form below to contribute a photo of this product.
In context files & documents (0)
Feedback from users, customers & distributors
Please let us know your experience in using this product through comments below.