Home > On-Demand Archives > Talks >

How to Win at 62304

Alan Cohen - Watch Now - EOC 2024 - Duration: 38:52

How to Win at 62304
Alan Cohen

IEC 62304 is the worldwide standard for developing medical device software. In this presentation, we'll start with a brief overview of the standard, then we'll look at how we can use it, along with some recent FDA regulation changes, that can substantially reduce development efforts while also increasing device safety.

M↓ MARKDOWN HELP
italicssurround text with
*asterisks*
boldsurround text with
**two asterisks**
hyperlink
[hyperlink](https://example.com)
or just a bare URL
code
surround text with
`backticks`
strikethroughsurround text with
~~two tilde characters~~
quote
prefix with
>

SimonSmith
Score: 0 | 2 months ago | 1 reply

Great talk thanks. I appreciated the high-level intro to 62304, as I have no experience with medical software development. It seems very similar to other regulated industries I am familiar with. Echoing Miro’s comment, D4R sounds like an excellent priority to have in mind, rather than a paperwork activity we do to get the project over the line after the fun bit is done. My first project was with Ada 83… all I remember was it took an age to build (on VAX VMS), but did so many checks at compile time, there were fewer bugs.

Al CohenSpeaker
Score: 0 | 1 month ago | no reply

Thanks for your kind words, and sorry for the delayed response. I never had the pleasure of using Ada, but in general safe languages are a good idea and I think they are underutilized!

CarlLewis
Score: 1 | 2 months ago | 1 reply

Thanks Alan. I thought this was a really good intro to 62304 and I was impressed with what you covered in the time. I found your example of the input screens ("reducing footprint") interesting and thought it was a shame you didn't have time to dig into it a bit further. While the addition of a dose summary screen seems a good risk control measure, there are two aspects of this example that prove challenging in practice if attempting to claim a reduction in safety class:

  • The need to provide segregation between software items to justify the reduction in safety class
  • The reliance on the user to inspect the summary screen, which may necessitate human factors activities to justify any reduction in risk.
    I'm always interested to hear how other engineers handle such cases. Thanks!
Al CohenSpeaker
Score: 1 | 2 months ago | no reply

Hi Carl,
Thanks for your observations, they're quite reasonable. I think I mentioned in the presentation that the things presented are simplified to make a point, there's always lots more bits to consider. In practice, as it sounds like you know, any of these decisions end up requiring a good bit of thought!
On the second point, it's also possible that adding the summary screen could potentially reduce human factors risk.

Miro
Score: 1 | 2 months ago | 1 reply

Thank you, Alan, for a very informative presentation. I particularly like your design for regulatory (D4R) approach, which I would translate as "design for risk". This is a paradigm shift, where risk reduction becomes the top priority, which is not how developers usually think.
Of course, your tip to acquire the standards from Evs.ee is a very nice touch. I checked it out, and it works. They have much more than IEC-62304!

Al CohenSpeaker
Score: 0 | 2 months ago | no reply

Thank you for your kind words, I'm glad it was helpful.
evs.ee is an amazing find. When I first found it, I couldn't believe it was real!

OUR SPONSORS

OUR PARTNERS