Building Scalable Platforms with Modern Tech Stacks

Scalability isn't just about handling more users; it's about designing systems that grow with the organisation — and that holds true for a hospital just as much as a tech startup.

The MedCore HMS Story

When St. Aloysius Hospital first approached us, they had paper records and manual billing. We built MedCore HMS as an on‑premise solution with React, ASP.NET Core, and PostgreSQL. But the real challenge came when St. Mary's Joint Hospital adopted the same system. Suddenly we had to support two independent installations with different workflows, yet keep the codebase maintainable.

Key Architectural Decisions

• Role‑Based Access: Each hospital could configure its own roles (reception, cashier, lab, etc.) without code changes.
• Modular Licensing: Hospitals activate only the modules they need — a small clinic might skip the imaging module, while a larger facility enables everything.
• Real‑Time Updates: Using SignalR, we ensured that when a doctor places an order, the lab and cashier see it instantly, reducing patient wait times by 35%.
• Companion Online Portal: A separate .NET service syncs summary data to a cloud dashboard for remote oversight by hospital management.

Lessons for Scalable Design

1. Plan for multi‑tenancy early. Even if you start with one client, design your schema to support multiple sites from day one.
2. Make role definitions flexible. Hardcoding roles per institution leads to brittle code.
3. Keep deployment simple. MedCore HMS is packaged as a Windows installer — a single .exe that sets up the database, API, and frontend. That simplicity was key to adoption.

Scalability isn't about Kubernetes clusters and microservices by default; it's about making the system easy to adapt, deploy, and maintain as needs evolve.