<?xml version="1.0" encoding="UTF-8"?>        <rss version="2.0"
             xmlns:atom="http://www.w3.org/2005/Atom"
             xmlns:dc="http://purl.org/dc/elements/1.1/"
             xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
             xmlns:admin="http://webns.net/mvcb/"
             xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
             xmlns:content="http://purl.org/rss/1.0/modules/content/">
        <channel>
            <title>
									Customer Needs and Design Input - Introduction to Design Controls				            </title>
            <link>https://medicaldevicecourses.com/forums/introduction-to-design-controls/customer-needs-and-design-input/</link>
            <description>Medical Device Courses Discussion Board</description>
            <language>en-US</language>
            <lastBuildDate>Sun, 13 Sep 2026 11:45:52 +0000</lastBuildDate>
            <generator>wpForo</generator>
            <ttl>60</ttl>
							                    <item>
                        <title>RE: Customer Needs and Design Input</title>
                        <link>https://medicaldevicecourses.com/forums/introduction-to-design-controls/customer-needs-and-design-input/paged/5/#post-22622</link>
                        <pubDate>Sat, 08 Nov 2025 15:47:08 +0000</pubDate>
                        <description><![CDATA[Understanding customer needs and translating them into clear design inputs is a fundamental step in medical device development, typically documented in the Design Input Document (DID). Custo...]]></description>
                        <content:encoded><![CDATA[<p>Understanding customer needs and translating them into clear design inputs is a fundamental step in medical device development, typically documented in the Design Input Document (DID). Customer needs, gathered from clinicians, patients, and other end users, are analyzed and converted into measurable, testable requirements within the DID. These inputs then guide the creation of the Design Specification Document (DSD), which details the engineering and technical parameters necessary to meet those needs. A well-prepared DID ensures that the DSD accurately reflects safety, performance, and usability expectations. Failure to properly document and link customer needs in the DID and DSD can lead to design gaps, usability problems, or noncompliance with regulatory standards. Continuous communication among design, clinical, and regulatory teams ensures that these documents stay aligned throughout development. Ultimately, well-structured DID and DSD documents help ensure that the final medical device meets user expectations, regulatory requirements, and clinical performance goals.</p>]]></content:encoded>
						                            <category domain="https://medicaldevicecourses.com/forums/introduction-to-design-controls/">Introduction to Design Controls</category>                        <dc:creator>ri62</dc:creator>
                        <guid isPermaLink="true">https://medicaldevicecourses.com/forums/introduction-to-design-controls/customer-needs-and-design-input/paged/5/#post-22622</guid>
                    </item>
				                    <item>
                        <title>RE: Customer Needs and Design Input</title>
                        <link>https://medicaldevicecourses.com/forums/introduction-to-design-controls/customer-needs-and-design-input/paged/5/#post-22614</link>
                        <pubDate>Thu, 06 Nov 2025 22:24:32 +0000</pubDate>
                        <description><![CDATA[In terms of design controls, the connection between the Design Input Document (DID) and the Design Specification Document (DSD) is essential to guaranteeing that a product is created methodi...]]></description>
                        <content:encoded><![CDATA[<p>In terms of design controls, the connection between the Design Input Document (DID) and the Design Specification Document (DSD) is essential to guaranteeing that a product is created methodically, precisely, and in accordance with legal requirements. In the process of developing a product, each has a specific function: the DSD specifies how the device will fulfill its requirements, while the DID specifies what the device must perform. Effective communication and responsibility throughout the project depend on this separation, which guarantees clarity between engineering execution and user needs. The DSD outlines how to turn that vision into a concrete, testable, and manufacturable reality, while the DID explains why the product should exist and what it should accomplish from a functional and therapeutic standpoint. Together, they provide the basis for traceability, which is essential to FDA and ISO 13485 design control compliance and guarantees that each design choice can be linked to an original user requirement. Without one, the process is either too restricted or too unclear. This raises the question of which document, in your perspective or experience, is more difficult to accurately maintain: the DSD with its intricate engineering limitations or the DID with its changing user requirements. In the end, the DID and DSD are complementary components of a single, well-managed design process. One guarantees that the device performs its intended function in a safe and efficient manner, while the other guarantees that the design can be consistently produced in accordance with those criteria. When combined, they safeguard the patient's safety as well as the product's integrity, which is the ultimate objective of any medical device development endeavor.</p>]]></content:encoded>
						                            <category domain="https://medicaldevicecourses.com/forums/introduction-to-design-controls/">Introduction to Design Controls</category>                        <dc:creator>NevinAntony</dc:creator>
                        <guid isPermaLink="true">https://medicaldevicecourses.com/forums/introduction-to-design-controls/customer-needs-and-design-input/paged/5/#post-22614</guid>
                    </item>
				                    <item>
                        <title>RE: Customer Needs and Design Input</title>
                        <link>https://medicaldevicecourses.com/forums/introduction-to-design-controls/customer-needs-and-design-input/paged/5/#post-22606</link>
                        <pubDate>Wed, 05 Nov 2025 18:27:51 +0000</pubDate>
                        <description><![CDATA[The Design Input Document (DID) and Design Specification Document (DSD) are both important for developing a medical device, but they serve different purposes. The DID provides a broad overvi...]]></description>
                        <content:encoded><![CDATA[<p>The Design Input Document (DID) and Design Specification Document (DSD) are both important for developing a medical device, but they serve different purposes. The DID provides a broad overview of the product concept, describing what the device should do and what the customer or user needs. It’s more qualitative and helps the team visualize the product’s goals and appearance. The DSD, on the other hand, gives quantitative technical details—such as measurements, materials, and tolerances—that guide manufacturing and ensure product consistency. The main advantage of the DID is flexibility and creativity during early development, while the DSD ensures precision and compliance with regulatory and quality standards. Without the DID, designers might lose sight of user needs; without the DSD, the product might not meet safety or performance requirements. </p>]]></content:encoded>
						                            <category domain="https://medicaldevicecourses.com/forums/introduction-to-design-controls/">Introduction to Design Controls</category>                        <dc:creator>Mariam Faragalla</dc:creator>
                        <guid isPermaLink="true">https://medicaldevicecourses.com/forums/introduction-to-design-controls/customer-needs-and-design-input/paged/5/#post-22606</guid>
                    </item>
				                    <item>
                        <title>RE: Customer Needs and Design Input</title>
                        <link>https://medicaldevicecourses.com/forums/introduction-to-design-controls/customer-needs-and-design-input/paged/5/#post-18699</link>
                        <pubDate>Mon, 13 Nov 2023 02:47:40 +0000</pubDate>
                        <description><![CDATA[I belive that both inputs and specifications have their intended purposes. In terms of actually constructing a device, it is impossible to do so based on solely inputs. Specifications are ne...]]></description>
                        <content:encoded><![CDATA[<p>I belive that both inputs and specifications have their intended purposes. In terms of actually constructing a device, it is impossible to do so based on solely inputs. Specifications are needed for the actual construction of the device and for the device to be constructed identically during the manufacturing process. However, inputs are important because they lay out how the design meets the intended needs without going into unnecessary detail. For instance, when describing a project to a group of investors, it is much more useful to talk to them about the inputs rather than the specifications. The inputs as the question of how the device works without the unnecessary details such as individual measurements or tolerances. Also, you need an input document in order to make a specifications document. </p>]]></content:encoded>
						                            <category domain="https://medicaldevicecourses.com/forums/introduction-to-design-controls/">Introduction to Design Controls</category>                        <dc:creator>noahyoussef</dc:creator>
                        <guid isPermaLink="true">https://medicaldevicecourses.com/forums/introduction-to-design-controls/customer-needs-and-design-input/paged/5/#post-18699</guid>
                    </item>
				                    <item>
                        <title>RE: Customer Needs and Design Input</title>
                        <link>https://medicaldevicecourses.com/forums/introduction-to-design-controls/customer-needs-and-design-input/paged/4/#post-16371</link>
                        <pubDate>Mon, 14 Nov 2022 06:46:11 +0000</pubDate>
                        <description><![CDATA[DID is the rough sketch of requirement whereas DSD is the specification of those requirements so both are needed. It&#039;s simple.]]></description>
                        <content:encoded><![CDATA[<p>DID is the rough sketch of requirement whereas DSD is the specification of those requirements so both are needed. It's simple.</p>]]></content:encoded>
						                            <category domain="https://medicaldevicecourses.com/forums/introduction-to-design-controls/">Introduction to Design Controls</category>                        <dc:creator>jt63</dc:creator>
                        <guid isPermaLink="true">https://medicaldevicecourses.com/forums/introduction-to-design-controls/customer-needs-and-design-input/paged/4/#post-16371</guid>
                    </item>
				                    <item>
                        <title>RE: Customer Needs and Design Input</title>
                        <link>https://medicaldevicecourses.com/forums/introduction-to-design-controls/customer-needs-and-design-input/paged/4/#post-16327</link>
                        <pubDate>Sun, 13 Nov 2022 21:40:30 +0000</pubDate>
                        <description><![CDATA[Both are important to have since the DID is more overarching and lets you trace inputs to outputs and requirements. It is also easier to read since it does not include all of the specifics w...]]></description>
                        <content:encoded><![CDATA[<p>Both are important to have since the DID is more overarching and lets you trace inputs to outputs and requirements. It is also easier to read since it does not include all of the specifics which may be unnecessary for what you need. The DSD is very important in its own right since manufacturing needs the exact specifications to be able to make the product correctly.</p>]]></content:encoded>
						                            <category domain="https://medicaldevicecourses.com/forums/introduction-to-design-controls/">Introduction to Design Controls</category>                        <dc:creator>ac825</dc:creator>
                        <guid isPermaLink="true">https://medicaldevicecourses.com/forums/introduction-to-design-controls/customer-needs-and-design-input/paged/4/#post-16327</guid>
                    </item>
				                    <item>
                        <title>RE: Customer Needs and Design Input</title>
                        <link>https://medicaldevicecourses.com/forums/introduction-to-design-controls/customer-needs-and-design-input/paged/4/#post-16317</link>
                        <pubDate>Sun, 13 Nov 2022 19:05:25 +0000</pubDate>
                        <description><![CDATA[Although we cannot say that these two documents are the same, we can say that they are similar to each other. While DID is a document prepared by marketing and contributed by other departmen...]]></description>
                        <content:encoded><![CDATA[<p>Although we cannot say that these two documents are the same, we can say that they are similar to each other. While DID is a document prepared by marketing and contributed by other departments, DSD is filled by the technical department. While DID is about needs, DSD can be considered as a document that enables needs to come to fruition. another important thing is, DID helps to prepare DSD.</p>]]></content:encoded>
						                            <category domain="https://medicaldevicecourses.com/forums/introduction-to-design-controls/">Introduction to Design Controls</category>                        <dc:creator>MK</dc:creator>
                        <guid isPermaLink="true">https://medicaldevicecourses.com/forums/introduction-to-design-controls/customer-needs-and-design-input/paged/4/#post-16317</guid>
                    </item>
				                    <item>
                        <title>RE: Customer Needs and Design Input</title>
                        <link>https://medicaldevicecourses.com/forums/introduction-to-design-controls/customer-needs-and-design-input/paged/4/#post-16298</link>
                        <pubDate>Fri, 11 Nov 2022 16:07:50 +0000</pubDate>
                        <description><![CDATA[In my opinion, the DID is helpful in creating something appealing to the customer visually and allows for the customers needs to be heard in a general sense. This document gives the engineer...]]></description>
                        <content:encoded><![CDATA[<p>In my opinion, the DID is helpful in creating something appealing to the customer visually and allows for the customers needs to be heard in a general sense. This document gives the engineers a general idea of how the device should look and what general features the customer would want to make it easier for their use. The DSD is more for the engineers. The DSD provides more detailed specifications to the generic wants and needs that the customers wanted for the device. The details are extremely important for the creation of the device because you don't want a device that is too large or too small for a customer to use and we want to make sure that the device is also easy to use for the customers.  Both documents are extremely important is design creation and you need to do both to create your product. The DID is more a generic start for your design and the DSD gives you more specific details. These devices both play off each other in order to develop the device. </p>]]></content:encoded>
						                            <category domain="https://medicaldevicecourses.com/forums/introduction-to-design-controls/">Introduction to Design Controls</category>                        <dc:creator>knm7</dc:creator>
                        <guid isPermaLink="true">https://medicaldevicecourses.com/forums/introduction-to-design-controls/customer-needs-and-design-input/paged/4/#post-16298</guid>
                    </item>
				                    <item>
                        <title>RE: Customer Needs and Design Input</title>
                        <link>https://medicaldevicecourses.com/forums/introduction-to-design-controls/customer-needs-and-design-input/paged/4/#post-16290</link>
                        <pubDate>Wed, 09 Nov 2022 17:22:31 +0000</pubDate>
                        <description><![CDATA[The Design Specification Document (DSD) gives the numerical details of the product and explains every individual piece with the size and tolerance. The DSD can contain all the drawings and b...]]></description>
                        <content:encoded><![CDATA[<p>The Design Specification Document (DSD) gives the numerical details of the product and explains every individual piece with the size and tolerance. The DSD can contain all the drawings and blueprints of the device; also, it is essential to include tolerances because the FDA can look into your product and measure each piece, and if the numbers don't line up, then your product can be recalled. The Design Input Document (DID) gives the product's overall desires, like the color. The whole team and customers provide input on the DID, and the team considers the desires for the device. I don't think the DID should have its own document; I believe it should be within the DSD since it is not that major of a component. </p>
<p> </p>]]></content:encoded>
						                            <category domain="https://medicaldevicecourses.com/forums/introduction-to-design-controls/">Introduction to Design Controls</category>                        <dc:creator>AJY6</dc:creator>
                        <guid isPermaLink="true">https://medicaldevicecourses.com/forums/introduction-to-design-controls/customer-needs-and-design-input/paged/4/#post-16290</guid>
                    </item>
				                    <item>
                        <title>RE: Customer Needs and Design Input</title>
                        <link>https://medicaldevicecourses.com/forums/introduction-to-design-controls/customer-needs-and-design-input/paged/4/#post-16283</link>
                        <pubDate>Mon, 07 Nov 2022 04:53:50 +0000</pubDate>
                        <description><![CDATA[Both the DID and DSD are important because one relies on the other. Design input is broad, so it will be easier to pertain and summarize the scope of your project: just form reading the inpu...]]></description>
                        <content:encoded><![CDATA[<p>Both the DID and DSD are important because one relies on the other. Design input is broad, so it will be easier to pertain and summarize the scope of your project: just form reading the inputs, you as either a manufacturers, designer, or provider will have an understating of what materials you might need in general for the development of your device. However, the disadvantage of this will be, you will not have the specifications, such as how much of the materials you might need. Design specifications will go into specifics, so now you can understand the quantities of the materials you might need, but additionally what they do and how they contribute to the functionality for the device. This will again go into specifics, and as a result there will most likely be wording that will be in general difficult to understand for someone not familiar with the device. As a result, if you did not understand the DID you will most likely have a hard time understanding the project through the DSD. Hence why both documents are equally as important.</p>]]></content:encoded>
						                            <category domain="https://medicaldevicecourses.com/forums/introduction-to-design-controls/">Introduction to Design Controls</category>                        <dc:creator>sg</dc:creator>
                        <guid isPermaLink="true">https://medicaldevicecourses.com/forums/introduction-to-design-controls/customer-needs-and-design-input/paged/4/#post-16283</guid>
                    </item>
							        </channel>
        </rss>
		