I wouldn't want to risk legacy proprietary medical applications for hardware interfaces into medical devices to be running on an API re-implementation layer that could easily be missing functionality, quirks and bug-for-bug compatibility.
CrossOver Office (the commercial version of Wine) is basically authored by picking particular versions of particular software that they want to get working, and then treating them as unit tests to write code against. When the program works, the library works. No more or less is needed.
According to what an ex-coworker told me, you only wish all medical software using Windows as an OS was remotely well maintained, tested, and vetted as MS Office.
For example, I worked for a company that was still coming across data corruption issues from time to time after a move between a platform where all memory was zeroed by default to Linux (where it isn't). Plenty of places were memory was allocated, and just used without zeroing it, and then jamming the whole thing into a database as a string.
As for most security cases, the best security is at the network level. Endpoint protection can protect after detection, while a good firewall will burn anything that moves in the wrong way.