OpenMRS

Introduction
OpenMRS Around the World
A Brief History
Example: Amani Clinic
Planning
Is OpenMRS for You?
Identifying Your Needs
Transitioning to OpenMRS
Getting Started
Installation and Initial Setup
OpenMRS Information Model
Getting Around the User Interface
Configuration
Customizing OpenMRS with Plug-in Modules
Managing Concepts and Metadata
Sharing Concepts and Metadata
Configuring Visits
Collecting Data
The Patient Dashboard In Depth
Registering Patients
Data Entry
HTML Forms
XForms
Using Data
Cohort Builder
Reporting
Patient Alerts and Flags
Administering OpenMRS
User Management and Access Control
Maintenance
Troubleshooting
Getting Help from the OpenMRS Community
Epilogue
Leaving Amani Clinic
About this Book
Appendices
Appendix A: Glossary
Appendix B: Example HTML Form Source
Appendix C: Document History

Data Entry

An OpenMRS data entry clerk in Masaka, Uganda.

An electronic medical records system has many advantages compared to a traditional paper-based system. Data is collected using electronic forms, and a standard template means that each user sees the same structure, simplifying the representation of the underlying information structure and complexity. Electronic forms also allow for basic data validation.

An administrator must design the form templates that data clerks will use. There are three forms modules in OpenMRS. An OpenMRS installation may use more than one style, but for simplicity, it's recommended you begin with one. They are compared below.


Form Type	Advantages	Disadvantages
HTML Forms	Easy to use Ongoing development of new features Supports complex logic operations Extendable Allows review of forms after submission	Requires HTML knowledge Not supported on mobile devices
XForms	Open source Easy to use Works well on mobile devices	Does not support some complex logic operations
InfoPath	Original approach to data entry via forms Others may already be familiar with the technology	Not open source Runs only on Windows Requires payment of license fees No new development by the OpenMRS team

The next chapters describe HTML Form Entry and XForms in more detail.

InfoPath forms, created with the FormEntry module and Microsoft InfoPath, are not recommended. Microsoft InfoPath is proprietary software, and the forms are difficult to troubleshoot. InfoPath forms will continue to work, but there will be no new development.