Implementer Documentation
- Paul Biondich
- Grace Potma
- Dana Dolan
Overview
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.
Choosing OpenMRS
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?)
Requirements
Once you have chosen OpenMRS, what are the preliminary steps.
Implementations
The OpenMRS Implementation Survey describes several organizations' implementations
Case study: Rolling out OpenMRS in Rwanda
More examples and information are on the Implementation Projects page.
Initial Setup - From Beginning to Launch
Initial configuration is created by the Installation Wizard
Customizing look and feel
Change the default theme to a different color palette
Use the custom branding module to add your own logo
Add your own CSS files and login, registration, and dashboard JSPs by overriding the default runtime properties
Using OpenMRS modules
Finding and selecting modules is covered in detail in this OpenMRS Guide
The module repository contains descriptions, downloads, and documentation links for each module .
If you encounter a problem after installing a module, the first step is to stop and restart it from the Administration > Manage Modules page. It will show an error message if there was a trouble during startup. If the problem persists, stop the module and recheck the symptoms. This will confirm that the problem comes from that module. See the module's documentation for troubleshooting suggestions. You can receive further help from the Implementers mailing list.
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.
Patients
Identifiers
Overview: administering identifiers
the ID Generation and Registration modules generate identifiers.
The Registration module supports biometric ID through fingerprints.
best practices
Deciding what information to collect
patient attributes
caretakers
Registration
best practices
Concept development
How to translate an idea to a concept - read EHSDI training course EH202, lecture 4, "Concepts, Observations, and Encounters"
Jump start with the OpenMRS Concept Collaborative (OCC)
Mapping - why and how to map concepts
Form development
Implementation options - XForms, InfoPath, HTMLForms - HTMLform Implementers Training
Best Practices for Translating Paper Forms - HTMLform Implementers Training - slides 22-24, "Guidelines for Managing Forms"
Examples at the Form Bank
Receiving information from external applications into OpenMRS
Ongoing Support - Launch and Beyond
Begin with the Administrator Guide.
System maintenance and performance
Server management
Database and server backups
Managing multiple servers
Sync servers
VMs
Multiple instances on the same server (for development or testing)
Monitoring the status of java application using java melody
User administration
Administering users: Adding users, Disabling logins
Managing metadata
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
Standards
OpenMRS concepts can be mapped to medical coding standards and other terminology sets, such as ICD-10, SNOMED, etc. Read more about mapping.
Working with HL7
Thei2b2 module exports OpenMRS data in XML format