Contextual Object Interface for Rapid Data Capture

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current interface environments are inefficient in capturing and storing complex and variable data, particularly for high-value users, as they require significant time and effort to enter detailed information.

Innovation Solution

An interface environment with contextual objects that respond to user input, allowing for the addition or removal of objects based on domain-specific knowledge, enabling rapid data capture and storage through a structured and adaptable system, including buttons for saving data and hierarchical levels that affect related content, facilitating access by external applications.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If traditional interface environments are used to capture complex data, then data can be stored in a database, but the time required for data entry increases significantly

Engineering Contradiction:
Improvedata capture robustnessVSAvoiddata entry time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary actions by automatically adding contextual objects to the document based on domain-specific knowledge before the user completes data entry. When a user begins entering data for a contextual object, the system proactively adds related contextual objects and establishes their relationships, reducing the time the user would otherwise need to manually create and connect each object.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system serves itself by automatically managing the addition, removal, and relationship establishment of contextual objects based on domain-specific knowledge. The system monitors user input and autonomously updates the document structure, adding related contextual objects and adjusting relationships without requiring manual intervention for each structural element.

Inventive Principle:
Principle #25Self-service

2Reliability

If detailed and structured data representation is implemented, then data can be stored in a robust manner, but the complexity of the interface increases

Engineering Contradiction:
Improvedata storage robustnessVSAvoidinterface complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The interface is segmented into distinct contextual objects, each representing a specific concept or entity within the domain. Each contextual object can be independently added, modified, or removed, and the system manages the relationships between these segmented objects. This segmentation allows complex data to be represented through multiple simple, manageable units rather than a monolithic complex structure.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system introduces an intermediary layer of domain-specific knowledge that mediates between the user's simple inputs and the complex data structure. This intermediary knowledge base automatically translates user actions into appropriate structural changes, relationships, and data organization, shielding the user from the underlying complexity while maintaining robust data representation.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Adaptability or versatility

If contextual objects are added and removed dynamically, then the interface becomes more adaptable, but the difficulty of detecting and measuring changes increases

Engineering Contradiction:
Improveinterface adaptabilityVSAvoidchange detection difficulty
Core Design Contradiction:
Adaptability or versatilityVSDifficulty of detecting and measuring

Solution Approach 1:

The system implements feedback mechanisms that automatically detect and respond to changes in contextual objects. When a user adds, modifies, or removes a contextual object, the system detects this change and provides feedback by updating relationships, triggering related object additions, and adjusting the document structure accordingly. This feedback loop makes change detection systematic and automated rather than manual and difficult.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The interface embraces dynamics by allowing contextual objects to be added, removed, and modified during data entry without requiring the user to predict or measure all possible changes in advance. The system dynamically adapts the document structure based on actual user input and domain-specific knowledge, making the interface flexible and responsive rather than static and rigid.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS20230325044A1Hierarchical interface environment
Publication Date: 2023.10.12 JULOTA INC
  • US20230325044A1 patent drawing
  • US20230325044A1 patent drawing
  • US20230325044A1 patent drawing

AI summary

An interface environment captures and stores complex and variable data from a user in a rapid, robust, adaptable, and structured manner. The interface environment includes a display of a document, and the document includes one or more contextual objects. Each contextual object is responsive to an input of a user changing the content of the contextual object, and adds or removes from the document one or more contextual objects. The one or more contextual objects are added or removed in accordance with the content of the contextual object mapped to a definition in a domain specific knowledge for the document and in response to external applications monitoring the contextual objects. The interface environment is applicable to all types of domains including healthcare, point-of-sale, legal, financial, and other services. The document and the contextual objects are saved to a database and accessible by other external applications.