Valid

YY/T 0664-2008Medical device software - Software life cycle processes (English PDF)

医疗器械软件 软件生存周期过程

Preview PDF

This is a limited preview

Buy now to download the full PDF (41 pages)

Need quotation for your management?

Get a formal quotation for YY/T 0664-2008 in 30 minutes.

Issued by

SFDA

Level / Type

Industry · Recommended

Issue date

April 25, 2008

Implementation date

June 1, 2009

Scope

YY/T 0664-2008 is the English-translated version of 医疗器械软件 软件生存周期过程.

YY/T 0664-2008 is the 2008 edition of the Chinese standard on medical device software life cycle processes, the Chinese adoption of IEC 62304:2006. It is superseded by YY/T 0664-2020, which is also available on this site; this edition remains the reference for software developed and documented under it.

It defines the processes, activities and tasks for developing and maintaining software that is itself a medical device or is embedded in one, scaled to a software safety class (A, B or C) assigned through risk management.

It covers the general requirements - quality management system, risk management to YY/T 0316 and software safety classification - and the software development process from planning, requirements analysis and architectural and detailed design to unit implementation and verification, integration, system testing and release, together with the maintenance, risk management, configuration management and problem resolution processes.

Validation and final release of the medical device itself are outside its scope. Issued by the State Food and Drug Administration on 25 April 2008, it applied from 1 June 2009.

Found what you need?

Document preview — YY/T 0664-2008

National Standard of the People's Republic of China

Issued by: State Food and Drug Administration

Contents

  • Foreword
  • Introduction
  • 1 Scope
  • 2 Normative references
  • 3 Terms and definitions
  • 4 General requirements
  • 4.1 Quality management system
  • 4.2 Risk management
  • 4.3 Software safety classification
  • 5 Software development process
  • 6 Software maintenance process
  • 7 Software risk management process
  • 8 Software configuration management process
  • 9 Software problem resolution process
  • Annex A (informative) Rationale for the requirements of this standard
  • Annex B (informative) Guidance on the provisions of this standard
  • Annex C (informative) Relationship to other standards
  • Annex D (informative) Implementation
  • Bibliography

Foreword

This document was issued on 25 April 2008 by the State Food and Drug Administration, and applied from 1 June 2009.

It has been superseded by YY/T 0664-2020, Medical device software - Software life cycle processes.

It is a YY/T standard: a recommended industry standard of China's pharmaceutical and medical device sector.

1 Scope

1.1 Purpose: this standard defines the life cycle requirements for medical device software. The set of processes, activities and tasks it describes establishes a common framework for medical device software life cycle processes.

1.2 Field of application: this standard applies to the development and maintenance of medical device software, whether the software is itself a medical device or is an embedded or integral part of the final medical device. It does not cover validation and final release of the medical device, even when the medical device consists entirely of software.

1.3 Relationship to other standards: this standard is used together with other appropriate standards when developing a medical device. Annex C shows the relationship between this standard and other relevant standards.

1.4 Compliance: compliance with this standard means implementing all the processes, activities and tasks it identifies in accordance with the software safety class. Compliance is determined by inspection of all documentation required by this standard, including the risk management file, and by assessment of the processes, activities and tasks required for the software safety class (see Annex D).

Note: The assessment may be an internal or external audit. The methods of implementing the processes and performing the activities and tasks are flexible. Where a requirement marked "as appropriate" is not performed, the justification shall be documented.

2 Normative references

The following documents contain provisions which, through reference in this standard, constitute provisions of this standard. For dated references, subsequent amendments (excluding corrigenda) or revisions do not apply; parties to agreements based on this standard are encouraged to investigate whether the most recent editions can be applied. For undated references, the latest edition applies.

YY/T 0316, Medical devices - Application of risk management to medical devices (YY/T 0316-2008, ISO 14971:2007, IDT)

3 Terms and definitions

For the purposes of this document, the following terms and definitions apply.

3.1 activity: set of one or more interrelated or interacting tasks

3.2 anomaly: any condition that deviates from the expected, based on requirements specifications, design documents, standards, or on someone's perceptions or experiences; anomalies may be found during, but are not limited to, the review, test, analysis, compilation or use of software products or applicable documentation [IEEE 1044:1993, definition 3.1]

3.3 architecture: organizational structure of a system or component [IEEE 610.12:1990]

3.4 change request: documented specification of a change to be made to a software product

3.5 configuration item: entity that can be uniquely identified at a given reference point (based on GB/T 8566-2007, definition 3.6)

3.6 deliverable: required result or output, including documentation, of an activity or task

3.7 evaluation: systematic determination of the extent to which an entity meets its specified criteria [GB/T 8566-2007, definition 3.9]

3.8 harm: physical injury, damage, or both, to the health of people, or damage to property or the environment [ISO/IEC Guide 51:1999, definition 3.3]

3.9 hazard: potential source of harm [ISO/IEC Guide 51:1999, definition 3.5]

3.10 manufacturer: natural or legal person with responsibility for designing, manufacturing, packaging or labelling a medical device, assembling a system, or adapting a medical device before it is placed on the market and/or put into service, whether these operations are carried out by that person or by a third party on that person's behalf [YY/T 0316-2008, definition 2.8]

3.12 medical device software: software system that has been developed for the purpose of being incorporated into the medical device being developed, or that is intended for use as a medical device in its own right

3.13 problem report: record of actual or potential behaviour of a software product that a user or other interested person believes to be unsafe, inappropriate for the intended use or contrary to specification

Note: This standard does not require every problem report to result in a change to the software product; a manufacturer can reject a problem report as a misunderstanding, error or insignificant event. For problem reports relating to a released product, extra decision steps are required (see Clause 6) so that regulatory actions are identified and implemented.

......
This preview omits tables, figures, formulas and parts of the technical clauses. The complete document — 41 pages — is available in the English PDF.

Referenced standards

Similar standards

Editions of YY/T 0664

EditionTitleRevisionStatus
YY/T 0664-2020Medical device software - Software life cycle processescurrent editionCurrent
YY/T 0664-2008Medical device software - Software life cycle processesthis editionSuperseded

This page sells the current edition, YY/T 0664-2008. Earlier editions are listed for reference only.

How to Download YY/T 0664-2008

  1. 1

    Add to cart

    Click "Download PDF" on this page and choose "Buy this standard". You can add more standards before checkout.

  2. 2

    Checkout

    Enter your email and billing details. Payment is processed securely by Stripe (cards or bank transfer). Prefer bank details? Request a quotation (min. order $300).

  3. 3

    Fast delivery

    After payment you'll receive an email confirmation. The English PDF is sent to the same address, usually within minutes and at the latest within 1 business day.

  4. 4

    Invoice included

    A tax invoice is attached to the confirmation email. Need a custom invoice? Contact us.

Related Standards

English PDF
41 pages
Fast delivery
Invoice included
View Cart

Secure payment via Stripe

Payments accepted

VisaMastercardAmerican ExpressApple PayGoogle PayStripe

YY/T 0664-2008

$475.00