Abstract: A computing system (100) that includes at least one microapp (202) and a container application (204) configured to receive an application output from the microapp(s) (202,602) via an application programming interface. The computing system (100) can include at least one processor (112,132) and at least one tangible, non-transitory computer-readable medium that stores instructions that, when executed by the at least one processor (112,132), cause the at least one processor (112,132) to perform operations. The operations can include providing, for display within a first panel (304) in a user interface (306), a navigation bar (302) based on data received from the container application (204); receiving, at the container application (204), the application output from the at least one microapp (202) via the application programming interface; and providing, for display within a second panel in the user interface (306), data describing the application output.

Abstract: A pharmaceutical company may employ a computer system that is configured to analyze anonymized patient data for patients treated by each of a plurality of healthcare providers (HCPs) to determine whether each such HCP is likely to make a given type of treatment decision for at least one patient in the foreseeable future. Based on the analysis, the computer system may predict that a given HCP is likely to make the given type of treatment decision for at least one patient at a given predicted time in the future and then responsively generate a trigger alert suggesting that the given HCP be visited prior to the given predicted time to deliver a message related to the given type of treatment decision. In turn, the computer system may cause the trigger alert to be sent to a target of the trigger alert, such as a representative of the pharmaceutical company.

Abstract: A computing system (100) that includes at least one microapp (202) and a container application (204) configured to receive an application output from the microapp(s) (202,602) via an application programming interface. The computing system (100) can include at least one processor (112,132) and at least one tangible, non-transitory computer-readable medium that stores instructions that, when executed by the at least one processor (112,132), cause the at least one processor (112,132) to perform operations. The operations can include providing, for display within a first panel (304) in a user interface (306), a navigation bar (302) based on data received from the container application (204); receiving, at the container application (204), the application output from the at least one microapp (202) via the application programming interface; and providing, for display within a second panel in the user interface (306), data describing the application output.

Abstract: Techniques to back up data associated with a cluster environment are disclosed. In various embodiments, an indication is received to back up data associated with the cluster. A backup configuration data associated with the cluster is used to back up, in a unified backup operation, one or more save sets associated with virtual resources associated with the cluster and one or more saves sets associated with physical nodes associated with the cluster, including by storing each respective save set in a manner that associates the save set with a virtual or physical node comprising the cluster suite.

Abstract: Techniques to back up a cluster resource are disclosed. In various embodiments, an active cluster node is used to take and store persistently on a cluster shared volume a snapshot of the cluster shared volume. The persistent snapshot is used to back up the cluster shared volume, including by storing checkpoint information indicating as the backup progresses which portions of the snapshot have been backed up. A cluster environment with which the cluster shared volume is associated is monitored to detect any failover or failback affecting the backup.

Abstract: A pharmaceutical company may employ a computer system that is configured to train a machine learning model for predicting a next time in the future at which a given type of treatment decision is likely to be made for a patient, use the trained machine learning model to analyze anonymized patient data for patients treated by a given health care provider (HCP) in order to predict a next time in the future at which the given HCP is likely to make a given type of treatment decision for at least one patient, and then responsively generate a trigger alert suggesting that the given HCP be visited prior to the predicted next time to deliver a message related to the given type of treatment decision, which may in turn be delivered to a target of the trigger alert.

Abstract: A pharmaceutical company may employ a computer system that is configured to analyze anonymized patient data for patients treated by each of a plurality of healthcare providers (HCPs) to determine whether each such HCP is likely to make a given type of treatment decision for at least one patient in the foreseeable future. Based on the analysis, the computer system may predict that a given HCP is likely to make the given type of treatment decision for at least one patient at a given predicted time in the future and then responsively generate a trigger alert suggesting that the given HCP be visited prior to the given predicted time to deliver a message related to the given type of treatment decision. In turn, the computer system may cause the trigger alert to be sent to a target of the trigger alert, such as a representative of the pharmaceutical company.

Abstract: Techniques to back up data associated with a cluster environment are disclosed. In various embodiments, an indication is received to back up data associated with the cluster. A backup configuration data associated with the cluster is used to back up, in a unified backup operation, one or more save sets associated with virtual resources associated with the cluster and one or more saves sets associated with physical nodes associated with the cluster, including by storing each respective save set in a manner that associates the save set with a virtual or physical node comprising the cluster suite.

Abstract: Techniques to back up data associated with a cluster environment are disclosed. In various embodiments, an indication is received to back up data associated with the cluster. A backup configuration data associated with the cluster is used to back up, in a unified backup operation, one or more save sets associated with virtual resources associated with the cluster and one or more saves sets associated with physical nodes associated with the cluster, including by storing each respective save set in a manner that associates the save set with a virtual or physical node comprising the cluster suite.

Abstract: A pharmaceutical company may employ a computer system that is configured to analyze anonymized patient data for patients treated by each of a plurality of healthcare providers (HCPs) to determine whether each such HCP is likely to make a given type of treatment decision for at least one patient in the foreseeable future. Based on the analysis, the computer system may predict that a given HCP is likely to make the given type of treatment decision for at least one patient at a given predicted time in the future and then responsively generate a trigger alert suggesting that the given HCP be visited prior to the given predicted time to deliver a message related to the given type of treatment decision. In turn, the computer system may cause the trigger alert to be sent to a target of the trigger alert, such as a representative of the pharmaceutical company.

Abstract: A method for recovering data from one or more storage systems for a group recovery. In response to receiving a request for the group recovery, the method implemented at a backup server identifies a group recovery resource based on the request, where the group recovery resource includes one or more recovery item lists. The backup server traverses the one or more recovery item lists of the group recovery resource to determine a source recovery storage system, target recovery storage systems, and one or more data items to be recovered to each of the target recovery storage systems. The backup server then initiates one or more recovery sessions to recover the one or more data items from the source recovery storage systems to the recovery target storage systems substantially concurrently.

Abstract: Techniques to back up a cluster shared volume (CSV) are disclosed. In various embodiments, a snapshot of the cluster shared volume is stored persistently on the cluster shared volume itself. A task to back up a corresponding assigned portion of the snapshot is assigned to each of one or more cluster servers available to participate in backing up the cluster shared volume. The cluster servers have shared access to the snapshot as stored on the cluster shared volume, and each is configured to perform the task assigned to it in parallel with any other cluster servers assigned to back up other portions of the same cluster shared volume snapshot. The respective assigned tasks are monitored to completion.

Abstract: Techniques to back up a cluster resource are disclosed. In various embodiments, an active cluster node is used to take and store persistently on a cluster shared volume a snapshot of the cluster shared volume. The persistent snapshot is used to back up the cluster shared volume, including by storing checkpoint information indicating as the backup progresses which portions of the snapshot have been backed up. A cluster environment with which the cluster shared volume is associated is monitored to detect any failover or failback affecting the backup.

Abstract: Techniques to back up a cluster resource are disclosed. In various embodiments, an active cluster node is used to take and store persistently on a cluster shared volume a snapshot of the cluster shared volume. The persistent snapshot is used to back up the cluster shared volume, including by storing checkpoint information indicating as the backup progresses which portions of the snapshot have been backed up. A cluster environment with which the cluster shared volume is associated is monitored to detect any failover or failback affecting the backup.

Abstract: Techniques to back up a cluster shared volume (CSV) are disclosed. In various embodiments, a snapshot of the cluster shared volume is stored persistently on the cluster shared volume itself. A task to back up a corresponding assigned portion of the snapshot is assigned to each of one or more cluster servers available to participate in backing up the cluster shared volume. The cluster servers have shared access to the snapshot as stored on the cluster shared volume, and each is configured to perform the task assigned to it in parallel with any other cluster servers assigned to back up other portions of the same cluster shared volume snapshot. The respective assigned tasks are monitored to completion.

Abstract: Techniques to back up a cluster shared volume (CSV) are disclosed. In various embodiments, a snapshot of the cluster shared volume is stored persistently on the cluster shared volume itself. A task to back up a corresponding assigned portion of the snapshot is assigned to each of one or more cluster servers available to participate in backing up the cluster shared volume. The cluster servers have shared access to the snapshot as stored on the cluster shared volume, and each is configured to perform the task assigned to it in parallel with any other cluster servers assigned to back up other portions of the same cluster shared volume snapshot. The respective assigned tasks are monitored to completion.

Abstract: Techniques to back up data associated with a cluster environment are disclosed. In various embodiments, an indication is received to back up data associated with the cluster. A backup configuration data associated with the cluster is used to back up, in a unified backup operation, one or more save sets associated with virtual resources associated with the cluster and one or more saves sets associated with physical nodes associated with the cluster, including by storing each respective save set in a manner that associates the save set with a virtual or physical node comprising the cluster suite.