Hospital Overview

Level 4 Hospital Overview & Operational Blueprint

1. Institutional Context & Healthcare Tiering

In the Kenyan healthcare ecosystem defined by the Health Act (2017) and managed by the Ministry of Health (MoH), a Level 4 Hospital (Primary Care Hospital) serves as a critical regional hub. It bridges the gap between community-based primary care facilities (Levels 2 and 3) and tertiary referral centers (Levels 5 and 6).

1.1 Socio-Economic and Infrastructure Realities

Operating a Level 4 facility in Western Kenya introduces specific infrastructural and economic operational parameters that the HMIS must natively accommodate:

• Intermittent Power & Network Connectivity: Infrastructure must withstand rolling blackouts and frequent fiber cuts. The system is deployed on-premise across dual physical nodes with automated local synchronization.
• Highly Constrained Patient Purchasing Power: Patients often lack upfront cash, relying on specialized funding streams. Out-of-pocket payments require flexible, atomic processing, allowing partial payments down to the single medication level.
• The Transition from NHIF to SHA: The system must interface with the Social Health Authority (SHA) and its component funds:
  • Primary Healthcare Fund (PHF): Covering outpatient services at Level 4 facilities without out-of-pocket copayments.
  • Social Health Insurance Fund (SHIF): Governing complex inpatient packages and specialist interventions.
  • Emergency, Chronic, and Critical Illness Fund (ECCIF): Providing financial coverage for immediate stabilization of trauma, ICU admissions, and critical diagnostic pathways.

2. Clinical Governance & Organizational Structure

The facility operates under a strict, multi-tiered hierarchy where administrative authority supports clinical accountability. The HMIS enforces this hierarchy via Role-Based Access Control (RBAC), conditional electronic signatures, and multi-stage workflow approvals.

2.1 Governance Hierarchy

2.2 Operational Roles and System Responsibilities

3. High-Level Patient Lifecycles & Routing

Patient routing through the Level 4 facility is divided into two primary lifecycles: Outpatient (OPD) and Inpatient (IPD), joined by emergency and diagnostic loops. The system models every patient interaction as an atomic Encounter nested within a broader, financial Billing Session.

3.1 Global Routing Architecture

4. Financial Core Realities & System Adaptations

The HMIS avoids idealized billing workflows in favor of defensive software engineering tailored to local financial edge cases.

4.1 Tiered Multi-Channel Revenue Processing

The billing engine maintains an atomic transaction log where a single encounter can split its liability across multiple payers:

{
  "encounter_id": "enc_982347102_level4",
  "patient_id": "pat_019234812_mpi",
  "total_billed_kes": 4200.00,
  "splits": [
    {
      "payer_type": "SHA_PHF",
      "allocation_kes": 1500.00,
      "status": "APPROVED",
      "pre_auth_code": "SHA-PHF-2026-09812"
    },
    {
      "payer_type": "PRIVATE_INSURANCE",
      "payer_name": "Jubilee Insurance",
      "allocation_kes": 2000.00,
      "status": "PENDING_PRE_AUTH",
      "pre_auth_code": "JUB-AUTH-77621"
    },
    {
      "payer_type": "CASH",
      "allocation_kes": 700.00,
      "status": "PAID",
      "receipt_number": "TXN-MPESA-8823192"
    }
  ]
}

4.2 Handling Complex Financial Edge Cases

Partial Payments for Pharmacy Items: If a patient is prescribed a full 30-day course of an antibiotic but can only afford a 10-day supply, the system splits the prescription. It marks 10 days as Dispensed, 20 days as Owed/Pending Financial Clearance, and generates an external source tracking flag if the patient chooses to buy the rest elsewhere.

Treatment on Credit / Corporate Guarantors: For corporate accounts (e.g., county government staff, local sugar factory employees), services are rendered against pre-configured credit lines. The system blocks treatment if an account's credit ceiling is breached, requiring an authenticated administrative override.

Broken Billing Loops: A frequent cause of revenue leakage occurs when clinicians provide informal bedside service extensions or send patients directly to diagnostic areas without system orders. The system mitigates this by making billing checks mandatory at the hardware interface level: the barcode scanners on laboratory analyzers will not accept a sample tube unless its corresponding electronic order carries a signed payment/exemption token.

5. Automated Clinical Exemption Paradigms

To prevent manual manipulation of clinical fees while maintaining fluid patient care, the HMIS embeds automated billing bypass rules within the database controller layer.

5.1 The 7-Day Clinical Review Rule

Patients returning to the facility for a follow-up or review of an ongoing medical issue within 7 days of their primary paid outpatient encounter are exempt from paying a new consultation fee.

5.2 Post-Surgical Care Windows

Major surgical procedures carry an inherent, standardized global care window (typically 14 to 30 days depending on the procedure's complexity). All post-operative checks, wound dressings, and routine stitch removals within this window are structurally exempt from consultation and basic nursing procedure fees. The system tracks this by checking for an authenticated Operative Report within the patient’s longitudinal EHR history.

6. Legacy System Interdependencies

The implementation of this modular monolith involves replacing a legacy Java/Spring Boot desktop application that currently holds five years of historical patient data. The system must maintain continuity throughout this transition.

6.1 Data Migration Pipeline Architecture

The migration strategy avoids bulk, big-bang updates. Instead, it utilizes an automated extraction pipeline running in parallel with the production deployment.

6.2 Key Data Dependencies for System Go-Live

The migration pipeline must successfully ingest and normalize several primary legacy datasets before decommissioning the older application:

Master Patient Index (MPI): 45,000 unique patient identity records containing demographic details, National IDs, and contact numbers. These are deduplicated and cleansed using a Jaro-Winkler string distance matrix (To be reviewed).

Longitudinal Medical Records: Historical ICD-10 codes, which are programmatically mapped to the new WHO ICD-11 taxonomy using structural translation maps.

Opening Financial Ledger: Unsettled corporate credit bills, outstanding patient balances, and active inventory asset counts across the primary and satellite pharmacies.