The goal of this page is to help you understand what it takes to implement OpenMRS. If you are already beginning an implementation and would like more detailed advice, see the Field Guide.
- One dedicated IT person for at least two or three months, usually full time. They need to know the whole stack (server maintenance, MySQL, Tomcat, Java, etc.) The level of expertise you need on site depends in part on whether or not you have the Internet to get help from online resources or remote developers.
- Tomcat expertise
- Install and manage Apache Tomcat
- Upload and install new WAR files
- Troubleshoot, read log files
- Database expertise
- Install and manage MySQL environment
- Understand the OpenMRS data model
- Metadata configuration e.g. locations, addresses, patient IDs, programs, relationships.
- Understand the capabilities of the module functionality
- Perform SQL queries and run SQL scripts
- Clinical form design
- Understand how to create meaningful, useful, and non-ambiguous questions/answers
- Medical expertise – to understand what questions/answers make sense, what's clinically relevant
- Technical expertise – to understand how questions/answers can be interpreted by a computer
- Data management expertise – to understand how questions/answers will be used for reporting, research, etc.
- Concept dictionary design
Concept dictionary management – understand the process of creating/modifying new concepts.
Ability to infer dictionary concepts from a form (both coded questions and answers), modeling expertise – e.g., do you create
CHEST PAIN has a class of diagnosis and datatype of N/A. The clinical form expects yes/no for chest pain. Do you create a new concept or use SIGNS AND SYMPTOMS construct with SIGN/SYMPTOM PRESENT (yes/no/unknown) and CHEST PAIN as a possible answer to SIGN/SYMPTOM NAME?
- Ability to install and configure Apache + SSL (if extending network beyond a single LAN)
- Report design expertise
Long-term IT support
OpenMRS relies on some basic infrastructure. After this infrastructure is in place, long-term IT support will be needed to ensure it continues working properly.
- Connectivity to the Internet and/or a local area network (for implementations with multiple locations)
- Computers, virus protection, and basic computer maintenance (e.g. a mouse stops working)
Many organizations lack the internal skills to deal with these issues, so a combination of staff training and external support can be critical.
Data entry clerks
Most health facilities have health records information staff who maintain data in the facility. Some facilities lacking such personnel opt to train casuals equipped with basic computer skills to perform these duties.
If you have more than 4 data entry clerks, it is often useful to train data managers to oversee the data entry clerks and ensure that they are maintaining high data quality.
System users such as clinicians and nurses need to have basic IT skills to assist in data entry process. For computer novices, it is recommended they attend IT training in preparation of adoption of the system.
OpenMRS is only as reliable as the power system that supports it. Unless electricity is almost 100% stable in your area, you will probably want a primary power source and a backup. Backup power systems usually involve some kind of battery. Using grid power with a diesel generator as a backup is probably not sufficient because there is a short lag inbetween losing grid power and turning on the generator, and the suddden loss of power can damage your server or data quality. Hybrid systems are ideal, where you have a primary power source (such as grid power or solar), and a secondary source (such as a generator or solar), both of which feed into short-term backup batteries.
Devices for entering, storing, and accessing data
- OpenMRS server (hardware and operating system) along with wired or wireless network, internet access (optional) and printers (optional).
- A server, recommended one or two processors 1.5+ GHz, 2 GB of memory, and 150+ GB of disk space with RAID and appropriate backup. See Field Guide for more information on selecting a server.
- Work stations for retrospective data entry: If you intend for clinicians to enter data on paper forms that are later entered into OpenMRS by data entry clerks, you estimate the number of work stations you will need based on the amount of data you will enter. As a general rule, it will take a data clerk about one day to enter 80-100 forms with 20 observations per form (this general rule may vary greatly from site to site). For retrospective data entry you may use regular computers that range in cost from $300-$1,000
- Work stations for point of care: If you intend to build a point of care system, you should estimate the number of work stations needed based on the number of clinicians or clinic rooms. You might want to consider using thin clients or touch-screen appliances, and may want to use mobile devices for remote clinics. Such devices range from $100 (for a J2ME smartphone capable of running OpenMRS) to $1,000 for some touch-screen appliances.
You can connect your server (which stores all OpenMRS data) to the work stations where people enter data within your facility using:
- Ethernet cable
- A local area wireless network
- Wireless Internet
If your implementation involves multiple facilities, you may want some means of communicating among sites. Options include:
- Bringing all paper forms to a central location and entering them into the electronic system (requires transportation, but no connectivity equipment)
- Setting up a local area network using long range wifi
- Installing VSAT or otherwise accessing Internet if you wish to communicate with very remote sites (such as a distant office in the country's capital or in another country)
Some projects require significant investment to protect equipment, potentially including installing doors, locks, bars on windows, or metal equipment storage cabinets. At other sites security is less of an issue, so consider the local context. Only local knowledge can guide this decision.
- Build power infrastructure or strengthen as needed
- Improve security to support safely storing electronic equipment
- Build connectivity infrastructure
- Ethernet cables, hubs, etc. as needed for local area network
- VSAT or other means of accessing Internet for remote support
- Design paper encounter forms (getting input from clinical and IT teams)
- Install server
- Install server with power backup – UPS for server and power backup (solar)
- Install the most preferred OS, Windows or Linux operating systems are both recommended
- Install OpenMRS system (MySQL, Apache, Tomcat, etc. — see Setting up an OpenMRS Server)
- Configure server to serve OpenMRS web application through Apache over HTTPS
- Setup OpenMRS core data set
- Install core data set (using SQL)
- Make user account and define privileges
- Define locations
- Define tribes
- Define encounter types
- Build dictionary concepts around forms
- Design electronic form(s) within OpenMRS
- Select a form entry tool from among HTMLFormEntry Module, XForms Module, FormEntry (uses InfoPath), or Remote FormEntry (also uses InfoPath).
- Define forms within OpenMRS
- Test form(s)
- Setup client workstations for data entry
- If using FormEntry or RemoteFormEntry modules, install InfoPath 2003 with Service Pack 2 or later
- Create a training plan, that may include both classrom and departmental training depending on nature of your implementation
- It is advisable to create an OpenMRS test instances for user training purposes before actual go-live use of system
- Issuing simple tests for your users after completion of each training session
- Training of trainers(TOT’s) approach is recommended especially for larger implementations and largely contributes to sustainability of system especially if the TOT's are actual system users
- Stake holder Engagement
- Successful OpenMRS system implementation largeley depends on top down involvement of all stakeholders in the implementation process. Involve the users, managers, sponsors and relevant stakeholders in all processes right from requirements gathering to project implementation. Top-down collaboration tends to provide avenues for providing solutions to challenges that may be experienced during the implementation process
- Review new concept proposals
- Make changes to forms over time (both paper and electronic versions)
- Building reports from data exports
- Managing user accounts
- Server maintenance
- Client maintenance
- VSAT maintenance
- Provide disaster recovery plan sush as providing standby servers / recovery disks to provide backup incase of system failure
- Access to modules updates
- Access to sofware updates such as tomcat, MySQL