Abstract: Systems and methods are disclosed that provide smart alerts to users, e.g., alerts to users about diabetic states that are only provided when it makes sense to do so, e.g., when the system can predict or estimate that the user is not already cognitively aware of their current condition, e.g., particularly where the current condition is a diabetic state warranting attention. In this way, the alert or alarm is personalized and made particularly effective for that user. Such systems and methods still alert the user when action is necessary, e.g., a bolus or temporary basal rate change, or provide a response to a missed bolus or a need for correction, but do not alert when action is unnecessary, e.g., if the user is already estimated or predicted to be cognitively aware of the diabetic state warranting attention, or if corrective action was already taken.

Abstract: Software systems and methods convert algorithms and software codes into time affecting linear pathways (TALPs) via decomposition and convert paired Input/Output (I/O) datasets into TALPs via Value Complexity polynomials. Generated TALPs can be enhanced through merging with other TALPs. TALPs can be grouped by matching the outputs of the TALP-associated prediction polynomials with some set of given criteria into families and cross-families that are useful in a new type of software optimization that allows for output values of grouped TALPs to be modeled, pooled, discretized and optimized to enhance goals or meet user goals.

Abstract: The functionality of a core application is extended using an add-on application (module) by extending native data types on the core application with custom data types and custom actions on the module. The module provides metadata associated with its custom data types and custom actions to the core application, which creates a dynamic type/action table. In some cases, native data types may be extended with custom data types and their associated actions. In other cases, native data types may be extended with custom actions from the module. The custom actions may be enabled for instances of native data types that have been extended. When a custom action is selected, code corresponding with the selected custom action is called from the module and run to perform the selected custom action.

Abstract: The functionality of a core application is extended using an add-on application (module) by extending native data types on the core application with custom data types and custom actions on the module. The module provides metadata associated with its custom data types and custom actions to the core application, which creates a dynamic type/action table. In some cases, native data types may be extended with custom data types and their associated actions. In other cases, native data types may be extended with custom actions from the module. The custom actions may be enabled for instances of native data types that have been extended. When a custom action is selected, code corresponding with the selected custom action is called from the module and run to perform the selected custom action.