Medication Request Workflow Automation via Triggered Operational Modes

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current workflows for processing medication requests are manually adjusted, lacking the ability to dynamically change based on factors like days of the week, time periods, staffing levels, and medication request volume, leading to inefficiencies and potential errors.

Innovation Solution

A system that associates operational modes with workflows for processing medication requests, where triggers such as days of the week, times, and request volumes initiate specific workflows, allowing for automated or semi-automated processing adjustments.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If workflows are manually adjusted, then flexibility to change workflows exists, but operational efficiency and productivity decrease due to manual intervention requirements

Engineering Contradiction:
Improveworkflow flexibilityVSAvoidoperational efficiency
Core Design Contradiction:
Adaptability or versatilityVSProductivity

Solution Approach 1:

The system implements dynamic workflow selection by automatically switching between different operational modes (e.g., normal mode, backup mode, maintenance mode) based on real-time system conditions, staffing levels, and medication request volumes. This eliminates manual workflow adjustments while maintaining adaptability to changing conditions.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system continuously monitors system conditions, staffing availability, and medication request patterns, then automatically adjusts workflow execution accordingly. This feedback loop enables the system to adapt to changing conditions without manual intervention, improving both efficiency and flexibility.

Inventive Principle:
Principle #23Feedback

2Productivity

If automated workflow switching is implemented, then operational efficiency and productivity improve, but device complexity increases

Engineering Contradiction:
Improveoperational efficiencyVSAvoidsystem complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The system divides workflow management into distinct operational modes (normal, backup, maintenance, etc.), each with predefined triggers and procedures. This segmentation simplifies the complexity by organizing automated decisions into manageable, discrete states rather than a single complex decision-making system.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system manages complexity by changing operational parameters (workflow mode, processing speed, resource allocation) based on predefined triggers rather than implementing a completely new complex system. This allows automated efficiency improvements through parameter adjustment rather than structural complexity.

Inventive Principle:
Principle #35Parameter changes

3Adaptability or versatility

If multiple operational modes are maintained for different conditions, then adaptability to various scenarios improves, but loss of time in mode switching occurs

Engineering Contradiction:
Improvescenario adaptabilityVSAvoidmode switching time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

Different operational modes are pre-configured with their workflows, triggers, and parameters before needed. When a trigger condition is detected, the system can immediately switch to the appropriate pre-prepared mode without time-consuming setup or decision-making, minimizing switching time while maintaining adaptability.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS10269085B2Modes and workflows for processing medication requests
Publication Date: 2019.04.23 OMNICELL INC
  • US10269085B2 patent drawing
  • US10269085B2 patent drawing
  • US10269085B2 patent drawing

AI summary

Systems, methods, apparatus, and computer program products are provided for processing medication requests. In one embodiment, a user may define an operational mode that can be initiated by one or more triggers. A user may also define one or more workflows for processing medication requests. The one or more workflows can be associated with the operational mode. In response to the occurrence of the appropriate triggers, the operational mode can automatically, semi-automatically, and/or manually be initiated. When the operational mode is initiated, the associated workflows are used for processing medication requests.