IntelliMedsol

An aging legacy system, surrounded by the workarounds legacy systems breed: department-level tools that didn't talk to each other, duplicate data entry as staff re-keyed the same patient information into different screens, and reporting that meant extracting from several places and reconciling by hand. Nothing was on fire — which is exactly why systems like this survive for years — but every administrative process paid a quiet tax, and management decisions waited on reports that took hours to assemble.

The brief for IntelliMedsol was consolidation with continuity: replace the legacy system and the silo tools around it with one platform, without interrupting a hospital environment that cannot simply pause while software changes underneath it. That constraint — a live clinical operation as the deployment target — shaped every technical decision more than any feature request did.

IntelliMedsol is a multi-module ASP.NET MVC backend with an Angular single-page frontend over SQL Server — deliberately mainstream technology for a system a hospital will run for a decade. The modules mirror how the hospital actually works: clinical workflows, diagnostic records, patient data, and billing each live in their own module, sharing one data model instead of passing exports around. Data-ingestion pipelines brought the existing records across from the legacy system and its satellite tools, so the platform started life already knowing the hospital's history rather than as an empty shell.

Role-based access control runs through everything: clinical staff, administrative staff, and management each see the modules and records their role justifies — a compliance requirement in a healthcare environment, but also a usability one. A records clerk and a department head don't need the same screens, and giving everyone everything is how hospital software becomes unusable.

The specific win is patient and billing reconciliation reporting. Before IntelliMedsol, producing a reconciled view of patient activity against billing across departments meant pulling from the legacy system and separate departmental records, then aligning them manually — a job measured in hours, repeated routinely. On the platform, patient, diagnostic, and billing records share one data model, so the same reconciliation is a query, not a project: management runs it from a live dashboard in minutes.

That's the pattern worth generalizing: most 'reporting problems' in hospital administration are actually data-model problems wearing a reporting costume. Once the records are unified and role-appropriate access is solved, the reports stop being work.

The platform runs live at Horizon Medical World across six to ten departments with a user base of roughly 50 to 150 staff spanning clinical, administrative, and management roles. It is the system of record for the workflows it covers — not a pilot, not a parallel run alongside the old tools, but the replacement. For a solo-architected build in a healthcare environment, that production status is the credential: hospitals do not keep software in the critical path out of politeness.