Application Modeler Engine for Cross-Platform Patient App Generation

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Current digital software applications for patient engagement post-discharge lack customization for varying physician regimens, require extensive coding, and fail to support co-morbidity, with no efficient cross-platform deployment on Android and iPhone.

Innovation Solution

A computerized method using an application modeler engine for generating personalized digital software applications, enabling drag-and-drop node integration, chatbot inclusion, and deployment on mobile devices, with machine learning for customization and co-morbidity support.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If boiler plate applications are used with heavy customization needs, then the application can serve multiple patients, but extensive software coding effort and overhead are required for each customization

Engineering Contradiction:

Improvecustomization capabilityVSAvoidsoftware coding effort

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The application is divided into reusable components called nodes that can be independently selected and combined. Each node represents a functional unit (e.g., discharge instructions, medication reminders, follow-up scheduling) that can be assembled differently for each patient without requiring custom coding, thus reducing software complexity while maintaining high adaptability.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

A single universal application framework supports multiple patient-specific regimens through configurable nodes. The same framework can generate customized applications for different patients with varying conditions and physician protocols, eliminating the need for separate custom applications for each patient while avoiding extensive coding effort.

Inventive Principle:

Principle #6Universality (Multi-functionality)

2Adaptability or versatility

If custom applications are built for each patient, then patient-specific needs are met, but deployment overhead increases for both Android and iPhone platforms

Engineering Contradiction:

Improvepatient-specific customizationVSAvoiddeployment overhead

Core Design Contradiction:

Adaptability or versatilityVSLoss of time

Solution Approach 1:

The application framework pre-defines a set of standardized nodes and templates that can be quickly assembled for different patients. Instead of building custom applications from scratch for each patient, the system uses pre-prepared components that reduce deployment time while still achieving patient-specific customization through selective combination of nodes.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The system generates patient-specific applications by copying and configuring existing template structures rather than creating entirely new applications. This allows rapid deployment of customized applications for both Android and iPhone platforms by reusing proven architectural patterns and reducing the work required for each new patient enrollment.

Inventive Principle:

Principle #26Copying

3Device complexity

If single disease focus is used, then application logic is simplified, but co-morbidity support is insufficient as patients need multiple apps

Engineering Contradiction:

Improveapplication logicVSAvoidco-morbidity support

Core Design Contradiction:

Device complexityVSAdaptability or versatility

Solution Approach 1:

Multiple disease-specific regimens are merged into a single unified application framework by combining different node types and configuration options. The same application can simultaneously manage multiple conditions (e.g., diabetes, hypertension, heart disease) through integrated node combinations, eliminating the need for separate applications for each condition while maintaining manageable logic through modular design.

Inventive Principle:

Principle #5Merging (Combining)

Data Source

PatentUS20220375549A1Method and system of generating, delivering and displaying cross platform personalized digital software applications

Publication Date: 2022.11.24 MELKOTE RAMASWAMY N

AI summary

In one aspect, a computerized method for generating a personalized digital software application comprising: providing an application modeler engine. With the application modeler engine the method provides a graphical display of a palate that comprises a list all the nodes that are available to include in an application definition file(s). The application modeler engine receives a set of nodes via a drag and drop operation into the application definition file. The application modeler engine defines and integrates a chatbot into the personalized digital software application. The application modeler engine automatically creates the application definition file to run on a mobile device of the patient, wherein the application definition file follows a protocol and logic created in the application by a care team and the drag and dropped nodes. The application modeler engine uses the application definition file to generate the application from the application definition file. The application modeler engine deploys the application to a user's mobile device.