• Close menu
  • Home
  • Consulting
    • Technical Documentation
      • Software (IEC 62304, FDA)
      • Risk Management (ISO 14971)
      • Clinical Evaluation
    • Quality Management (QM)
      • QM System (ISO 13485)
      • Mock Audits & Inspections
      • Quality Representative
    • Services
      • Human Factors Engineering
      • Regulatory Affairs
  • E-Learning
    • Training videos
      • Market your medical device
      • Content
      • Premium Version
      • Watch training videos
  • Training Seminars
    • Medical Device Regulation
    • CPMS Seminar
    • Medical Device Software
    • Human Factors Engineering
    • Risk Management Seminar
    • Inhouse Seminars
    • Medical Device Regulatory Affairs
  • Articles
    • Regulatory Affairs
      • Medical Device Regulation
      • IVD Regulation (IVDR)
      • Medical Device Directive
      • Classification
      • CE Marking
      • Conformity Assessment
      • Harmonized Standards
      • MEDDEV 2.7/1
      • FDA
        • Breakthrough Devices
      • And more ...
        • Accessories
        • Essential Requirements
        • EUDAMED
        • MDR Rule 11 (Software)
        • MEDDEV Documents
        • Post-Market Surveillance
        • Notified Bodies
        • Premarket Approval (510k)
        • Technical File versus DHF
        • Unique Device Identification
        • Harmonized Standards
        • GDPR
        • 21 CFR Part 11
        • Design input
        • Declaration of Conformity
        • Systems & Procedure Packs
        • Laboratory Developed Tests
        • Free Sales Certificates
        • Physiological processes
    • QM System & ISO 13485
      • ISO 13485:2016
      • Quality Policy & Objectives
      • Process Validation
      • Audits
      • Unannounced Audit
      • MDSAP
      • CSV
    • Software & IEC 62304
      • Software Lifecycle
        • Agile Software Development
        • Software Requirements
        • Software Architecture
        • Code Reviews
        • Coding Guidelines
        • Software Testing
      • Safety Classes & Level of Concern
      • SOUP and OTS
      • Medical Apps
      • IT-Security
      • Artificial Intelligence
      • And more...
        • Parameterization
    • Artificial Intelligence in Medicine
    • Risk Management & ISO 14971
      • Life Cycle Risk Management
      • Update 14971:2012
      • Harm and Severity
      • Hazard and Hazardous Situation
      • Risk Acceptance
      • Risk Mitigation
      • Risk Analysis
      • Software Specifics
    • Usability & IEC 62366
      • Main Operating Functions
      • ISO 9241
      • User stories
      • Usability Validation
    • Product Development
      • Intended Use Description
      • System Architecture
      • Verification versus Validation
      • Clinical Evaluation
  • Login
  • Logout
  • Contact Us
  • About us
Search
+1 (301) 244-6335

info@johner-institute.com
  • LoginI
  • Contact UsI
  • About us
Search
Logo Johner Institut
  • Display menu
  • Close menu
  • Home
  • Consulting
    Technical Documentation
    • Software (IEC 62304, FDA)
    • Risk Management (ISO 14971)
    • Clinical Evaluation
    Quality Management (QM)
    • QM System (ISO 13485)
    • Mock Audits & Inspections
    • Quality Representative
    Services
    • Human Factors Engineering
    • Regulatory Affairs
  • E-Learning
    Training videos
    • Market your medical device
    • Content
    • Premium Version
    • Watch training videos
  • Training Seminars
    Medical Device Regulation
    CPMS Seminar
    Medical Device Software
    Human Factors Engineering
    Risk Management Seminar
    Inhouse Seminars
    Medical Device Regulatory Affairs
  • Articles
    Regulatory Affairs
    • Medical Device Regulation
    • IVD Regulation (IVDR)
    • Medical Device Directive
    • Classification
    • CE Marking
    • Conformity Assessment
    • Harmonized Standards
    • MEDDEV 2.7/1
    • FDA
    • And more ...
    QM System & ISO 13485
    • ISO 13485:2016
    • Quality Policy & Objectives
    • Process Validation
    • Audits
    • Unannounced Audit
    • MDSAP
    • CSV
    Software & IEC 62304
    • Software Lifecycle
    • Safety Classes & Level of Concern
    • SOUP and OTS
    • Medical Apps
    • IT-Security
    • Artificial Intelligence
    • And more...
    Artificial Intelligence in Medicine
    Risk Management & ISO 14971
    • Life Cycle Risk Management
    • Update 14971:2012
    • Harm and Severity
    • Hazard and Hazardous Situation
    • Risk Acceptance
    • Risk Mitigation
    • Risk Analysis
    • Software Specifics
    Usability & IEC 62366
    • Main Operating Functions
    • ISO 9241
    • User stories
    • Usability Validation
    Product Development
    • Intended Use Description
    • System Architecture
    • Verification versus Validation
    • Clinical Evaluation
  • Regulatory Affairs
    • Medical Device Regulation
    • IVD Regulation (IVDR)
    • Medical Device Directive
    • Classification
    • CE Marking
    • Conformity Assessment
    • Harmonized Standards
    • MEDDEV 2.7/1
    • FDA
    • And more ...
  • QM System & ISO 13485
    • ISO 13485:2016
    • Quality Policy & Objectives
    • Process Validation
    • Audits
    • Unannounced Audit
    • MDSAP
    • CSV
  • Software & IEC 62304
    • Software Lifecycle
    • Safety Classes & Level of Concern
    • SOUP and OTS
    • Medical Apps
    • IT-Security
    • Artificial Intelligence
    • And more...
  • Artificial Intelligence in Medicine
  • Risk Management & ISO 14971
    • Life Cycle Risk Management
    • Update 14971:2012
    • Harm and Severity
    • Hazard and Hazardous Situation
    • Risk Acceptance
    • Risk Mitigation
    • Risk Analysis
    • Software Specifics
  • Usability & IEC 62366
    • Main Operating Functions
    • ISO 9241
    • User stories
    • Usability Validation
  • Product Development
    • Intended Use Description
    • System Architecture
    • Verification versus Validation
    • Clinical Evaluation

System Architecture for Medical Devices

The System Architecture describes how a (medical) product is composed of components and how the components are related to each other via interfaces. In stand-alone software systems architecture and software architecture fall together.

Documentation of the system architecture

The documentation should reveal the individual components and their interaction. We recommend that you use standard notations like UML or SysML and not to work in PowerPoint with undefined notation elements.

In addition to the charts with the different views, the interfaces of the individual components is to be specified. Here you will find instructions on how to fully describe the specific requirements of interoperability.

Regulatory requirements for the system architecture

There are some regulatory requirements for documentation of system architectures. On the one hand calls for the Medical Device Directive MDD that manufacturers have to document design drawings [...] as well as diagrams of components, sub-assemblies and circuits in the product file. Without an explicitly documented system architecture this legal requirement would not be met.

The IEC 60601-1 requires that the medical device manufacturer identifies the programmable electrical subsystems PESS, formulates requirements and verifies their fulfillment. Without a documented system architecture the demand can not be fulfilled.

A documented system architecture is also a necessary condition for a more accurate risk analysis for an FMEA. A suitable system architecture doubles the risk control. In the Audit Guarantor you will find video training on safety-critical system architectures.

Analysis of systems in components

Risk in relation to dismantling systems in layers

In the dismantlement of systems into components, some manufacturers tend to dismantle them in different ‘subsections’, for example, in mechanics, electro-mechanics, electronics and software. We would advise against this because on the one hand this layered system architecture (hopefully) does not reflect reality and on the other you can not consistently think in components.

Only a component-based system architecture is a maintainable, testable, reusable architecture.

System Architecture and Software Architecture

In particular, it can and should not be, that software components are modeled on the first level of the system architecture. Whether that's the case for you also depends on what you define as software architecture.

Option 1: A software system is part of a PESS

If you define a software system as the totality of all software that runs in a memory / processor (and thus in a ) PESS, no software should be seen in the system architecture. Unless the system is a stand-alone software. Otherwise, you would only recognise in the system architecture, the components which are a subset of PESS. And in each PESS there is software (ie, a software system), for which there is a software architecture and software requirements so that again and again software components are identified. But the latter is not visible in the system architecture.

Option 2: A software system is the totality of all software

If you, however, understand the totality of all software in the medical device under a software system (I do not recommend this definition), then you would get a "lasagna-subdivision". They would then have no right system architecture, but a software architecture, an electronic architecture and a "mechanical architecture".

The standard gives no specification as to which variant you have to choose.

Assistance in the creation and testing of system architectures

The team of Johner Institute specialises in using, creating and testing system architectures with and for medical device manufacturers and thus:

  • Identify and dominate risks posed by the medical device,
  • Avoid difficulties during the audit and in the approval,
  • Keep system architectures condensed, precise, meaningful and in compliance with standards as well as
  • Find mistakes early and fix them and thus avoiding costly rework and project delays.

Wha not get in touch now with our experts?

Contact us

Next Article: Verification versus validation

Company

  • About us
  • Contact
  • About Prof. Dr. Johner
  • Our customers
  • Imprint
  • Privacy Policy

Links

  • Consulting
  • Login Auditgarant
  • Trainings
  • Articles

Products

  • Auditgarant (E-Learning)
  • CPMS Seminar
  • Usability Seminar

Free offers

  • Starter-Kit
  • Ask an expert
  • SSRS-Checklist
ISO 13485:2016
Logo Johner Institut

This site uses cookies. By using this website, you agree to the use of cookies.

For more information see our Privacy Policy