Case study 03 / Healthcare · Clinical product
Core modules for the SAP-recommended successor to IS-H
Technical direction of the roughly 30-engineer Tanbits account building the operations module, integrations module, BI modules and workflow engine for Avelios, the SAP-recommended successor to IS-H. Architecture, quality, client-facing leadership, delivery, and coordination between Tanbits directors and the client’s product organization.
- Client
- Avelios Medical
- Program
- Operations, integrations, BI modules and workflow engine
- Period
- 2023 – Present
- Employer
- Tanbits
- Role
- Tech Lead · technical direction of the account
- Team
- ~30 engineers
- Where
- Munich, Germany
The chapter: the frontier
Tanbits is a 120-person software house with offices in Lahore and Doha and a Boston association. I direct roughly 80 engineers through their team leads, across every web and mobile discipline, and own client handling, delivery, approvals, product decisions and market research alongside the directors. Second-line leadership: I manage the leads who manage the teams.
Over the past year the whole pipeline has run agentically. PRDs → AI development → AI Playwright testing → AI CI/CD → UAT → final delivery, on compound engineering with file-based durable state. Not AI tools bolted onto a team, but a development operating model.
The stakes. Velocity is worthless with quality drift. The system exists to make speed safe: PRDs as contracts, reviewer agents, and near-total, CI-enforced AI test suites.
The client
Avelios Medical was founded in Munich in 2020 and later took a strategic investment from SAP that made it the SAP-recommended successor to IS-H. Customers include Sana with 56 facilities, LMU University Hospital Munich, Hannover Medical School, Klinikum Stuttgart, which chose Avelios for a full SAP IS-H and i.s.h.med replacement via a Europe-wide tender, Städtisches Klinikum Braunschweig and Thoraxklinik Heidelberg.
The market context is unusual: SAP is exiting the hospital information system business, IS-H support ends around 2030, and up to 1,000 hospitals across Germany and Europe must replace their legacy HIS. The incumbents are Dedalus and CGM. Building a complete HIS is not for the faint-hearted, and that is precisely what Avelios is building.
The Tanbits account
Tanbits runs a roughly 30-engineer account for Avelios. I hold technical direction of it: architecture, quality, client-facing leadership, delivery, and the coordination between Tanbits directors and the client’s product organization.
The team builds four things: the operations module, the integrations module, the BI modules and the workflow engine. In a hospital information system these are not peripheral. Operations is where the hospital runs its day. Integrations is where a new HIS proves it can live alongside the lab, imaging, billing and national infrastructure that already exist. BI is how administrators see the hospital. The workflow engine is what lets clinical and administrative processes be modeled rather than hard-coded.
Why it is hard
Replacing legacy hospital IT is one of healthtech’s hardest problems. Migration windows are small, the cost of a wrong record is not abstract, and every customer hospital has decades of local process baked into the system being replaced. Delivering core modules for that from an offshore team means quality gates that hold under pressure and a leadership layer the client trusts. That is the job.
Where it sits in my career
Together with the NHCC work in Saudi Arabia, Avelios makes healthcare my deepest domain: national health infrastructure on one side, ministry asset management on Laravel; core clinical product on the other, a venture-backed European HIS on a modern stack.