AAMI TIR45-2012 (2018) PDF

Full title and description

St AAMI TIR45-2012 (2018) — AAMI TIR45:2012/(R)2018, "Guidance on the use of AGILE practices in the development of medical device software." The Technical Information Report explains how Agile methods can be applied within regulated medical device software development while meeting applicable design control, risk management and software lifecycle requirements.

Abstract

AAMI TIR45:2012/(R)2018 provides practical guidance and examples for mapping Agile practices to medical device regulatory and standards requirements (for example IEC 62304, ISO 13485, ISO 14971 and 21 CFR Part 820). It describes how to plan and implement iterative/incremental development while preserving traceability, verification & validation, change control, and risk management so that Agile teams can demonstrate compliance in audits and submissions.

General information

• Status: Superseded (replaced by AAMI TIR45:2023).
• Publication date: Original: 2012 (AAMI TIR45:2012); reaffirmation/republished entry shown 2018 (listed as TIR45:2012/(R)2018).
• Publisher: Association for the Advancement of Medical Instrumentation (AAMI).
• ICS / categories: Software / Informatics; Medical device software lifecycle and quality systems; Design control.
• Edition / version: TIR45:2012 (reaffirmed/recorded 2018) — commonly referenced as "TIR45:2012/(R)2018".
• Number of pages: 74 pages (typical published PDF/hardcopy length).

Scope

This Technical Information Report provides perspectives and practical examples for applying Agile and iterative development methods to medical device software projects. It focuses on how Agile practices can be aligned with applicable regulatory expectations and software lifecycle standards (for example how to demonstrate design control, traceability, verification/validation, and risk management within iterative development). The TIR is intended as guidance — not a prescriptive normative standard — to help organizations document and justify the use of Agile when developing regulated software.

Key topics and requirements

• Mapping Agile lifecycle models to IEC 62304 software lifecycle requirements and showing compliance with design control (21 CFR 820).
• Establishing documentation and traceability strategies that support iterative development (backlog, sprint artifacts, test records, and trace matrices).
• Integrating risk management (ISO 14971) with incremental design and change control processes.
• Verification and validation approaches suitable for incremental releases, configuration and release control, and regression testing.
• Roles, governance and audit-readiness: how QA/regulatory functions participate in Agile teams and review cadence to satisfy regulators.

Typical use and users

Used by medical device software development teams, product managers, quality and regulatory affairs professionals, auditors, and consultants who need to adopt or evaluate Agile methods for regulated software (including Software as a Medical Device — SaMD). The guidance helps teams demonstrate to auditors and regulators how Agile practices meet established quality and safety requirements.

Related standards

Commonly referenced with IEC 62304 (medical device software lifecycle), ISO 13485 (quality management), ISO 14971 (risk management), FDA design control requirements (21 CFR Part 820), IEC 62366 (usability), and other AAMI and ISO TIRs and guidance documents. TIR45 was written to be applied in the context of these normative standards.

Keywords

AAMI TIR45, Agile, medical device software, SaMD, design control, IEC 62304, ISO 14971, verification and validation, traceability, regulatory compliance, iterative development.

FAQ

Q: What is this standard?

A: AAMI TIR45:2012/(R)2018 is a Technical Information Report offering guidance on using Agile practices in the development of medical device software — showing how to meet regulatory and standards expectations while working iteratively.

Q: What does it cover?

A: It covers practical approaches for mapping Agile activities to design control, risk management, verification/validation, configuration management and documentation so teams can remain audit-ready and compliant when using iterative development.

Q: Who typically uses it?

A: Software development teams in medical device companies, quality and regulatory staff, technical leads, and consultants who need to adopt Agile while satisfying medical device regulatory requirements.

Q: Is it current or superseded?

A: The 2012 report (listed with a 2018 reaffirmation entry) has been superseded by a newer edition, AAMI TIR45:2023. Organizations should reference the 2023 edition for the most up-to-date guidance; the original TIR45:2012 remains part of the historical record and was recognized by FDA as a consensus guidance document.

Q: Is it part of a series?

A: TIR45 is a Technical Information Report (TIR) published by AAMI and forms part of AAMI's body of TIRs and guidance documents addressing medical device standards, software and quality topics. It is complementary to other normative standards (IEC 62304, ISO 13485, ISO 14971) rather than a replacement for them.

Q: What are the key keywords?

A: Agile, medical device software, SaMD, design control, traceability, verification and validation, risk management, IEC 62304, TIR45.