Implementation is the process of business analysis, system customization, server installation and configuration, user training and support, with the aim of collecting data for analysis and decision making purposes.
These documents describe how to implement OpenMRS.
- Getting Started with OpenMRS
- OpenMRS from Scratch
- Field Guide
- The EHSDI Training Course, section 202, which covers implementation
There is an "Openmrs Book" / Guide online as well: om.rs/guide
This should discuss how you define your problem, set goals and scope. Who are your users? What do they want? Do you have funding for equipment and support? What do you want? Will OpenMRS fit your needs? Should add a checklist and/or grid with features. (copy from Field Guide?)
Once you have chosen OpenMRS, what are the preliminary steps.
Initial Setup - From Beginning to Launch
- Role and User development
- OpenMRS uses roles to manage permissions. Typical roles include:
- system administrator - configures OpenMRS, installs and updates modules, manage user accounts
- registrars - adds new patients to OpenMRS at check-in; adds patients to programs
- data entry clerk - creates and updates encounters after a visit
- care providers - views patient records at point of care; creates or updates orders or encounters; assigns regimens
- content editors - creates or updates the forms that collect encounter data; adds or changes concepts in the concept dictionary; adds or updates programs
- Users, roles, and permissions are managed through the administrator control panel at Administration > Users.
- Deciding what information to collect
- patient attributes
- Concept development
- Form development
- Some best practices for implementations
- Data migration
- Receiving information from external applications into OpenMRS
Ongoing Support - Launch and Beyond
- Begin with the Administrator Guide.
- System maintenance and performance
- Managing multiple servers
- User administration
- Managing metadata
- Concept administration
- concept-related modules
- Default concept dictionary
- Millennium Villages Project dictionary
- Maternal concept lab - The Maternal Concept Lab exists to unify and amplify efforts to use mobile devices to improve maternal health primarily in resource-poor settings. This site is a resource for organizations looking to utilize mHealth for maternal health, to improve interoperability and component sharing, and to foster experience sharing about building and using such tools
- other concept related projects
- Import/export of metadata
- The Metadata Sharing Module allows all kinds of metadata (concepts, htmlforms, locations, roles, programs, etc.) to be exchanged between different OpenMRS installations. It supports metadata defined in the core as well as in modules provided appropriate handlers are registered. Conflicts between local and incoming metadata can be identified and resolved. The module can be used both through an API and a web interface.
Reporting and Data Analysis
- The Reporting Module is the most popular tool for generating reports. It's extensively documented; see the module's project page.
- AMPATH exports data through SQL for analysis with other tools
- De-identifying data to protect patient privacy
- Data policy (IRB, country and/or organization restrictions, encryption)
- Data analysis in OpenMRS
- There is a proof of concept project to use Pentaho for analysis
- OpenMRS concepts can be mapped to medical coding standards and other terminology sets, such as ICD-10, SNOMED, etc. Read more about mapping.