Find the standard you are looking for at Engineering360. Documents are available for purchase from the IHS Standards Store.

1 - 18 of 18 results

AAMI TIR32 - MEDICAL DEVICE SOFTWARE RISK MANAGEMENT Organization: AAMI
Date: 2004-01-01
Description: The report provides guidance for those new to the concepts of software system safety in the medical device industry and as an aide-memoire for medical device and software designers more familiar with the topic.
SAE JA1003 - SOFTWARE RELIABILITY PROGRAM IMPLEMENTATION GUIDE Organization: SAE
Date: 2004-01-01
Description: However, having a "number", even with the appropriate accompanying evidence, is not generally sufficient to convince customers, regulatory authorities, or even the system/software suppliers that the software satisfies its requirements. Thus, software reliability is also (qualitatively) defined as a set of attributes that bear on the capability of software to maintain its level of performance under stated conditions for a stated period of time.
AAMI TIR36 - VALIDATION OF SOFTWARE FOR REGULATED PROCESSES Organization: AAMI
Date: 2007-01-01
Description: It does not apply to • software used as a component, part, or accessory of a medical device, or • software that is itself a medical device. This TIR may provide useful information and recommendations to • people responsible for determining the appropriate content and size of a validation effort; • people responsible for performing the analyses and evaluations that drive the content or size determination; • people responsible for planning and executing the validation activities; • people responsible for reviewing and approving the adequacy of the validation effort; and • people responsible for auditing, inspecting, and evaluating the validation for compliance to regulation.
DSF/IEC/FDIS 82304-1 - HEALTH SOFTWARE -- PART 1: GENERAL REQUIREMENTS FOR PRODUCT SAFETY Organization: DS
Description: 1.1 Purpose This Part of 82304 applies to the SAFETY and SECURITY of HEALTH SOFTWARE PRODUCTS designed to operate on general computing platforms and intended to be placed on the market without dedicated hardware, and its primary focus is on the requirements for MANUFACTURERS. 1.2 Field of application This document covers the entire lifecycle including design, development, VALIDATION, installation, maintenance, and disposal of HEALTH SOFTWARE PRODUCTS. In each referenced standard, the term “medical device” or “medical device software” is to be substituted by the term “HEALTH SOFTWARE” or “HEALTH SOFTWARE PRODUCT”, as appropriate.
DS/IEC 82304-1 - HEALTH SOFTWARE – PART 1: GENERAL REQUIREMENTS FOR PRODUCT SAFETY Organization: DS
Date: 2016-11-10
Description: 1.1 Purpose This Part of 82304 applies to the SAFETY and SECURITY of HEALTH SOFTWARE PRODUCTS designed to operate on general computing platforms and intended to be placed on the market without dedicated hardware, and its primary focus is on the requirements for MANUFACTURERS. 1.2 Field of application This document covers the entire lifecycle including design, development, VALIDATION, installation, maintenance, and disposal of HEALTH SOFTWARE PRODUCTS. In each referenced standard, the term “medical device” or “medical device software” is to be substituted by the term “HEALTH SOFTWARE” or “HEALTH SOFTWARE PRODUCT”, as appropriate.
ISO/IEC DIS 82304-1 - HEALTH SOFTWARE - PART 1: GENERAL REQUIREMENTS FOR PRODUCT SAFETY Organization: ISO
Date: 2015-07-31
Description: Specifically, IEC 82304-1 does not apply to: a) medical electrical equipment or systems covered by the IEC 60601/IEC 80601 series; b) in vitro diagnostic equipment covered by the IEC 61010 series; c) implantable devices covered by the ISO 14708 series NOTE This standard also applies to HEALTH SOFTWARE PRODUCTS (e.g., medical apps, health apps) intended to be used in combination with mobile computing platforms.
SEPT - UL 1998 CHECKLIST - SOFTWARE ENGINEERING PROCESS TECHNOLOGY-EVIDENCE PRODUCT CHECKLIST FOR ANSI/UL 1998-2004 STANDARD FOR SOFTWARE IN PROGRAMMABLE COMPONENTS - REVISION 1 - REVISION 1 Organization: SEPT
Date: 2012-01-10
Description: A general software configuration of a microprocessor based programmable component typically includes the operating system or executive software, communication software, micro-controller, input/output hardware, and any generic software libraries, database management or user interface software.
CENELEC - EN 61508-3 - FUNCTIONAL SAFETY OF ELECTRICAL/ELECTRONIC/PROGRAMMABLE ELECTRONIC SAFETY-RELATED SYSTEMS - PART 3: SOFTWARE REQUIREMENTS Organization: CENELEC
Date: 2010-05-01
Description: This part of the IEC 61508 series a) is intended to be utilized only after a thorough understanding of IEC 61508-1 and IEC 61508-2; b) applies to any software forming part of a safety-related system or used to develop a safety-related system within the scope of IEC 61508-1 and IEC 61508-2. Such software is termed safety-related software (including operating systems, system software, software in communication networks, human-computer interface functions, and firmware as well as application software); c) provides specific requirements applicable to support tools used to develop and configure a safety-related system within the scope of IEC 61508-1 and IEC 61508-2; d) requires that the software safety functions and software systematic capability are specified; NOTE 1 If this has already been done as part of the specification of the E/E/PE safety-related systems (see 7.2 of IEC 61508-2), then it does not have to be repeated in this part.
IEC 61508-3 - FUNCTIONAL SAFETY OF ELECTRICAL/ELECTRONIC/PROGRAMMABLE ELECTRONIC SAFETY-RELATED SYSTEMS – PART 3: SOFTWARE REQUIREMENTS - EDITION 2.0 Organization: IEC
Date: 2010-04-01
Description: This part of the IEC 61508 series a) is intended to be utilized only after a thorough understanding of IEC 61508-1 and IEC 61508-2; b) applies to any software forming part of a safety-related system or used to develop a safety-related system within the scope of IEC 61508-1 and IEC 61508-2. Such software is termed safety-related software (including operating systems, system software, software in communication networks, human-computer interface functions, and firmware as well as application software); c) provides specific requirements applicable to support tools used to develop and configure a safety-related system within the scope of IEC 61508-1 and IEC 61508-2; d) requires that the software safety functions and software systematic capability are specified; NOTE 1 If this has already been done as part of the specification of the E/E/PE safety-related systems (see 7.2 of IEC 61508-2), then it does not have to be repeated in this part.
SEPT - UL 1998 CHECKLIST* - * IN EDITABLE MICROSOFT WORD - SOFTWARE ENGINEERING PROCESS TECHNOLOGY-EVIDENCE PRODUCT CHECKLIST FOR ANSI/UL 1998-2004 STANDARD FOR SOFTWARE IN PROGRAMMABLE COMPONENTS - REVISION 1 - REVISION 1; INCLUDES ACCESS TO ADDITIONAL CONTENT Organization: SEPT
Date: 2012-01-10
Description: A general software configuration of a microprocessor based programmable component typically includes the operating system or executive software, communication software, micro-controller, input/output hardware, and any generic software libraries, database management or user interface software.
AAMI HE74 - HUMAN FACTORS DESIGN PROCESS FOR MEDICAL DEVICES Organization: AAMI
Date: 2001-01-01
Description: Practice differences occur because of the wide variety and complexity of medical devices, which range from simple syringes to complex imaging systems, and which may be used in hospitals, clinics, or the home by various professionals and laypersons.
DSF/PRCEN ISO/TS 29321 - HEALTH INFORMATICS - APPLICATION OF CLINICAL RISK MANAGEMENT TO THE MANUFACTURE OF HEALTH SOFTWARE (ISO/TS 29321:2008) Organization: DS
Description: It is acknowledged that, on the boundary, there are health software products that are encompassed by medical device regulations in some countries but not in others.
CEI 62-236 - MEDICAL PLANTAR PRESSURE MEASUREMENT DEVICES (PPMDS): MEASURING PERFORMANCE Organization: CEI
Date: 2015-01-01
Description: NOTE 1 The above technical assessment partly takes into account the appropriateness of the acquisition software associated with the PPMD, since the measured quantities shall be read through it (i.e. data from the PPMD shall be obtained only by means of interfaces delivered by the Manufacturer and Operating Systems declared by the Manufacturer). The assessment of the eventual further software applications associated with the PPMD is beyond the scope of this Standard.
ARMY - AR 710-2 - SUPPLY POLICY BELOW THE NATIONAL LEVEL Organization: ARMY
Date: 2008-03-28
Description: Provisions apply to the management of medical materiel and medical repair parts (classes 8 and 9 supplies), except as indicated in AR 40-61.
CRC - ATLAS OF FUNCTIONAL NEURO - ATLAS OF FUNCTIONAL NEUROANATOMY - SECOND EDITION Organization: CRC
Date: 2005-10-31
Description: The CD-ROM accompanying this new edition of the atlas, thanks to another student, employs newer software that allows the creative use of "rollover" labeling, and also adds animation to some of the illustrations (please see the User's Guide).
CTA-CEB18 - RECOMMENDED PRACTICE FOR TRANSMITTER CONTROL AND STATUS INDICATION IN TRANSMITTING PORTABLE ELECTRONIC DEVICES (T-PEDS) - FORMERLY CEA-CEB18 Organization: CTA
Date: 2007-01-01
Description: For instance, it is understood that operation of WiFi may involve different subtypes including 802.11a that operates in the 5.1 – 5.8 GHz band and 802.11b/g that operates in the 2.4 – 2.5 GHz band.
CRC - PALEOIMAGING: FIELD APPLI - PALEOIMAGING: FIELD APPLICATIONS FOR CULTURAL REMAINS AND ARTIFACTS Organization: CRC
Date: 2009-09-21
Description: Although "portable" CT scanners exist, their size and the logistics of terrain often result in limited availability in remote field settings. In addition, the hardware and software of these units place limitations on the type of data obtainable.
CRC - DEVELOPING A POLY-CHRONIC - DEVELOPING A POLY-CHRONIC CARE NETWORK: AN ENGINEERED, COMMUNITY-WIDE APPROACH TO DISEASE MANAGEMENT Organization: CRC
Date: 2012-10-29
Description: But they too struggled. Both their antiquated computer systems and the latest software gave them regular fits. Dr. Goodall chased specialists for opinions, while the specialists chased down results of someone else's last lab orders.

1 - 18 of 18 results