Overcoming Common Compliance Issues for Medical Software
Questions? Request more information from our specialists
CONTACT US
One of the areas of significant growth in medical devices has been the role of software. It can function as an integral component of a medical device, as a standalone device, or, more recently, as an application on mobile devices.
Unfortunately, it's not always clear what regulations apply to software. Regulatory authorities across the globe have provided little (or confusing) guidance, leaving developers to question: When is software considered a medical device?
In this white paper:
- The IEC 60601 standard and medical device software
- IEC 62304 for stand-alone and component medical device software
- IEC 82304: A dedicated health software system standard
About the Author:
Brian Goemans is the Country Manager, South Africa and a Senior Consultant at Emergo. Brian is a biomedical engineer with more than 20 years of experience in medical device product design and development, and 15 years in medical device regulations. His expertise includes hardware and software development for medical devices, telecom systems and consumer devices, program management, and software lifecycle development. Brian previously held positions at Cape Biotech, Sitwala, and Flextronics.
Related
-
WATCH NOW: Navigating Regulatory Requirements for Wireless Medical Devices
Cellular technology adds exciting new possibilities for healthcare but can also bring regulatory burden. When you incorporate a wireless module int
read more -
WATCH NOW: Human Factors Engineering for Combination Products
Human factors engineering (HFE) efforts are becoming a regulatory necessity for medical device companies in markets around the world. Combination p
read more