Genericized Medical Device Architecture for Development Cycle Reduction

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

The complexity of heterogeneous hardware and software configurations in medical devices prolongs product development cycles, hindering businesses from achieving quick market entry and efficient product design and manufacturing.

Innovation Solution

A genericized medical device architecture that includes a location-independent communications module, diagnostics module, hardware abstraction layer, and modular software design, allowing for parallel development and easy extension of medical devices without requiring new product creation.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If heterogeneous hardware and software configurations are used to meet specific product needs, then product functionality and adaptability are improved, but device complexity and development cycle duration increase

Engineering Contradiction:

Improveproduct functionalityVSAvoidconfiguration complexity

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system is divided into distinct layers: hardware abstraction layer, device independent software layer, and device specific software layer. This segmentation allows each layer to be developed and modified independently, reducing overall system complexity while maintaining adaptability.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

A hardware abstraction layer is introduced as an intermediary between the hardware and software layers. This abstraction layer provides standardized interfaces and handles hardware-specific variations, allowing the upper software layers to remain hardware-independent while supporting diverse configurations.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Adaptability or versatility

If heterogeneous hardware and software configurations are used to meet specific product needs, then product functionality is improved, but product development cycle time increases

Engineering Contradiction:

Improveproduct functionalityVSAvoiddevelopment cycle time

Core Design Contradiction:

Adaptability or versatilityVSLoss of time

Solution Approach 1:

The hardware abstraction layer and device independent software are developed and standardized in advance. This preliminary action creates reusable components that can be applied across multiple products, significantly reducing development time for new devices while maintaining functionality.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The device independent software layer is designed to be universal and hardware-agnostic, capable of supporting multiple different hardware configurations. This universality allows a single software base to serve multiple product variants, reducing development cycle time while maintaining adaptability.

Inventive Principle:

Principle #6Universality (Multi-functionality)

3Adaptability or versatility

If device-specific software architecture is used for each medical device, then product customization is improved, but ease of manufacture and maintenance deteriorate

Engineering Contradiction:

Improveproduct customizationVSAvoidmanufacturing efficiency

Core Design Contradiction:

Adaptability or versatilityVSEase of manufacture

Solution Approach 1:

The software architecture is segmented into standardized core components and customizable device-specific components. This segmentation allows standardized components to be manufactured and deployed efficiently across multiple devices, while device-specific customization is handled through configuration rather than separate development.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

Common functionality across multiple medical devices is merged into a shared device independent software layer. This merging eliminates redundant development and manufacturing efforts while allowing each device to maintain its specific characteristics through the layered architecture.

Inventive Principle:

Principle #5Merging (Combining)

4Adaptability or versatility

If device-specific software architecture is used for each medical device, then product customization is improved, but ease of repair and maintenance deteriorate

Engineering Contradiction:

Improveproduct customizationVSAvoidmaintenance difficulty

Core Design Contradiction:

Adaptability or versatilityVSEase of repair

Solution Approach 1:

The layered architecture segments common functionality into reusable, standardized components that can be independently maintained and updated. This segmentation allows maintenance personnel to work on standardized components without affecting device-specific functionality, improving ease of repair.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The device independent software layer provides universal maintenance and diagnostic capabilities across all devices in the family. This universality simplifies training, troubleshooting, and repair procedures while allowing each device to maintain its specific characteristics.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Data Source

PatentUS9898584B2System and method for providing a common medical device architecture

Publication Date: 2018.02.20 JOHNSON & JOHNSON SURGICAL VISION INC

AI summary

Systems, methods, and computer readable storage medium for providing a genericized medical device architecture common to a plurality of medical devices are disclosed. The architecture may comprise at least one diagnostics module associated with at least one of the plurality of medical devices, wherein the at least one diagnostics module is configured to monitor an operational status of the at least one medical device. At least one hardware abstraction layer may be associated with at least one of the plurality of medical devices, and may be configured to provide abstracted access to hardware of the at least one medical device.