We surveyed a global audience of medical device development leaders about their work.
- What challenges do you encounter in development?
- What tools & methodologies are you using?
- What regulations are you watching?
- What will boost innovation?
Results are in.
The data shows an industry in search of steady footing amid market, regulatory, and technological changes.
2019 Key Findings
- Manual processes are limiting productivity.
- Confidence in compliance is down.
- More user & lifecycle visibility is desired.
- Teams shifting toward hybrid Agile.
- Innovation needs investment in R&D.
- All eyes are on EU MDR regulations.
Continue reading to explore 2019 medical device development trends, challenges, and innovations.
Too Many Meetings, Emails, Status Updates
What’s not adding value to the workday? Meetings, documentation, email, and chasing down project status, say industry professionals.
In Your Words
“Getting people to respond to emails.”
“Tracking component status to support product builds.”
“Correcting poor virtual development documentation.”
Manual Development Process Dominates
The use of specialized medical device development tools has increased by 25% since 2016. The majority of teams, however, still manage work with a combination of Word documents and spreadsheets.
According to the survey:
- 65% use Microsoft Word to manage requirements.
- 65% use Microsoft Excel to manage test cases.
- 59% use Microsoft Excel to manage and track issues.
As we can see, teams with a predominantly manual process dedicate time to daily project administrative work.
Good ALM tools can streamline much of the manual processes and free up time for higher priority work.
Collaboration Challenges in Embedded Development
Cross-team collaboration was the number one challenge for development teams building embedded devices. The rise of distributed teams is impacting organizations everywhere. It's also affecting modern device designers.
Teams developing products with hardware and software often work in disparate systems. This disconnect can stall collaboration among designers, hardware engineers, and coders.
More and more, companies find talent where it lives rather than bring it all together into one office. To work across geographic and time zone boundaries, teams need an accessible system that provides a secure, reliable single source of truth for managing assets, no matter where they sit.
The right tooling — a version control system with proper integrations, for example — can ease many of these asset challenges.
Resource: Why Is Version Control Important?
Design Control Challenges
From user needs to project status, low visibility or knowledge into design control activities is creating challenges.
Taking action is difficult when you don’t have all the information.
Responses suggest teams want more context throughout the design control phase. More thorough requirements gathering, with more data on user needs, may reduce unknowns.
The data also highlights opportunities to provide teams with more context around defects, documentation, project status, change management, and more.
Challenges like these can be common for siloed teams using predominantly manual development processes.
In Your Words
“Aligning user feedback with the pace of the project to stay on schedule, while also taking time to make sure the product is right.”
“Coworkers are unaware of processes, make up their own, then complain about everything being complicated.”
Resource: FDA Design Controls Guidance
Quality & Compliance
Doubt Rising in Audit Compliance
There’s an unexpected FDA audit. How confident are you that you’ll pass? Medical device industry leaders in 2019 have less confidence than last year.
Why is confidence down? Lifecycle visibility challenges, noted above during the design control phase, could be contributing. For leaders feeling similarly, solid end-to-end lifecycle traceability can provide assurance.
The Proof Is in the Documentation
Proving compliance is never simple. For those involved in the process, three challenges shared top spots: documentation, objective evidence, and risk & hazard analysis.
These results should not surprise anyone with a manual development process. When teams need proof, they have to dive into documentation to make all the necessary connections. Objective evidence, for instance, can be buried (or worse: lost) in spreadsheets. A more formalized documentation & testing process, a robust test management tool, or a combination of both can help greatly.
Few Focused On Coding Standards
A surprising majority, 75% of respondents, either aren’t using a coding standard or are unaware if the team is even applying one.
Coding standards help reduce risk by ensuring the development team is conforming to a shared set of industry requirements. Static code analysis can play a pivotal role.
Resource: Coding Standards 101
Teams that changed development methodologies in 2018 moved away from Scrum (a popular Agile development method) and Stage-Gate (a proprietary Waterfall-based method).
Instead, teams struck balance in the middle. A hybrid Agile development process, which combines elements of Agile with more traditional development methods, appears to be a settling point — for now.
Are they happy with their current process? 75% of respondents that switched processes were satisfied with the results.
Resistance to Change, Inadequate Tools Balk Agile Transition
Numerous teams transitioned to Agile methods in the last year. Not everyone thought it succeeded. Why not? Resistance to change (19%), inadequate tools (19%), and lack of internal knowledge (14%), say respondents.
Technologies unheard of as recently as a decade ago are finding a place on product roadmaps.
Key Drivers of Innovation
What will spur innovation? Industry leaders believe the answer lies in simplified regulations, unified standards, and more investment in R&D.
Simpler Standards & Regulations — Down From 2018
It appears some progress has been made in improving innovation despite the overhead of industry standards and regulations.
Innovation Demands More R&D
Today’s technological landscape offers opportunities to capitalize on innovation. But incorporating these innovations into design requires more investment in R&D. A majority are either currently working on or planning to include emerging tech in product design.
Regulations on the Radar
It’s no surprise. Many are watching the European Union Medical Device Regulations (MDR) scheduled to take effect on May 25, 2020.
FDA regulations are second. After that, developers are concerned with ISO 13455:2016 (for quality management systems). They’re also watching revisions to ISO 14971, which requires a well-documented narrative of the product lifecycle.
What else? Write in responses included:
• Medical Device Single Audit Program (MDSAP).
• FDA Cybersecurity Regulations (draft currently available for review).
• FDA Section 508 (for formatting requirements documents in Microsoft Office).
Will hybrid Agile development continue to be the preferred process for medical device developers? Will device developers address manual processes? How exactly will the increase in emerging technologies impact how teams collaborate?
All good questions. We plan to investigate them for 2020.
ABOUT THE SURVEY
Perforce surveyed 267 medical device professionals in February 2019. Participants represented a wide range of experience. From industry veterans with 10+ years of experience in the upper tiers of management to development professionals with under a year of experience. Survey respondents also represented a diverse range of device types (hardware, software, both), and classes (I, II, III, IV, De Novo).