DHR (Device History Record) for Medical Device Software

I

ic007832

#1
Hi,

I have read lots of things about DHR which is applicable to manafacturing industry(medical device).
Can somebody help me in understanding following question about DHR for software industry(medical device).
What is DHR?what is the intended of DHR?What DHR should contain for software product?

Thanks
 
Elsmar Forum Sponsor

Stijloor

Staff member
Super Moderator
#2
Re: DHR for software

Hi,

I have read lots of things about DHR which is applicable to manafacturing industry(medical device).
Can somebody help me in understanding following question about DHR for software industry(medical device).
What is DHR?what is the intended of DHR?What DHR should contain for software product?

Thanks
Welcome to The Cove Forums! :bigwave: :bigwave:

DHR = Device History Record.

I leave the rest up to the medical device experts here at The Cove...;)

Stijloor.
 

bio_subbu

Super Moderator
#3
The intent of the DHR (Device history Record) is to provide evidence that the device lot or batch was manufactured in accordance with the DMR. Though minimum requirements for a DHR are identified in 21 CFR 820.184, it is not uncommon for a DHR to contain or reference the following information (as applicable to the product manufactured).

1. Details of Finished device batch, lot or serial number
2. Materials used and may identifiers (part number, control number)
3. Manufacturing dates
4. Quantity started and completed
5. Quantity released
6. Details of testing and inspection records
7. Primary Labeling
8. Identification of individuals performing the operations
9. Documents utilized
10. References to appropriate nonconforming material reports.

If software is part of the device, the details of the software version, assembling in to the device, results from evaluating the device software, will be included in the DHR and it’s provide a manufacturer with traceability.

Thanks and Regards
S. Subramaniam
 
Q

QA_RA_Lady

#4
I *THINK* we're talking about software AS the device, not just part of the device...

First of all, is this software only, or hardware and software?

Then the rest of the DHR is going to depend on your repository info....
I've done the batch number as the release number down to the build (at a few companies)
I've also worked at companies where they have a ERP that the ISO or executable is checked into and that unique identifier becomes the batch number.... I never really wrapped my head around that methodology.

Usually your materials used would be a list of 3rd party apps (including version) included in your software product, your build system, anything used to write the code

Quantity is usually tied directly to license generation (digital or physical, depending on what you use)

Testing and inspection is your sw v&v and installation v&v records... unless you are mfg hw too -then you need the production info as well

labeling is obviously your GUI, User Manual, Release Notes,etc.

Hope that helps
 
Q

QA_RA_Lady

#5
Oh - and most importantly... a traveler of some sort... what ever is used to document that each unit was build and tested correctly... so with software this would be the lisc generation and cd creation... if no CD (electronic distribution) these should be someone on site doing a check sum or the like verifying that the right thing was built... if hw is also included it's that and that the box, work stations, whatever, was built and tested by mfg....
 
C

Chris Ford

#6
The intent of the DHR (Device history Record) is to provide evidence that the device lot or batch was manufactured in accordance with the DMR. Though minimum requirements for a DHR are identified in 21 CFR 820.184, it is not uncommon for a DHR to contain or reference the following information (as applicable to the product manufactured).

1. Details of Finished device batch, lot or serial number
2. Materials used and may identifiers (part number, control number)
3. Manufacturing dates
4. Quantity started and completed
5. Quantity released
6. Details of testing and inspection records
7. Primary Labeling
8. Identification of individuals performing the operations
9. Documents utilized
10. References to appropriate nonconforming material reports.

If software is part of the device, the details of the software version, assembling in to the device, results from evaluating the device software, will be included in the DHR and it’s provide a manufacturer with traceability.

Thanks and Regards
S. Subramaniam

I believe this is a software device - not necessarily software as part of a device, since this is a software company. These requirements for DHR are still applicable.

For software devices, DHR's usually identify the production part number for the software, list the parts (executables, media, instructions, etc), the procedures for "manufacturing" (how the software is copied and packaged, issue of serial number, etc), QC testing procedures, and final acceptance procedures. Of course... dates and individuals performing all of these activities are recorded in the DHR.

Depending on how your procedures are written, you can construct a DHR to suit your needs. I've seen DHRs as one or two sheet summaries, and I've seen them actually include the procedures used for that batch.

Your DHR could represent a single serial number or a batch of serial numbers, again depending on how you've defined your manufacturing process.

In the end, the intent of the DHR is to record the manufacturing and acceptance activities. It should paint a clear picture of the entire manufacturing process from the issue of components to the final release, and will describe all of the material, equipment and processes used for that batch to assemble, test, and release the product.
 
S

sarkalgud

#8
This is a very interesting discussion.

Is DHR applicable for hosted software (Software as a Service) and Mobile Applications that are downloaded from App Store? Such software is not manufactured and distributed (unlike the software on media/CDs). Hence, I am inclined to think that DHR is not applicable to software that is downloaded on internet (like mobile apps) and software as a service (like websites that can be used to view medical reports which aid in treatment change)

Thanks!
 
Thread starter Similar threads Forum Replies Date
E Procedure ( SOP) for Device Master Record ( DMR ) and for Device History Record (DHR)? 21 CFR Part 820 - US FDA Quality System Regulations (QSR) 1
R Are DMR (device master record) and DHR (device history record) inspected by FDA or audited by an NB ISO 13485:2016 - Medical Device Quality Management Systems 6
A Medical Device Service Records linked to DHR (Design History Record)? 21 CFR Part 820 - US FDA Quality System Regulations (QSR) 2
R Who owns the DHR (Device History Record) for the Medical Device? US Food and Drug Administration (FDA) 4
E Traceability Requirements for Medical Device History Records (DHR's) 21 CFR Part 820 - US FDA Quality System Regulations (QSR) 5
B DHR's (Device History Record) for Class 1 and 2 Medical Devices Not Required? 21 CFR Part 820 - US FDA Quality System Regulations (QSR) 4
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
Q How much detail in DHR (Device History Record) is too much? US Food and Drug Administration (FDA) 3
S Device History Records (DHR) Component Traceability / Serial Number Requirements ISO 13485:2016 - Medical Device Quality Management Systems 16
S Device History Record (DHR) Templates or Examples Wanted Document Control Systems, Procedures, Forms and Templates 5
E What are appropriate deviations for a LHR/DHR? (Medical Device Company) Manufacturing and Related Processes 3
Q Is a DHR enough to fulfill 13485:2016's Medical Device File requirement? ISO 13485:2016 - Medical Device Quality Management Systems 3
R Sec. 820.120 Device Labeling & DHR - Count and Document All Labels 21 CFR Part 820 - US FDA Quality System Regulations (QSR) 8
R DHR question: Traceability of components ISO 13485:2016 - Medical Device Quality Management Systems 2
P DHF, DMR and DHR in MDR? EU Medical Device Regulations 6
W Is it required to stamp obsolete hard copy DHR's "obsolete"? ISO 13485:2016 - Medical Device Quality Management Systems 6
R In this type of Legal Manufacturer-CMO arrangement, what happens to the DHR? ISO 13485:2016 - Medical Device Quality Management Systems 1
M 13485- DHR requirement for a distributor? ISO 13485:2016 - Medical Device Quality Management Systems 1
L Page Numbering requirement for DHR Report Records and Data - Quality, Legal and Other Evidence 3
V What is required in terms of the DHR, DMR, DHF? Other Medical Device and Orthopedic Related Topics 4
K DHR approval requirements for stand-alone software US Food and Drug Administration (FDA) 4
Q Incomplete Process Sheets Closure - DHR - Doc Control Document Control Systems, Procedures, Forms and Templates 3
Q DMR and DHR - Two requirements, One Document 21 CFR Part 820 - US FDA Quality System Regulations (QSR) 6
C Are DHR and Design Dossier synonymous? US Food and Drug Administration (FDA) 9
W Maintaining Component Traceability in DHR (Design History Record) 21 CFR Part 820 - US FDA Quality System Regulations (QSR) 5
G Could I destroy my DHR hard copy after 2 years after pdf'ing them ? ISO 13485:2016 - Medical Device Quality Management Systems 4
E Better control of DHR (Design History Record) during processing Document Control Systems, Procedures, Forms and Templates 5
M DHR (Design History Record) Requirements - Concessions Quality Manager and Management Related Issues 12
C What is the Minimum Regulatory Requirement for Record Retention of DHR by Suppliers Records and Data - Quality, Legal and Other Evidence 9
P DHR and components under deviation - Medical Devices ISO 13485:2016 - Medical Device Quality Management Systems 4
T DMR/DHF/DHR/Batch Records/Master Batch Records ISO 13485:2016 - Medical Device Quality Management Systems 3
M DMR, DHR and DHF physical form 21 CFR Part 820 - US FDA Quality System Regulations (QSR) 1
S Specific records to be retained for Class II devices per 820.184 DHR ISO 13485:2016 - Medical Device Quality Management Systems 8
shimonv Clinical evaluation report for class I device EU Medical Device Regulations 2
P UDI-PI requirements on reusable surgical device, do we need serialisation? ISO 13485:2016 - Medical Device Quality Management Systems 0
M Medical device certificate in Australia - ARTG certificate Other Medical Device Regulations World-Wide 0
Q Software as a medical device vs software not sold as medical device: local regulations for sale? EU Medical Device Regulations 4
H Medical device Product Registration Registrars and Notified Bodies 2
A Can a power Supply be an accessory to a medical device, if it is an 'off-the-shelf' product. IEC 60601 - Medical Electrical Equipment Safety Standards Series 3
A Medical device labelling Date of manufacture US Food and Drug Administration (FDA) 2
W Non Sterile Medical Device Environmental Tests Other Medical Device Related Standards 4
A Clinical assessment sample size - Medical device Class IIb implantable (93/42 directive) EU Medical Device Regulations 2
K 25-year lifetime of medical device - document storage period EU Medical Device Regulations 1
M Sample record for verification performed by importers before placing a device on the market EU Medical Device Regulations 0
S IVD Device History Record ISO 13485:2016 - Medical Device Quality Management Systems 3
K Relabeling an existing medical device in the field? Other US Medical Device Regulations 6
J Should a Class 1 medical device with an option to measure body weight be considered Class 1m? EU Medical Device Regulations 0
A Reliable sources for following EU medical device regulatory EU Medical Device Regulations 0
T IVDR Medical device software CE Marking (Conformité Européene) / CB Scheme 8
N ISO 13485 7.3.9 Change control in medical device software ISO 13485:2016 - Medical Device Quality Management Systems 6

Similar threads

Top Bottom