In-depth interpretationTechnical deep dive
What Annex C is for
Annex C (normative) defines the procedure by which a working group, manufacturer or individual proposes a new small-bore connector design for inclusion in the ISO/IEC 80369 series - either for a new clinical application or, via Clause 6, as an alternative within an existing one. The applicant applies to the standards body and, under C.1.2, carries the responsibility to identify and declare any patent rights in the design.
Annex A (A.2.11) explains the twin purpose of the proposal: justify a new application category, and introduce the connector design for it. Safety justification rests on severity analysis of wrong-route delivery - the same evidence base of risk analyses, adverse events and reported complaints used throughout Part 1.
The design proposal (C.2)
The proposal must describe every related connection that needs to be non-interconnectable, support the case with a literature review and an analysis of adverse events and complaints, and be grounded in the existing harm profile of wrong-route delivery between applications.
Design requirements must cover the user profile and use environment, the functional requirements preserving clinical performance, the requirements needed to avoid unacceptable risk, and the requirements maintaining non-interconnectability - plus the ISO 14971 risk analysis, including results from comparable earlier designs. A complete user interface specification satisfying all design requirements closes the submission.
The user interface specification: usability is not optional
C.2c) requires the user interface specification to embed the risk controls needed for acceptable risk, explicitly considering misuse, ageing, and the effects of cleaning and disinfection and, where applicable, cleaning and sterilisation. These factors matter because a connector that loses its geometry in service loses its non-interconnectability.
Design confirmation (C.3.4) closes the loop with a summative evaluation of hazard-related use scenarios in a clinical or simulated environment, using the intended user population on the target device, with conclusions that are statistically justified and demonstrate the performance objectives were met.
Engineering analysis (C.3.1)
The design is analysed against the non-interconnectability detail of Annex B and against the performance requirements: evaluation of the proposed design at minimum and maximum tolerance states against all existing and proposed series designs, using CAD evaluation or equivalent feasibility tools. This is where a proposal usually discovers which of the four Annex B interface types drives its critical clearances.
Design verification (C.3.3)
Verification combines design review with verification testing across four demonstration targets: conformance to the specification, satisfaction of the physical performance characteristics, compliance with the Clause 4 non-interconnectability requirement, and satisfaction of the medical device performance requirements.
- Dimensional analysis per Annex B.
- Physical testing, including the misconnection test where indicated.
- Medical device performance testing with a sample size sufficient for statistical analysis.
- A verification report summary covering the identified design requirements and every specification element.
Review and the data and report summary (C.4)
The standards body reviews the submission and decides whether the connector is added to the series for the intended application. The applicant compiles a data and report summary as an informative annex that becomes the factual basis for drafting the future part of the standard. Annex E of Part 1 is itself the worked example: every residual misconnection, its test result and its risk justification, tabulated for public scrutiny.
Practical guidance for manufacturers
Two strategic notes from the laboratory side. First, the Chapter 6 alternative-design route and the Annex C series-inclusion route share most of their evidence - dimensional analysis, misconnection testing and engineering analysis - so designing the evidence pack once for dual use avoids duplicated programmes. Second, connectability is not binary: Annex E teaches that accepted residual misconnections are normal, and a submission that honestly characterises them with severity-based reasoning is far stronger than one claiming absolute incompatibility.