Multi-Tenant EMR Software for Fertility Clinicson .NET and Angular
A fertility network running 150+ clinics held patient data in disconnected systems, with no unified patient view and an eight-week onboarding process for every new location. Kansoft built one multi-tenant EMR platform covering the full IVF lifecycle, with billing and analytics built in.
150 clinics, one patient record that did not exist.
Indira IVF is one of India's largest fertility care providers, running more than 150 clinics that deliver IVF, ICSI and genetic diagnostics. Each clinic handles the full treatment journey, from first consultation through stimulation protocols, retrieval, transfer and pregnancy monitoring.
Growth had outpaced the systems underneath it. Patient data, clinical records and operational information lived in disconnected systems at individual clinics, so the organisation had no unified view of a patient and no reliable view of itself.
Architecture diagram for this engagement is being drawn.
Five constraints that came from running 150 clinics as 150 systems.
None of these were failures of any single clinic. They were consequences of an architecture that treated each location as its own island.
No unified patient view
Records were spread across disconnected systems, causing duplicate data entry and inconsistencies in treatment records between locations. A patient seen at two clinics effectively existed twice.
Manual operational workflows
Scheduling, billing and reporting relied on manual processes that were error-prone and slow. Staff time went to administration rather than patient care, and scheduling conflicts produced missed appointments.
Eight weeks to open a clinic
Onboarding a new location meant manual configuration, data setup and staff training. As expansion accelerated, that bottleneck became the limit on how fast the network could grow.
No centralised security governance
Sensitive patient records across 150+ clinics needed consistent access control and audit trails. The existing systems had neither, and the exposure grew with every location added.
Leadership flying blind
Organisation-wide reporting required manually aggregating data from individual clinics, taking up to seven days. Clinical outcomes, patient flow and revenue could not be seen across the network in any usable timeframe.
One multi-tenant platform, modelled on how clinicians actually work.
Generic clinic software forces fertility workflows into patterns built for general practice. We modelled the platform around the IVF lifecycle itself, then used a mature multi-tenant framework so engineering effort went into clinical workflow rather than rebuilding authentication and tenancy.
Architecture
A multi-tenant SaaS design balancing tenant isolation against shared infrastructure, so each clinic operates independently while benefiting from centralised updates and one codebase.
Domain modelling
The platform modelled around the full IVF lifecycle — consultation, diagnostic workup, stimulation protocols, retrieval, transfer and pregnancy monitoring — rather than a generic patient record bent to fit.
Accelerated build
ASP.NET Zero carried multi-tenancy, authentication, role-based access and audit logging, freeing the team to spend its time on the clinical workflows that differentiate the platform.
Analytics and security
A reporting layer covering clinical outcomes, patient flow and revenue, built alongside encryption, fine-grained access control, audit trails and consent management rather than added afterwards.
Chosen to put engineering time into clinical workflow.
Each choice removes work that is not specific to fertility care, so the build concentrates on the parts that are.
From 150 islands to one network that can see itself.
Four measured changes between the fragmented estate and the unified platform now running across every clinic.
Four changes that mattered as much as the numbers.
The platform removed the ceiling on expansion and gave leadership a view of the network it had never had.
A patient exists once
One record follows a patient across locations, so treatment history is complete wherever they are seen and clinicians stop reconstructing it.
Growth stopped waiting on IT
Opening a clinic is a configuration exercise rather than a project. The onboarding bottleneck that threatened the expansion plan is gone.
Leadership sees the network live
Clinical outcomes, patient flow and revenue are visible at clinic, regional and organisation level without anyone aggregating spreadsheets.
Revenue leakage closed
Integrated billing and automated invoicing contributed Rs 12M in the first six months, largely by recovering what the manual process had been losing.
How the work was shaped.
Fertility workflow understood, not approximated.
The difference between a usable clinical platform and an expensive one is whether the people building it understand stimulation protocols and embryo grading well enough to model them properly. Running as a dedicated team embedded with clinical and IT stakeholders meant that domain knowledge accumulated across the engagement rather than being re-explained each sprint, and the platform continues to evolve with the network rather than freezing at handover.
Related Case Studies
HIPAA-Ready Cloud Landing Zone for Healthcare on AWS and Terraform
A global IVF platform serving 250+ clinics moved to a multi-account AWS landing zone built with Terraform, cutting environment provisioning by 80%.
Xamarin to .NET MAUI Migration for Manufacturing Mobile Apps
A cement manufacturer moved three business-critical apps from end-of-life Xamarin to .NET MAUI in roughly 15 days each, all at UAT inside four weeks.
Procurement Modernization for Manufacturing on .NET 6 and Angular
A cement manufacturer re-engineered its ASP.NET Web Forms procurement platform into a .NET 6 and Angular stack on Azure, keeping every workflow intact.