I work on a similar project but WinForms, but not as mission critical as a hospital setting. I'm currently decoupling UI from application logic as much as possi

I work on a similar project but WinForms, but not as mission critical as a hospital setting. I'm currently decoupling UI from application logic as much as possible, and will move from .Net Framework to .Net Core 3.0 when it launches this year. At that point, I'll begin replacing WinForms with client-side Blazor. When there's just one current version of .Net again with .Net 5's release in 2020, those transitions will be seamless since I'll already be on .Net Core 3.0. Full-stack C# which grants me easy flexibility on what I want to happen client vs server-side, with near-native performance. I can drop a Safari shortcut on home screens for iOS, and an Edge link on desktops for Windows. If you wanted some sort of iOS specific behavior that you can only access from there, the application could be wrapped in a webview. It'll also be seamless to package it as an Electron app for Ubuntu support. I don't intend to go with Electron or put it in a native iOS app, just browser links for whatever platform they want to use, but there's plenty of flexibility. This is a webapp-done-right in my opinion and really a PWA. Perhaps the path I've set out for myself would work for you. The application I work on is critical to the daily functions of a large business, but not "medical grade", so I may be able to work on the knife's edge a bit more.