Since the Intelehealth platform primarily uses OpenMRS as a backend database, its important to understand the data model and information model. In this section we will learn about how information is stored in OpenMRS, the database schema and key tables that are used by the Intelehealth platform. An easily searchable version of the data model can be found here. In addition to this page, we also recommend you read this section from the OpenMRS Implementer guide that explains the same concepts in further detail. This page assumes a base level knowledge of relational databases.
Person
Anybody with a record within the system is a person. A person may be a patient, a user of the system like a receptionist or a doctor. The following tables store data about persons like the person’s name, address, date of birth, gender, etc.
...
This wiki section describes the Concept dictionary in detail. We recommend reading this section in detail since the concept dictionary is an important core of the platform.
| Info |
|---|
In order to make an implementation easier, we provide a |
...
Data Dictionary with each new release of the Intelehealth platform that contains basic data needed in the above mentioned tables (such as encounter types, person_attributes and all the concept tables.) |
Metadata
Metadata means data about data. For each data entry in the OpenMRS tables there is a uuid (encounter_uuid, visit_uuid, obs_uuid, person_uuid), this uuid is used in the REST API to request for resources. Data can be voided or unvoided, a better practice than deleting data. Each entry also contains metadata like the creator, date_created, date_updated, date_started, voided_by, date_voided, void_reason.
...
This is one of the most important sections of the wiki to understand since the data and information model drive the platform’s flexibility.