21
TGA—Software inspections and therapeutic goods A systems-engineering approach David Wotton Office of Manufacturing Quality ABEC Conference | 21 August 2014

Presentation: TGA - Software inspections and therapeutic goods

Embed Size (px)

Citation preview

Page 1: Presentation: TGA - Software inspections and therapeutic goods

TGA—Software inspections and therapeutic goodsA systems-engineering approach

David Wotton Office of Manufacturing Quality

ABEC Conference | 21 August 2014

Page 2: Presentation: TGA - Software inspections and therapeutic goods

Today

TGA—Software inspections and therapeutic goods, a systems-engineering approach 2

Regulated by the TGA

Problem reporting

Inspection considerations

Quick recap and Q&A

Page 3: Presentation: TGA - Software inspections and therapeutic goods

Today

TGA—Software inspections and therapeutic goods, a systems-engineering approach 2

Problem reporting

Quick recap and Q&A

Regulated by the TGA

Inspection considerations

Page 4: Presentation: TGA - Software inspections and therapeutic goods

3

Regulated by the TGA

Administered by the TGA

Legislation • Therapeutic Goods Act 1989 • Therapeutic Goods Regulations 1990 • Therapeutic Goods (Medical Devices) Regulations 2002 • Other legislative instruments including excluded and

exempt goods orders

Page 5: Presentation: TGA - Software inspections and therapeutic goods

4

Regulated by the TGA

SW with a therapeutic purpose (diagnosis, monitoring, treatment) • Mobile, server, desktop programs and apps • Embedded software (firmware, EPROM, etc) • Programmable hardware (e.g., FPGAs) • Software that drives or controls other medical devices • etc.

!—Regulation of software and mobile medical ‘apps’, 2013, TGA

Pacemaker firmware

Page 6: Presentation: TGA - Software inspections and therapeutic goods

5

Regulated by the TGA

SW for manufacturing control & monitoring systems, e.g.: • Production, sterilisation, water, and cleaning systems…. • Statistical-process control • Building-management systems • Lab equipment used in manufacturing

—ISO 13485 and the Therapeutic Goods Act 1989

Control system

Page 7: Presentation: TGA - Software inspections and therapeutic goods

6

Regulated by the TGA

Software used for maintaining quality management systems, e.g.: • Enterprise resource planning systems • Documentation management systems • Corrective Action Preventive Action systems • Training • Record-keeping systems

—ISO 13485 and the Therapeutic Goods Act 1989

Record keeping

Page 8: Presentation: TGA - Software inspections and therapeutic goods

7

Regulated by the TGA

Applicable to all • Backup, fail-over, and redundant systems • Infrastructure and security systems (networks, firewalls, etc.) • Software-development toolsets (IDEs, compilers, etc.) • etc.

—ISO 13485 and the Therapeutic Goods Act 1989

Server room

Page 9: Presentation: TGA - Software inspections and therapeutic goods

Today

TGA—Software inspections and therapeutic goods, a systems-engineering approach 8

Problem reporting

Quick recap and Q&A

Regulated by the TGA

Inspection considerations

Page 10: Presentation: TGA - Software inspections and therapeutic goods

9

!

!

Inspection considerations

The TGA looks to see that the manufacturer:• designs for safety and performance • develops for quality, robustness,

resilience, and predictability • monitors, reports, and improves using appropriate, sufficient, robust, and defensible tools, approaches, and methods.

With sufficient breadth and depth of expertise.

Some of the lifecycle steps

Design

Develop

Monitor

Improve

Report

Page 11: Presentation: TGA - Software inspections and therapeutic goods

10

Inspection considerations

Where applicable, the TGA might look for: • Necessary and sufficient technical competence • Understanding of safe system states and constraints • Resilience engineering (robust, resilient designs) • Use of appropriate and sufficient risk management tools • Methodical and systematic design and development

(e.g., design patterns and contracts)

Designs for safety and performance

—ISO/IEC/IEEE 29148; IEC 62304; ISO 14971; IEC/TR 80002-1; and IEC 62366.

Page 12: Presentation: TGA - Software inspections and therapeutic goods

11

Inspection considerations

Where applicable, the TGA might look for: • Lifecycle development of software (i.e., IEC 62304) • Use of good software– and systems-engineering practice • Understanding of benefits and limitations of chosen development tools • Use of appropriate and sufficient risk-management tools • Methodical and systematic design and development

(e.g., design patterns and contracts)

Development for quality, predictability

—ISO 13485; ISO/IEC/IEEE 29148; IEC 62304; ISO 14971; and IEC/TR 80002-1.

Page 13: Presentation: TGA - Software inspections and therapeutic goods

12

Inspection considerations

The TGA might also look for: • Signal monitoring and analysis (ISO 13485, ISO 14971) • Understanding of limitations of monitoring processes

(Shadow faults?) • Adverse-event and fault reporting (transparency) • Trends analysis

Monitoring, reporting, and continual improvement

—ISO 13485; ISO/IEC/IEEE 29148; IEC 62304; ISO 14971; and IEC/TR 80002-1.

Page 14: Presentation: TGA - Software inspections and therapeutic goods

13

Inspection considerations

A systems-engineering approach

The TGA approaches inspections by: • taking a holistic rather than reductionist view • treating safety and performance as a dynamic control problem • identifying system behaviour safety constraints • assessing the sufficiency and adequacy of controls put in

place by manufacturers

Types of safety constraints: • technical, • process (e.g., procedures), • social (people), • environmental, • etc.

SafeMay include specific

performance

requirements

(e.g., timing in a

pacemaker)

Page 15: Presentation: TGA - Software inspections and therapeutic goods

14

Inspection considerations

Review of safety controls

The TGA will look at controls that might affect safety, e.g.: 1. An unsafe control action is provided that creates a hazard 2. A required control action is not provided to avoid a hazard 3. A potentially safe control action is provided too late, too

early, or in the wrong order 4. A continuous safe control action is provided too long or is

stopped too soon 5. A control action required to enforce a safety constraint

(avoid a hazard) is provided but not followed.

Page 16: Presentation: TGA - Software inspections and therapeutic goods

Today

15TGA—Software inspections and therapeutic goods, a systems-engineering approach

Problem reporting

Quick recap and Q&A

Regulated by the TGA

Inspection considerations

Page 17: Presentation: TGA - Software inspections and therapeutic goods

Please report adverse events (incidents)…

16

Large datasets are needed for the identification of shadow faults.

TGA In addition to the direct management of safety issues, the data reported to us helps us to see trends and better understand the causes of adverse events where software is involved.

Your reporting helps us to identify and respond to safety matters.

www.tga.gov.au

Page 18: Presentation: TGA - Software inspections and therapeutic goods

Today

17TGA—Software inspections and therapeutic goods, a systems-engineering approach

Problem reporting

Quick recap and Q&A

Regulated by the TGA

Inspection considerations

Page 19: Presentation: TGA - Software inspections and therapeutic goods

18

Recap

Quick recap and Q&A

The TGA regulates a broad range of software

systems.

Many factors may be reviewed during an

inspection

Please help by reporting adverse events

A holistic systems-engineering approach

is used

Lifecycle, design and development, monitoring,

and reporting are very important elements for

safety

Page 20: Presentation: TGA - Software inspections and therapeutic goods

19

Q&A

Quick recap and Q&A

TGA information services: • Safety alerts • Recall actions • Medicines Safety Update • Medical Devices Safety Update • Consultations • Publications • Schedulingwww.tga.gov.au

Page 21: Presentation: TGA - Software inspections and therapeutic goods