SBS - The best value in QMS software

Design History File (DHF) for New Generation of Product

M

mscottf

Scott Fine
#1
#1
I work for a med device startup that is still in a development phase. The first generation product (GEN 1) has a well-laid out Design History File (DHF), maintained both in an index and a separate hard copy set of documents, but will not be developed further.

GEN 2 has some significant changes but is basically an evolution of GEN 1. I intend to only maintain an index as keeping a hard copy set seems a waste of time, although the auditors like it.

Should all the documents in the GEN 1 DHF be included in the GEN 2 DHF? There would then be 2 sets of customer requirements, product requirements, user requirements, software development plans, etc. If so, should I identify each document as being for GEN 1 or GEN 2, or both?

I took over this project from my predecessor and did not have input into the first DHF.

Thanks in advance for your help.
 
Standard Work Instruction Software by Dozuki
Elsmar Forum Sponsor
T

TWA - not the airline

Trusted Information Resource
#2
#2
First and foremost: What does your Design Control procedure require?

Can you handle this as a design change, i.e. indication/contraindication/user group and environment/performance requirements stay the same? If so, then you'd need to follow your design control/change control procedures and IMHO typically you'd keep the old DHF and just up-date the respective sections regarding design output and design verification&validation with either a new revision or a new doc valid only for GEN2.
If not then it probably would be considered a really new product and you'd develop it acc. to your design control procedure and typically you'd end up with a complete set of documents, where even the ones that have a copy&paste content would at least have to be reviewed again during design review. In that case I personally would not just reference to the doc of the GEN1 DHF...
 
Ronen E

Ronen E

Problem Solver
Staff member
Moderator
#3
#3
mscottf said:
I work for a med device startup that is still in a development phase. The first generation product (GEN 1) has a well-laid out Design History File (DHF), maintained both in an index and a separate hard copy set of documents, but will not be developed further.

GEN 2 has some significant changes but is basically an evolution of GEN 1. I intend to only maintain an index as keeping a hard copy set seems a waste of time, although the auditors like it.

Should all the documents in the GEN 1 DHF be included in the GEN 2 DHF? There would then be 2 sets of customer requirements, product requirements, user requirements, software development plans, etc. If so, should I identify each document as being for GEN 1 or GEN 2, or both?

I took over this project from my predecessor and did not have input into the first DHF.

Thanks in advance for your help.
Click to expand...
I would simply reference GEN 1 DHF index (as a whole) in GEN 2 DHF.

Cheers,
Ronen.
 
O

Oscar Wang

#4
#4
TWA said:
First and foremost: What does your Design Control procedure require?

Can you handle this as a design change, i.e. indication/contraindication/user group and environment/performance requirements stay the same? If so, then you'd need to follow your design control/change control procedures and IMHO typically you'd keep the old DHF and just up-date the respective sections regarding design output and design verification&validation with either a new revision or a new doc valid only for GEN2.
If not then it probably would be considered a really new product and you'd develop it acc. to your design control procedure and typically you'd end up with a complete set of documents, where even the ones that have a copy&paste content would at least have to be reviewed again during design review. In that case I personally would not just reference to the doc of the GEN1 DHF...
Click to expand...
Aye. do you think all DHFs of your GEN 1 are suitable for GEN2 including all descriptive informaiton in these DHF? If so, i suggest you follow a change control process but not a brand new NPI process.
 
You must log in or register to reply here.
Thread starter Similar threads Forum Replies Date
A Design History File - Not ready to share the design drawings or Bill of Material US Food and Drug Administration (FDA) 2
R No design history file or device master record ISO 13485:2016 - Medical Device Quality Management Systems 5
R Suggestions for putting together a DHF (Design History File) ISO 13485:2016 - Medical Device Quality Management Systems 3
D Questions about the contents of a Design History File 21 CFR Part 820 - US FDA Quality System Regulations (QSR) 3
E Updating DHF (Design History File) to include Alternative Component 21 CFR Part 820 - US FDA Quality System Regulations (QSR) 2
V Template / format for Device History File & Design Verification of transdermal patch 21 CFR Part 820 - US FDA Quality System Regulations (QSR) 1
JoCam Ownership of Design History File EU Medical Device Regulations 6
K ISO 13485 and DHF (Design History File) requirements ISO 13485:2016 - Medical Device Quality Management Systems 9
N 510k without DHF (Design History File) that we bought a 3 years ago US Food and Drug Administration (FDA) 4
A DHF (Design History File) for a Legacy Product (Class iii Medical Device) 21 CFR Part 820 - US FDA Quality System Regulations (QSR) 6
B When To Share Your DHF (Design History File) With A Customer US Food and Drug Administration (FDA) 1
S Cost Targets as Design Inputs in your DHF (Design History File) US Food and Drug Administration (FDA) 7
C Should Research Findings be in the Design History File? 21 CFR Part 820 - US FDA Quality System Regulations (QSR) 1
renenatasha Usage of web articles in DHF (Design History File) 21 CFR Part 820 - US FDA Quality System Regulations (QSR) 10
A Medical Device DHF (Design History File) - One per Design Change? 21 CFR Part 820 - US FDA Quality System Regulations (QSR) 17
L Creating DHF (Design History File) for Medical Device Systems Design and Development of Products and Processes 8
O ISO Standards For Intramedullary Pin Design History File Other Medical Device Related Standards 2
K How to start a Design History File (DHF) for Medical devices Company 21 CFR Part 820 - US FDA Quality System Regulations (QSR) 2
R Design History File DHF Practices and Contract Manufacturer 21 CFR Part 820 - US FDA Quality System Regulations (QSR) 2
D Design History File (DHF) - Buy-For-Resell Products 21 CFR Part 820 - US FDA Quality System Regulations (QSR) 7
A Design History File Maintenance - Who is responsible for the Design History File 21 CFR Part 820 - US FDA Quality System Regulations (QSR) 5
M What are typical Roles & Responsibilities of DHF (Design History File) Librarian? US Food and Drug Administration (FDA) 6
H Paper based DHF (Design History File) updates for Software Updates 21 CFR Part 820 - US FDA Quality System Regulations (QSR) 4
R Who should document the Design Review Meeting and Design History File? 21 CFR Part 820 - US FDA Quality System Regulations (QSR) 8
Q DMR-Device Master Record vs DHF-Design History File vs DHR-Device History Record 21 CFR Part 820 - US FDA Quality System Regulations (QSR) 50
C Remediating a Design History File (DHF) for an IVD developed prior to 1997 21 CFR Part 820 - US FDA Quality System Regulations (QSR) 4
S Design History File (DHF) Maintenance Information wanted 21 CFR Part 820 - US FDA Quality System Regulations (QSR) 6
O DHF (Design History File) Template Other US Medical Device Regulations 13
C How to establish a Design History file (DHF)? 21 CFR Part 820 - US FDA Quality System Regulations (QSR) 15
W Design History File (DHF) Template Example for Consideration. Design and Development of Products and Processes 12
S Which documents in the DHF (Design History File) should be controlled? ISO 13485:2016 - Medical Device Quality Management Systems 2
Q DHF (Design History File) on New Medical Device Product ISO 13485:2016 - Medical Device Quality Management Systems 9
M Design History File - Medical Device Quality Systems Manual Section 3, Design Control Design and Development of Products and Processes 1
R Implementing Design History Documents/ Technical Documents in the QMS ISO 13485:2016 - Medical Device Quality Management Systems 3
N Design Validation Conventions for Design History Files 21 CFR Part 820 - US FDA Quality System Regulations (QSR) 5
B Design history files for combination products 21 CFR Part 820 - US FDA Quality System Regulations (QSR) 1
W Maintaining Component Traceability in DHR (Design History Record) 21 CFR Part 820 - US FDA Quality System Regulations (QSR) 5
A Medical Device Service Records linked to DHR (Design History Record)? 21 CFR Part 820 - US FDA Quality System Regulations (QSR) 2
E Better control of DHR (Design History Record) during processing Document Control Systems, Procedures, Forms and Templates 5
R Cloud Computing Requirements for Design History Files for Software Medical Devices 21 CFR Part 820 - US FDA Quality System Regulations (QSR) 4
M DHR (Design History Record) Requirements - Concessions Quality Manager and Management Related Issues 12
W Design History Verification Records Control and Approvals US Food and Drug Administration (FDA) 3
A Is a Distributor responsible for Design History Files 21 CFR Part 820 - US FDA Quality System Regulations (QSR) 10
H Working from a previous design history. How can I best leverage the exisitng DHF? Other US Medical Device Regulations 4
N Example for design and development planning,input,output,review,verification,validation and transfer Misc. Quality Assurance and Business Systems Related Topics 4
A 8.6 Release of products and services, 8.3 Design and development - evidence required ISO 9000, ISO 9001, and ISO 9004 Quality Management Systems Standards 9
C Stress / Challenge Conditions for Design Verification Testing to Reduce Sample Size 21 CFR Part 820 - US FDA Quality System Regulations (QSR) 11
J Significant change related to design and intended use EU Medical Device Regulations 2
S Traceability of requirements to design and risk Design and Development of Products and Processes 3
U NOC - What is considered a "design change" EU Medical Device Regulations 5

Similar threads

Top Bottom