Loading

Medical Device Testing · Medical

Usability — IEC 62366-1

IEC 62366-1
Medikal Cihaz Testleri laboratory work

What Is Usability — IEC 62366-1?

IEC 62366-1 defines the usability engineering process to be followed for managing risks arising from use error in medical devices. The process begins with defining the use environment and user profile; formative studies are carried out during design and a summative study at the end.

Purpose of Usability — IEC 62366-1

The purpose is to reduce, at the design stage, the harm that could arise from misuse of the device. Use error underlies a significant share of medical device incidents, and this process directly targets it.

Which Products Is Usability — IEC 62366-1 Applied To?

  • Infusion pumps and injectors
  • Medical devices for home use
  • Patient monitors and alarmed devices
  • Diagnostic devices with a user interface
  • Mobile health applications

In Which Sectors Is Usability — IEC 62366-1 Used?

Medical DevicePharmaceuticalsHealthcareBiotechnology

Standards Related to Usability — IEC 62366-1

  • IEC 62366-1usability engineering in medical devices test

Usability — IEC 62366-1 Conditions

Use specification
User profiles, use environment and use scenarios
Critical tasks
Identifying tasks that could cause harm if performed incorrectly
Study type
Formative study during design, summative study at the end
Participants
With participants representing each user group, in an environment reflecting real use conditions

Equipment for Usability — IEC 62366-1

  • Usability observation room and recording system
  • Simulation setups mimicking the use environment
  • Task recording and timing tools
  • Participant interview and questionnaire tools

Sample Requirements for Usability — IEC 62366-1

  • The device must be supplied in its final design form for the summative study.
  • The instructions for use and training materials must be provided in their final form.
  • User profiles and the use environment definition must be shared.
  • The critical task list and its link to the risk analysis must be provided.
  • The interface software version must be recorded.

Duration of Usability — IEC 62366-1

Formative studies are repeated throughout design. The summative study, together with recruiting participants and running sessions, is a process of several weeks.

Usability — IEC 62366-1 Procedure

  1. 1The intended use, user profiles and use environment are defined.
  2. 2Hazards related to the user interface and critical tasks are identified.
  3. 3The usability engineering plan is prepared.
  4. 4Formative studies are carried out during design and the design is updated.
  5. 5The summative study is planned with the final design.
  6. 6Participants perform the critical tasks under real use conditions.
  7. 7Observed use errors and difficulties are analysed and reported.

Usability — IEC 62366-1 Acceptance Criteria

The acceptance criterion is selected from the relevant section of the standard according to the device's contact type (surface, externally communicating, implant), contact duration and intended use. The assessment relies not on a single test result but on the biological evaluation plan carried out under ISO 10993-1; this page therefore gives no fixed limit.

Evaluation of Results

The assessment relies on whether observed use errors lead to unacceptable risk. Not every error is a non-conformity; its root cause is analysed and whether it can be addressed through design, instructions or training is decided within the risk management process.

Usability — IEC 62366-1 Report

  • Device identification, model and lot number, if any
  • Device contact type, duration and intended use
  • Standard and section applied
  • Extraction or sample preparation conditions
  • Cell line, test system or test rig used
  • Controls and their results
  • Observations, measurement results and assessment
  • A statement that the result applies only to the specimen submitted for testing

Accreditation

EUROLAB holds internationally recognised accreditation obtained from accreditation bodies party to the IAF and ILAC multilateral recognition arrangements, under ISO/IEC 17025 for laboratory testing, ISO/IEC 17020 for inspection and surveillance, and ISO/IEC 17021-1 and ISO/IEC 17065 for system and product certification. This chain ensures the reports and certificates issued are accepted worldwide.

Whether this test can be offered within accredited scope depends on your product and the standard applied; since accreditation is method-based, the scope is confirmed in writing at the quotation stage.

Scope and authorisations

Related Regulations

  • EU 2017/745 Medical Device Regulation (MDR)
  • Medical Device Regulation (Türkiye)
  • ISO 14971 (risk management for medical devices)
  • ISO 13485 (medical devices — quality management system)

Medikal Cihaz Testleri — What Does This Testing Field Cover?

The section below describes the field that the Usability test belongs to; the conditions and acceptance criteria of this particular test are given in the sections above. The scope specific to your product is confirmed in writing at the quotation stage.

Medical device testing shows that a device is safe for the patient and the user and maintains its intended performance. In this family safety is not only about avoiding harm; a device failing to perform its expected function is also treated as a risk. A monitor missing an alarm or a pump delivering the wrong dose is directly a patient safety event.

At the centre of the field is RISK MANAGEMENT, and this is what sets medical apart from other sectors. The risk management process run under ISO 14971 also determines which tests are required. The test list is not copied from a table of standards; it is derived and justified from the device's intended use, the nature and duration of patient contact, the use environment and foreseeable misuse.

Assessment consists of several separate bodies of work, each with its own set of standards. Biocompatibility runs through the ISO 10993 series, electrical device safety through the IEC 60601 series, sterilisation through ISO 11135/11137/17665, packaging through ISO 11607, software through IEC 62304 and usability through IEC 62366. The quality system (ISO 13485) is the framework that binds these together.

Which tests are required is determined by the device's CLASS and its MODE OF CONTACT WITH THE BODY. A product in brief contact with skin and an implant entering the bloodstream do not go through the same test set; the scope is set by a biological evaluation plan prepared under ISO 10993-1. That plan justifies in writing which endpoints are required and why the others are not.

Packaging and sterilisation are taken as seriously as the device itself in this field. For a sterile device the packaging is not a transport container but the barrier that maintains sterility; if the barrier is breached, the device is no longer sterile. Packaging processes are therefore validated and shelf life is supported by real-time ageing data.

For devices containing software, assessment shifts from testing towards PROCESS assurance. IEC 62304 defines which development and verification steps must be followed according to the safety class of the software; the evidence is the traceability of the development process. Testing software does not make it safe — the process record does.

The clinical side is a separate column of the technical file. Test reports show that the device is technically safe; clinical evaluation establishes that the device delivers the intended clinical benefit and that the benefit-risk balance is acceptable. Neither replaces the other.

Method groups in this field

  • Biocompatibility

    Cytotoxicity, irritation, skin sensitisation, systemic toxicity, haemocompatibility, genotoxicity and local effects after implantation. The required endpoints are set by the ISO 10993-1 plan.

  • Electrical device safety

    IEC 60601-1 basic safety and essential performance; EMC, alarm, usability and environmental requirements through the collateral standards.

  • Sterilisation validation

    Validation of sterilisation processes by ethylene oxide, radiation or moist heat; bioburden and sterility assurance level studies.

  • Packaging

    Integrity of the sterile barrier system, seal strength, distribution simulation and shelf-life studies.

  • Microbiological tests

    Bioburden determination, sterility testing, bacterial endotoxin and, where required, carrier validation studies.

  • Software and usability

    IEC 62304 life cycle evidence and use-error focused evaluation under IEC 62366.

Commonly confused in this field

  • Cytotoxicity alone is not evidence of biocompatibility; the required set of endpoints is determined and justified according to ISO 10993-1.
  • An ISO 13485 certificate does not confer CE marking; classification under the MDR, the technical file and the notified body process run separately.
  • Accelerated ageing does not replace real-time ageing; a shelf life claim is supported by real-time data.
  • A change of material (supplier, pigment, sterilisation method) may require the biological evaluation to be repeated; it is not a silent change.
  • An assessment made without the collateral and particular standards for IEC 60601-1 is incomplete; which -1-x and -2-x standards were applied must appear in the report.
  • In vitro diagnostic devices fall under the IVDR rather than the MDR, and laboratory equipment is often on the IEC 61010-1 side.

Which decisions these results support

  • MDR/IVDR technical file and notified body assessment
  • Completing the biological evaluation plan
  • Sterilisation and packaging validation
  • Determining shelf life and storage conditions
  • Determining the scope of reassessment after a design change

Related Tests

Frequently Asked Questions About Usability — IEC 62366-1

How many participants are needed?

IEC 62366-1 gives no fixed number; it requires a justified number of participants. In practice a separate set of participants is planned for each distinct user group, with the justification stated in the report.

Is a formative study mandatory?

The standard does not directly mandate it, but the process calls for it: testing the design only at the end means it is too late to fix problems found.

We use cookies required for the site to work. With your permission we also add an analytics cookie to understand how pages are used. Cookie Policy