Cited by 245Safety Systems Engineering in AutonomyHealthcare RegulationSoftware Engineering Techniques and Practices

The DOI matches its Crossref record.

Standard IEC 62304 - Medical device software - Software lifecycle processes

Jordan, P.·2006·IET Seminar on Software for Medical Devices

Abstract

IEC 62304, if accepted, requires what reputable medical device manufacturers are already doing. The author therefore expect them to welcome it. It would remove the obligation to describe their processes in detail in regulatory submissions to the FDA. With all its limitations, the author commends IEC 62304. There are still medical device manufacturers whose software development processes are quite rudimentary, and this threatens the lives of patients. IEC 62304 will prevent this and provide a more level playing field for all medical device manufacturers. There appears to be no appetite among either medical device manufacturers or regulators for a more extensive standard prescribing methods and techniques. Holding out for more at this stage would ensure that we get nothing. IEC 62304 also takes a big step towards simpler and more uniform expectations on both sides of the Atlantic.

Overview

Integrity signals

Registry

Crossref · 10.1049/ic:20060141

Cites

Statistics

Recomputing p-values needs the paper’s full text.

Verification

Claims the paper makes

This paper’s full text isn’t openly available, so its claims and self-check weren’t run. The registry and citation checks still apply.

Claims other papers make about this one

Each is checked against this paper’s own text: does it say what the citing paper says it does?

  • The FDA has acknowledged that its traditional paradigm for device regulation was not designed for continuously learning AI/ML systems.

    “Indeed, the FDA has acknowledged that its traditional paradigm for device regulation was not designed for continuously learning AI/ML systems [62,63,73].”
  • AIPM software developers are recommended to follow relevant existing international standards for software testing.

    “AIPM software developers are recommended to follow relevant existing international standards with regard to software testing, such as the IEC 62304:2006117, the IEC 82304-1:2016118, IEC 62366-1:201598, ISO 14971:2019119, Food and Drug Administration principles of software validation120, and Food and Drug Administration guidance for off-the-shelf software use in medical devices121.”

Citations

Cites

Still being checked.

Cited by

Sorted by citations

Metadata

Authors
Jordan, P.
Corresponding author
Jordan, P.
Venue
IET Seminar on Software for Medical Devices
Publisher
IEE
Published
2006
Volume
2006
Pages
41-47
OpenAlex
W2037889871
Cited by
244
References
0
Citations by year
2026: 45 · 2025: 21 · 2024: 15 · 2023: 12 · 2022: 17 · 2021: 15 · 2020: 6 · 2019: 5 · 2018: 4 · 2017: 12 · 2016: 14 · 2015: 14 · 2014: 14 · 2013: 13 · 2012: 11
FWCI
8.32
Type
conference paper
Language
en
Open access
closed
Topics
  • Physical Sciences › Engineering › Safety, Risk, Reliability and Quality › Safety Systems Engineering in Autonomy
  • Health Sciences › Medicine › Public Health, Environmental and Occupational Health › Healthcare Regulation
  • Physical Sciences › Computer Science › Information Systems › Software Engineering Techniques and Practices
Keywords
IEC 62304, medical device software, medical device regulation, FDA regulatory submissions, software development process, software safety standards, international regulatory harmonization

About these checks

Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.

Statistics and arithmetic are recomputed, not judged.

Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.

What counts as a claim ›How we measure confidence ›How we check this ›

Are you an author, or do you see a problem with this page? Request a review