Class II Medical Device Software Development and Testing for a San Diego-based Company
Our client is a San Diego biotech company specializing in FDA approved Class II Medical Devices. This project, which we initially joined more than 5 years ago, is responsible for redesigning and manufacturing biomedical hardware that’s provided in hospitals in the United States and Europe. This hardware targets multiple areas of health including hematology, cancer monitoring and treatment, and more.
The software for this project is divided into two purposes:
- One software, connected via intranet, provides updates to the hardware
- The second software tracks maintenance activities for the hardware to ensure working devices prior to being used on patients
The Integrant team works with several stakeholders on the customer side to continue to build upgrades, implement new features, identify clear requirements, maintain FDA approval standards, and more. There are so many things we love about this project, especially the partnership we’ve formed with this client that has really helped empower us to bring the best ideas and solutions to the table to be a small part of the giant impact they have on the healthcare world.
Medical Device Software Development, Automation Testing
.NET, C#, WPF, SQL, InstallShield
Medical Device, Manufacturing
Integrant Team Structure
Read more about our 4Plus1 Shadow Engineering Program Here!
With almost 30 years of experience under our belts, we’ve seen the whole gambit of software development project challenges. We know the stakes are high when it comes to global health, and we don’t take that lightly. Our teams were able to come together and tackle the challenges below:
For this project, we work with 8-9 stakeholders across four departments. These departments help ensure the highest quality applications and working devices to best service the end user. These four departments also have differing priorities and needs. The challenge here is to balance each department’s needs and compromise on what leaves the backlog first.
Changing Requirements and Scope Changes
Some amount of change requirements or scope changes are expected on a project. For this project, when we were all set to begin work on the next release, a new set of features came up in an emergency situation for the current version of the medical device. This meant halting all work on the upcoming release and refocusing energy on new features that needed to get done with high quality and in a timely manner.
Rigorous Standards and FDA Approval
When it comes to FDA approved software and medical devices, there is no room for error. Quality and uptime are important components to the livelihood of so many. In the past, significant amounts of time have gone into regression testing to guarantee the effectiveness of the medical device. In addition, becau se an intranet is required to upgrade the device’s software (different than the internet upgrading the software on your iPhone or Android device), technicians’ training and reports become increasingly significant in pinpointing faulty equipment and/or software.
Check out how we create change in the software industry. Read more case studies today!
Like with every software project, we ran into a few challenges. We were able to remain calm, come up with a plan, pivot when needed, and provide quality results and solutions for this medical device company. We’re thankful to our client for being with us every step of the way so we can continue the journey successfully together.
Agile Practices, Alignment, and a Business Analyst
While the development team practices a daily stand-up, our meetings with the client look a little different. To maximize effectiveness for this project, key stakeholders on the client side meet Mondays to align prior to meeting with Integrant employees three days mid-week. This helps facilitate priorities and move decisions along faster.
In addition, we added a Business Analyst, who has been instrumental in guaranteeing clear requirements that incorporate all necessary features. This has allowed the Technical Project Lead (TPL) to focus even more on quality code and the implementation of more efficient solutions like automated regression testing.