AAMI規格 AAMI 62304, 6th Edition, 2016: Medical device software - Software life cycle processes, 医療機器向けソフトウェア - ソフトウェアライフサイクルプロセス

AAMI規格 62304, 6th Edition, 2016

産業規格・仕様書  >  AAMI  > 




AAMI規格 62304, 6th Edition, 2016

62,920(税込)

数量

書名

AAMI 62304, 6th Edition, 2016: Medical device software - Software life cycle processes
(Includes all amendments and changes through Amendment 1, 2016)
AAMI規格 62304, 6th Edition, 2016: 医療機器向けソフトウェア - ソフトウェアライフサイクルプロセス
発行元 Association for the Advancement of Medical Instrumentation (AAMI)
発行年/月 2016年1月   
装丁 ペーパー
ページ数 82 ページ
発送予定 海外倉庫よりお取り寄せ 1-2週間以内に発送します
※PDF版をご希望のお客様は別途お問合せ下さいませ。
※当ウェブ・ショップに未掲載のAAMI規格につきましては、別途お問合せ下さいませ。
※掲載の規格は、当ウェブ・ショップに掲載時点で確認できた最新版でございます。
最新の発行状況につきましては受注時に改めて確認をさせて頂きますので予めご了承下さい。

 

Description

Purpose
This standard defines the life cycle requirements for MEDICAL DEVICE SOFTWARE. The set of PROCESSES, ACTIVITIES, and TASKS described in this standard establishes a common framework for MEDICAL DEVICE SOFTWARE life cycle PROCESSES.

Field of application
This standard applies to the development and maintenance of MEDICAL DEVICE SOFTWARE when software is itself a MEDICAL DEVICE or when software is an embedded or integral part of the final MEDICAL DEVICE.

NOTE 1 This standard can be used in the development and maintenance of software that is itself a medical device. However, additional development activities are needed at the system level before this type of software can be placed into service. These system activities are not covered by this standard, but can be found in IEC 82304-11 [22].
  - This standard describes PROCESSES that are intended to be applied to software which executes on a processor or which is executed by other software (for example an interpreter) which executes on a processor.
  - This standard applies regardless of the persistent storage device(s) used to store the software (for example: hard disk, optical disk, permanent or flash memory).
  - This standard applies regardless of the method of delivery of the software (for example: transmission by network or email, optical disk, flash memory or EEPROM). The method of software delivery itself is not considered MEDICAL DEVICE SOFTWARE.
  - This standard does not cover validation and final release of the MEDICAL DEVICE, even when the MEDICAL DEVICE consists entirely of software.

NOTE 2 If a medical device incorporates embedded software intended to be executed on a processor, the requirements of this standard apply to the software, including the requirements concerning software of unknown provenance (see 8.1.2).
NOTE 3 Validation and other development activities are needed at the system level before the software and medical device can be placed into service. These system activities are not covered by this standard, but can be found in related product standards (e.g., IEC 60601-1, IEC 82304-1, etc.).