<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Contract Manufacturing &#8211; ComplianceAcuity</title>
	<atom:link href="https://www.complianceacuity.com/category/contract-manufacturing/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.complianceacuity.com</link>
	<description>Medical Device Regulatory Consultants</description>
	<lastBuildDate>Thu, 06 Apr 2023 20:22:35 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.0.2</generator>

<image>
	<url>https://www.complianceacuity.com/wp-content/uploads/2021/06/Screen-Shot-2021-06-30-at-11.34.06-AM.png</url>
	<title>Contract Manufacturing &#8211; ComplianceAcuity</title>
	<link>https://www.complianceacuity.com</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>ISO 13485: Design &#038; Development Obligations of Contract Manufacturers</title>
		<link>https://www.complianceacuity.com/iso-13485-design-development-obligations-of-contract-manufacturers/</link>
					<comments>https://www.complianceacuity.com/iso-13485-design-development-obligations-of-contract-manufacturers/#respond</comments>
		
		<dc:creator><![CDATA[Kevin Randall]]></dc:creator>
		<pubDate>Wed, 29 Mar 2023 14:55:57 +0000</pubDate>
				<category><![CDATA[Contract Manufacturing]]></category>
		<category><![CDATA[Design & Development]]></category>
		<category><![CDATA[ISO 13485]]></category>
		<guid isPermaLink="false">https://www.complianceacuity.com/?p=16954</guid>

					<description><![CDATA[March 29, 2023 ISO 13485: Design &#38; Development Obligations of Contract Manufacturers &#160; As a general rule, a contract manufacturer who doesn&#8217;t perform any design and development for the subject device is thereby not required to have design and development in the scope of that contract manufacturer&#8217;s ISO 13485 certificate.  So its certificate scope statement [&#8230;]]]></description>
										<content:encoded><![CDATA[<p>March 29, 2023</p>
<h1>ISO 13485: Design &amp; Development Obligations of Contract Manufacturers</h1>
<p>&nbsp;</p>
<h3>As a general rule, a contract manufacturer who doesn&#8217;t perform any design and development for the subject device is thereby not required to have design and development in the scope of that contract manufacturer&#8217;s ISO 13485 certificate.  So its certificate scope statement would be something like, &#8220;<em>The contract manufacturing of ABC widget devices</em>&#8220;, whereas the original manufacturer&#8217;s certificate scope would be something like, &#8220;<em>The design and manufacture of</em>&#8230;&#8221;.  As a general rule, the OEM, rather than the contract manufacturer, is ultimately accountable and responsible for design and development in this kind of scenario.</h3>
<p>&nbsp;</p>
<h3>But if the contractor performs / leads any design and development operations, then that could trigger the need for design to be included in its QMS and certificate depending on the nature of those operations.  In such cases, different ISO registrars might have varying interpretations about how they want the certificate scope statement to read; accordingly, consulting the particular ISO registrar(s) involved is a good idea in my opinion regarding borderline scenarios.</h3>
]]></content:encoded>
					
					<wfw:commentRss>https://www.complianceacuity.com/iso-13485-design-development-obligations-of-contract-manufacturers/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
	</channel>
</rss>
