US-20260128167-A1 - MEDICAL DEVICE APPLICATION MANAGEMENT

US20260128167A1US 20260128167 A1US20260128167 A1US 20260128167A1US-20260128167-A1

Abstract

A system for managing medical device applications. The system provides a user interface engine and receives a custom resource definition of the user interface engine for an application configured for execution on a medical device. The system processes the custom resource definition, launches a configuration portal, and dynamically renders a user interface in the configuration portal. The user interface is rendered based on the custom resource definition. The system receives configuration inputs on the user interface, and persist the configuration inputs into a catalogue database that causes the application to be executed on the medical device based on the configuration inputs.

Inventors

Matthew J. Winter
Nicholas J. Fabbricante
Christopher M. Haigney
Christopher M. Keegan
Michael E. Rice

Assignees

WELCH ALLYN, INC.

Dates

Publication Date: 20260507
Application Date: 20241101

Claims (20)

1 . A system for managing medical device applications, the system comprising: at least one processing device; and a memory device storing instructions which, when executed by the at least one processing device, cause the at least one processing device to: provide a user interface engine; receive a custom resource definition of the user interface engine for an application configured for execution on a medical device; process the custom resource definition; launch a configuration portal; dynamically render a user interface in the configuration portal, the user interface being rendered based on the custom resource definition; receive configuration inputs on the user interface; and persist the configuration inputs into a catalogue database that causes the application to be executed on the medical device based on the configuration inputs.
2 . The system of claim 1 , wherein the user interface engine provides an interface specification between the application and the configuration portal for obtaining configuration data for the application.
3 . The system of claim 1 , wherein the application and the configuration portal operate asynchronously with respect to one another.
4 . The system of claim 1 , wherein the memory device stores additional instructions which, when executed by the at least one processing device, cause the at least one processing device to: receive one or more changes to the custom resource definition; and update the user interface displayed in the configuration portal based on the one or more changes to the custom resource definition, wherein the user interface is updated without modifying the configuration portal.
5 . The system of claim 1 , wherein the user interface rendered in the configuration portal enables a plurality of configurations for execution of the application.
6 . The system of claim 1 , wherein the configuration inputs define at least one inbound connection and at least one outbound connection for the application.
7 . The system of claim 1 , further comprising: the medical device, and wherein the medical device includes a sensor for capturing physiological data from a patient.
8 . The system of claim 7 , wherein the configuration inputs determine how the physiological data captured by the sensor of the medical device is persisted in a database.
9 . The system of claim 7 , wherein the medical device is a patient monitoring device or a hospital bed.
10 . A method of managing medical device applications, the method comprising: providing a user interface engine; receiving a custom resource definition of the user interface engine for an application configured for execution on a medical device; processing the custom resource definition; launching a configuration portal; dynamically rendering a user interface in the configuration portal, the user interface being rendered based on the custom resource definition; receiving configuration inputs on the user interface; and persisting the configuration inputs into a catalogue database that causes the application to be executed on the medical device based on the configuration inputs.
11 . The method of claim 10 , wherein the user interface engine provides an interface specification between the application and the configuration portal for obtaining configuration data for the application.
12 . The method of claim 10 , wherein the application and the configuration portal operate asynchronously with respect to one another.
13 . The method of claim 10 , wherein the user interface rendered in the configuration portal enables a plurality of configurations for execution of the application.
14 . The method of claim 10 , wherein the configuration inputs define at least one inbound connection and at least one outbound connection for the application.
15 . The method of claim 10 , wherein the configuration inputs determine how physiological data captured by a sensor of the medical device is persisted in a database.
16 . The method of claim 10 , further comprising: receiving a change to the custom resource definition for the application; and updating the user interface displayed in the configuration portal based on the change to the custom resource definition, wherein the user interface is updated without modifying the configuration portal.
17 . Computer-readable non-transitory storage media embodying software that is operable when executed to: provide a user interface engine; receive a custom resource definition of the user interface engine for an application configured for execution on a medical device; process the custom resource definition; launch a configuration portal; dynamically render a user interface in the configuration portal, the user interface being rendered based on the custom resource definition; receive configuration inputs on the user interface; and persist the configuration inputs into a catalogue database that causes the application to be executed on the medical device based on the configuration inputs.
18 . The computer-readable non-transitory storage media of claim 17 , wherein the user interface engine provides an interface specification between the application and the configuration portal for obtaining configuration data for the application.
19 . The computer-readable non-transitory storage media of claim 17 , wherein the application and the configuration portal operate asynchronously with respect to one another.
20 . The computer-readable non-transitory storage media of claim 17 , wherein the configuration inputs define at least one inbound connection and at least one outbound connection for the application.

Description

BACKGROUND The management of software applications for medical devices is a critical component of modern healthcare delivery, encompassing the development, deployment, and maintenance of software that is either embedded in or intended to be used with medical devices. This management ensures that software applications meet regulatory requirements, function as intended, and provide secure and effective operation throughout their lifecycle. Software applications for medical devices are often updated to work seamlessly with other systems and devices within a healthcare environment. Interoperability ensures that data can be shared and utilized effectively, improving patient care and clinical decision-making. Also, software applications for medical devices often require regular updates to correct any defects, improve functionality, and address security vulnerabilities. Maintenance also involves ensuring compatibility with updated hardware or other software systems. The management of software applications for medical devices is a comprehensive and dynamic process that is driven by the need to ensure interoperability, patient safety, data security, and regulatory compliance, while also fostering innovation and the efficient use of technology in healthcare. As medical devices become more software-driven and interconnected, the importance of robust software management practices will continue to escalate. SUMMARY In general terms, the present disclosure relates to managing medical device applications. In one possible configuration, an application configuration registration custom resource is defined for dynamically rendering a user interface in a configuration portal that can be used to configure an application for use on one or more medical devices. Various aspects are described in this disclosure, which include, but are not limited to, the following aspects. One aspect relates to a system for managing medical device applications, the system comprising: at least one processing device; and a memory device storing instructions which, when executed by the at least one processing device, cause the at least one processing device to: provide a user interface engine; receive a custom resource definition of the user interface engine for an application configured for execution on a medical device; process the custom resource definition; launch a configuration portal; dynamically render a user interface in the configuration portal, the user interface being rendered based on the custom resource definition; receive configuration inputs on the user interface; and persist the configuration inputs into a catalogue database that causes the application to be executed on the medical device based on the configuration inputs. Another aspect relates to a method of managing medical device applications, the method comprising: providing a user interface engine; receiving a custom resource definition of the user interface engine for an application configured for execution on a medical device; processing the custom resource definition; launching a configuration portal; dynamically rendering a user interface in the configuration portal, the user interface being rendered based on the custom resource definition; receiving configuration inputs on the user interface; and persisting the configuration inputs into a catalogue database that causes the application to be executed on the medical device based on the configuration inputs. Another aspect relates to a computer-readable non-transitory storage media embodying software that is operable when executed to: provide a user interface engine; receive a custom resource definition of the user interface engine for an application configured for execution on a medical device; process the custom resource definition; launch a configuration portal; dynamically render a user interface in the configuration portal, the user interface being rendered based on the custom resource definition; receive configuration inputs on the user interface; and persist the configuration inputs into a catalogue database that causes the application to be executed on the medical device based on the configuration inputs. A variety of additional aspects will be set forth in the description that follows. The aspects can relate to individual features and to combination of features. It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the broad inventive concepts upon which the embodiments disclosed herein are based. DESCRIPTION OF THE FIGURES The following drawing figures, which form a part of this application, are illustrative of the described technology and are not meant to limit the scope of the disclosure in any manner. FIG. 1 schematically illustrates an example of a system for managing medical device applications that includes a connectivity platform communicatively coupled to a plurality of medical devices and a work