MajstroMajstro

KCH - Unified Patient Care and Operations Into One Platform

KCH - Unified Patient Care and Operations Into One Platform
Web Redesign
Web App Development
System Integration

Key Outcomes

  • Unified Platform: Multi-department coverage spanning management, administration, doctors, and nursing
  • 100% Role-Based Security: Secured access tiers restricting sensitive medical and financial data

Client Snapshot

  • Client: Kandy Central Hospital
  • Industry & Business Type: Multi-department hospital covering hospital leadership, doctors, nursing staff, and administrative teams
  • Geography: Kandy, Sri Lanka
  • Departments Served: Management, Administration, Clinical (Doctors & Theatres), Front-desk / Nursing
  • System Users: Two role tiers - Admin (full access) and User (patient & visit operations)
  • Why They Came to Us: Kandy Central Hospital needed one system that could carry a patient's entire journey-admission, treatment, room and theatre allocation, billing, and reporting-without staff having to work across disconnected tools or manual registers. They needed a platform structured enough for management-level oversight, yet simple enough for daily use at the front desk.

The Challenge

Like many hospitals running critical operations without a unified system, Kandy Central was constrained by process, not ambition. The operational gaps below shaped everything that was built.

Specific Pain Points & Solutions

Specific Pain PointsWhat They Actually Needed
Manual Partial Payment Tracking: Manual, largely undocumented tracking of partial payments left staff dependent on memory and scattered notes to determine what patients had paid versus what remained outstanding, increasing the risk of missed or miscalculated balances.Structured partial payment tracking with a dedicated report showing what's outstanding.
Uncoordinated Resource Management: Hospital resources such as doctors, procedures, theatres, and rooms were managed independently of one another, with no centralized system to coordinate availability, creating inefficiencies and making real-time oversight nearly impossible.Dedicated modules for doctors, procedures, theatres, rooms & beds, and bill items.
Lack of Leadership Visibility: Hospital leadership lacked a consolidated way to monitor revenue, doctor performance, and lab activity, forcing them to gather fragmented data from multiple sources and slowing down informed, timely decision-making.Built-in reporting covering revenue, partial payments, doctor performance, and lab revenue.
Data Security & Accountability Risks: Sensitive hospital and financial data was accessible to anyone using the system, with no distinction between what administrative staff, doctors, or front-desk teams were actually meant to see or handle.Secure, role-based login with two access tiers (Admin and User), so each person only sees the data and functions relevant to their responsibilities.
Fragmented Patient Records: Patient records, visit histories, and admission details were scattered across manual registers and disconnected processes, making it difficult to track a patient's full journey from admission through discharge and billing.A unified Patients and Visits module that keeps registration, visit history, bills, refunds, and admission updates all in one continuous record.

How We Worked

The platform was delivered across four core implementation phases and an ongoing maintenance phase over four months-moving from initial requirements to a fully operational system without disrupting live hospital operations.

  • Phase 1: Discovery & Planning (Weeks 1–2)
  • Focus: Requirements gathering across management, admin, and clinical teams; role mapping; data model and system architecture definition.
  • Phase 2: Build UI Prototype (Weeks 3–8)
  • Focus: Core Admin and Management modules-doctors, procedures, bill items, theatres, rooms & beds, patients, and visits-with secure role-based authentication.
  • Phase 3: Reporting & Billing Systems (Weeks 9–12)
  • Focus: Overview dashboards (revenue, partial payment, doctor, lab reports); implementation of five bill and receipt types; partial payment logic.
  • Phase 4: Integration & Launch (Weeks 13–16)
  • Focus: End-to-end testing, staff training across all roles, system go-live, and handover.
  • Phase 5: Maintenance (Weeks 17+)
  • Focus: Continuous monitoring, performance analysis, and post-launch system support.

Throughout delivery, Kandy Central's admin and management teams reviewed each module as it was built, keeping the platform aligned to how staff actually work, phase by phase.

What We Built

A single web platform structured around three core operational areas-Overview, Admin, and Management-ensuring every role works from the same system.

Core Modules & Platform Structure

A single web platform structured around three core operational areas-Overview, Admin, and Management-ensuring every role works from the same system.

Core Modules & Platform Structure


                  Kandy Central Hospital Web Platform
                                   |
 +---------------------------------+---------------------------------+
 |                                 |                                 |

OVERVIEW                           ADMIN                          MANAGEMENT
|                                 |                                 |
• Revenue Report                  • Doctors                         • Patients
• Partial Payment Report          • Procedures                      • Visits
• Doctor Report                   • Bill Items                      • Schedules (Doctor & Theatre)
• Lab Revenue Report              • Theatres
• Rooms & Beds
• Configurations
  • Overview - Reporting at a Glance: Gives leadership a clear, centralized view of hospital performance. Features a consolidated dropdown with the Revenue Report, Partial Payment Report, Doctor Report, and Lab Revenue Report.
  • Admin - Full Operational Control: Accessible by the Admin role to manage doctors, procedures, billable items, operating theatres, rooms/beds availability, and system configurations (item/procedure categories, units, doctor ranks/specializations, room categories).
  • Management - Day-to-Day Operations: Used daily by both Admin and User roles to handle patient registration, visit histories, active bill items, refunds, admission updates, and schedules for doctors and operating theatres.

Role-Based Access Control (RBAC)

System AreaAdmin RoleUser Role
Overview ReportsFull AccessRestricted
Admin ConfigurationFull AccessRestricted
Patients & VisitsFull AccessFull Access

Billing & Financial Workflows

The platform automates five key billing documents and supports flexible payment handling:

  • Split & Partial Payments: Allows patients to pay in two installments while automatically logging remaining balances on outstanding payment reports.
  • Automated Documents: Generates Detail Bills, Final Bills, Inpatient Receipts, Doctor Fee Entry Bills, and Cash Receipts directly from the platform.

Results & Impact

The platform replaced disconnected, manual processes with one structured system-giving every role the exact tools built for their daily responsibilities.

  • One Platform, Every Role: Management, admin staff, doctors, and nursing all work from the same system instead of separate tools or paper processes.
  • Full Financial Visibility: Revenue, partial payments, and lab revenue are tracked and reportable in real time, not reconciled after the fact.
  • Faster, Safer Resource Management: Doctors, procedures, theatres, rooms, and beds are managed centrally with clear availability at a glance.
  • Flexible Patient Payments: Patients can pay in installments, with the partial payment report showing exactly what remains outstanding.
  • Built-in Access Control: Role-based login means sensitive hospital and financial data is only visible to the people who need it.
  • A Complete Patient Journey: From admission and room assignment to discharge and final billing, the full visit lifecycle lives in one place.

Want results
like these?