Decentralized Health Module Publishing System

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Creating and distributing mobile applications that meet the diverse health needs of organizations and individuals is costly and time-consuming, as existing solutions lack customization options and integration with healthcare services.

Innovation Solution

A publishing system that allows organizations to create and customize health management modules with predefined templates, branding, and specific health initiatives, which can be easily integrated into existing mobile applications, enabling tailored user experiences and data tracking without requiring extensive development or maintenance.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If organizations create and distribute customized mobile applications to meet diverse health needs, then user experience and health management effectiveness are improved, but development cost and time consumption increase significantly

Engineering Contradiction:
Improvecustomization capabilityVSAvoiddevelopment efficiency
Core Design Contradiction:
Adaptability or versatilityVSProductivity

Solution Approach 1:

The application is divided into a core framework and separate customizable modules. Each module can be independently developed, configured, and distributed. Organizations can select and assemble pre-built modules to create customized health management applications without developing everything from scratch, thus improving development efficiency while maintaining adaptability.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

A universal module library is provided that contains multi-functional health management modules applicable to various organizations and health needs. These modules can be reused across different applications and organizations, reducing redundant development work while providing versatile health management capabilities.

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

2Adaptability or versatility

If organizations invest in creating fully customized applications with branding and specific health initiatives, then brand identity and user engagement are enhanced, but maintenance burden and costs increase

Engineering Contradiction:
Improvebranding customizationVSAvoidapplication maintenance complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

Branding and customization elements are segmented into separate configuration files and assets that can be updated independently from the core application. Organizations can modify their branding, logos, and health initiative parameters without requiring application re-compilation or complex maintenance operations.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

Successful application configurations, module assemblies, and branding templates are replicated and distributed to multiple organizations. Once a customized application is created and validated, it can be copied and adapted for similar organizations, significantly reducing maintenance burden and enabling consistent updates across multiple deployments.

Inventive Principle:
Principle #26Copying

3Reliability

If a centralized system is used to manage health data collection from multiple devices, then data integration and monitoring are improved, but system complexity and security risks increase

Engineering Contradiction:
Improvedata collection reliabilityVSAvoidsystem architecture complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

A standardized data interface layer acts as an intermediary between diverse health devices and the central management system. This interface layer handles device-specific protocols and data formats, translating them into a unified structure that the central system can process. This reduces system complexity by abstracting device diversity while maintaining reliable data collection from multiple sources.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS11954470B2On-demand decentralized collection of clinical data from digital devices of remote patients
Publication Date: 2024.04.09 VIGNET INC
  • US11954470B2 patent drawing
  • US11954470B2 patent drawing
  • US11954470B2 patent drawing

AI summary

In some implementations, a user interface for designing a health management module is provided by a server system. The user interface identifies a plurality of health management templates. The server system initially receives data indicating a user input received through the user interface that selects one of the plurality of module templates. The server system also receives customization parameters that customize the selected module template for a particular organization. The server system then generates a customized health management module for the particular organization based on the selected template and the customization parameters. The server system finally publishes the customized health management module for the particular organization that includes instructions configuring an application provided by a third-party application store.