Medical Device and Pharmaceutical Product Development and Compliance

An introduction to how smart data utilizes information and actionable context to support business-critical decisions.

In the highly regulated world of medical device manufacturing, the relentless requirement to minimize and mitigate risk places a huge onus on design, development, and manufacturing teams. That’s why companies, large and small, are looking for software solutions to help ensure consistency and objectivity in the creation, auditing, and monitoring of critical risk management processes.

Key takeaway: The ability to reuse product data can dramatically reduce the time taken to design, gain regulatory approvals, and ultimately bring new medical devices to market. Time equates to money in any business, and in the world of medical device design and manufacturing, that can mean BIG numbers! Depending on the route taken, following FDA regulations, the average cost to bring a medical device to market through the Premarket Approval pathway is $94 million. The less intensive 510(k) process averages out at $31 million.

Using unstructured tools such as Word and Excel when doing risk management for medical devices could result in harm to a patient. Why? Because many medical devices are complex, with hundreds to thousands of inter-related design inputs/outputs, testing, and risk management data. Managing that amount of data manually is nearly impossible when using tools like Word and Excel...

Systems engineering should be used more often in medical device product development. This may be a strong statement, but it can be transformative for device development through decreased development costs, streamlining of interactions with the FDA, and reduced time-to-market. We would like to address this through a series of articles on systems engineering role in Medical Device Product Development of which this is the first.

Often in medical device product development, functions exist in silos. Risk, requirements, and test management functions often exist separately, on their own - different systems, different teams, different objectives. Yet, the data related to these functions are both continuously changing and highly dependent on one another. Some type of process is needed to (1) manage the effect of changes across all three systems and (2) provide evidence of a process for notified bodies if and when needed.

Your product’s intended patients have a wealth of experience and information that can be valuable to your development process. Whether it’s the day-to-day realities of the condition, the symptoms they feel need the most attention, or things they might be missing in their current treatment regimens, this data cannot be elicited from doctors and engineers alone.

Life science product development is all about process: to ensure safety and effectiveness of your product, processes must be in place to maintain high quality in your design and development work. In smaller organizations, these processes and procedures can be fairly easy to control and manage. However, as your business grows, so do the scope and complexity of your development activities. To maintain and improve your life science product development processes, there are a handful of methods your organization can undertake.