External Interface Device for Cardiac Rhythm Management Data Collection

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Current medical systems for implanted devices lack the ability to effectively collect and store patient outcome and event information, such as hospitalizations and device reprogramming reasons, which are crucial for improving device programming and device design.

Innovation Solution

An external interface device is used to initiate transmission sessions with implanted cardiac rhythm management (CRM) devices, prompting users to select reasons for the sessions, which are then stored and uploaded to a patient management computer system, allowing for the collection and storage of patient event information.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of information

If in-home monitoring systems collect device data and sensor readings, then data volume increases, but patient outcome and event information remains insufficient

Engineering Contradiction:

Improvepatient outcome informationVSAvoidsystem complexity

Core Design Contradiction:

Loss of informationVSDevice complexity

Solution Approach 1:

The patent introduces an intermediary component (external interface device/programmer) that mediates between the implanted CRM device and the data collection system. This intermediary captures transmission session information and patient event data that would otherwise be lost, bridging the gap between device operations and comprehensive outcome tracking without requiring direct modification of the implanted device

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The system enables self-service data collection by automatically capturing transmission session metadata and linking it to patient events. The external interface device autonomously records session reasons, timestamps, and outcomes without requiring manual intervention or extensive electronic medical records, allowing the system to gather valuable information through its own operational processes

Inventive Principle:

Principle #25Self-service

2Loss of information

If comprehensive patient data is collected through electronic medical records and frequent hospital visits, then information completeness improves, but patient burden and system cost increase

Engineering Contradiction:

Improvepatient event informationVSAvoidhospital visit time

Core Design Contradiction:

Loss of informationVSLoss of time

Solution Approach 1:

The system performs preliminary data collection during routine transmission sessions by capturing session metadata, reasons, and timestamps before patient events occur. This advance capture of transmission information enables retrospective linkage to patient outcomes without requiring additional hospital visits or time investment from patients

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The system establishes a feedback loop where transmission session information is continuously captured and linked to patient events. This feedback mechanism automatically associates device programming changes with patient outcomes, enabling comprehensive information collection through the natural operational rhythm of device monitoring without imposing additional time burdens

Inventive Principle:

Principle #23Feedback

3Loss of information

If transmission session information is captured and stored, then data value for device improvement increases, but data management complexity increases

Engineering Contradiction:

Improvetransmission session informationVSAvoiddata management complexity

Core Design Contradiction:

Loss of informationVSDevice complexity

Solution Approach 1:

The patent merges transmission session metadata capture with existing device programming and monitoring operations. By combining session reason collection, timestamp recording, and outcome linkage into the routine transmission session workflow, the system captures valuable information without creating separate complex data management processes

Inventive Principle:

Principle #5Merging (Combining)

Solution Approach 2:

The external interface device performs multiple functions: it programs the CRM device, monitors sensor data, collects transmission session metadata, and links information to patient events. This multi-functionality consolidates data collection responsibilities into an existing device rather than requiring separate specialized systems, managing complexity through functional integration

Inventive Principle:

Principle #6Universality (Multi-functionality)

Data Source

PatentUS8260423B2Systems and methods for collecting patient event information

Publication Date: 2012.09.04 CARDIAC PACEMAKERS INC

AI summary

A method of collecting patient event information from a cardiac rhythm management system (CRM system) is described, where the CRM system includes a cardiac rhythm management device (CRM device) and an external interface device. The method includes the steps of initiating a transmission session wherein the interface device communicates with the CRM device, prompting a user of the CRM system to select a reason for the transmission session, inputting the selected reason for the transmission session to the interface device, and storing the selected reason for the transmission session and timestamp information for the transmission session.