Effectively Communicating to FDA

FDA Questions

Effectively Communicating to FDA – being able to appropriately articulate what your software function is intended to do or intended to provide is –

the foundation – the corner stone – the linchpin to navigating the correct path, investing your resource wisely, and defending your decisions now and into the future.  Solid foundations lead to solid futures.

Most companies can do a great job of providing a detailed engineering description of their product, but then come up way short on the clinical benefit side of the equation.

Your intended software function description needs to start to address:

  • how does this benefit the patient
  • how does this benefit the practitioner
  • how does this benefit health care
About the author

John is a 25 year FDA veteran. John served as a regulatory and compliance expert for FDA regulated computers and software. Practice (focus) areas include FDA software related guidances, software device classification determination, pre-market software review, post market software inspectional 483’s, additional information software requests, Digital Health Pre-certification, AAMI Software related TIRs and related medical device software standards.

SoftwareCPR Training Courses

IEC 62304 and Emerging Standards Impacting Medical Device and HealthIT Software

ISO 14971 Risk Management (typically with heavy emphasis on software aspect)

IEC 81001-5-1 Cybersecurity Lifecycle

ISO 13485 QMS Requirements & optionally ISO 19011 for leading audits

Being Agile Yet Compliant (AAMI TIR 45)

IEC 29119-1 Software and System Testing

US Classification for Software Devices

IEC 62366 Usability Process and Documentation

Or just email training@softwarecpr.com for more info.

Corporate Office

15148 Springview St.
Tampa, FL 33624
USA
+1-781-721-2921
Partners located in the US (CA, FL, MA, MN, TX) and Canada.