Interview with Guillaume GOUBERT, Process Manager at Bow Medical

Bow Medical has announced Class IIb certification for its Diane software suite. Behind this regulatory milestone lies in-depth work on process structuring, software architecture and team organisation.

Guillaume GOUBERT, Process Manager, looks back on this transformation and its impact for healthcare facilities.

What was your role in obtaining Class IIb certification?

Guillaume GOUBERT (G.G.): The Class IIb certification project is part of a long-term initiative that really got under way in 2022, driven jointly by the Chief Technology Officer and the Regulatory Affairs Manager, in collaboration with the technical teams.

At that point, we began foundational work around IEC 62304, the standard that defines lifecycle requirements for medical device software. My role covered both the process and product dimensions, with a clear objective: to transform an existing organisation into a system capable of meeting very high regulatory requirements, without reducing team efficiency. This involved substantial work to formalise documentation, and also to build tooling around our processes, so that day-to-day practices became smoother and more accessible for developers, product managers and quality teams.

In 2023, we undertook an architectural transformation. In particular, we segmented the code very finely in order to isolate the scope covered by the medical CE marking.

The stakes were strategic: allowing the solution to keep evolving rapidly on certain functional building blocks, while ensuring that the certified scope remains strictly controlled. Without this separation, every major change could have required lengthy and costly requalification.

Finally, in 2024, we entered a regulatory consolidation phase, putting the final controls in place, finalising the evidence of compliance and compiling the submission file.

What were the main process workstreams you had to put in place?

G.G.: We set up several workstreams, which profoundly transformed the way we design and validate changes to the software.

The first workstream involved strengthening patient safety risk analysis, in line with ISO 14971. This approach, already in place since we obtained Class I CE marking in November 2021, was reinforced for Class IIb by integrating it into our in-house project management and task tracking tool. This now enables us to better trace, monitor and manage the risks associated with each change to the medical device, while ensuring consistency between requirements, risks and implementation.

The second workstream focused on separating the code between the medical device (MD) scope and the non-medical device scope, together with tighter control of changes to the MD code to ensure compliance with IEC 62304 requirements.

The third area concerned structuring the final testing phases, in order to validate robustly that the applications function correctly against the requirements defined and approved by QARA (Quality Assurance & Regulatory Affairs).

Finally, significant work was carried out on the IAU, an internal validation mechanism that strengthens quality controls by incorporating structured reviews of software changes, particularly from a safety and clinical use perspective.

We also introduced a multi-level approach to evaluating features, notably through summative evaluations. These involve submitting changes to a panel of medical experts, who validate not only functional compliance but also functional relevance to clinical practice, usability and the safety of the patient pathway.

The overall objective is to move from after-the-fact validation to continuous risk control, built in from the design stage and centred on patient safety.

In practice, what does this change in the way Diane is developed?

G.G.: The change is profound, both in the way we work and in the level of control we now have over what we produce.

In concrete terms, we have significantly reduced the number of defects detected late. Strengthened requirements specification and testing processes allow us to identify, very early on, most of the potential issues typically encountered in the development cycle.

This completely changes team dynamics: we are moving from a corrective approach to a preventive one.

Another major impact concerns the overall quality of the software. Robustness is now far more consistent, regardless of the feature or the team developing it.

Moreover, contrary to a common perception of highly regulated environments, these processes have not slowed innovation. On the contrary, they have accelerated it in some respects, notably by making the design and development cycle more secure. This avoids costly back-and-forth between formalising change requirements and implementing them, while enabling efficient validation of features through the testing processes.

As a result, teams can deliver the product roadmap more reliably, and approach it with much greater confidence.

How did you bring the teams on board with this transformation?

G.G.: Supporting the teams was an absolutely decisive factor in the project’s success. We built up skills gradually, starting from existing practices, on both the R&D and product sides. The idea was not to rebuild everything from scratch, but to integrate IEC 62304 requirements into everyday practice step by step.

This required a considerable effort in explanation, because we needed to show that these regulatory constraints are not merely administrative obligations, but contribute directly to software quality and safety.

We also worked on adapting our tools so that they fit naturally into the teams’ daily work without creating unnecessary friction.

Looking back, this initial investment was significant, but it is now paying off: less time spent debugging, more reliable test cycles, better anticipation of issues and, above all, the ability to release versions more smoothly and with greater agility.

What about hospital decision-makers and IT teams?

G.G.: For healthcare facilities, the benefits are not always immediately visible in the technical detail, but they are very tangible in day-to-day use.

Class IIb certification attests above all to a very high level of control over the entire software lifecycle. This means that every change is carefully designed, tested and validated to a higher standard, which translates directly into greater reliability in production.

In anaesthesia, the ICU or operating theatres, this reliability is essential. It reduces the risks associated with updates, improves overall system stability and safeguards clinical use over time.

It also brings a significant organisational advantage for healthcare facilities, notably by reducing the compliance and documentation burden. Much of what is needed for clinical and hospital audits and certifications is already structured and available, which makes the work of IT and quality teams considerably easier.

Ultimately, this allows healthcare professionals to focus on their core work, relying on a solution designed to be robust, well controlled and sustainable.

What are the next process challenges?

G.G.: Today, the main challenge is no longer just achieving compliance, but continuously optimising what we have built.

We are actively working on further automating our testing, validation and control mechanisms, to streamline the entire development cycle.

The aim is to industrialise our processes even further, without losing the level of rigour achieved with Class IIb.

This also means better tool integration, fewer manual tasks and the ability to speed up delivery cycles while maintaining high safety standards.

In short, the challenge is to reconcile three dimensions: regulatory requirements, industrial performance and product agility.

To conclude?

G.G.: With Class IIb certification, Bow Medical has undertaken far more than regulatory compliance. The company has profoundly transformed its development methods, structuring its processes around safety, quality and risk control.

This evolution now makes it possible to offer healthcare facilities a more robust, more reliable and better-controlled solution, helping to improve the entire care pathway. It helps hospitals and clinics optimise patient care, better capture and bill the procedures performed, strengthen risk prevention and, ultimately, achieve lasting improvements in the overall quality of care.

For more than 20 years, we have been supporting healthcare professionals in transforming the critical care pathway. This French company, a European leader in its field, has made improving and securing critical care its core mission.

Bow Medical’s expertise focuses on one specific challenge: digitising critical care. This particular segment of the electronic patient record (EPR) requires in-depth knowledge of clinical practices and operational constraints. The Diane platform, the product of this expertise, delivers real added value in terms of performance, reliability, safety and optimisation of clinicians’ time.

The figures speak for themselves: more than 450 healthcare facilities trust our software for anaesthesia and ICU care. Diane Consult handles 5 million anaesthesia consultations a year, representing around 70% of digitised consultations in France. In operating theatres, 3,000 rooms rely on Diane Op, while more than 1,200 ICU beds use Diane Rea to optimise the care pathway for the most critically ill patients.

Share This