Software in Medical Devices, by MD101 Consulting

To content | To menu | To search

Friday, 20 March 2015

When the FDA releases guidances in burst mode

If you watch from time to time the new guidances released by the FDA, you probably noticed that two guidances about software were released in january and february 2015.

Continue reading...

Friday, 21 November 2014

Analysis of the FDA Cybersecurity Guidance

At last! The FDA has published last October a guidance about cybersecurity that matters!
Not that the guidance previously published about Off-the-shelf software cybersecurity wasn’t worth reading it (Guidance to Industry: Cybersecurity for Networked Medical Devices Containing Off-the-Shelf Software), but its scope was more than reduced.

Continue reading...

Friday, 31 October 2014

Content of DHF, DMR and DHR for medical device software - Part 3 DHR

We continue this series about DHF, DMR and DHR, with the Device History Record.

Continue reading...

Friday, 17 October 2014

Content of DHF, DMR and DHR for medical device software - Part 2 DMR

We continue this series about DHF, DMR and DHR, with the Device Master Record.

Continue reading...

Friday, 3 October 2014

Content of DHF, DMR and DHR for medical device software - Part 1 DHF

After a temporary absence, I'm back on the waves with a new series of articles to talk about the files required by the 21 CFR 820 regulations:

  • DHF: Design History File,
  • DMR: Device Master Record,
  • DHR: Device History Record.

Let's begin with the DHF.

Continue reading...

Friday, 27 June 2014

ISO/DIS 13485:2014 strengthens requirements about software - Part 2

Continuing with ISO/DIS 13485:2014, after having made an overview of software-related changes in the last article, let's focus on the new clause #4.1.6.

Continue reading...

Monday, 26 May 2014

IMDRF consultation: Software as a Medical Device

After MHRA's guidance on standalone software, we continue with another official document published by the International Medical Device Regulators Forum (IMDRF): the consultation on software as a medical device: Possible Framework for Risk Categorization and Corresponding Controls.

Continue reading...

Friday, 11 April 2014

Validation of compiler and IDE - Why, when and how to? - Part 3

Coming back to the discussion about validating compilers and IDE, here are a few more comments I have on this topic.

Continue reading...

Friday, 14 March 2014

Validation of compiler and IDE - Why, when and how to? - Part 1

Validating the compiler used in software development is a recurring issue. To what extent a compiler should be validated, when, how and why?
In the same vein, we can extend the question of validation to all tools used in the software development environment: integrated development environment, configuration management tools, compiler (and linker), automated test tools.

Continue reading...

Friday, 14 February 2014

How to develop a smartphone App to be FDA-cleared or CE Marked? - part 6 Conclusion

To conclude this series about clearance of mobile medical apps, here are a few tips to newcomers in the world in medical devices.

Continue reading...

Friday, 31 January 2014

How to develop a smartphone App to be FDA-cleared or CE Marked? - part 5 Deployment

Back to my blog after a while (you missed me :-)). After the previous article about usability, we're going to see the deployment of mobile medical apps. This article is the last of this series on clearance of mobile medical applications, before conclusion.

Continue reading...

Friday, 17 January 2014

How to develop a smartphone App to be FDA-cleared or CE Marked? - part 4 Usability

In the last article, we saw the concerns about the reliability of wireless connections and how to handle them.
Today, we are going to have a look at something quite important for mobile platforms: usability and humans factors engineering (HFE).

Continue reading...

Friday, 3 January 2014

How to develop a smartphone App to be FDA-cleared or CE Marked? - part 3 Wireless

In the last article, we explained why agile methods are so popular for mobile app software development. Today, we are going to review a major characteristic of mobile platforms: wireless connection.

Continue reading...

Friday, 15 November 2013

How to develop a smartphone App to be FDA-cleared or CE Marked? - part 1 regulations

Today I begin a new series of articles about developing (or more broadly designing) a smartphone App that is a medical device.

The very first question is:

Is your App a medical device and does it need to be CE Marked or FDA cleared ?

Continue reading...

Wednesday, 25 September 2013

FDA issues final Mobile Medical Apps Guidance

After two years of gestation, FDA issues final Guidance on Mobile Medical Apps!

Continue reading...

Friday, 2 August 2013

FDA Mobile Medical App Guidances should be released by the end of the year

To continue the topic about FDA draft guidances related to software and information systems, the FDA put in its top list the release of the Guidance of Mobile Medical Apps.

Guidance of Mobile Medical Apps is in the "A-list" of FDA and should be released by the end of 2013.

In hot topics, we have also a warning letter sent by the FDA to Biosense Technologies. The mobile App named uChek Urine Analyzer and developed by Biosense Technologies, falls into the category of medical devices, says FDA. Biosense claims on its website that the App turns the smartphone into a medical lab.

With such claim, it's not surprising that the FDA wants Biosense to submit a 510k!

Friday, 12 July 2013

Unique Device Identification for software medical device - part 1

Unique Device Identification (UDI) had been in the pipes of regulators for a few years, beginning with the US in 2007, and following (as usual) by the European Union a few years later in 2012.
In parallel, the International Medical Device Regulators Forum (IMDRF) issued in 2011 a guidance on UDI, with the honorable objective of harmonizing UDI's all over the world.
What is the impact of these regulations and guidances on medical device software?

Continue reading...

Friday, 8 March 2013

How to bring legacy software into line with IEC 62304? - part 3

We've seen in the two previous posts several solutions on how to treat legacy software according to IEC 62304.
But there is nothing equivalent to this discussion in IEC 62304. The standard is silent about these situations.

Continue reading...

Friday, 8 February 2013

AAMI TIR45 on the use of agile methods becomes new FDA recognized standard

The AAMI TIR45:2012, Guidance on the use of AGILE practices in the development of medical device software enters in the list of recognized standards by the FDA. See here on Federal Register website.

Continue reading...

Monday, 21 January 2013

Class A, B and C. Is it possible to reduce the documentation of detailed design of software medical devices?

In the last two posts, we've seen what a software unit is, and when to do software detailed design, according to IEC 62304 and FDA Guidances.

Continue reading...

- page 2 of 3 -