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 kay key tables that are used by the Intelehealth platform. An easily searchable version of the data model can be found here.
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.
...
If there are additional pieces of information that need to be captured about persons that are not included in the above tables, we can define a person_attribute_type (for example educational status or race). The values of the attribute for each person is stored in the person_attribute table.
...
Patient
A Patient is a child of the Person class. All entries within the person table who are patients are mapped in the patient table with the person_id.
| Info |
|---|
The person_id and patient_id are always the same. These are the primary keys for the person table and patient table respectively. |
A patient may have multiple identifiers, the default identifier in OpenMRS is the OpenMRS ID.
| Info |
|---|
The OpenMRS Identifier is an automatically generated identifier by the Idgen Module. It is a 6 digit alphanumeric ID, the 6th digit is a checksum digit (eg: 1004D-3). From OpenMRS Platform version 2.1.4 the identifier is 7 digits where the 7th is the checksum digit. This wiki post provides more information about administering patient identifiers. |
...
User
Provider
Location
Visits
Encounters
Obs
| Table of Contents |
|---|