SBS - The best value in QMS software

IEC 62304 & FDA: Software Development Methodologies for Class II- DICOM device

T

Taimoore

#1
:DHello Everyone,

we are trying to decide which Software Development Methology/ies or a mix of them would be most suitable for a CLASS-II Software medical device (Moderate Level of Concern) such as DICOM and PACS.

I know there are many methodologies available i.e. Agile, SCRUM, V, Waterfall etc but which one or mixture would be most suitable for our product development?

Anyone from the Class-II (moderate level of concern) want to emphasize? Bare in mind that we will be applying for FDA-510(k) and IEC 62304 certification for our DICOM/PACS medical software product.

Please provide your input and suggestions....

Thank you

best regards
Tim
 
Elsmar Forum Sponsor

Marc

Hunkered Down for the Duration with a Mask on...
Staff member
Admin
#3
'Bump". If anyone can help with this, I apreciate it! My Thanks in advance!
 

sagai

Quite Involved in Discussions
#4
When you submit traditional 510k, you only shall comply with 21CFR820 (and some more CFRs you will be notified at the last 2 paragraph of you clearance letter from FDA).
In case you submit abbreviated, you shall comply with 62304 (you shall declare).
62304 does NOT set your development methodology, regardless it describes the implementation 62304 into waterfall, your method "only" shall comply with the processes/activities/tasks declared in 62304.
Be aware, in case you declare conformance with 62304, only fully conformance acceptable as it is clearly defined in the standard inself.
br
Sz.
 

yodon

Staff member
Super Moderator
#6
Agile and SCRUM are methods that are intended to solicit frequent feedback during development. They require developers and team leads that understand the methods and a management team that understands what they're getting. If your development team is not well versed in the methodology, I don't think it would be wise to try it out on a medical device.

If your development team is experienced in waterfall but you need to increase in-process visibility, you can take an iterative (or spiral) approach.

So I'd say it depends as much on your existing developmetn team as it does your product. As Sagai pointed out, in the end, you have a product that is required to be compliant with FDA regs.
 
E

ErikaP - 2010

#7
We are a small software company developing a Class IIa (CE) MD.

As already mentioned in a previous post IEC 62304 suggests the waterfall modell as the best way to implement medical device software. This modell is also strongly recommended by our notified body.

However, our programmers is not found of the waterfall modell as a programming method as such. What we have done is to implement a waterfallish process with several phases: "Prototype" - "Requirement" - "Design" - "Implementation" - "Validation/Verification" - "Production" - "Maintenance". Throughout development we freely iterate between the first 5 phases. When coming closer to a product release we practice the waterfall modell by having specified toll gates for each phase in our process. These tollgates are verified before we moving on to the next phase.

Note: We have no FDA-appoval so I have no knowledge about the requirements of FDA.

Good Luck!
 
J

Jerome

#8
We've experimented with some models such as waterfall, V-model, also more iterative ones (re-occurring V) but found all a bit rigid.
Via the ISPE(.org) I found that the medical and pharma industry is moving towards more dynamic models based on ASTM E2500-7.
(have a peek at: http://www.qbd-dtc.com/wp-content/uploads/continuous%20verification.jpg (found via google))
This kind of model is more appealing to me as it integrates more easely with my standard QMS and gives more freedom to theengineer in the design stage.
For a full version of this guide go and get it at ASTM for less then $40,- (I'm not affiliated to ASTM in any way).
Hope it helps
 

sagai

Quite Involved in Discussions
#9
Anybody can use any development model.
But the implemented model shall maintain integrity with the process/activity/task defined in 62304 according to the MD classification.
br
Sz.
 
Thread starter Similar threads Forum Replies Date
F FDA PMK 510(k) - IEC 62304 Software Components Segregation Other US Medical Device Regulations 3
M IEC 62304, ISO 14971 and FDA Medical Device SW Guidance 21 CFR Part 820 - US FDA Quality System Regulations (QSR) 5
R IEC 62304 was brought up during an FDA Inspection/Audit IEC 62304 - Medical Device Software Life Cycle Processes 6
L IEC 62304 and FDA Level of Concern IEC 62304 - Medical Device Software Life Cycle Processes 8
T IEC 62304:2006: Medical device software SDLC- CE Vs. Fda 510(k) submission IEC 62304 - Medical Device Software Life Cycle Processes 16
J Use of FDA recognized standards: IEC 62304 IEC 62304 - Medical Device Software Life Cycle Processes 3
E Any sample of a full software life cycle IEC 62304 report ( any class )? IEC 62304 - Medical Device Software Life Cycle Processes 1
G Adopting old product - compliance with IEC 62304 IEC 62304 - Medical Device Software Life Cycle Processes 9
A IEC 62304 safety classification, External Controls and off-label use related risks IEC 62304 - Medical Device Software Life Cycle Processes 5
S IEC 62304 software costs and time Medical Device and FDA Regulations and Standards News 3
S IEC 62304 - Software verification cost IEC 62304 - Medical Device Software Life Cycle Processes 3
Sravan Manchikanti Software Risk Management & probability of occurrence as per IEC 62304 IEC 62304 - Medical Device Software Life Cycle Processes 8
M IEC 62304 Software changes - Minor labeling changes on the GUI IEC 62304 - Medical Device Software Life Cycle Processes 3
K IEC 62304 - Testing Independance IEC 62304 - Medical Device Software Life Cycle Processes 5
K IEC 62304 - Functional and performance requirements for SOUP items IEC 62304 - Medical Device Software Life Cycle Processes 2
K IEC 62304 compliance - Code reviews as part of verification strategy IEC 62304 - Medical Device Software Life Cycle Processes 5
M Risk Analysis Flow - Confusion between ISO 14971 and IEC 62304 IEC 62304 - Medical Device Software Life Cycle Processes 8
D IEC 62304 Risk Classification - With and without hardware control IEC 62304 - Medical Device Software Life Cycle Processes 2
M IEC 62304 Class A Project IEC 62304 - Medical Device Software Life Cycle Processes 15
B Clause 5.1.12 of Technical Standard IEC 62304/A1 IEC 62304 - Medical Device Software Life Cycle Processes 5
P SOUP anomaly evaluation for MMA (Mobile Medical Application) IEC 62304 clause 7.1.3 IEC 62304 - Medical Device Software Life Cycle Processes 6
P IEC 62304 - evaluation of integration and system testing IEC 62304 - Medical Device Software Life Cycle Processes 4
P Risk acceptability alignment between ISO 14971 and IEC 62304 IEC 62304 - Medical Device Software Life Cycle Processes 6
D Required Checklist Showing Compliance to IEC 62304 IEC 62304 - Medical Device Software Life Cycle Processes 11
P Proposed revision of IEC 62304 - 2019 IEC 62304 - Medical Device Software Life Cycle Processes 6
S Relationship between IEC 62304 problem resolution and ISO 13485 IEC 62304 - Medical Device Software Life Cycle Processes 8
P IEC 62304:2006 A1:2015 - Software from the early 1990s IEC 62304 - Medical Device Software Life Cycle Processes 4
B IEC 62304:2015 vs IEC 62304:2006 + AMD1 IEC 62304 - Medical Device Software Life Cycle Processes 4
F IEC 62304 - Segregation and communication between software items IEC 62304 - Medical Device Software Life Cycle Processes 1
B Class IIB Device - IEC 62304 Software Classification IEC 62304 - Medical Device Software Life Cycle Processes 13
B IEC 62304 - Update Checklist IEC 62304 - Medical Device Software Life Cycle Processes 2
L Connection between IEC 62304 and Chapter 14 of IEC 60601-1 IEC 60601 - Medical Electrical Equipment Safety Standards Series 2
M IEC 62304 - Develop an Architecture for the Interfaces of Software Items IEC 62304 - Medical Device Software Life Cycle Processes 8
S Does IEC 62304 require documenting unresolved anomalies for all safety classes? IEC 62304 - Medical Device Software Life Cycle Processes 4
A SOP for software validation of software in medical device IEC 62304 IEC 62304 - Medical Device Software Life Cycle Processes 5
T I need to make test reports according IEC 62304 & IEC 62366 IEC 62366 - Medical Device Usability Engineering 2
D Changing software classification via software - IEC 62304 IEC 62304 - Medical Device Software Life Cycle Processes 3
D Software as risk control - Confused on one aspect of IEC 62304 IEC 62304 - Medical Device Software Life Cycle Processes 20
K Trying to figure out what satisfies a few aspects of IEC 62304 IEC 62304 - Medical Device Software Life Cycle Processes 2
Y IEC 62304 Section 4.3(a) - 100% probability of failure IEC 62304 - Medical Device Software Life Cycle Processes 3
Y Application of IEC/EN 62304 at an advanced stage of software development IEC 62304 - Medical Device Software Life Cycle Processes 4
T Is there any requirement to be compliant with IEC 62304 while implementing ISO 13485 ISO 13485:2016 - Medical Device Quality Management Systems 5
L Documentation Planning - IEC 62304 Clause 5.1.8 IEC 62304 - Medical Device Software Life Cycle Processes 2
C Software for Medical Devices - Requirements Content for compliance with IEC 62304 IEC 62304 - Medical Device Software Life Cycle Processes 1
W CPU BIST IEC 62304 - Embedded code has CPU instruction tests IEC 62304 - Medical Device Software Life Cycle Processes 2
K IEC 62304 Amd 1 2015 - Figure 3 – Assigning Software Safety Classification IEC 62304 - Medical Device Software Life Cycle Processes 11
K Risk Reduction by Risk Control: IEC:62304-Class C ISO 14971 - Medical Device Risk Management 15
C Per IEC 62304, are DHF documents Configuration Items? IEC 62304 - Medical Device Software Life Cycle Processes 8
P IEC 62304 AMD1:2015: What's new vs.the 2006 Edition? IEC 62304 - Medical Device Software Life Cycle Processes 4
M IEC 62304 Applicability - GUI Control Software IEC 62304 - Medical Device Software Life Cycle Processes 3

Similar threads

Top Bottom