The Elsmar Cove Wiki More Free Files The Elsmar Cove Forums Discussion Thread Index Post Attachments Listing Failure Modes Services and Solutions to Problems Elsmar cove Forums Main Page Elsmar Cove Home Page
Google
  Web Elsmar.com
*Please be aware that SOME RECENT forum threads may not yet be indexed by Google.

View Full Version : Working from a previous design history. How can I best leverage the exisitng DHF?


HighRisk
16th March 2009, 03:09 AM
We acquired a medical device design from another company and it came with a pretty complete design history for a specific intended use. We plan to use the same design for a different intended use with essentially no change. How can I best leverage the exisitng DHF without re-doing all the work. For example, can I treat the entire previous DHF as design input to my "new" device, and only update the risk analysis and design validation?

Thanks for your inputs.

gholland
17th March 2009, 07:02 PM
Do you have your own list of input requirements? You could leverage the existing work when linking Outputs (what you have from the existing DHF) to Inputs.

HighRisk
17th March 2009, 08:01 PM
Actually, I was thinking that the old DHF (including the design outputs from that) would be part of my new product's design INPUT. In addition, I will also need a new statement of intended use and requirements specific to that use. Then I can have an abbreviated design plan. Does that make sense?

gholland
18th March 2009, 02:43 AM
It is probably just semantics. 'Inputs' where I am used to working are the requirements of your device, both external (customer requirements) and internal. You most likely have a list of things your device is required to do and you could easily link your existing DHF to these requirements w/out re-doing the work.

The way we would handle it is we would make a requirements document listing the requirement, acceptance criteria, source of the requirement, etc. Then we would have a results document that would link each requirement to the existing paperwork and you would be able to state 'xxx document from the prior DHF shows the device meets this requirement'. This would also show you where you have holes in your coverage.

HighRisk
18th March 2009, 10:38 AM
Yes, creating a requirements document sounds like it would work perfectly for us. Really appreciate the "input"!