Contract Development and Manufacturing Organization (CDMO)

A Contract Development and Manufacturing Organization (CDMO) is a company that provides outsourced design, engineering, and manufacturing services for medical devices on behalf of an OEM. It carries a device from early concept through verified production under a certified quality system such as ISO 13485, adding engineering and manufacturing capacity that a device company would otherwise build in-house.


What is a Contract Development and Manufacturing Organization (CDMO)?

A Contract Development and Manufacturing Organization, or CDMO, sits between a medical device OEM’s idea and a shippable, regulated product. Rather than splitting design work and production across separate vendors, a CDMO combines both under one contract and one quality system, so a device moves from user needs and concept sketches through design controls, verification and validation, design transfer, and volume manufacturing with a single accountable partner.

The “development” half covers mechanical, electrical, embedded, and software engineering, plus risk management and usability work. The “manufacturing” half covers everything from PCB assembly and injection molding to final device integration, packaging, and labeling. Some CDMOs specialize in one phase; a full-service CDMO covers the whole arc, which is what most OEMs mean when they use the term today.


Why a CDMO matters in medical device development

Choosing a CDMO is a regulatory decision as much as a commercial one. Under FDA 21 CFR Part 820 and EU MDR 2017/745, the OEM remains the legal manufacturer and stays responsible for the device’s safety and quality even when a CDMO builds it. That means the CDMO’s quality system, documentation practices, and audit history feed directly into the OEM’s own compliance risk.

Time-to-market is the other driver. A CDMO with in-house design, tooling, and cleanroom manufacturing can move a device from design freeze to first article inspection without the handoffs and schedule risk of coordinating separate design and manufacturing vendors. For a startup, that gap can decide whether a funding-linked milestone is hit or missed. For an established OEM, it can free internal engineering headcount for next-generation platforms while the CDMO owns sustaining production of the current one.


How a CDMO engagement works

A CDMO engagement typically moves through defined phases, each with its own deliverables and design controls documentation:

  • Feasibility and concept: user needs analysis, initial risk assessment under ISO 14971, and technology selection.
  • Design and development: mechanical, electrical, embedded, and software engineering against documented design inputs.
  • Verification and validation: bench testing, IEC 60601-1 electrical safety and EMC testing, software verification under IEC 62304, and usability validation per IEC 62366-1.
  • Design transfer: moving the verified design into a controlled manufacturing process, including process validation (IQ/OQ/PQ) and first article inspection.
  • Production and sustaining: volume manufacturing, supply-chain management, and change control through the device’s commercial life.

Throughout, the CDMO operates under a quality management system certified to ISO 13485, maintaining design history file (DHF) and device master record (DMR) documentation that the OEM can present to notified bodies or the FDA during a submission or audit. Contracts typically define ownership of intellectual property, responsibility for regulatory submissions, and which party holds the manufacturing license in a given market, since these terms vary by CDMO and by country.


Common challenges and best practices

The most common failure mode is treating CDMO selection as a pricing exercise. Two CDMOs quoting similar per-unit costs can carry very different audit risk if one has a thin quality system or a history of FDA 483 observations. OEMs that skip a quality-system audit before signing often pay for it later in delayed submissions or post-market findings.

Communication during design transfer is another weak point. A design that verifies cleanly on an engineering bench can still fail process validation if manufacturing tolerances, fixture design, or component sourcing were not considered during development. CDMOs that avoid this problem build manufacturing engineers into the design phase instead of handing off a finished design and expecting production to make it work on its own.

Good practice on the OEM side includes defining design inputs and acceptance criteria clearly up front, requesting the CDMO’s quality manual and recent audit history, and clarifying early who owns regulatory submissions and post-market surveillance obligations once the device ships.


How SJML helps with contract development and manufacturing

SJML operates as an end-to-end medical device CDMO, combining design and engineering, manufacturing, and regulatory compliance under one quality system instead of splitting them across vendors. Its engineering teams cover mechanical, electronics, embedded, and software design with risk management and usability engineering built into the process, backed by in-house electrical safety, EMC, and reliability testing. On the manufacturing side, SJML runs cleanroom PCB assembly, medical-grade plastics and precision metal work, and system integration with process validation and traceability. A dedicated QARA team supports regulatory strategy, submissions, and post-market surveillance, so OEMs get design, build, and compliance from one accountable partner.

Talk to SJML’s engineering team →


Frequently asked questions

What is the difference between a CDMO and a CMO?

A CMO, or Contract Manufacturing Organization, handles production only: molding, PCB assembly, and final build. A CDMO adds development services such as mechanical, electrical, embedded, and software engineering, so the same company can take a device from concept through manufacturing instead of starting only once a design is finished.

Does the OEM or the CDMO hold FDA and EU MDR compliance responsibility?

The OEM is the legal manufacturer under FDA 21 CFR Part 820 and EU MDR 2017/745, and keeps ultimate responsibility for the device’s safety and regulatory compliance. The CDMO’s quality system and documentation support that compliance, but contracts should state clearly who prepares and owns submissions, technical files, and post-market surveillance records.

When should a medical device company use a CDMO instead of building in-house?

A CDMO makes sense when a company needs specialized engineering, cleanroom manufacturing, or regulatory experience it does not have internally, or when speed to launch matters more than owning fixed manufacturing assets. Building in-house can make more sense at very high volumes with a stable, mature design and no near-term change traffic.

What quality standards do medical device CDMOs typically operate under?

Most established medical device CDMOs are certified to ISO 13485 for quality management and often ISO 27001 for information security. Their engineering and manufacturing processes reference IEC 60601-1 for electrical safety, IEC 62304 for software, IEC 62366-1 for usability, and ISO 14971 for risk management, aligned to FDA 21 CFR Part 820 and EU MDR 2017/745.


Related terms

  • Design Transfer
  • Original Equipment Manufacturer (OEM)
  • Design History File (DHF)
  • Device Master Record (DMR)
  • Design Verification and Validation (V&V)

Table of Contents

Free EU MDR Technical Documentation Compliance Checklist

Understand documentation gaps and use our single-window worksheet to prepare for Notified Body review.

Related Glossaries

Ask Sygma AI

AI-Powered Assistant

SJ Assistant