Webinar on The Role of FDA in Health Care Software Regulations and Development

This presentation will describe the developing area of Health Care Software regulation in the US. It will explain the role of FDA, ONC (Office of the National Coordinator for Health Information Technology), and for wireless apps, the FCC. It will also describe expectations for software that is a device component, as well as standalone software that is a regulated medical device

Why should you Attend:

Inadequate validation of software continues to be a leading component of device warning letters. Problems mainly include 1) Software that is a component of the manufacturing process (not necessarily a medical device, but like all device class II and III, manufacturing elements, subject to QSR’s), or 2) software that is a component or accessory of some Class III or Class II medical device (Itself a medical device, per FDA guidance). 

Areas Covered in the Session:

• Who regulates software and why
• How to tell if the software you are developing is a medical device
• What does “enforcement discretion” mean and how does it apply to software
• What are the expectations for software that’s an integral part of a device
• What about software that is offered to analyze signal from a medical device, but is not a part of the device, has a different manufacturer and seller? (e.g., sequencer raw data from manufacturer A, can be analyzed by software from either software seller B or C, and translated using different interfaces from either B or C to the local LIMS
• What about software used in the manufacturing process but not sold
• Who is enforcing HIPAA, Patient privacy, for device software?
• And what does Part 11 have to do with my software?

• Code Developers working on Medical Applications
• Regulatory Affairs Associates
• Health Care Software Marketing Associates
• QA associates for firms that are developing/revising Medical Software

Speaker Profile: