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 ten basic domains.
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.
- Person: Basic information about person in the system.
- Business: Non medical data used to administrate openmrs
- Groups/Workflow: Workflows and Cohort data
Data Model Frequently Asked Questions (FAQ)
- What is the difference between retire and void columns?
- What are the conventions for changing the OpenMRS data model definition?
- We really like your data model image. How does OpenMRS make it?
Other
- Download an SVG version
- Download a MySQL Workbench version (requires MySQL Workbench)
