Mapping of IEC 62304 artefacts (SRS, SAD, etc) to the 820.30 phases

A

andypatkinson

#1
Hi,

Can anyone provide a mapping of IEC 62304 artefacts (SRS, SAD, etc) to the 820.30 phases: Planning, Design Input, Device Design, Design Output, Verification, Validation, Design Review.

(As a side note, I cannot even find a good definition of what 'Design' means when considering 820.30 Design Controls and medical device software development - any thoughts, interpretations, suggestions?)

I have seen so many contradictory and incorrect answers,
the favourite being:

Planning: SDP
Design Input: System Requirements, Medical Device Risk Assessment, SRS
Device Design: SAD, SDD, Code
Design Output: Release Notes, Binary
Verification: Verification Report

What say you learned folk?

TIA

Andy
 
Elsmar Forum Sponsor

yodon

Staff member
Super Moderator
#2
First off, here are a couple of links that may be helpful:

http://www.fda.gov/MedicalDevices/DeviceRegulationandGuidance/GuidanceDocuments/ucm085281.htm

http://www.fda.gov/MedicalDevices/DeviceRegulationandGuidance/GuidanceDocuments/ucm089543.htm

The last one provides a fairly good mapping.

As far as your list goes, it's not bad. I would move 'code' to a design output (it's implementation of the design). It can go along with the binaries since those are outputs, too. I would add verification protocols and results along with the report.

A lot depends on the classification and the way you guys do business. I personally recommend (when applicable) a design artifact be an Interface Control Document. Other things you may need to consider / do based on class would be unit test documentation (procedures, results), integration test documentation, change records, etc. Procedurally, you may want to have a Configuration Management / Release Management Plan, a Risk Management Plan, and a V&V Plan. If you have risk controls implemented in software, you'll need verification of those (if not included in your verification documentation already). You may want to include review records.

If you have SOUP / COTS in the system, you'll want to do some additional analysis / documentation / testing.

Those jump to mind - may not be complete.
 
A

andypatkinson

#3
Hi Yodon,

Thanks for the reply. A few questions if I may:

1) what specifically is of interest in the linked docs? I had a skim read and couldn't immediately see the correlation?

2) What does the FDA mean when they say 'Design'? It seems to be anything and everything prior to Transfer and therefore Design Outputs are the artefacts transferred into Production which does not include Source Code - it's the binary + release notes + installation / programming instructions.

3) Quote "As far as your list goes, it's not bad. I would move 'code' to a design output (it's implementation of the design)." - and herein lies some of my 'confusion'. If I look at this as a software engineer, I know what design is - it's where I turn 'what' (reqs) into 'how' (designs) and I then implement my design as code (as you suggest). I don't think this use of 'design' is synonymous with the FDA use of the term 'design' - Design Output is what I put into production. Do you agree?

Either I am making heavy weather of this or it's not as clear as hoped it would be.....

Any further help appreciated - anyone else feel free to chime in. Showing how (as software folk) we satisfy 820.30 must be a pretty universal thing (if you're headed into the US market).

TIA

Andy
 

yodon

Staff member
Super Moderator
#4
The first link talks a little about how the FDA views the software life cycle (with a focus on validation). The second talks about the artifacts expected for submission based on the level of concern.

Design is, as you suggest, everything up to production but it certainly includes the software source code since that's what's touched when you have to make changes. That's why validation talks so much about the life cycle and control.

So design outputs are ALL the results of the process of translating the design inputs into the final product. Not just the things that go into production (i.e., binaries).
 

mihzago

Trusted Information Resource
#5
I think you shouldn't be looking at Design Controls described in 820.30 as "phases", but rather as required elements that drive activities and deliverables within your own development process.

Your mapping is mostly correct, but as Yodon mentioned, your "device design" artefacts should be under "Design Outputs". There is no design control called "Device Design"; loosely "design" applies to everything that makes up your product, including the code. I've noticed this concept is confusing to software folks, they think "design" applies to the process of creating the software or the UI; I sometimes for example hear "this is not a design change, we only changed one line of middleware code".
Also, I think that the "Design History File" provides suggestion what is considered "design" - which is everything that happened before you transferred your to production (deployed, for many stand-alone software transfer to production equates to a few mouse clicks).

I created a table with mapping of FDA design control elements, IEC62304, my company's development phases, typical deliverables, and brief description. I try to attach it, but I'm not sure if I have enough privileges to be able to post files. (if not, I'll be happy to share via email)
I hope this is helpful. Feel free to share any feedback; I'm sure what i have is not perfect and needs more work.
 

Attachments

A

andypatkinson

#6
Hi Guys,

Thanks for your feedback.

Yes, for SW folk it's a shift in their thinking - overloaded terms with very different meanings and implications.

I think I am OK with this now.

Thank you for your time and attention.

Regards

Andy
 
Thread starter Similar threads Forum Replies Date
T ISO/IEC 27001 to ISO/IEC 12207 Mapping - Cross Reference Matrix IEC 27001 - Information Security Management Systems (ISMS) 2
R Where does IATF 16949 address Process mapping? IATF 16949 - Automotive Quality Systems Standard 3
K Process Mapping - Inputs/Outputs/Detail Activities/Control points/Measurement? Process Maps, Process Mapping and Turtle Diagrams 4
J Here is my definition of Defect Mapping Quality Tools, Improvement and Analysis 2
Z 21 CFR and Annex 11 mapping document Pharmaceuticals (21 CFR Part 210, 21 CFR Part 211 and related Regulations) 1
qualprod Cycle times, value stream mapping, inventory, average values? Lean in Manufacturing and Service Industries 1
R Process Mapping for a BPMS (Business Process Management System) vs ISO Process Maps, Process Mapping and Turtle Diagrams 1
M PDCA cycle - Process mapping - Environmental ISO 14001 ISO 14001:2015 Specific Discussions 1
R Process Mapping a Civil Infrastructure Construction company Process Maps, Process Mapping and Turtle Diagrams 4
Q Guidance Needed For Mapping Career Path Career and Occupation Discussions 5
L Mapping the loan lending bank process Process Maps, Process Mapping and Turtle Diagrams 7
R PPM, Pictorial Process Mapping, Templates Manufacturing and Related Processes 5
M Value Stream Mapping Calculations Process Maps, Process Mapping and Turtle Diagrams 5
S ISO14001:2015 Factory Process Mapping ISO 14001:2015 Specific Discussions 7
O Process Mapping prior to Validation and Software to use to Map Process Maps, Process Mapping and Turtle Diagrams 12
J Agenda of Value Stream Mapping workshop required Quality Tools, Improvement and Analysis 1
R VSM - Value Stream Mapping (catheter manufacturing unit) Customer Complaints 10
M Mapping Processes to 7.3 Development and Design - AS9100 Process Maps, Process Mapping and Turtle Diagrams 3
C Dose Mapping - How to relate back to Routine Monitoring Position ISO 13485:2016 - Medical Device Quality Management Systems 3
S Value Stream Mapping for a Product Family Lean in Manufacturing and Service Industries 5
A Assessing/Mapping Employee Attitude during Competency Mapping (Assessment) IATF 16949 - Automotive Quality Systems Standard 15
M Value Stream Mapping or Deployment Chart in Services Lean in Manufacturing and Service Industries 6
T ISO 20000 Mapping to ITIL and COBIT IT (Information Technology) Service Management 4
BradM What is the minimum size chamber for mapping? ISO 13485:2016 - Medical Device Quality Management Systems 2
B Macro Process Mapping (pre-GAP analysis) ISO 9000, ISO 9001, and ISO 9004 Quality Management Systems Standards 3
C Value Stream Mapping Template Document Control Systems, Procedures, Forms and Templates 2
I Stability Chamber Temperature Mapping General Measurement Device and Calibration Topics 5
V Any examples of Value Stream Mapping (VSM) for Product Development Processes (PDP) ? Six Sigma 3
C Process Mapping Electronic Document Control Software Recommendations Quality Tools, Improvement and Analysis 5
P Value Stream Mapping - Trying to do Value Stream Mapping of our Products Lean in Manufacturing and Service Industries 3
D Is Process Mapping an ISO 13485 Requirement? Process Maps, Process Mapping and Turtle Diagrams 4
S Value Stream Mapping (VSM) in After Sales Customer Support Service Department Lean in Manufacturing and Service Industries 4
S Business Case for Process Mapping Process Maps, Process Mapping and Turtle Diagrams 4
V Value Stream Mapping - Loan Processing for Vehicle Asset Financing (VAF) Lean in Manufacturing and Service Industries 4
A Information Technology Process Mapping per ISO 13485 - example wanted Process Maps, Process Mapping and Turtle Diagrams 1
F Updating a Quality Manual from ISO 9001 to ISO TS 16949 - Process Mapping IATF 16949 - Automotive Quality Systems Standard 2
L Qualiware Software & Process Mapping Process Maps, Process Mapping and Turtle Diagrams 7
Q Correlation Matrix and Value Stream Mapping? Quality Assurance and Compliance Software Tools and Solutions 1
F How does Process Mapping help to make a process more Transparent to the Customer? Process Maps, Process Mapping and Turtle Diagrams 2
M SIPOC (Suppliers Inputs Process Outputs Customers) Process Mapping Tool example Process Maps, Process Mapping and Turtle Diagrams 11
N Process Mapping a Private Company that deals with Insurance Process Maps, Process Mapping and Turtle Diagrams 8
J Definition Activity vs. Task - Definitions in Process Mapping and Projects Definitions, Acronyms, Abbreviations and Interpretations Listed Alphabetically 9
G Using Visio 2010 as a Mapping Program for Circuit Boards Quality Assurance and Compliance Software Tools and Solutions 3
S Value Add Time Calculation in Value Stream Mapping (VSM) Lean in Manufacturing and Service Industries 8
R Process VSM (Value Stream Mapping) help needed Lean in Manufacturing and Service Industries 5
N Does anyone have any experience or feedback using mind mapping software? Quality Tools, Improvement and Analysis 5
S Mapping CMMI to FDA Requirements IEC 62304 - Medical Device Software Life Cycle Processes 5
H Process Mapping related to EMS for ISO 14001:2004 ISO 14001:2015 Specific Discussions 5
R Value Stream Mapping in Forging and Machining company Quality Tools, Improvement and Analysis 2
L Definition Poka Yoke, Process Mapping, MSA - What are these terms please? Definitions, Acronyms, Abbreviations and Interpretations Listed Alphabetically 3

Similar threads

Top Bottom