Documenting Software Safety Classifications

cwilburn

Starting to get Involved
#1
My company provides software engineering services to medical device manufacturers, and we have documented/tracked software safety classifications of software systems and items in different ways. I was wondering how others do it and what you think is best.

Most of the time, we include the software systems and a break down into software items, each with their classifications, in the software architecture document. But for some clients, we have had a separate form that lists each software system and item with its corresponding classification. We also have a column in our traceability matrix for the software item and its classification.

Where do you document the software safety classifications of your software systems and items?

Thanks!
Cathy
 
Elsmar Forum Sponsor

yodon

Staff member
Super Moderator
#2
I generally prefer to put it in the Software Development Plan since that frames up what has to be done. I don't think there's a specific, "right" answer, though.
 

mihzago

Trusted Information Resource
#3
concur with Yodon.

Software development plan is a good place for the safety classification, which is where I typically put it, but as long as you have the classification somewhere, and it's properly referenced, and included in your Technical File (or DHF), then you should be good.
 

glork98

Involved In Discussions
#5
Would either of you that responded post a scrubbed version of an SDP showing how you do it?
I'll tell you how I do it.

First off, there are reference documents (A) on the product and/or software architecture(s) that allow specific software systems to be identified.

Then there are hazard analyses (B) of the product and software system(s) that provide a basis for the classification(s).

Then in the SDP a section says "Software System X, as defined in document A, is classification Y based on document B per SOP 123."

Then the fun really gets going as the SDP describes how the quality practices for X will be performed for Y per SOP 123. Might be multiple of each X, A, Y, B and 123, to be sure.
 
Thread starter Similar threads Forum Replies Date
L Problems while documenting the SOUPs used for the software we are developing IEC 62304 - Medical Device Software Life Cycle Processes 4
M Customer Format - Documenting Customer Software Requirement Specification and DDD Software Quality Assurance 10
S Documenting Design Verification Test Results (ISO 9001) Design and Development of Products and Processes 1
adir88 Documenting Risk Control Option Analysis ISO 14971 - Medical Device Risk Management 8
M Defining and Documenting Record Retention CE Marking (Conformité Européene) / CB Scheme 5
J Documenting a Calibration Interval Extension Calibration Frequency (Interval) 7
B Documenting hardware on Form 2 of AS9102 AS9100, IAQG, NADCAP and Aerospace related Standards and Requirements 5
bryan willemot Documenting past problem history for fasteners for AS9100 Rev D AS9100, IAQG, NADCAP and Aerospace related Standards and Requirements 2
Q Documenting Customer Complaints (Records) Customer Complaints 6
R Documenting Expiration Date Extension for a specific lot ISO 13485:2016 - Medical Device Quality Management Systems 12
J ISO 13485:2016 Section 6.2 - Documenting the process for establishing competence ISO 13485:2016 - Medical Device Quality Management Systems 6
S Does IEC 62304 require documenting unresolved anomalies for all safety classes? IEC 62304 - Medical Device Software Life Cycle Processes 4
C Documenting Cleaning Production Lines in Medical Device Pkg facility ISO 13485:2016 - Medical Device Quality Management Systems 1
C Documenting Cleaning Production Lines in Medical Device Pkg facility 21 CFR Part 820 - US FDA Quality System Regulations (QSR) 0
C Documenting Cleaning Production Lines in Medical Device Pkg facility 21 CFR Part 820 - US FDA Quality System Regulations (QSR) 1
R Documenting Self-Training and Effectiveness - ISO 13485:2016 Training - Internal, External, Online and Distance Learning 4
B Approaches to Documenting an ISO 22000 FSMA Food Safety - ISO 22000, HACCP (21 CFR 120) 3
G Process for Product Safety - Ideas for Documenting Process for 4.4.1.2 IATF 16949 - Automotive Quality Systems Standard 3
dubrizo Are you documenting Internal Audit findings as NCRs? Internal Auditing 18
M What is the value of documenting in-process rework for easily-detectable issues? Quality Manager and Management Related Issues 4
R What is the typical industry standard for documenting Usability Risk? Human Factors and Ergonomics in Engineering 16
C Importance of Documenting NCP's and CA/PA's ISO 9000, ISO 9001, and ISO 9004 Quality Management Systems Standards 23
D Documenting Meetings through Meeting Minutes or a Form ISO 9000, ISO 9001, and ISO 9004 Quality Management Systems Standards 5
Colin Objectives Form - Format for Documenting Information Security Objectives IEC 27001 - Information Security Management Systems (ISMS) 2
O Documenting Processes requiring Customer Notification Misc. Quality Assurance and Business Systems Related Topics 2
M Documenting Vendor (Supplier) Issues Document Control Systems, Procedures, Forms and Templates 4
V Documenting Exceptions and use of Deviation Request Form APQP and PPAP 2
K AS9100 Clause 7.2.2 - Documenting "Special Requirements" and risks AS9100, IAQG, NADCAP and Aerospace related Standards and Requirements 1
K Competence, Training and Awareness - Documenting Training and Confidentiality Aspects ISO 9000, ISO 9001, and ISO 9004 Quality Management Systems Standards 12
Q Documenting the Review of Adverse Effects from Rework ISO 13485:2016 - Medical Device Quality Management Systems 4
A Formal Way for Documenting Design Input Requirements 21 CFR Part 820 - US FDA Quality System Regulations (QSR) 1
A Documenting 5S Guidelines in the Sales Department (Office 5S) Quality Tools, Improvement and Analysis 4
C Training Planning - Using Summary Sheet for Documenting Training Activities Training - Internal, External, Online and Distance Learning 3
J Requirements for Documenting Lifetime of a Medical Device ISO 13485:2016 - Medical Device Quality Management Systems 5
A Best Practice for Documenting Design Reviews 21 CFR Part 820 - US FDA Quality System Regulations (QSR) 13
F Documenting Historical Preventive Action at a Daycare Preventive Action and Continuous Improvement 20
N Documenting Medical Device Complaints 21 CFR Part 820 - US FDA Quality System Regulations (QSR) 6
R Documenting Quality Inspections - Material Released prior to Lot Acceptance Quality Manager and Management Related Issues 10
V Documenting the Root Causes for Internal Audit Non-Conformance Findings Problem Solving, Root Cause Fault and Failure Analysis 5
V Approach towards defining/documenting Requirements COTS vs. New-Product Software Quality Assurance 1
Crusader New Documenting Methods for Manufacturing Process Audits? Process Audits and Layered Process Audits 9
M Documenting an outsourced process - Distribution company with some manufacturing ISO 9000, ISO 9001, and ISO 9004 Quality Management Systems Standards 2
P Process Map vs. User Guide - Documenting business procedures Process Maps, Process Mapping and Turtle Diagrams 3
T Documenting Effectiveness of Corrective/Preventive Action Nonconformance and Corrective Action 8
D Documenting Machine Shop In-Process Checks Records and Data - Quality, Legal and Other Evidence 9
Crusader Continuous Improvements - How are you documenting them? Preventive Action and Continuous Improvement 66
R Documenting Processes such as Receiving Inspection, and Auditing to Turtle Diagrams Process Maps, Process Mapping and Turtle Diagrams 20
Gert Sorensen Requirement for specified agendas and meeting minutes when documenting projects? Document Control Systems, Procedures, Forms and Templates 2
A Submit a 510(k) to an existing device vs. Just Documenting a Change ISO 13485:2016 - Medical Device Quality Management Systems 2
D Documenting Revision History - Single ?Revision Record? Document Document Control Systems, Procedures, Forms and Templates 4

Similar threads

Top Bottom