Multi-Layer Software Architecture for Diagnostic Lab Routing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional diagnostic laboratory systems face inefficiencies due to heuristic rule-based routing of sample containers, which leads to traffic jams and require substantial customization for layout changes, making them inflexible and costly.

Innovation Solution

A multi-layer software architecture with individually replaceable modules for routing and transport control, allowing dynamic routing and efficient sample container movement, adaptable to various laboratory configurations without affecting other system tasks.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If heuristic rule-based routing is used to transport sample containers, then the system operation is simple, but the routing efficiency deteriorates causing traffic jams

Engineering Contradiction:
Improvesystem operation simplicityVSAvoidrouting efficiency
Core Design Contradiction:
Ease of operationVSProductivity

Solution Approach 1:

The routing program is divided into multiple software layers (first software layer for high-level routing decisions, second software layer for detailed path planning, third software layer for real-time control) that operate independently and can be updated separately, improving routing efficiency without complicating overall system operation

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system transitions from static heuristic rules to dynamic software layers that can adapt routing decisions in real-time based on current laboratory conditions, hardware configurations, and sample priorities, thereby eliminating traffic jams while maintaining operational simplicity through automated decision-making

Inventive Principle:
Principle #15Dynamics

2Productivity

If custom routing programs are created for each new laboratory layout, then the routing efficiency is optimized for that specific layout, but the development time and cost increase substantially

Engineering Contradiction:
Improverouting optimizationVSAvoiddevelopment time
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The multi-layer software architecture is designed to be universally applicable across different laboratory layouts and configurations. The same core software structure can accommodate various instrument arrangements, track configurations, and routing requirements through parameter adjustments rather than complete program rewriting

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

By segmenting the routing program into independent software layers, the system allows selective updating of only the affected layer when laboratory layouts change, rather than rewriting the entire routing program, thus reducing development time and cost while maintaining routing optimization

Inventive Principle:
Principle #1Segmentation

3Adaptability or versatility

If the routing program is updated to accommodate hardware changes, then the system adapts to new configurations, but the entire program must be substantially updated which is time consuming and expensive

Engineering Contradiction:
Improvehardware configuration adaptabilityVSAvoidprogram update time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The routing program is segmented into independent software layers, allowing hardware changes to be accommodated by updating only the specific layer affected by the hardware modification. This modular approach minimizes the scope of updates required and reduces both time and cost

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The software architecture is designed with dynamic flexibility, where the relationship between software layers and hardware components is established through configurable interfaces rather than hard-coded dependencies. This enables the system to adapt to hardware changes through parameter modifications and layer reconfiguration without requiring comprehensive program rewriting

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS20250271456A1Multi-layer software architecture for operating diagnostic laboratory systems
Publication Date: 2025.08.28 SIEMENS HEALTHCARE DIAGNOSTICS INC
  • US20250271456A1 patent drawing
  • US20250271456A1 patent drawing
  • US20250271456A1 patent drawing

AI summary

A diagnostic laboratory system includes one or more instruments and a transport system configured to transport sample containers to and from the one or more instruments, wherein each of the sample containers contains a biological sample. A computer is configured to execute a program to control operation of the diagnostic laboratory system. The program has an architecture comprising a plurality of individually replaceable software modules, wherein one or more software modules identify at least one test or plan at least one phase thereof to be performed on the biological sample. Another software module generates instructions to cause one or more of the sample containers to move to or from the one or more instruments in accordance with the at least one test or the at least one phase thereof. Methods of operating a diagnostic laboratory system are also disclosed.