Medical device manufacturers in DACH regularly need more software capacity than they can hire, and an external team is an obvious option. The regulatory question is not whether external development is allowed. It is. The question is whether the resulting lifecycle evidence will satisfy a notified body. Under the Medical Device Regulation (EU) 2017/745, the manufacturer remains fully responsible for the device, including its software. Annex I, section 17.2, requires software to be developed in accordance with the state of the art, taking into account the principles of development life cycle, risk management, including information security, verification and validation. In practice that state of the art is IEC 62304 (harmonised as EN 62304). The external team must therefore work inside your 62304 process and produce evidence that fits into your technical documentation. This guide explains how to allocate the activities.
The market and the certification bottleneck
The stakes are considerable. According to BVMed, citing Destatis and Spectaris, the German medtech industry generated 42.72 billion euros in revenue in 2025, exported 68 percent of it and reinvests around 8 percent of revenue in research and development. Around 93 percent of companies in the sector are SMEs, which is exactly where software capacity runs short. Certification remains the bottleneck. Team-NB, the association of European notified bodies, reported 16,453 MDR and IVDR certificates issued in 2025, up from 11,292 in 2024, and according to RAPS coverage of the survey, reviews typically take 13 to 18 months. Under Regulation (EU) 2023/607, legacy certificates for class III and implantable class IIb devices remain valid until 31 December 2027, and those for most other classes until 31 December 2028, provided the manufacturer met the 2024 conditions. Software documentation that is incomplete when the notified body opens the file adds months to an already long queue.
Start from the software safety class
IEC 62304 (Edition 1 with Amendment 1 of 2015) scales the required activities by software safety class: A (no injury or damage to health possible), B (non-serious injury possible) and C (death or serious injury possible). The class determines, for example, whether detailed design and unit verification must be documented for each software unit. Before engaging an external team, the class of each software system and, where you segregate, each software item, should be fixed and justified in your risk management file under ISO 14971. An external team should not be the party that proposes a lower class.
Note that a second edition of IEC 62304 is in preparation. Current drafts broaden the scope to health software and replace classes A, B and C with two process rigour levels. It has not been published, so plan your process on the current edition and keep an eye on the transition.
Who owns which activity
| IEC 62304 activity | Manufacturer | External team |
|---|---|---|
| 5.1 Software development planning | Owns the plan, approves | Contributes tooling, branching and build sections |
| 5.2 Software requirements analysis | Owns, derives from system requirements and risk controls | Reviews for testability, proposes refinements |
| 5.3 Architectural design | Approves, especially segregation arguments | Drafts architecture, identifies SOUP |
| 5.4 Detailed design (class B, C) | Reviews samples | Produces |
| 5.5 Unit implementation and verification | Defines acceptance criteria | Produces code, unit tests, review records |
| 5.6 Integration and integration testing | Reviews | Produces in CI |
| 5.7 Software system testing | Owns and approves results | Automates and executes under your protocol |
| 5.8 Software release | Owns, signs off | Prepares release package |
| 7 Software risk management | Owns | Identifies software contributions to hazards, implements risk controls |
| 8 Configuration management | Owns the system | Works inside it |
| 9 Problem resolution | Owns the process | Investigates and fixes under it |
The pattern is consistent: the manufacturer owns decisions, plans and releases, the external team produces engineering artefacts and the records that prove how they were made.
SOUP is where external teams create risk
Software of unknown provenance (SOUP) includes open-source libraries and third-party components not developed under your process. External engineers tend to add dependencies quickly. Under IEC 62304, each SOUP item must be identified with title, manufacturer and version, and for class B and C its functional and performance requirements and known anomalies must be evaluated. Make this a rule in the contract: no new dependency without a SOUP entry, and the CI pipeline fails if the dependency manifest contains an item not in the SOUP list. That single control prevents most surprises in an audit.
Cybersecurity is part of the lifecycle
MDR Annex I section 17 explicitly includes information security, and MDCG 2019-16 provides guidance on cybersecurity for medical devices. For an external team, that translates into secure coding rules, dependency vulnerability scanning, a software bill of materials per release, and a process for handling vulnerabilities reported after release. IEC 81001-5-1 is increasingly used as the reference for security activities in the health software lifecycle and fits alongside IEC 62304.
Tooling that makes evidence cheap
Evidence becomes expensive when it is produced manually at the end. It becomes cheap when the toolchain produces it as a side effect. Minimum setup:
- Requirements, risk controls and tests in one traceable system, with links created as work happens.
- Merge requests that reference requirement or problem report IDs, with mandatory review.
- CI that stores unit and integration test results per build, linked to the commit.
- Automated traceability report generated per release candidate.
- Tool validation records for tools whose output is relied upon without further verification.
An example definition of done per sprint
Under a Werkvertrag with sprint-based acceptance, the definition of done is where 62304 becomes operational. An illustrative version for a class B software item:
- Every merged change references an approved requirement or problem report.
- Detailed design for new or changed units is updated and reviewed.
- Unit tests exist for new or changed units and pass in CI, with results stored against the build.
- Integration tests for affected interfaces pass.
- SOUP list and SBOM are updated, and no new dependency lacks a SOUP entry.
- Risk control measures implemented in the sprint are linked to their verification.
- Open anomalies are recorded in the problem resolution system with an initial assessment.
Acceptance (Abnahme) of the sprint then means that the manufacturer has checked these records, not just watched a demo. That distinction is what makes the records usable in the technical documentation later.
Checklist before engaging an external team
- Fix software safety classes and segregation in the risk management file.
- Qualify the external team as a supplier under your QMS (see our separate article on ISO 13485 supplier control).
- Train the team on your SOPs for development, configuration management and problem resolution, and keep training records.
- Define the deliverables per sprint as 62304 artefacts, not only as features.
- Implement the SOUP gate in CI.
- Agree that the external team does not release software. Release remains a manufacturer act.
- Ensure all records are stored in your systems, not the supplier's.
This article is general information and not legal or regulatory advice. Confirm your specific approach with your notified body and qualified regulatory advisors.
Under the MDR, external capacity is only useful if its output is already ready for the notified body when it arrives. niogod™ pods work inside the manufacturer's QMS and toolchain under a Werkvertrag whose sprint Abnahme includes the IEC 62304 records, with a German-speaking Projektleiter as the contact for your QA/RA team and access handled as described on our security page. If a recertification or a new software release is planned before the 2027 and 2028 deadlines, it is a conversation worth having early.
Talk to niogod™
Planning engineering capacity in DACH? Book a 30-minute consultation with the niogod™ team.
Book consultation