Pharmacy Data Interface Emulating Pseudo TTY Devices

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing pharmacy systems are often proprietary and not easily integrated, making it difficult to obtain data on pharmaceutical compounds dispensed by multiple pharmacies without requiring extensive interface development.

Innovation Solution

A pharmacy system data interface method that emulates a device, such as a pseudo TTY feature, to receive and transmit prescription data from multiple proprietary systems to a centralized location without modifying the systems, allowing for independent data storage and transmission to a data warehouse.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If proprietary pharmacy systems are integrated through custom interfaces, then data can be obtained from multiple pharmacies, but system complexity and integration costs increase significantly

Engineering Contradiction:
Improvedata integration capabilityVSAvoidinterface development complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system segments the integration problem by creating separate, standardized interface modules for each pharmacy system type. Each module handles specific pharmacy systems independently, allowing the central data collection system to remain simple while supporting multiple proprietary systems through modular, interchangeable interface components.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces a standardized intermediary interface layer between proprietary pharmacy systems and the central data collection system. This mediator translates various proprietary data formats into a common standard, eliminating the need for complex custom integration for each system while maintaining full data access capability.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Loss of information

If custom interfaces are developed for each proprietary system, then complete data access is achieved, but implementation time and resources increase

Engineering Contradiction:
Improvedata completenessVSAvoidimplementation time
Core Design Contradiction:
Loss of informationVSLoss of time

Solution Approach 1:

The system implements a universal interface standard that can handle multiple proprietary pharmacy systems through a single framework. This multi-functional interface design allows the system to access complete data from various sources without requiring separate development projects for each system, significantly reducing implementation time while maintaining data completeness.

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

Solution Approach 2:

The patent establishes predetermined interface protocols and standardized data formats in advance before actual system integration. By pre-defining communication standards and data structures, the system can rapidly integrate new pharmacy systems without extensive custom development, reducing implementation time while ensuring complete data capture.

Inventive Principle:
Principle #10Preliminary action

3Ease of operation

If pharmacy systems are modified to enable data collection, then data access is simplified, but system reliability and security may be compromised

Engineering Contradiction:
Improvedata collection easeVSAvoidsystem reliability
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The system uses an intermediary interface layer that collects data without modifying the original pharmacy systems. This mediator approach simplifies data collection by providing a standardized access point while maintaining the integrity and reliability of the source systems, as no changes are made to the proprietary software or hardware.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent implements data copying mechanisms where information is replicated from the original pharmacy systems through standardized interfaces rather than modifying the source systems. This copying approach maintains system reliability by preserving the original system integrity while enabling easy data collection through the replicated data streams.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS8577691B2Pharmacy system data interface system and method
Publication Date: 2013.11.05 OUTCOMES OPERATING INC
  • US8577691B2 patent drawing
  • US8577691B2 patent drawing
  • US8577691B2 patent drawing

AI summary

A method for receiving prescription data from a pharmacy is provided. The method includes emulating a device, such as using a pseudo TTY feature of a Unix operating system or a pseudo device of a Windows operating system. A prescription authorization system is then set to transmit data to the emulated device when the prescription data is provided to a claims approval agency by the prescription authorization system. The data can be supplemented with data from a secondary source, such as a system that acquires data in accordance with the Health Insurance Portability and Accountability Act or other suitable systems. The prescription data and any supplemental data is then received at the prescription authorization system, and is transmitted to the emulated device. The prescription data is also stored in a local log file, and is transmitted to a data warehouse over a network using the emulated device.