Overview
Ormeda brings together modules that traditionally live in separate hospital applications, including medical imaging, into one platform. Resser is the sole engineering provider and a product co-owner, with a team of eight. It is piloting in seven clinics across Croatia, Germany, Pakistan and Brazil, with Videoreha integrated as one of its modules.
The challenge
Harmonising identities, roles and permissions across medical, orthopaedic and technical staff so a single platform could carry all of their workflows. Hospitals do not have one kind of user, and a permission model built for one group makes the software unusable for the others.
What we built
Built from zero on .NET 10 and ASP.NET Core with Blazor Server and WASM on the front, SQL Server behind it, and DICOM imaging handled through Cornerstone3D and fo-dicom. Stripe, Firebase, AWS SES and Vimeo are integrated where the workflows need them, with xUnit, Application Insights, OpenTelemetry and GitHub Actions carrying quality and operations.
Outcome
In pilot since 2025 across seven clinics in four countries, with Resser as the only engineering provider and a co-owner of the product. Medical imaging inside a general operating platform is unusual for a team this size, and it is the part that took the most engineering.
Frequently asked questions
What does sole engineering provider mean?
Everything technical is ours: architecture, backend, web, mobile, imaging, DevOps and QA. There is no second supplier and no internal engineering team to coordinate with.
Why does medical imaging matter here?
Because it is normally a separate system. Handling DICOM inside the same platform that carries scheduling and clinical workflows removes a whole integration layer, and the handling of it is regulated work rather than ordinary file storage.
Is Videoreha part of this?
Yes, it is integrated as one of the modules. The two products share engineering, which is one of the advantages of co-owning both.
Can this approach work outside healthcare?
The pattern can: one platform carrying workflows that usually need several systems, with a permission model that survives different kinds of user. The clinical and imaging parts are specific to this domain.
Further reading
Working on something similar?
We are always open to a short conversation about a project, even when the brief is still rough.