Skip to main content

Technical submission guidance

A list of documents required for technical submission

Updated over a week ago

This article outlines the general set of documents that manufacturers are expected to submit in the technical documentation when applying for conformity assessment through Scarlet as a notified body. These documents support clinical, safety, and performance claims in accordance with EU MDR requirements.

⚠️ Important: This is not an exhaustive list. Requirements may vary depending on the type and classification of the device, specific regulatory pathway, applicable standards (e.g. software or AI components), and risk profile.

Device Information

These documents describe the device, its intended use, and basic technical data

Software

Use Requirement & Validation

These documents define the medical device’s use requirements and ensure that these requirements are met through the planning and execution of validation activities.

  • Use requirements – Defines a comprehensive set of requirements that the medical device must meet to ensure fitness for purpose, usability, and clinical safety, including software-specific requirements covering information security, installation, operation, maintenance, and decommissioning.

  • Validation plans – Defines planned validation activities, the validation personnel and any constraints of the validation activities.

  • Validation reports – Reports that detail the execution and outcomes of the planned validation activities.

Software and AI Model Development

These are required for devices incorporating software, including AI-driven features

  • Software development plansDescribes the strategies for software development, configuration management, verification, maintenance and problem resolution.

  • Software requirementsA comprehensive set of technical requirements that the medical device software must fulfil.

  • Software architecture & designDefines the composition and safety classification of the software components in terms of software modules, interfaces, units and SOUP.

  • AI model designDescribes the training and inference of any models within the medical device software that are based on machine learning or deep learning techniques.

  • Software test specification and test reportsDocuments the detailed test specifications within each software verification activity and the associated test execution reports.

  • Software verification summary reportConcludes the verification with a summary of the executions and outcomes.

  • Software releaseDescribes the software release.

Risk / Usability

Risk

Risk-related documentation demonstrates the proactive identification and control of hazards:

  • Risk management plan – Describes the risk management strategy throughout the product life cycle.

  • Risk records – Documents the safety/security characteristics of the medical device, use errors, hazards-related use scenarios and the possible risk sequences of hazards leading to hazardous situations and harms, including the risk estimation, evaluation, controls, and benefit-risk analyses.

  • Risk management report – Summary and conclusions of the risk management activities that are required for a technical submission.

  • Risk management process review – A record that persons with appropriate authority have reviewed the implementation and results of the risk management process.

Usability

Documents demonstrating human factors engineering and use-related risk mitigation:

Clinical

These documents provide the foundation for demonstrating the clinical performance and safety of the device:

Post market surveillance

These documents support ongoing evaluation after the product is on the market.

  • Post-market surveillance plan – Strategy for monitoring the device in real-world use.

  • Post-market clinical follow-up (PCMF) plan – Strategy for ongoing clinical data collection post-market.

  • Post-market clinical follow-up report – Outcomes of post-market clinical investigations.

  • Periodic safety update report (PSUR) – Rolling evaluation of the benefit-risk profile, adverse events, and field actions.

Did this answer your question?