Implementing a new compliance software tool into your organization isn’t easy. Between establishing new processes, evaluating impacts on your quality system, and determining short- and long-term timelines of adoption and use, there are a lot of considerations to be managed. On top of that, getting your teams to use the tool is an entirely different challenge; if there’s resistance, then things only get more complicated. So how do you promote user adoption for new compliance software?

September 2019 saw the release of several final guidance documents relating to 510(k) submissions. One of the most utilized pathways by medical device manufacturers, the 510(k) has evolved quite a bit over time. The release of all these new documents speaks to FDA’s commitment to keeping this method of premarket submission up-to-date and aligned with agency directives. Taking a brief, high-level overview of each of these final guidance documents is extremely important for organizations looking to stay ahead of the ever-changing regulatory landscape.

In September 2019, FDA released final guidance on its Special 510(k) Program. This optional pathway allows medical device manufacturers a simplified approach to submitting changes to their legally marketed products, provided they are currently well-understood by the agency. However, figuring out whether or not your submission qualifies under the Special 510(k) is tricky. Diving into the final guidance, there are hallmarks you can use to understand your device’s qualification under this program.

Your organization has decided it needs a compliance software tool—now what? Well, conducting a search is a good place to start. However, your search for a new tool needs to be well-informed and methodical. Otherwise, you might wind up with a tool that’s not mature enough or inappropriate for your needs. To avoid these issues and streamline your search, here are some tips that can help.

The deadline for the official implementation of the EU Medical Device Regulation (MDR) is approaching. By May 2020, your medical device organization must be in compliance with many new requirements for your product throughout its life cycle. With this increased focus on the total product life cycle comes an expanded suite of regulations for postmarket surveillance you must be in compliance with. There is a lot to unpack in this aspect of EU MDR, but there are some major compliance areas your organization should be putting in place now.

NAVIGATE2019, Cognition’s annual user conference, has officially wrapped up. We heard many great talks, panels, and discussions over the course of the two-day event. Here’s a brief overview of the conference—what we discussed, what we learned, and how that information will impact Cognition moving forward.

Drug stability reporting has been a major area of interest for Cognition as of late. To get a better understanding the current environment, we coordinated our Summer Internship Program around this topic. Led by our interns Olivia O'Brien and Brigitte Cronin, this effort has yielded a vast amount of important and intriguing insights about the current state of drug stability reporting in pharmaceutical industries. Here are a few of those insights and what they can tell us about this vital aspect of pharmaceutical compliance.

The new European Medical Device Regulation (EU MDR) is on its way. Soon, medical device manufacturers wishing to submit to European markets will need to comply with a set of new and critically important regulations. However, even with the 2020 deadline coming up, many organizations are still in the dark about what the MDR is and what it means for them. Here are some common questions we’ve heard about this new European regulation and what it means for your product development and compliance activities.

There’s so much work that already goes into the development of life science products before even thinking about the necessary compliance steps. This high volume of work often leads development teams to push away compliance activities until later on, which can actually lead to rework and other negative consequences. Yet one compliance avenue that can get folded into this shuffle is your product’s use specification.