PATH DRC EMR Documentation

Welcome to the documentation for PATH DRC EMR, an OpenMRS 3.0-based Electronic Medical Record system designed for PATH DRC healthcare facilities.

What is PATH DRC EMR?

PATH DRC EMR is a containerized distribution of OpenMRS 3.0, configured specifically for healthcare facilities in the Democratic Republic of Congo. It provides a complete, ready-to-deploy EMR system with:

  • Modern web-based interface (OpenMRS 3.0 SPA)
  • Pre-configured metadata and workflows
  • Site-specific customizations
  • Automated backup capabilities
  • Support for both online and offline deployments

Choose your path based on what you need to do:

I want to deploy PATH DRC EMR

Start here if you’re setting up a new installation.

Getting Started Online Installation Offline Installation

I want to operate an existing system

Manage day-to-day operations, backups, monitoring, and troubleshooting.

Operations Guide Backup & Restore User Management

I want to customize for my site

Configure site-specific settings, add new locations, or manage metadata.

Administration Guide Adding Sites Metadata Management

I want to contribute to development

Build images locally, understand the architecture, or contribute code.

Development Guide Architecture Contributing

System Architecture

PATH DRC EMR consists of five main components:

graph TB
    Client[Web Browser] -->|HTTP| Gateway[Gateway<br/>nginx reverse proxy]
    Gateway -->|/openmrs/spa/*| Frontend[Frontend<br/>OpenMRS 3.0 SPA]
    Gateway -->|/openmrs/| Backend[Backend<br/>OpenMRS Core]
    Backend --> DB[(MariaDB<br/>Database)]
    Backup[Backup Service<br/>Restic] -.->|Scheduled| DB
    Backup -.->|Data Volumes| Backend

    style Client fill:#e1f5ff
    style Gateway fill:#fff4e6
    style Frontend fill:#e8f5e9
    style Backend fill:#e8f5e9
    style DB fill:#fce4ec
    style Backup fill:#f3e5f5

Components:

  • Gateway: Nginx reverse proxy handling routing and CORS
  • Frontend: OpenMRS 3.0 Single Page Application
  • Backend: OpenMRS server with modules and configuration
  • Database: MariaDB for data persistence
  • Backup: Automated backup service using Restic

Learn more about the architecture

Key Features

Site-Specific Configurations

Deploy with pre-configured settings for specific facilities (e.g., Akram, Libikisi) or use the base distribution.

Online and Offline Support

Install with internet connectivity or use pre-packaged bundles for air-gapped environments.

Automated Backups

Built-in backup and restore capabilities with support for local and cloud storage backends.

Modern Interface

OpenMRS 3.0 provides a fast, intuitive web interface optimized for clinical workflows.

Need Help?