Custom file system for IVDR
Appfront builds documentation systems for manufacturers of in vitro diagnostics covered by the European IVDR. Per device: the technical documentation, the general safety and performance requirements with their evidence, the performance evaluation with plan and report, risk management and post-market data. With versions, an overview of what is still missing, and a file that is ready when the notified body asks questions.
What is a documentation system for IVDR?
Since the European regulation on in vitro diagnostics (IVDR) came into effect, the documentation requirements for tests, reagents, analysers and diagnostic software have become far stricter. Devices are divided into classes A to D. Every device needs technical documentation, including the general safety and performance requirements, a performance evaluation with plan and report, risk management and post-market surveillance data. For most classes, a notified body assesses that documentation.
In practice, that documentation sits in folders of documents, linked through a spreadsheet showing which document covers which requirement. A document gets a new version, but the spreadsheet still points to the old one. A requirement has no evidence, and that only comes to light when the notified body asks about it. Post-market surveillance data has to feed back into the performance evaluation, but it sits in another system.
We build custom because manufacturers differ: which devices and classes, how their quality system is set up, which documents already exist, and which notified body they work with. What the regulation requires for your devices is something you determine with your regulatory adviser and the notified body; the system records what is needed and shows where it is missing.
Complete per device
Technical documentation per device, with class, intended purpose and every section the regulation requires.
Requirements with evidence
Every general safety and performance requirement linked to its evidence and the standards applied, with versions.
Ready for assessment
An overview of what is missing, and access for the notified body or adviser to what they need to see.
How we build your documentation system for IVDR
We start with one device: which class, what documentation already exists, how it is currently organised, and where the gaps are.
Your devices, classes, existing documents, quality system and notified body.
The structure of the technical documentation, and the requirements linked to evidence.
Plan and report for the performance evaluation, and post-market data.
An overview of open actions, access for assessors, and management of new versions.
What a documentation system for IVDR actually does
The components below appear at almost every manufacturer of in-vitro diagnostics. Which ones you need depends on your devices.
Devices
Devices with their class and intended purpose.
Technical documentation
The components the regulation requires, per device.
Requirements and evidence
Safety and performance requirements linked to evidence and standards.
Performance
Plan and report of the performance evaluation, with the underlying data.
Risk management
Risks and measures per device.
Versions and approval
Document versions with approval and history.
Who we build an IVDR documentation system for
The system is intended for anyone who prepares, manages or reviews IVDR documentation.
Test manufacturers
Reagents and tests across several classes. The requirements with their evidence are the core.
Software manufacturers
Software for diagnostics. The performance evaluation matters most.
Laboratories
In-house tests within the institution. The overview of what is needed is what matters.
Regulatory consultants
Supporting multiple manufacturers. The file per client is the core.
Test your idea first: a working prototype in 1 day
With OneDayBuild, we make your idea tangible in a single day for €1,150, so you know whether further development is worth the investment. Decide to go ahead with the full build? Then we deduct the cost in full.
View OneDayBuild →Technology and integrations
This page is about documentation for the IVDR. For medical devices under the MDR, see our page on an MDR technical file and PMS system, for laboratories our page on laboratory software, and for quality systems our page on a custom quality management system. You can read about our approach on building software.
Why Appfront for your IVDR documentation system?
A requirement without evidence gets found by the notified body, and that costs time at a moment when you don't have any. That's what we build on: documentation per device, requirements with evidence, and an overview of what is missing.
Gaps seen in advance
What is missing is visible before the assessment.
Versions are correct
A requirement always points to the current version of the evidence.
Fewer questions
The reviewer finds what is needed.
Security and privacy in an IVDR documentation system
The system contains confidential information about your devices, such as design, performance and risks. Access is set up per role and per device, reviewers only see what is meant for them, and every change is logged.
The system runs in a European data centre or in your own environment, with encrypted storage, daily backups and two-factor login.
Frequently asked questions about an IVDR documentation system
Questions that manufacturers and consultants ask before they start.
It organises the technical documentation per device, links each general safety and performance requirement to its evidence, manages the performance evaluation and risk management, keeps track of versions, and shows what is still missing. A reviewer only sees what is intended for that review.
The European regulation for in-vitro diagnostic medical devices, Regulation (EU) 2017/746. It applies to tests, reagents, analysers and diagnostic software, divides devices into classes A to D, and sets requirements for technical documentation and performance evaluation.
The MDR applies to other medical devices and requires a clinical evaluation. The IVDR requires a performance evaluation, with its own requirements for scientific validity and analytical and clinical performance. The MDR has its own page.
That depends on the class and type of device. The regulation describes what the technical documentation must contain. What applies to your devices is something you determine with your regulatory consultant and the notified body; the system follows the structure you define.
Yes. Existing documents are placed into the structure and linked to the requirements. That way you can see straight away which requirements already have evidence and which do not.
Yes, if that system has an interface. Documents and versions can come from the quality system, so they are not managed twice.
Check that first. A quality system manages documents and versions, and that is a large part of the work. Custom software makes sense when the link between requirements and evidence, the performance evaluation and the overview of gaps are missing.
Technical documentation that is ready for assessment?
Tell us which devices and classes you have, how your documentation is currently organised and which notified body you work with. We will show you what the file, the requirements and the overview look like.