OpenMRS Data Model Documentation

1 Introduction
2 Domains
3 Data Model FAQ
4 Suggestions

Welcome to the OpenMRS Data Model documentation wiki!

Introduction

At the heart of any enterprise electronic medical record system lies a robust, explicit representation of how care information is stored. The structure of this data model dictates the scalability and flexibility of a system. The OpenMRS collaborative therefore invests continuous effort into shaping the OpenMRS data model using knowledge and experience gleaned from practical experiences from the Regenstrief Institute, Partners in Health, and all of our developmental partners around the world. The core of this data model addresses the who, what, when, where, and how of medical encounters. You may view a current image of the data model. This model is divided into seven basic domains:

[edit]

Domains

Concept: Concepts are defined and used to support strongly coded data throughout the system
Encounter: Contains the meta-data regarding health care providers interventions with a patient.
Form: Essentially, the user interface description for the various components.
Observation: This is where the actual health care information is stored. There are many observations per Encounter.
Order: Things/actions that have been requested to occur.
Patient: Basic information about patients in this system.
User: Basic information about the people that use this system.

[edit]

Data Model FAQ

Q: We really like your data model image. How does OpenMRS make it?

A: We found a useful, open-source tool, DBDesigner, which we used to build and manipulate the data model in a rich graphical interface. However, this project has evolved into a new suite, MySQL Workbench, which has the potential to be an improvement.

[edit]