Hikma Health Hikma Health

Introduction

Key Concepts

Core data concepts in Hikma Health and how they relate to each other.

Key Concepts

This page describes the core data concepts in Hikma Health and how they relate to each other. Understanding these concepts will help you make the most of the system when recording and managing patient data.

Patient Records

A patient record is the central entity in Hikma Health. Every visit, event, appointment, prescription, vital sign, and diagnosis is linked to a patient.

Patient registration forms are fully dynamic. Administrators create and customize registration forms through the admin portal. This means the fields you see when registering a patient are configured by your organization β€” not hardcoded into the app.

Every patient has a set of base fields that are always available:

FieldDescription
Given namePatient’s first name
SurnamePatient’s last name
Date of birthIn YYYY-MM-DD format
SexMale or female
PhoneContact number
HometownPlace of origin
CitizenshipNationality
CampRefugee camp or settlement (if applicable)
Government IDNational or government-issued ID
External patient IDID from referral systems or other sources
PhotoOptional patient photo

Beyond these base fields, your organization can define custom fields of various types β€” text, number, date, select dropdown, checkbox, and boolean β€” through the admin portal. Custom field values are stored as patient additional attributes linked to the patient record.

Visits

A visit represents a single patient encounter at a clinic. When a patient arrives and is seen by a provider, a visit is created to group together everything that happens during that encounter.

Each visit records:

FieldDescription
PatientThe patient being seen
ClinicWhere the visit takes place
ProviderThe healthcare worker conducting the visit
Check-in timeWhen the patient was checked in

A visit on its own is a container. The clinical data collected during the visit is stored as events within that visit.

Events and Event Forms

Events are the primary way clinical data is recorded during a visit. Each event is a submission of an event form β€” a dynamic form designed by administrators in the admin portal.

Event forms are fully dynamic. Your organization defines what forms are available, what fields they contain, and which clinics can use them. This means the clinical data you collect is entirely customizable to your workflows. Common examples include history-taking forms, physical examination forms, treatment forms, and counseling forms.

Event form fields support a range of input types:

  • Free text and numbers
  • Radio buttons and checkboxes
  • Date pickers
  • Dropdown selects
  • Diagnosis fields (with ICD code search)
  • Medication fields (with dosage details)
  • File uploads
  • Grouped inputs

Each event stores the completed form data, the form template it was based on, and which provider recorded it.

Vitals

Vitals are structured recordings of a patient’s physiological measurements. They are recorded as dedicated entries within the patient file and can optionally be linked to a specific visit.

The following measurements are supported:

Vital SignUnit
Systolic blood pressuremmHg
Diastolic blood pressuremmHg
Blood pressure positionSitting, standing, or lying
Heart ratebpm
Pulse ratebpm
Oxygen saturation (SpO2)%
Respiratory ratebreaths/min
TemperatureΒ°C
Heightcm
Weightkg
BMICalculated
Waist circumferencecm
Pain level0–10 scale

Note: We strongly recommend using the dedicated vitals entry within the patient file to record vital signs, rather than capturing them through event forms. Dedicated vitals entries are stored in a structured format, making them easier to track over time, trend, and query across patients. When vitals are embedded in event forms, they are stored as free-form data and lose this structure.

Diagnoses

Diagnoses (also referred to as patient problems) are structured records of a patient’s clinical conditions. They are recorded as dedicated entries within the patient file and use standardized medical coding.

Each diagnosis entry captures:

FieldDescription
Problem codeA standardized code (ICD-10 or ICD-11)
Problem labelHuman-readable description of the condition
Code systemWhich coding system is used (ICD-10, ICD-11, SNOMED)
Clinical statusActive, in remission, resolved, or unknown
Verification statusProvisional, confirmed, refuted, or unconfirmed
Severity scoreOptional, on a 1–10 scale
Onset dateWhen the condition started (optional)
End dateWhen the condition resolved (optional)

The app includes a built-in ICD-11 diagnosis search that lets providers search by code or description using fuzzy matching, making it fast to find the right diagnosis.

Note: We strongly recommend using the dedicated diagnosis entry within the patient file to record diagnoses, rather than capturing them through event forms. Structured diagnosis entries use standardized codes, support clinical and verification statuses, and enable meaningful reporting across your patient population. Diagnoses embedded in event forms lack this structure and are harder to aggregate.

Appointments

Appointments track scheduled and walk-in patient visits. They support multi-department routing, allowing a single appointment to be tracked across multiple departments within a clinic.

Each appointment records:

FieldDescription
PatientWho the appointment is for
ClinicWhere the appointment takes place
ProviderAssigned healthcare worker (optional)
Date and timeScheduled appointment time
DurationExpected length in minutes (optional)
ReasonWhy the patient is being seen
NotesAdditional context
Walk-inWhether this is a walk-in rather than scheduled
DepartmentsWhich departments the patient needs to visit
StatusCurrent state of the appointment

Appointment statuses: pending, scheduled, checked in, in progress, confirmed, cancelled, completed.

For appointments that involve multiple departments, each department tracks its own status independently β€” including who saw the patient and when β€” so staff can see at a glance which departments the patient still needs to visit.

Prescriptions

A prescription is an order for one or more medications for a patient. Prescriptions can be linked to a specific visit and are assigned a priority and status to support pharmacy workflows.

Each prescription records:

FieldDescription
PatientWho the prescription is for
ProviderWho wrote the prescription
PriorityEmergency, high, normal, or low
StatusPending, prepared, picked up, partially picked up, not picked up, cancelled, expired
Pickup clinicWhere the patient should collect the medication (optional)
Prescribed atWhen the prescription was written
Expiration dateWhen the prescription expires
NotesAdditional instructions

Prescription Items

Each prescription contains one or more prescription items, each representing a single medication:

FieldDescription
DrugSelected from the drug catalogue
Dosage instructionsHow to take the medication
Quantity prescribedAmount ordered
Quantity dispensedAmount actually given
Refills authorizedNumber of refills allowed
Refills usedNumber of refills consumed
Item statusActive, completed, or cancelled

Dispensing

When a prescription item is dispensed, a dispensing record is created that tracks:

  • Which drug and batch were used
  • The quantity dispensed
  • Days supply
  • Who dispensed it and when

Dispensing is done from the pharmacy view, where staff can select specific inventory batches to fulfill each prescription item. Inventory quantities are updated accordingly.

Drug Catalogue

The drug catalogue is the master list of medications available across your organization. Each entry describes a single drug formulation:

FieldDescription
Generic nameNon-proprietary drug name
Brand nameCommercial name (optional)
FormTablet, syrup, capsule, cream, injection, etc.
RouteOral, IV, IM, topical, inhalation, etc.
Dosage quantityStrength per unit (e.g., 500)
Dosage unitsUnit of strength (e.g., mg)
ManufacturerDrug manufacturer (optional)
BarcodeFor scanning (optional)
Sale price / currencyCost information (optional)
Min / max stock levelFor inventory management
Controlled substanceWhether the drug is a controlled substance
Requires refrigerationCold chain flag
ActiveWhether the drug is currently in use

The drug catalogue is managed through the admin portal and synced to all devices. When creating a prescription, providers select medications from this catalogue.

Clinic Inventory

Each clinic maintains its own inventory, tracked by batch:

FieldDescription
DrugWhich drug from the catalogue
Batch numberManufacturer’s batch/lot number
Expiry dateWhen the batch expires
Quantity availableCurrent stock
Reserved quantityStock reserved for pending prescriptions
Last counted atMost recent physical count

How It All Fits Together

Patient
  β”‚
  β”œβ”€β”€ Visits
  β”‚     └── Events (dynamic form submissions)
  β”‚
  β”œβ”€β”€ Vitals (structured measurements)
  β”‚
  β”œβ”€β”€ Diagnoses (coded clinical problems)
  β”‚
  β”œβ”€β”€ Appointments
  β”‚
  └── Prescriptions
        └── Prescription Items
              └── Dispensing Records
                    └── Clinic Inventory (batch tracking)
                          └── Drug Catalogue

A patient comes to the clinic and either has a scheduled appointment or walks in. A visit is created for the encounter. During the visit, providers fill out event forms to capture clinical data, record vitals, and document diagnoses. If medication is needed, a prescription is created with one or more prescription items selected from the drug catalogue. The pharmacy staff then dispenses the medication from available clinic inventory batches.