Granted Patent B1

US 12,585,438 · App. 17/854,971 · Granted Mar 24, 2026

Inventors: Raja Sanevelly (Cumming, GA); Sam Kyatham (Alpharetta, GA); Omkaram Sangem (Cumming, GA)

Assignee: Elevance Health, Inc.

G06F8/34

Abstract

Claims (47)

1 . A method for shell-based web application implementation, comprising:

while an application host module executes and hosts a shell-based web application accessible by third party client computing devices:

hosting, at an application build module, a developer user interface accessible by third party developer computing devices to reconfigure the shell-based web application wherein the application build module is operating on a separate and distinct web server from the application host module,

receiving, at the application build module, from the third party developer computing devices, application configuration data required to reconfigure the shell-based web application;

transmitting, by the application build module, the application configuration data to an application renderer module of the application host module;

automatically generating, at the application renderer module, web application source code using the application configuration data received from the application build module, without manual input of source code from third party developer computing devices; and

reconfiguring, at the application renderer module, the shell-based web application without redeploying the shell-based web application using:

(i) the generated web application source code, and

(ii) native source code of the shell-based web application,

wherein the method further comprises:

interpreting, at the application renderer module, the application configuration data;

selecting, at the application renderer module, a portion of source code that corresponds to respective portions of the application configuration data; and

modifying the selected portion of the source code based on the respective portions of the application configuration data.

2 . The method of claim 1 , wherein transmitting the application configuration data to the application renderer module includes converting the application configuration data into a key-value pair format.

3 . The method of claim 2 , wherein application configuration data include:

web module definition,

web module fields,

web module rules, and

publishing attributes, received from the third party developer computing devices via the developer user interface.

4 . The method of claim 3 , wherein web module rules include branching rules, scoring configuration, and general module rules.

5 . The method of claim 4 , wherein branching rules include: generating a web module expression defining an action to be performed on a respective web module element based on an input received at the shell-based web application from a respective third party client computing device.

6 . The method of claim 4 , wherein branching rules include: generating a web module expression defining an action to be performed on a respective web module element based on existing third party data relating to the third party client computing device.

7 . The method of claim 4 , wherein the scoring configuration is a scoring rubric for scoring user inputs to a web module for further processing.

8 . The method of claim 7 , wherein the web module rules include defining an action to be performed on a respective web module element based on a result of the scoring rubric.

9 . The method of claim 4 , wherein the general module rules include one or more actions to perform on one or more components of a web module based on certain criteria.

10 . The method of claim 3 , wherein the publishing attributes include target web application name, environment information, and effective date range.

11 . The method of claim 1 , further comprising, before transmitting the application configuration data to the application renderer module:

generating an application preview user interface,

transmitting the application preview user interface to the third party developer computing devices, and

receiving verification from the third party developer computing devices.

12 . The method of claim 11 , including generating web application source code using the application configuration data that comprises web module definition, web module elements, web module rules, and publishing attributes, received from the third party developer computing devices via the developer user interface.

13 . The method of claim 12 , wherein the shell-based web application is selected based on the publishing attributes received from the third party developer computing devices via the developer user interface.

14 . The method of claim 13 , further comprising storing the application configuration data for the shell-based web application and applying a portion of the application configuration data to a second shell-based application based on a command received from the third party developer computing devices via the developer user interface.

15 . A system for shell-based web application implementation, comprising:

an application host module server storing instructions for executing and hosting a shell-based web application accessible by third party client computing devices, the application host module server comprising an application renderer module; and

an application build module server, separate and distinct from the application host module server, the application build module server storing instructions for, while the application host module server executes and hosts the shell-based web application:

hosting a developer user interface accessible by third party developer computing devices to reconfigure the shell-based web application,

receiving, from the third party developer computing devices, application configuration data required to reconfigure the shell-based web application; and

transmitting the application configuration data to the application renderer module;

the application renderer module storing instructions for:

automatically generating web application source code using the application configuration data received from the application build module without manual input of source code from third party developer computing devices;

reconfiguring the shell-based web application without redeploying the shell-based web application using:

(i) the generated web application source code, and

(ii) native source code of the shell-based web application;

interpreting, at the application renderer module, the application configuration data;

selecting, at the application renderer module, a portion of source code that corresponds to respective portions of the application configuration data; and

modifying the selected portion of the source code based on the respective portions of the application configuration data.

Continuity (1)

References Cited (10)