Case Studies
Software modernization for acquired aesthetic devices
Key Results
- 2 platforms integrated into existing ecosystem
- Zero-downtime updates for deployed devices
- MDR compliance artifacts and documentation
About the project
A global manufacturer of aesthetic medical devices expanded its product portfolio through acquisition, inheriting two established software platforms built on different technologies, development practices, and architectural decisions. The products needed to become part of the company’s existing engineering ecosystem while supporting preparation for the European market under MDR requirements.
PerformaCode joined the project with two senior software engineers to work directly alongside the client’s R&D organization. Rather than developing a new application, the team was responsible for understanding the inherited software, documenting the existing architecture, and establishing the technical foundation for future development. This required close collaboration with engineering teams across multiple countries and participation in architecture, design, and requirements reviews.
The project focused on modernizing legacy desktop software, improving software update mechanisms, strengthening patient data protection during upgrades, and replacing technologies that limited future development. Database migration, backward compatibility between software versions, and secure software updates were key parts of the modernization effort.
All engineering activities, including requirements analysis, software architecture, documentation, implementation, testing, and code reviews, were performed within an ISO 13485 quality management process to support long-term development of regulated medical device software.
2
engineers
12
months
Outstaff
delivery model
Client challenges
The acquisition brought two mature medical device platforms into an engineering organization with its own development standards, software architecture, and quality processes. The software had been developed by another company, using different technologies and design decisions, yet it now had to become part of a single product portfolio.
The acquired platforms were already running on a few thousand deployed medical devices. Software changes could not risk taking devices out of operation, corrupting stored patient data, or breaking compatibility between software versions. Updates had to preserve device behavior and keep existing users working.
Although the client had an established in-house R&D team, the project required senior engineers capable of independently understanding inherited software, documenting the existing architecture, and extending the platform with minimal guidance.
The products also had to support preparation for the European market under MDR requirements. That meant requirements analysis, SRS documentation, architecture documentation, cross-reviews, implementation, unit testing, and code review inside an ISO 13485 process while defects were fixed and legacy technologies were replaced.
Tasks performed
- Analyzed legacy software architecture to establish a technical baseline for future development.
- Created software requirements and SRS documentation in accordance with ISO 13485 development processes.
- Designed and reviewed software architecture with the client’s engineering teams.
- Developed new software features for inherited medical device platforms.
- Refactored legacy components to improve maintainability and support future platform evolution.
- Redesigned the remote software update mechanism to prevent device operation interruption during updates.
- Developed a database conversion tool to maintain compatibility between encrypted and non-encrypted software versions.
- Migrated the application database from Microsoft Access to SQLite to improve encryption support and technology independence.
- Implemented backup and recovery mechanisms to protect patient treatment data during software updates and unexpected power loss.
- Resolved legacy software defects affecting stability and maintainability.
- Performed unit testing, code reviews, and architecture cross-reviews throughout the development lifecycle.
Project results
2 platforms integrated
Two acquired software platforms were integrated into the client’s engineering ecosystem through architecture alignment, software modernization, and unified development processes.
Zero-downtime updates
Remote update mechanisms were redesigned so 1,000+ deployed devices could receive software updates without interrupting operation.
Patient data protected
Patient and treatment records remained stable during software upgrades through backup redesign and database conversion between encrypted and non-encrypted versions.
Regulated data storage enabled
Patient and treatment data moved to an encrypted SQLite-based storage layer, replacing Access limitations with a database architecture suitable for regulated software updates.
Cross-version compatibility
Legacy and updated software versions remained compatible through dedicated database conversion logic and controlled upgrade paths.
MDR artifacts completed
Requirements, SRS, architecture documentation, reviews, and verification artifacts were prepared under ISO13485 processes for MDR activities.
Legacy architecture documented
The inherited software architecture was analyzed and documented, enabling continued development by the client’s engineering organization.
Vendor lock reduced
Legacy technology dependencies were replaced with a cross-technology software stack designed to support future development.
Value we bring
Integrating acquired medical device software
A medical device acquisition is almost never “just add it to the portfolio.” Engineering inherits old documents, different architecture decisions, missing product experts, pending recertification work, and deployed users who may leave if updates take devices down. We take over the software baseline, restore the missing technical picture, prepare the artifacts needed for regulatory work, and change the code without turning modernization into a rewrite.
Adding senior engineers without taking over control
Sometimes the right answer is two or four senior engineers, not a managed delivery layer. The client keeps ownership, architecture decisions, and day-to-day management. We add engineers who can work inside the existing R&D process, absorb inherited software, write documents, join reviews, fix defects, and move the platform forward while the internal team keeps maintaining the rest of the product line.
Reducing technology dependency without rewriting the product
Old languages, unsupported components, proprietary dependencies, and vendor-locked stacks eventually become release risks. We isolate the parts that block future development, choose replacement paths that fit the existing product, and modernize incrementally. That may mean open-source components, AI-assisted engineering workflows, or a new hardware/software stack, but the rule stays the same: reduce dependency without breaking the product.
Technologies
- C#
- .NET Framework
- WinForms
- Microsoft Access
- SQLite
- SQL
- Helix ALM
- ISO 13485
- MDR
PerformaCode’s engineers brought strong technical competence, fast self-education, and close attention to our engineering needs.
- Medical aesthetic device company
- Global director, Software Engineering
Other Case Studies
Alarm Subsystem Compliance for Infusion Systems
Alarm subsystem validation for a medical device, delivering IEC 60...
