- Connectivity to the Internet and/or a local area network (for implementations with multiple locations)
- Computers, Anti-virus protection, and basic computer maintenance (e.g. a mouse stops working)
Many organizations lack the internal skills to deal with these issues , so but a combination of staff training and external support can be criticalof help.
Data entry clerks
Most health facilities have trained health records information staff who maintain data in the facility. Some facilities lacking lack such personnel and opt to train casuals a casual person equipped with basic computer skills to perform these duties.
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 in-between losing grid power and turning on the generator , and the suddden sudden 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.
You can connect your server (which stores all OpenMRS data) to the work stations where people enter data within your facility using:
- 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 wifiWiFi
- 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 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 classroom and departmental training depending on the 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 trainersTrainers(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 largely 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 such as providing standby servers / recovery disks to provide backup incase of system failure
- Access to modules updates
- Access to sofware software updates such as tomcat, MySQL