When Quality and Regulatory Don't Talk, the Technical File Gets Stuck Halfway
They were sure they were on the right track.
MedImplantX (the real name is withheld) had developed an advanced Class III implant and completed every stage of development. The quality department took care of the DHF files, and the regulatory team was hard at work on submitting the technical documentation according to the MDR requirements.
Each department worked efficiently, each within its own area.
But when the time came to submit, critical gaps surfaced that no one had taken into account.
The problem that surfaced: when departments don't share a common language
It all started with a fairly routine request.
The regulatory team asked the quality department for the updated risk management report, so they could include it in the technical documentation and cross-check it against the findings of the clinical evaluation report (CER).
What they received was professional and clear, but it did not match the clinical documents.
The clinical evaluation report included findings from a clinical study that showed a slight increase in the rate of implant migration in revision surgeries. The clinical team had classified this finding as a "known risk" that required PMCF follow-up and the presentation of controls in the risk file.
But in the risk management report, this risk did not appear at all.
As a result, its severity had not been assessed, no control measures had been presented, and no RPN value had been calculated.
This was not the only case. Other risks that appeared in the risk analysis were not mentioned at all in the clinical evaluation report, with no clinical traceability shown and no reference to data from the literature.
Comments from the notified body were not long in coming:
"There is inconsistency between clinical risks mentioned in the CER and the risk analysis submitted. Please demonstrate traceability and consistency across technical documentation."
From there, the entire file was sent back for corrections.
That meant weeks of rework, coordination, updates and supplementary reports.
Why did this happen?
Simply put, there was no organized system for collaboration between quality and regulatory.
Each department worked within its own framework. The regulatory department ran the process like a regulatory submission project, following the structure of the file and the expectations of the notified body. In other words, they worked from an organized checklist they had received from the notified body, which is based on Annexes II, III and XIV of the MDR and includes clear, detailed requirements for the documents to be submitted in the technical documentation. The quality department, meanwhile, focused on meeting the requirements of the quality management and risk management standards (ISO 13485, ISO 14971). The gap formed because each department looked at the process through a different lens: quality saw it as an internal process of documentation and compliance with standards, while regulatory saw it as the formal preparation of a technical file for submission.
There were no cross-departmental meetings.
There was no document that brought the risks together and verified the traceability between them.
There was no process of mutual review of the critical documents.
The result was inconsistency.
And the MDR is not forgiving when it comes to traceability between clinical risk and engineering risk.
How did we solve it?
We connected quality and regulatory in a practical, clear way, without inventing complicated processes.
We set up a cross-departmental team of quality, regulatory and clinical, which met every two weeks, together with other teams as needed, to go through the critical documents together.
We went line by line through the list of risks and clinical events and checked that each one appeared in both the risk analysis and the clinical evaluation report, with clear traceability.
We updated terms and definitions so that the "clinical language" and the "engineering language" could talk to each other.
We created a simple internal review process in which every key document gets a second pair of eyes from another department before it goes into the technical documentation.
Key insights for Class III manufacturers (and not only them)
Quality and regulatory documents have to speak the same language, even when different teams write them.
The MDR requires full traceability between risk management and clinical evaluation, and these gaps are a common reason for a file to be rejected.
Simple solutions, such as a traceability table and a regular synchronization process, can prevent delays of months.
In complex projects, quality and regulatory are not two departments. They are one team with shared responsibility.
In closing
If you work in a company where quality writes documents for itself and regulatory runs ahead without consulting anyone, then
this is the time to stop.
It's time to build the bridges.
And remember that a successful submission depends not only on the quality of each document, but on how well they match one another.