Medical Device Interoperability Workshop
The purpose of the workshop is to facilitate discussion…on issues related to safe and effective interoperable medical devices.
The purpose of the workshop is to facilitate discussion…on issues related to safe and effective interoperable medical devices.
While designers of such systems like to say it is “just an aid” and thereby in part try to avoid responsibility for the quality of the output, the likely reality is that it will be relied upon, and therefore a high level of performance should be assured.
Unfortunately for you, congress did not wish to extend the physician exemption to hospitals.
Any software that receives and manipulates patient data is a medical device.
The same vague promises of working out an industry standard after the fact were made when WMTS was created.
If a medical device system runs on a network (physically separate or as a VLAN on your hospital enterprise network) the network is part of the medical device.
The ability to support third party apps on a PC that’s a medical device is highly dependent on the design approach and verification testing used by the manufacturer.
One should not mistake past regulatory discretion for lackadaisical enformcement on the part of the FDA.
What are your risks in being part of a regulated device, and what can you do to make yourself a more attractive supplier?
Gulp. This makes the initial R&D costs seem like a bargain.