Systems, methods, and computer program products for medical device event management

Abstract

A system for artificial intelligence-based event management includes at least one processor that performs the following operations: receiving data associated with an event related to a medical device via a user interface (UI) associated with the medical device; receiving data associated with an identifying characteristic of the medical device; generating an event message, the event message including the data associated with the event related to the medical device and the data associated with the identifying characteristic of the medical device; providing a response message via the UI associated with the medical device based on the data associated with the event related to the medical device, the response message including information based on the output of a generation and conversational artificial intelligence (AI) platform; determining a category of the event message; and performing an action based on the category of the event message. A method and computer program product are also disclosed.

Description

[Technical Field]

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS This application claims priority to U.S. Provisional Patent Application No. 63 / 487,865, filed March 1, 2023, the disclosure of which is incorporated herein by reference in its entirety.

[0002] The present disclosure relates generally to systems, methods, and / or products for use in diagnostic and interventional medical imaging procedures, and in non-limiting embodiments, to systems, methods, and computer program products for event management associated with medical devices, including artificial intelligence-based event management. [Background technology]

[0003] Medical Device Reporting (MDR) may be subject to regulations that require entities, such as manufacturers, to monitor device performance, detect potential device-related safety hazards, and / or contribute to benefit-risk assessments of medical devices and related products.

[0004] Mandatory reporters, such as manufacturers, medical device user facilities, and importers of medical devices, may be required to submit certain types of reports of adverse events and / or product problems related to medical devices to government regulatory agencies. Additionally, government regulatory agencies may also encourage healthcare professionals, patients, caregivers, and / or consumers to submit voluntary reports of serious adverse events, as well as use errors, product quality problems, and treatment failures that may be associated with medical devices.

[0005] In some cases, government regulatory agencies may require medical device manufacturers to analyze customer complaints within a short timeframe when they are received. Depending on the nature of the complaint, some complaints may be reported to regulatory agencies. Medical device reporting timelines vary globally and can range from two days for significant public health threats to three to 30 days for all other reportable incidents based on the severity of the incident. This timeline may require that customer complaint information arrive within a short timeframe and that the information associated with the customer complaint is as complete as possible and accurately reported to all parties, including the medical device manufacturer. Summary of the Invention [Means for solving the problem]

[0006] Accordingly, systems, methods, and computer program products are provided for event management associated with medical devices, including artificial intelligence (AI)-based event management, which may include the use of machine learning models, including deep learning models.

[0007] Further non-limiting embodiments or aspects are described in the following numbered clauses:

[0008] Clause 1. A system for processing information associated with an event related to a medical device, the system comprising at least one processor configured to: receive data associated with the event related to the medical device via a user interface (UI) associated with the medical device; receive data associated with an identifying characteristic of the medical device; generate an event message, the event message including the data associated with the event related to the medical device and the data associated with the identifying characteristic of the medical device; provide a response message via the UI associated with the medical device based on the data associated with the event related to the medical device, the response message including information based on output of a generation and conversational artificial intelligence (AI) platform; determine a category of the event message based on at least one of the data associated with the event related to the medical device, the data associated with the identifying characteristic of the medical device, or any combination thereof; and perform an action based on the category of the event message.

[0009] Clause 2. The system of clause 1, wherein the generative and conversational AI platform comprises at least one of a generative AI model, a conversational AI model, or any combination thereof.

[0010] Clause 3: The system described in Clause 1 or 2, wherein at least one processor is configured to perform: generating a response message based on receiving data associated with an event related to the medical device, wherein when generating the response message, the at least one processor is configured to provide the data associated with the event related to the medical device as input to a generative AI model and determine an output of the generative AI model based on the input, the output including information associated with potential solutions to the event related to the medical device; and when providing the response message via a UI associated with the medical device, the at least one processor is configured to provide information associated with potential solutions to the event related to the medical device.

[0011] Clause 4: The system of any one of clauses 1 to 3, wherein when providing a response message via a UI associated with the medical device, at least one processor is configured to provide a prompt for receiving information from a user via a UI associated with the medical device, the prompt including a question associated with an event related to the medical device.

[0012] Clause 5: The system of any one of clauses 1 to 4, wherein when performing the operation, at least one processor is configured to transmit the event message based on a category of the event message.

[0013] Clause 6: The system of any one of clauses 1 to 5, wherein when transmitting the event message, at least one processor is configured to: transmit the event message to a healthcare provider communication network; transmit the event message to a system for trend analysis related to one or more events related to the medical device; transmit the event message to a communication gateway for further transmission; or any combination thereof.

[0014] Clause 7: The system of any one of clauses 1 to 6, wherein at least one processor is further configured to capture data associated with a timestamp related to an event related to the medical device, wherein the data associated with the timestamp includes at least one of data associated with a time when the data associated with the event related to the medical device was received via a UI associated with the medical device, data associated with a time when a malfunction of the medical device occurred, or any combination thereof.

[0015] 8. The system of any one of clauses 1 to 7, further configured to implement clause 8, wherein at least one processor provides a UI associated with the medical device on the mobile device.

[0016] Clause 9: The system of any one of clauses 1 to 8, wherein when providing a UI associated with the medical device on the mobile device, at least one processor is configured to provide a UI associated with the medical device on the mobile device via an application on the mobile device based on receiving an input prompt on the mobile device.

[0017] Clause 10: The system of any one of clauses 1 to 9, wherein when receiving data associated with an event related to a medical device, at least one processor receives the data associated with the event related to the medical device via a chatbot that interacts with a UI associated with the medical device.

[0018] Clause 11: The system of any one of clauses 1 to 10, wherein when receiving data associated with an event related to the medical device, at least one processor is configured to receive voice data from a user via a user interface (UI) associated with the medical device, convert the voice data into text data using a speech-to-text algorithm, and convert the text data into data associated with the event related to the medical device using a natural language processing (NLP) algorithm.

[0019] Clause 12. A method for processing information associated with an event related to a medical device, the method comprising: receiving, with at least one processor, data associated with the event related to the medical device via a user interface (UI) associated with the medical device; receiving, with the at least one processor, data associated with an identifying characteristic of the medical device; generating, with the at least one processor, an event message, the event message including data associated with the event related to the medical device and data associated with an identifying characteristic of the medical device; providing, with the at least one processor, a response message via the UI associated with the medical device based on the data associated with the event related to the medical device, the response message including information based on output of a generation and conversational artificial intelligence (AI) platform; determining, with the at least one processor, a category of the event message based on at least one of the data associated with the event related to the medical device, the data associated with the identifying characteristic of the medical device, or any combination thereof; and performing, with the at least one processor, an action based on the category of the event message.

[0020] Clause 13. The method of clause 12, wherein the generative and conversational AI platform comprises at least one of a generative AI model, a conversational AI model, or any combination thereof.

[0021] Clause 14: The method of clause 12 or 13, further comprising generating a response message based on receiving data associated with an event related to a medical device, wherein generating the response message includes providing the data associated with the event related to the medical device as input to a generative AI model, determining an output of the generative AI model based on the input, wherein the output includes information associated with potential solutions to the event related to the medical device, and providing the response message via a UI associated with the medical device includes providing information associated with potential solutions to the event related to the medical device.

[0022] Clause 15. The method of any one of clauses 12 to 14, wherein providing a response message via a UI associated with the medical device includes providing a prompt for receiving information from a user via a UI associated with the medical device, the prompt including a question associated with an event related to the medical device.

[0023] Clause 16. The method of any one of clauses 12 to 15, wherein performing an action includes transmitting the event message based on a category of the event message.

[0024] Clause 17. The method of any one of clauses 12 to 16, wherein transmitting the event message includes transmitting the event message to a healthcare provider communications network, transmitting the event message to a system for trend analysis related to one or more events related to the medical device, transmitting the event message to a communications gateway for further transmission, or any combination thereof.

[0025] Clause 18. The method of any one of clauses 12 to 17, further comprising capturing data associated with a timestamp related to an event related to the medical device, wherein the data associated with the timestamp includes at least one of data associated with a time when the data associated with the event related to the medical device was received via a UI associated with the medical device, data associated with a time when a malfunction of the medical device occurred, or any combination thereof.

[0026] Clause 19. The method of any one of clauses 12 to 18, further comprising providing a UI associated with the medical device on a mobile device.

[0027] Clause 20. The method of any one of clauses 12 to 19, wherein providing a UI associated with the medical device on the mobile device includes providing a UI associated with the medical device on the mobile device via an application on the mobile device based on receiving an input prompt on the mobile device.

[0028] Clause 21. The method of any one of clauses 12 to 20, wherein receiving data associated with an event related to a medical device includes receiving data associated with an event related to the medical device via a chatbot that interacts with a UI associated with the medical device.

[0029] Clause 22: The method of any one of clauses 12 to 21, wherein receiving data associated with an event related to the medical device includes receiving voice data from a user via a user interface (UI) associated with the medical device, converting the voice data into text data using a speech-to-text algorithm, and converting the text data into data associated with the event related to the medical device using a natural language processing (NLP) algorithm.

[0030] Clause 23. A computer program product for processing information associated with an event related to a medical device, comprising at least one non-transitory computer-readable medium containing one or more instructions, which, when executed by at least one processor, cause the at least one processor to perform the following: receive, via a user interface (UI) associated with the medical device, data associated with the event related to the medical device; receive data associated with an identifying characteristic of the medical device; generate an event message, the event message including the data associated with the event related to the medical device and the data associated with the identifying characteristic of the medical device; provide a response message via the UI associated with the medical device based on the data associated with the event related to the medical device, the response message including information based on output of a generation and conversational artificial intelligence (AI) platform; determine a category of the event message based on at least one of the data associated with the event related to the medical device, the data associated with the identifying characteristic of the medical device, or any combination thereof; and perform an action based on the category of the event message.

[0031] Clause 24. The computer program product of clause 23, wherein the generative and conversational AI platform includes at least one of a generative AI model, a conversational AI model, or any combination thereof.

[0032] Clause 25: The computer program product of clause 23 or 24, wherein the one or more instructions cause at least one processor to generate a response message based on receiving data associated with an event related to a medical device, wherein the one or more instructions causing the at least one processor to generate the response message further cause the at least one processor to: provide the data associated with the event related to the medical device as input to a generative AI model; determine an output of the generative AI model based on the input, wherein the output includes information associated with potential solutions to the event related to the medical device; and wherein the one or more instructions causing the at least one processor to provide the response message via a UI associated with the medical device causes the at least one processor to provide the information associated with potential solutions to the event related to the medical device.

[0033] Clause 26: A computer program product as described in any of clauses 23 to 25, wherein the one or more instructions that cause at least one processor to provide a response message via a UI associated with the medical device cause the at least one processor to provide a prompt for receiving information from a user via a UI associated with the medical device, the prompt including a question associated with an event related to the medical device.

[0034] Clause 27: A computer program product as described in any one of clauses 23 to 26, wherein the one or more instructions causing at least one processor to perform an operation cause the at least one processor to transmit the event message based on a category of the event message.

[0035] Clause 28. The computer program product of any one of clauses 23 to 27, wherein the one or more instructions for causing at least one processor to transmit the event message cause the at least one processor to: transmit the event message to a healthcare provider communication network; transmit the event message to a system for trend analysis relating to one or more events related to the medical device; transmit the event message to a communication gateway for further transmission; or any combination thereof.

[0036] Clause 29. The computer program product of any one of clauses 23 to 28, wherein the one or more instructions further cause at least one processor to capture data associated with a timestamp related to an event related to the medical device, wherein the data associated with the timestamp includes at least one of data associated with a time when the data associated with the event related to the medical device was received via a UI associated with the medical device, data associated with a time when a malfunction of the medical device occurred, or any combination thereof.

[0037] Clause 30. The computer program product of any one of clauses 23 to 29, wherein the one or more instructions further cause at least one processor to: provide a UI associated with the medical device on the mobile device.

[0038] Clause 31. The computer program product of any one of clauses 23 to 30, wherein the one or more instructions for causing at least one processor to provide a UI associated with a medical device on a mobile device cause the at least one processor to perform: providing a UI associated with a medical device on a mobile device via an application on the mobile device based on receiving an input prompt on the mobile device.

[0039] Clause 32: The computer program product of any one of clauses 23 to 31, wherein the one or more instructions for causing at least one processor to receive data associated with an event related to a medical device cause the at least one processor to receive the data associated with the event related to the medical device via a chatbot that interacts with a UI associated with the medical device.

[0040] Clause 33: The computer program product of any one of clauses 23 to 32, wherein when receiving data associated with an event related to the medical device, at least one processor is configured to: receive voice data from a user via a user interface (UI) associated with the medical device; convert the voice data into text data using a speech-to-text algorithm; and convert the text data into data associated with the event related to the medical device using a natural language processing (NLP) algorithm.

[0041] These and other features and characteristics of the present disclosure, as well as the method and function of operation of the associated elements of structure, and economies of combination of parts and manufacture, will become more apparent from a consideration of the following description and appended claims, taken in conjunction with the accompanying drawings, all of which form a part hereof, and in which like reference numerals indicate corresponding parts in the various views. It is to be expressly understood, however, that the drawings are for the purpose of illustration and description only and are not intended as a definition of the limits of the present disclosure. As used in this specification and claims, the singular forms "a," "an," and "the" include plural referents unless the context clearly dictates otherwise.

[0042] Additional advantages and details of non-limiting embodiments or aspects are described in detail below with reference to exemplary embodiments shown in the accompanying schematic drawings. [Brief explanation of the drawings]

[0043] [Figure 1]FIG. 1 is a diagram of a non-limiting embodiment of an environment in which the systems, methods, and / or products described herein may be implemented in accordance with the principles of the present disclosure. [Figure 2] FIG. 1 is a diagram of a non-limiting embodiment of a system for providing AI-based event management. [Figure 3] FIG. 3 is a diagram of a non-limiting embodiment of components of one or more systems or one or more devices of FIGS. 1 and 2. [Figure 4] 1 is a flow diagram of a non-limiting embodiment of a process for processing information associated with an event related to a medical device. [Figure 5A] FIG. 10 is a diagram of an implementation of a non-limiting embodiment or aspect of a process for processing information associated with an event related to a medical device. [Figure 5B] FIG. 10 is a diagram of an implementation of a non-limiting embodiment or aspect of a process for processing information associated with an event related to a medical device. [Figure 5C] FIG. 10 is a diagram of an implementation of a non-limiting embodiment or aspect of a process for processing information associated with an event related to a medical device. [Figure 5D] FIG. 10 is a diagram of an implementation of a non-limiting embodiment or aspect of a process for processing information associated with an event related to a medical device. DETAILED DESCRIPTION OF THE INVENTION

[0044] For purposes of the following description, the terms "end," "upper," "lower," "right," "left," "vertical," "horizontal," "top," "bottom," "transverse," "longitudinal," and their derivatives refer to the present disclosure as directions in the drawings. However, it should be understood that the present disclosure may contemplate various alternative modifications and step sequences unless expressly specified to the contrary. It should also be understood that the specific equipment and processes illustrated in the accompanying drawings and described in the following specification are merely exemplary embodiments of the present disclosure. Accordingly, specific dimensions and other physical characteristics related to the embodiments, or aspects of the embodiments, disclosed herein are not to be considered limiting, unless expressly stated.

[0045] As used herein, aspects, components, elements, structures, operations, steps, functions, instructions, and the like should not be construed as critical or essential unless explicitly stated otherwise. Also, as used herein, the articles "a" and "an" are intended to include one or more items and may be used interchangeably with "one or more" and "at least one." Furthermore, as used herein, the term "set" is intended to include one or more items (e.g., related items, unrelated items, a combination of related and unrelated items, etc.) and may be used interchangeably with "one or more" or "at least one." When only one item is intended, the term "one" or similar term is used. Also, as used herein, terms such as "has," "have," and "having" are intended to be open-ended terms. Furthermore, the phrase "based on" is intended to mean "based at least in part on," unless otherwise specified. The phrase "based on" also means "in response to" and may refer to a condition for automatically triggering a specified action of an electronic device (e.g., a processor, a computing device, etc.), as appropriately referenced herein.

[0046] As used herein, the terms “communication” and “communicating” may refer to receiving, receiving, transmitting, forwarding, providing, etc., information (e.g., data, signals, messages, instructions, commands, etc.). For one unit (e.g., a device, a system, a component of a device or system, combinations thereof, etc.) to communicate with another unit means that the one unit may receive information directly or indirectly from the other unit and / or transmit information to the other unit. This may refer to a direct or indirect connection that is wired and / or wireless in nature. Furthermore, two units may communicate with each other even if the transmitted information is modified, processed, relayed, and / or routed between the first and second units. For example, a first unit may communicate with a second unit even if the first unit passively receives information and does not actively transmit information to the second unit. As another example, a first unit may communicate with a second unit if at least one intermediate unit (e.g., a third unit located between the first unit and the second unit) processes information received from the first unit and communicates the processed information to the second unit. In a non-limiting embodiment, a message may refer to a network packet (e.g., a data packet, etc.) containing data. It will be understood that many other configurations are possible.

[0047] As used herein, the term "system" may refer to one or more computing devices or combinations of computing devices, such as, but not limited to, a processor, a server, a client device, a software application, and / or other similar components. Additionally, references to a "server" or a "processor" as used herein may refer to a previously listed server and / or processor, a different server and / or processor, and / or a combination of servers and / or processors listed as performing the previous step or function. For example, as used herein and in the claims, a first server and / or a first processor listed as performing a first step or function may refer to the same or a different server and / or processor listed as performing a second step or function.

[0048] Non-limiting embodiments of the present disclosure relate to systems, methods, and computer program products for event management, including artificial intelligence (AI)-based event management. In non-limiting embodiments or aspects, the event management system may receive data associated with an event related to a medical device via a user interface (UI) associated with the medical device, receive data associated with an identifying characteristic of the medical device, generate an event message, the event message including the data associated with the event related to the medical device and the data associated with the identifying characteristic of the medical device, provide a response message via the UI associated with the medical device based on the data associated with the event related to the medical device, the response message including information based on output of a generative and conversational artificial intelligence (AI) platform, determine a category of the event message based on at least one of the data associated with the event related to the medical device, the data associated with the identifying characteristic of the medical device, or any combination thereof, and perform an action based on the category of the event message. In non-limiting embodiments, the generative and conversational AI platform may include at least one of a generative AI model, a conversational AI model, or any combination thereof. In non-limiting embodiments, information communicated to or received from a user via the UI (e.g., in the form of feedback) may be via a visual display and / or via auditory feedback, e.g., voice or language. In some non-limiting embodiments, the medical device may include a treatment device such as a fluid injector, a therapeutic device including, but not limited to, a robotic surgical device, a radiation therapy device, etc. Additionally or alternatively, the medical device may include a diagnostic device.

[0049] In a non-limiting embodiment, the event management system may generate a response message based on receiving data associated with the event related to the medical device, and when generating the response message, the event management system may provide the data associated with the event related to the medical device as input to a generative AI model and determine an output of the generative AI model based on the input, the output including information associated with a potential resolution for the event related to the medical device. In a non-limiting embodiment, when providing the response message via a UI associated with the medical device, the event management system may provide information associated with a potential resolution for the event related to the medical device.

[0050] In a non-limiting embodiment, when providing a response message via a UI associated with the medical device, the event management system may provide a prompt to receive information from a user via a UI associated with the medical device, where the prompt includes a question associated with the event related to the medical device. In a non-limiting embodiment, when performing the action, the event management system may transmit the event message based on a category of the event message. In a non-limiting embodiment, when sending the event message, the event management system may transmit the event message to a healthcare provider communication network, transmit the event message to a system for trend analysis related to one or more events related to the medical device, transmit the event message to a communication gateway for further transmission, or any combination thereof.

[0051] In non-limiting embodiments, the event management system may capture data associated with a medical device and / or data associated with a timestamp related to an event related to the medical device, and the data associated with the timestamp may include at least one of data associated with a time when the data associated with the event related to the medical device was received via a UI associated with the medical device, data associated with a time when a medical device malfunction occurred, or any combination thereof. The data associated with the medical device may include data associated with device identification (e.g., serial number, unit identifier, etc.), data associated with device location, data associated with the device owner of record, and / or data associated with a current user identification. Data associated with medical devices may also include data associated with device usage history (e.g., many procedures, such as injections) and device service history (e.g., the amount of time the device has been in operation), as disclosed in U.S. Patent No. 10,522,250, U.S. Patent No. 11,232,862, U.S. Patent Application Publication No. 2022 / 0375586, and U.S. Patent Application Publication No. 2023 / 0364325, all owned by Bayer HealthCare LLC and incorporated herein by reference.

[0052] In a non-limiting embodiment, the event management system may provide a UI associated with the medical device on a mobile device. In a non-limiting embodiment, when providing a UI associated with the medical device on a mobile device, the event management system may provide the UI associated with the medical device on the mobile device via an application on the mobile device based on receipt of an input prompt by the mobile device. In a non-limiting embodiment, when receiving data associated with an event related to the medical device, the event management system may receive the data associated with the event related to the medical device via a chatbot interacting with a UI associated with the medical device. In a non-limiting embodiment, when receiving data associated with an event related to the medical device, the event management system may receive voice data from a user via a UI associated with the medical device, convert the voice data into text data using a speech-to-text algorithm, and convert the text data into data associated with the event related to the medical device using a natural language processing (NLP) algorithm.

[0053] In this manner, non-limiting embodiments of the present disclosure provide an event management system that can accurately identify, record, and / or transmit information associated with an event related to a medical device within a predetermined time after the event occurs. The event management system may include artificial intelligence, database systems, and / or other computer programs as methods for implementing the functionality of the event management system. The event management system may utilize natural language and / or voice control that may be integrated into a radiology diagnostic setting. Furthermore, according to some non-limiting embodiments, by integrating voice data in the form of natural conversation into the event reporting process, the event management system may reduce the time and increase the accuracy of reporting details surrounding the event. It may also convert collected information into natural language (e.g., a predetermined language) so that the event can be immediately addressed by the appropriate individuals. Furthermore, collected information may be in the native language of the speaker or the location where the procedure is being performed, and may be made available to local authorities in such language, and / or may be automatically converted into a common language for central analysis and storage and further reporting as needed. In non-limiting embodiments, the event management system may collect, report, and classify adverse events, and machine learning may be applied to look for trends between events, device types, and event frequencies. In non-limiting embodiments, the event management system may enable automated reporting, which may aid in connecting with engineering, commercial, and / or service personnel (e.g., dispatching service personnel and / or connecting with customers experiencing issues). System improvements may be achieved through data analysis and time with both engineers and medical device manufacturers. The use of natural language processing in the form of recording and / or translating voice data (e.g., conversations) may generate more accurate and timely event information. In non-limiting embodiments, the event management system may automate communication related to events and allow faster transmission of data internally to manufacturers to initiate event investigations with the most accurate details of the event.This proposed automated method of collecting, reporting, and / or classifying events on the front line could potentially replace existing time- and network resource-consuming manual processes related to scheduling, calling, interviewing, and / or surveying individuals (e.g., technicians) who are working to provide services to other patients.

[0054] Referring now to FIG. 1, FIG. 1 is a diagram of a non-limiting embodiment of an environment 100 in which the devices, systems, methods, and / or computer program products described herein may be implemented. As shown in FIG. 1, the environment 100 includes an event management system 102, a fluid infusion system 104, a workstation device 106, a user device 108, an Internet of Things (IoT) management system 110, a hospital information system 112, and a communication network 114. In a non-limiting embodiment, the event management system 102, the fluid infusion system 104, the workstation device 106, the user device 108, the IoT management system 110, and / or the hospital information system 112 may be interconnected (e.g., establish a connection to communicate) via wired connections, wireless connections, or a combination of wired and wireless connections. Any devices or systems in the environment 100 may communicate with each other, directly or indirectly, within the same or different communication network 114 as other devices or systems.

[0055] In a non-limiting embodiment, the event management system 102 may include one or more devices that may communicate with the fluid infusion system 104, the workstation device 106, the user device 108, the IoT management system 110, and / or the hospital information system 112 via a communication network 114. For example, the event management system 102 may include one or more computing devices, such as one or more computers, one or more servers (e.g., cloud servers, groups of servers, etc.), one or more desktop computers, one or more mobile devices (e.g., one or more tablets, one or more smartphones, etc.). In a non-limiting embodiment, the event management system 102 may include one or more (e.g., multiple) applications (e.g., software applications) that implement a set of functions on an external application programming interface (API) to which the event management system 102 may send data and receive data from external systems associated with the external API. In a non-limiting embodiment, the application may be supported by an application associated with the user device 108 that allows the event management system 102, which may function as a workstation (e.g., a workstation in a control room where a medical procedure is performed), to be the only device controlling other systems and / or equipment, and in such an example, the event management system 102 may provide authentication functionality.

[0056] Additionally or alternatively, the event management system 102 may generate (e.g., train, validate, retrain, etc.), store, and / or implement (e.g., manipulate, provide input, and / or provide output, etc.) one or more artificial intelligence (AI) models (e.g., machine learning models), such as generative AI models. For example, the event management system 102 may generate one or more machine learning models by fitting (e.g., validating) one or more AI models against data used for training (e.g., training data). In non-limiting embodiments or aspects, the event management system 102 may generate, store, and / or implement one or more AI models that are provided to a real-time environment (e.g., a runtime environment) used to provide inferences based on data in live situations. In non-limiting embodiments or aspects, the event management system 102 may communicate with data storage devices, which may be local or remote to the event management system 102.

[0057] In non-limiting embodiments, the event management system 102 may be able to receive information from (e.g., retrieve via pull) a data source (e.g., a medical data source), store information in the data source, transmit information to the data source, and / or retrieve information stored in the data source. In non-limiting embodiments, the event management system 102 may be a component of the fluid infusion system 104, the workstation device 106, the user device 108, the IoT management system 110, and / or the hospital information system 112.

[0058] In a non-limiting embodiment, the event management system 102 may operate based on the use of a generative and conversational AI platform. For example, the event management system 102 may include one or more AI algorithms (e.g., machine learning models) and / or one or more chatbots that may cooperate with each other to generate messages (e.g., response messages and / or event messages) associated with a medical device, such as a fluid injector, based on data associated with an event related to the medical device.

[0059] In a non-limiting embodiment, the fluid injection system 104 may include one or more devices that may communicate with the event management system 102, the workstation device 106, the user device 108, the IoT management system 110, and / or the hospital information system 112 via a communication network 114. For example, the fluid injection system 104 may include one or more computing devices, such as one or more computers, one or more servers (e.g., cloud servers, groups of servers, etc.), one or more desktop computers, one or more mobile devices (e.g., one or more tablets, one or more smartphones, etc.). In a non-limiting embodiment, the fluid injection system 104 may include one or more injection devices (e.g., one or more fluid injection devices, one or more fluid injectors). In a non-limiting embodiment, the fluid injection system 104 is configured to administer (e.g., inject, deliver, etc.) a contrast fluid containing a contrast agent to the patient and / or administer an aqueous fluid, such as saline, to the patient before, during, and / or after administration of the contrast fluid. For example, the fluid injection system 104 can be user-programmed to inject one or more prescribed doses of contrast fluid directly into the patient's bloodstream via a hypodermic needle, a syringe, or by an automated fluid injection system. In some non-limiting embodiments, the fluid injection system 104 may be configured to continuously administer an aqueous fluid to the patient through a peripheral intravenous line (PIV) or intraarterially during a cardiovascular intervention, or these aforementioned methods may be used to introduce one or more prescribed doses of contrast fluid and administer it to the patient via a catheter. In some non-limiting embodiments, the fluid injection system 104 is configured to inject a dose of contrast fluid simultaneously with and / or subsequent to the administration of a specific amount of aqueous fluid.In non-limiting embodiments, the fluid injection system 104 may be configured as a fluid injection system according to U.S. patent application Ser. No. 09 / 715,330, filed Nov. 17, 2000, issued as U.S. Patent No. 6,643,537; U.S. patent application Ser. No. 09 / 982,518, filed Oct. 18, 2001, issued as U.S. Patent No. 7,094,216; U.S. patent application Ser. No. 10 / 825,866, filed Apr. 16, 2004, issued as U.S. Patent No. 7,556,619; U.S. patent application Ser. No. 8,337,456; No. 12 / 437,011, filed May 7, 2009, which issued as U.S. Patent Application No. 12 / 476,513, filed June 2, 2009, which issued as U.S. Patent No. 8,147,464, and U.S. Patent Application No. 11 / 004,670, filed December 3, 2004, which issued as U.S. Patent No. 8,540,698, the disclosures of each of which are incorporated herein by reference in their entirety. In non-limiting embodiments, the fluid injection system 104 may include a MEDRAD® Stellant CT Injection System, a MEDRAD® Stellant Flex CT Injection System, a MEDRAD® MRXperion MR Injection System, a MEDRAD® Mark 7 Arterion Injection System, a MEDRAD® Intego PET Injection System, or a MEDRAD® Centargo CT Injection System, all of which are provided by Bayer Healthcare LLC.

[0060] In a non-limiting embodiment, the workstation device 106 may include one or more devices that may communicate with the event management system 102, the fluid injection system 104, the user device 108, the IoT management system 110, and / or the hospital information system 112 via the communications network 114. For example, the workstation device 106 may include computing devices such as one or more computers, including desktop computers, laptops, tablets, etc. At least a portion of the processes executed on the workstation device 106 may be executed on a remote server (e.g., a cloud computing server). In a non-limiting embodiment, the workstation device 106 may provide a user interface for controlling the operation of the fluid injection system 104, including generating instructions for and / or providing instructions to the fluid injection system 104. Additionally or alternatively, the workstation device 106 may display operating parameters of the fluid injection system 104 during operation (e.g., during real-time operation). In a non-limiting embodiment, the workstation device 106 may provide interconnectivity between the fluid injection system 104 and other devices or systems, such as a scanner device (e.g., a magnetic resonance imaging (MRI) scanner, a computed tomography (CT) scanner, a CT coronary angiography system, a positron emission tomography (PET) scanner, a single photon emission computed tomography (SPECT) scanner, not shown). In a non-limiting embodiment, the workstation device 106 may include a Certegra® workstation offered by Bayer.In non-limiting embodiments, the workstation device 106 may include a display unit (e.g., display device, display screen, etc.), such as a computer monitor, touch screen, heads-up display, etc., which may be used to display a user interface (e.g., a graphical user interface (GUI) of a software application) through which a user may interact with the workstation device 106 to view parameters and / or control operation of the fluid injection system 104. In some non-limiting embodiments, the workstation device 106 may include a speaker for outputting tones or sounds related to operation of the device and / or for outputting language to communicate with the user, e.g., to affirm or repeat input provided by the user. For example, a user of the workstation device 106 may provide input to the workstation device 106 using one or more hardware or software components of the workstation device 106 related to a touch screen, a mouse, a trackpad, a keyboard, a stylus, a gesture-detecting camera, a microphone for receiving voice commands, etc.

[0061] In a non-limiting embodiment, the user equipment 108 may include one or more devices that may communicate with the event management system 102, the fluid injection system 104, the workstation device 106, the IoT management system 110, and / or the hospital information system 112 via the communications network 114. For example, the user equipment 108 may include computing devices such as one or more computers, including desktop computers, workstation devices, mobile devices such as laptops, tablets, smartphones, etc. In a non-limiting embodiment, at least a portion of the processes executed on the user equipment 108 may be executed on a remote server (e.g., a cloud computing server, a server hosting a software application, etc.). In a non-limiting embodiment, the user equipment 108 may provide a user interface for receiving data associated with events related to medical devices. Additionally or alternatively, the user equipment 108 may display operating parameters of the event management system 102 during operation (e.g., during real-time operation) of the event management system 102. In non-limiting embodiments, user equipment 108 may provide interconnectivity between event management system 102 and other devices or systems, such as fluid injection system 104, workstation device 106, IoT management system 110, and / or hospital information system 112, and / or other systems or devices (e.g., medical imaging systems). In non-limiting embodiments, user equipment 108 may include a display unit (e.g., display device, display screen, etc.), such as a computer monitor, touch screen, heads-up display, etc., that may be used to display a user interface (e.g., a graphical user interface (GUI) of a software application), through which a user may interact with user equipment 108 to view parameters of and / or control the operation of event management system 102, fluid injection system 104, workstation device 106, IoT management system 110, and / or hospital information system 112.For example, a user of user equipment 108 may provide input to user equipment 108 using one or more hardware or software components of user equipment 108 related to a touch screen, a mouse, a trackpad, a keyboard, a stylus, a gesture-detecting camera, a microphone for receiving voice commands, etc.

[0062] In a non-limiting embodiment, the IoT management system 110 may include one or more devices that may communicate with the event management system 102, the fluid infusion system 104, the workstation device 106, the user device 108, and / or the hospital information system 112 via the communications network 114. For example, the IoT management system 110 may include one or more computing devices, such as one or more computers, one or more servers (e.g., cloud servers, groups of servers, etc.), one or more desktop computers, one or more mobile devices (e.g., one or more tablets, one or more smartphones, etc.). In a non-limiting embodiment, the IoT management system 110 may include one or more (e.g., multiple) applications (e.g., software applications) that implement a set of functions on an external API to which the IoT management system 110 may send data and receive data from external systems associated with the external API. In a non-limiting embodiment, the applications may be supported by applications associated with the user device 108 that enable the IoT management system 110 to be a device that controls other systems and / or devices; in such an example, the IoT management system 110 may provide information retrieval functionality. In a non-limiting embodiment, the IoT management system 110 may receive data from and / or transmit data to one or more connected devices (e.g., medical devices), and the data may include, but is not limited to, protocols, software updates, and / or user access permissions associated with the connected devices. Other uses may include remote asset monitoring, remote maintenance and / or servicing, predictive maintenance, asset management, billing, and / or optimized equipment effectiveness. One example of an IoT management system 110 may be ThingWorx by PTC Inc. of Boston, Massachusetts.

[0063] In a non-limiting embodiment, the hospital information system 112 may include one or more devices that may communicate with the event management system 102, the fluid injection system 104, the workstation devices 106, the user devices 108, and / or the IoT management system 110 via a communication network 114. For example, the hospital information system 112 may include one or more computing devices, such as one or more desktop computers, one or more mobile devices, one or more servers, etc. In a non-limiting embodiment, the hospital information system 112 may include one or more subsystems, such as a patient procedure tracking system (e.g., a system that operates a modality worklist, a system that provides patient demographic information for fluid injection procedures and / or medical imaging procedures, etc.), a fluid injection management system, an image archiving and communication system (e.g., a Picture Archiving and Communication System (PACS)), a radiology information system, and / or a radiology analysis system (e.g., Radimetrics® Enterprise Application, marketed and sold by Bayer HealthCare LLC). In a non-limiting embodiment, the hospital information system 112 may include one or more databases that store patient records (e.g., data files or data objects containing patient data) that may be accessed (e.g., have read and / or write permissions) by equipment or systems in the environment 100, such as the event management system 102 and / or the workstation equipment 106. In a non-limiting embodiment, the communications network 114 may include one or more wired and / or wireless networks.For example, the communication network 114 may include a cellular network (e.g., a Long Term Evolution (LTE) network, a third generation (3G) network, a fourth generation (4G) network, a fifth generation (5G) network, a sixth generation (6G) network, a code division multiple access (CDMA) network, etc.), a public land mobile network (PLMN), a local area network (LAN), a wide area network (WAN), a metropolitan area network (MAN), a telephone network (e.g., a public switched telephone network (PSTN)), a private network, an ad hoc network, an intranet, the Internet, an optical fiber-based network, a cloud computing network, a short-range wireless communication network (e.g., a Bluetooth network, a near field communication (NFC) network, etc.), etc., and / or a combination of these or other types of networks.

[0064] The number and arrangement of systems and / or devices shown in Figure 1 are provided as an example. Additional, fewer, different, or differently arranged systems and / or devices may be present. Furthermore, two or more systems and / or devices shown in Figure 1 may be implemented within a single system or device, or a single system or device shown in Figure 1 may be implemented as multiple distributed systems or devices. Additionally or alternatively, a set of systems or devices (e.g., one or more systems, one or more devices) of environment 100 may perform one or more functions that are described as being performed by another set of systems or another set of devices of environment 100.

[0065] 2, which is a diagram of a non-limiting embodiment of a system 200 for processing information associated with events related to medical devices. In a non-limiting embodiment, one or more of the functions described herein in connection with system 200 may be performed (e.g., fully, partially, etc.) by event management system 102. In a non-limiting embodiment, one or more of the functions described in connection with system 200 may be performed (e.g., fully, partially, etc.) by another device or group of devices separate from and / or including event management system 102, such as fluid infusion system 204, workstation device 206, user device 208, and / or IoT management system 110.

[0066] 2 , system 200 includes event management system 102, fluid injection system 204 including fluid injector 204A, workstation device 206 including display unit 206A, user device 208, gateway device 210, and IoT management system 110. In a non-limiting embodiment, event management system 102 may interconnect (e.g., establish a connection to communicate with) fluid injection system 204, workstation device 206 including display unit 206A, user device 208, gateway device 210, and / or IoT management system 110 via a wired connection, a wireless connection, or a combination of wired and wireless connections. In a non-limiting embodiment, fluid injection system 204 may be the same as or similar to fluid injection system 104. In a non-limiting embodiment, workstation device 206 may be the same as or similar to workstation device 106. In a non-limiting embodiment, user device 208 may be the same as or similar to user device 108. In non-limiting embodiments, healthcare provider communication network 212-1 and / or communication network 212-2 may be the same as or similar to communication network 114. In non-limiting embodiments, healthcare provider communication network 212-1 may communicate information according to a communication protocol appropriate for the setting (e.g., a Health Level Seven (HL7) standard communication protocol, a network protocol (e.g., HTTP, HTTPS, etc.), a Digital Imaging and Communications in Medicine (DICOM) communication protocol, etc.). In non-limiting embodiments, healthcare provider communication network 212-1 may include a hospital communication network and / or a healthcare enterprise communication network.

[0067] In a non-limiting embodiment, the event management system 102 may include multiple applications, each of which may be associated with an API (e.g., a first API associated with a first application, a second API associated with a second application, a third API associated with a third application, etc.) associated with the respective application through which other systems and / or devices may interface (e.g., communicate, establish a communications interface, etc.) with the event management system 102 and / or through which the event management system 102 may interface with other systems and / or devices (e.g., individual subsystems of the hospital information system 112) via the healthcare provider communications network 212-1 and the communications network 212-2. In a non-limiting embodiment, the event management system 102 may provide a user interface through which a user may access, receive, store, and / or transmit information (e.g., via an application that includes a user interface, such as a web-based user interface). For example, the event management system 102 may provide a user interface that is displayed on the fluid injection system 204, the user device 208, and / or the workstation device 206 (eg, the display unit 206A of the workstation device 206).

[0068] 2, the workstation device 206 may include a display unit 206A. In non-limiting embodiments, the display unit 206A may display a user interface (e.g., a web-based user interface) provided by the event management system 102. In some non-limiting embodiments, the display unit 206A may include a computing device such as a smart display unit, a portable computer such as a tablet or laptop, or the like. In some non-limiting embodiments, the display unit 206A may include a touch screen for receiving input by a user. In non-limiting embodiments, the display unit 206A may include a display device (e.g., a monitor, screen, etc. for displaying visual information) or a speaker for communicating information through sound or language.

[0069] In a non-limiting embodiment, gateway device 210 may include one or more devices (e.g., one or more communication gateways) that may communicate with event management system 102, fluid infusion system 204, workstation device 206, user device 208, and / or IoT management system 110 via healthcare provider communication network 212-1 and / or communication network 212-2. For example, gateway device 210 may include devices such as a telecommunications gateway (e.g., a network gateway), a universal gateway, etc. Additionally or alternatively, gateway device 210 may include one or more computing devices such as one or more desktop computers, one or more mobile devices (e.g., one or more tablets, one or more smartphones, etc.), one or more servers, etc. In a non-limiting embodiment, gateway device 210 may include one or more (e.g., multiple) applications (e.g., software applications) that implement a set of functions on an external application programming interface (API) through which fluid infusion system 204, workstation device 206, and / or user device 208 may send data to and receive data from external systems associated with the external APIs. In one example, gateway device 210 may provide the ability to download applications, such as Bayer S / W applications, to gateway device 210 (e.g., a mobile device of gateway device 210, providing carry-on operation for personal devices). In some non-limiting embodiments, the applications may be supported by an application associated with fluid injection system 204, allowing gateway device 210 (e.g., a mobile device of gateway device 210), which may function as a control room display, to be the only device controlling fluid injection system 204; in such an example, gateway device 210 may provide authentication functionality.In some non-limiting embodiments, gateway device 210 may access a network resource, such as a uniform resource locator (URL), to determine applications (e.g., application services) available to gateway device 210, and gateway device 210 and / or fluid infusion system 104 may download one or more applications via gateway device 210. Further details related to gateway device 210 and associated systems and / or equipment are disclosed in International Patent Application No. PCT / US2021 / 040800, filed July 8, 2021, published as WO 2022 / 015560 on January 20, 2022, the disclosure of which is incorporated herein by reference in its entirety.

[0070] In a non-limiting embodiment, the event management system 102 may communicate with the fluid injection system 204, the workstation device 206, and / or the user device 208 via a healthcare provider communication network 212-1 and a communication network 212-2 such that the fluid injection system 204, the workstation device 206, and / or the user device 208 may receive the data based on an API call to the event management system 102. In a non-limiting embodiment, the event management system 102 may transmit data associated with informatics (e.g., data associated with identifying characteristics of a medical device received from the IoT management system 110) to the fluid injection system 204 via a communication network (e.g., healthcare provider communication network 212-1 and communication network 212-2). For example, the event management system 102 may transmit data associated with received informatics from the IoT management system 110 to the fluid injection system 204 via a communication network based on an API call from the fluid injection system 204.

[0071] 3, which is a diagram of example components of device 300. Device 300 may correspond to one or more of event management system 102, fluid infusion system 104, fluid infusion system 204, workstation device 106, workstation device 206, user device 108, user device 208, IoT management system 110, gateway device 210, and / or hospital information system 112. In a non-limiting embodiment, event management system 102, fluid infusion system 104, fluid infusion system 204, workstation device 106, workstation device 206, user device 108, user device 208, IoT management system 110, gateway device 210, and / or hospital information system 112 may include at least one device 300 and / or at least one component of device 300.

[0072] 3, device 300 may include a bus 302, a processor 304, a memory 306, a storage component 308, an input component 310, an output component 312, and a communication interface 314. Bus 302 may include components that enable communication between the components of device 300. In a non-limiting embodiment, processor 304 may be implemented in hardware, firmware, or a combination of hardware and software. For example, processor 304 may include a processor (e.g., a central processing unit (CPU), a graphics processing unit (GPU), an accelerated processing unit (APU), etc.), a microprocessor, a digital signal processor (DSP), and / or any processing component that can be programmed to perform a function (e.g., a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), etc.). The memory 306 may include random access memory (RAM), read-only memory (ROM), and / or another type of dynamic or static storage device (e.g., flash memory, magnetic memory, optical memory, etc.) that stores information and / or instructions for use by the processor 304.

[0073] Storage component 308 may store information and / or software related to the operation and use of device 300. For example, storage component 308 may include a hard disk (e.g., a magnetic disk, optical disk, magneto-optical disk, solid-state disk, etc.), a compact disk (CD), a digital versatile disk (DVD), a floppy disk, a cartridge, a magnetic tape, and / or another type of computer-readable medium along with a corresponding drive.

[0074] Input components 310 may include components through which device 300 may receive information, such as via user input (e.g., a touchscreen display, a keyboard, a keypad, a mouse, a button, a switch, a microphone, etc.). Additionally or alternatively, input components 310 may include sensors that detect information (e.g., a global positioning system (GPS) component, an accelerometer, a gyroscope, an actuator, etc.). Output components 312 may include components that provide output information from device 300 (e.g., a display, a speaker, one or more light-emitting diodes (LEDs), etc.).

[0075] The communication interface 314 may include transceiver-like components (e.g., a transceiver, a separate receiver and transmitter, etc.) that allow the device 300 to communicate with other devices via a wired connection, a wireless connection, a combination of wired and wireless connections, etc. The communication interface 314 may enable the device 300 to receive information from another device and / or provide information to another device. For example, the communication interface 314 may include an Ethernet interface, an optical interface, a coaxial interface, an infrared interface, a radio frequency (RF) interface, a universal serial bus (USB) interface, a Wi-Fi interface, a cellular network interface, etc.

[0076] The device 300 may perform one or more processes described herein. The device 300 may perform these processes based on the processor 304 executing software instructions stored by a computer-readable medium, such as the memory 306 and / or the storage component 308. A computer-readable medium (e.g., a non-transitory computer-readable medium) is defined herein as a non-transitory memory device. A memory device may include memory space located within a single physical storage device or memory space spread across multiple physical storage devices.

[0077] Software instructions may be read into memory 306 and / or storage component 308 from another computer-readable medium or from another device via communications interface 314. When executed, the software instructions stored in memory 306 and / or storage component 308 may cause processor 304 to perform one or more processes described herein. Additionally, or alternatively, hardwired circuitry may be used in place of or in combination with software instructions to implement one or more processes described herein. Thus, the embodiments described herein are not limited to any specific combination of hardware circuitry and software.

[0078] The number and arrangement of components shown in Figure 3 are provided as an example. In non-limiting embodiments, device 300 may include additional, fewer, different, or differently arranged components than those shown in Figure 3. Additionally or alternatively, a set of components (e.g., one or more components) of device 300 may perform one or more functions that are described as being performed by another set of components of device 300.

[0079] 4, which is a flow diagram of a non-limiting embodiment of a process 400 for processing information associated with an event related to a medical device. In a non-limiting embodiment, one or more of the steps of process 400 are performed (e.g., fully, partially, etc.) by event management system 102. In a non-limiting embodiment, one or more of the steps of process 400 are performed (e.g., fully, partially, etc.) by another device or group of devices separate from or including event management system 102, such as a fluid infusion system (e.g., fluid infusion system 104, such as one or more devices of fluid infusion system 104), a workstation device (e.g., workstation device 106), a user device (e.g., user device 108), an IoT management system (e.g., IoT management system 110, such as one or more devices of IoT management system 110), and / or a hospital information system (e.g., hospital information system 112, such as one or more subsystems of hospital information system 112). According to a non-limiting embodiment, although FIG. 4 is described in the context of events relating to medical equipment, the steps of process 400 may be performed in connection with other types of medical equipment, such as medical imaging equipment, surgical equipment, health monitoring equipment, etc.

[0080] 4, in step 402, process 400 may include receiving data associated with an event related to a medical device. For example, event management system 102 may receive data associated with an event related to a medical device of fluid infusion system 204. In a non-limiting embodiment, event management system 102 may receive the data via a user interface (UI) associated with a medical device of fluid infusion system 204. For example, event management system 102 may receive the data via a UI displayed on a display unit 206A of workstation device 206, displayed on a user device 208, displayed on a display screen of fluid infusion system 204, etc. In a non-limiting embodiment, the UI may be the UI of a software application (e.g., a mobile application, a client-side application of a web-based software application, etc.) located on workstation device 206, user device 208, and / or fluid infusion system 204.

[0081] In a non-limiting embodiment, the event management system 102 may receive data associated with events related to medical devices via a generative and conversational AI platform. For example, the event management system 102 may receive data via a generative AI model, a chatbot, or any combination thereof. In a non-limiting embodiment, the event management system 102 may receive data via a chatbot and / or a generative AI model interacting with a UI associated with the medical device. For example, a user may provide input to a chatbot and / or a generative AI model via a UI on the user device 108, and the event management system 102 may receive the data as output of the chatbot and / or the generative AI model. In a non-limiting embodiment, the event management system 102 may receive voice data from a user via a UI associated with the medical device, convert the voice data to text using a speech-to-text algorithm, and convert the text data to data associated with events related to the medical device using a natural language processing (NLP) algorithm. In a non-limiting embodiment, the event management system 102 may receive data associated with events related to the medical device via email, text, and / or as data from an interaction with a UI (e.g., selecting a graphical user element in the UI, pressing a button, etc.).

[0082] In a non-limiting embodiment, the event management system 102 may receive data associated with an identifying characteristic of a medical device of the fluid injection system 204. For example, the event management system 102 may receive data associated with an identifying characteristic of a medical device from the IoT management system 110. In a non-limiting embodiment, the IoT management system 110 may provide the data associated with an identifying characteristic of a medical device based on receiving a notification of an event related to the medical device. For example, the IoT management system 110 may provide the data associated with an identifying characteristic of a medical device based on receiving a notification from the event management system 102, the fluid injection system 204, the workstation device 206, and / or the user device 208 via the healthcare provider communication network 212-1 and / or the communication network 212-2.

[0083] In a non-limiting embodiment, the event management system 102 may provide a UI associated with a medical device based on receipt of an input prompt (e.g., a voice prompt) by the mobile device. For example, the event management system 102 may provide a UI associated with a medical device (e.g., a fluid injector on the fluid injection system 204), the workstation device 206, and / or the user device 208 via an application (e.g., a software application) on the fluid injection system 204, the workstation device 206, and / or the user device 208 based on receipt of the input prompt. In a non-limiting embodiment, the event management system 102 may receive data associated with an event related to a medical device (e.g., a fluid injector) before, during, and / or after a fluid injection procedure related to the medical device.

[0084] In a non-limiting embodiment, the event management system 102 may provide an input prompt for receiving information from a user via a UI associated with a medical device. In a non-limiting embodiment, the input prompt includes one or more questions associated with the medical device event. For example, the input prompt may include a question requesting a description of the medical device event. Additionally or alternatively, the input prompt may include a series of consecutive questions (e.g., "YES" or "NO") associated with a type of medical device event. In a non-limiting embodiment, the event management system 102 may provide one or more questions requesting a description of the medical device event, where the one or more questions are pre-scripted or generated by a generative and conversational AI platform based on data associated with the medical device event received from a user (e.g., a user of the fluid infusion system 204, the workstation device 206, and / or the user device 208).

[0085] In a non-limiting embodiment, the event management system 102 may provide one or more response prompts based on receiving initial data associated with an event related to a medical device. For example, the event management system 102 may receive initial data associated with an event related to a medical device, and the event management system 102 may provide one or more response prompts requesting additional data associated with the event related to the medical device (e.g., data for the event message in addition to the initial data associated with the event related to the medical device).

[0086] In a non-limiting embodiment, the event management system 102 may receive data associated with an event related to a medical device via healthcare provider communication network 212-1 and / or communication network 212-2. For example, a user may provide data associated with an event related to a medical device to a UI that is displayed on display unit 206A of workstation device 206, displayed on user device 208, and / or displayed on a display screen of fluid injection system 204, and the data may be provided to gateway device 210. Gateway device 210 may transmit the data to the event management system 102 via healthcare provider communication network 212-1 and communication network 212-2.

[0087] In non-limiting embodiments, the events may include incidents related to adverse events of a medical device (e.g., a fluid injection procedure related to a patient safety event, including extravasation, contrast overload, air injection, particulates in the fluid path, electrical shock, and / or any other safety-related event). Additionally or alternatively, the events may include events related to medical device malfunctions and / or safety issues, problems with pharmaceutical products (e.g., contrast agents for fluid injectors), and / or events related to product quality issues. In non-limiting embodiments, the product quality issues may relate to the need for medical device maintenance, product replacement or replacement of product components, clinical applications of the medical device, or customer complaints regarding the system (e.g., a fluid injector including associated disposables).

[0088] In non-limiting embodiments, the data associated with the medical device event may include an indication of a type of medical device event. For example, the data associated with the medical device event may include an indication of an event related to an adverse event of the medical device, an indication of an event related to a drug problem with the medical device, and / or an indication of an event related to a product quality problem. Additionally or alternatively, the data associated with the medical device event may include data associated with a timestamp associated with the medical device event. In non-limiting embodiments, the data associated with the timestamp may include data associated with a time when the data associated with the medical device event was received (e.g., from a user via a UI associated with the medical device) and / or data associated with a time when the medical device problem (e.g., a malfunction) occurred. In non-limiting embodiments, the event management system 102 may capture data associated with a timestamp associated with the medical device event.

[0089] Additionally or alternatively, the data associated with the event related to the medical device may include product details related to the event related to the medical device, including injector model identification information, the serial number of the medical device, the lot number of disposables used in the fluid injection procedure, the amount (e.g., volume) of contrast agent used in the fluid injection procedure, and / or the amount of contrast agent and / or cleaning agent (e.g., saline) delivered to the patient in the fluid injection procedure.

[0090] Additionally or alternatively, data associated with the medical device event may include test details associated with the medical device event, such as injection parameters, including the size of the catheter used in the fluid injection procedure, the timing, flow rate and / or volume of the fluid used in the fluid injection procedure, the pressure settings used in the fluid injection procedure, the components in the fluid pathway used in the fluid injection procedure, the type of scan performed in connection with the fluid injection procedure, whether an injection protocol personalized software program was used in the fluid injection procedure, the location where the fluid injection procedure was initiated, an indication of whether the injection site was monitored (e.g., visually monitored) during the fluid injection procedure, an indication of whether a pressure monitor change occurred during the fluid injection procedure, and / or the type of scan being performed in connection with the fluid injection procedure.

[0091] Additionally or alternatively, the data associated with the medical device event may include details of the extravascular leak related to the medical device event, such as when the extravascular leak occurred during the fluid injection procedure (e.g., at the beginning, middle, or end), the location of the affected area on the patient's body where the extravascular leak occurred, the amount of fluid that extravasated for the extravascular leak, the amount of fluid or tissue infiltrate that extravasated for the extravascular leak, the type of fluid that extravasated for the extravascular leak (e.g., contrast and / or saline), the pressure setting during the fluid injection procedure where the extravascular leak occurred, and / or an indication of whether scanner bolus detection software was used during the fluid injection procedure where the extravascular leak occurred.

[0092] Additionally or alternatively, the data associated with the medical device event may include details of the air injection related to the medical device event, such as the location of the air within the patient's body (e.g., coronary vessels, pulmonary artery trunk or bifurcation, etc.), the amount of air (e.g., small amount, 5 ml, 10 ml, amount above a threshold amount, etc.), an indication of whether a prime tube was used, and / or an indication of whether a wet contact connection was used when preparing the disposable.

[0093] Additionally or alternatively, data associated with a medical device event may include details of the fluid path particulates associated with the medical device event, such as an indication of whether a particular type of disposable was used, an indication of when the particulates were discovered (e.g., an indication upon opening the kit, an indication during use, an indication that procedures were followed, etc.), and / or the lot number of one or more affected disposables.

[0094] Additionally or alternatively, the data associated with the medical device event may include details of the patient outcome related to the medical device event, such as the patient's age, the patient's gender, the patient's admitting diagnosis, the patient's pre-existing conditions, an indication of whether the patient required any type of medical treatment (e.g., intervention) during and / or after the event, an indication of the type of medical treatment provided to the patient during and / or after the event, if treatment was provided, an indication of the patient's condition during and / or after the event, if treatment was provided or not provided, and / or an indication of the reason as to why treatment was ordered or performed (e.g., an indication of what the physician wanted to rule out).

[0095] Additionally or alternatively, data associated with a medical device event may include details of the complaint related to the medical device event, such as an image of the product, an image of the product defect, an identification number of the product and / or part of the product that had the defect, and / or a description of the product malfunction (e.g., breakdown), such as the manner of the malfunction (e.g., the product was dropped), an indication of when the product was last repaired, an indication of who serviced the product when it was last repaired, and / or an indication of whether there were any notable issues with the product prior to the malfunction (e.g., noticeable defects, difficulty in operation, etc.). Additionally or alternatively, data associated with a medical device event may include details of the product outcome, such as an indication of the result of the product malfunction, a description of an adverse outcome based on the product malfunction, an indication of whether the patient required any type of medical treatment as a result of the product malfunction, an indication of a safety suspicion related to the product, a description of an adverse outcome based on the product safety suspicion, and / or an indication of whether the patient required any type of medical treatment as a result of the product safety suspicion.

[0096] 4, in step 404, the process 400 may include generating an event message. For example, the event management system 102 may generate the event message based on data associated with the event related to the medical device. Additionally or alternatively, the event management system 102 may generate the event message based on data associated with an identifying characteristic of the medical device. In a non-limiting embodiment, the event message may include data associated with the event related to the medical device and / or data associated with an identifying characteristic of the medical device.

[0097] 4, in step 406, process 400 may include providing a response message including information based on the output of the generative and conversational artificial intelligence (AI) platform. For example, the event management system 102 may provide one or more response messages including information based on the output of the generative and conversational AI platform. In a non-limiting embodiment, the generative and conversational AI platform includes at least one of a generative AI model, a chatbot, or any combination thereof.

[0098] In a non-limiting embodiment, the one or more response messages may include an output of the generative and conversational AI platform. In a non-limiting embodiment, the one or more response messages may include information associated with the output of the generative and conversational AI platform, such as a question requesting data associated with an event related to a medical device of the fluid infusion system 204. In a non-limiting embodiment, the event management system 102 may provide a response message via a UI associated with the medical device (e.g., a UI displayed on the fluid infusion system 204, the workstation device 206, and / or the user device 208) based on the data associated with the event related to the medical device.

[0099] In a non-limiting embodiment, the event management system 102 may generate a response message based on receiving data associated with an event related to a medical device. In one example, the event management system 102 may provide the data associated with the event related to the medical device as input to a generative AI model, and the event management system 102 may determine an output of the generative AI model based on the input. The output may include information associated with a potential resolution of the event related to the medical device. In a non-limiting embodiment, the event management system 102 may provide information associated with a potential resolution of the event related to the medical device. For example, the event management system 102 may provide information associated with a potential resolution of the event related to the medical device to the fluid infusion system 204, the workstation device 206, and / or the user device 208 (e.g., via a UI associated with the medical device).

[0100] In a non-limiting embodiment, the event management system 102 may provide one or more response messages based on receipt of data associated with the event related to the medical device. In a non-limiting embodiment, the one or more response messages may include one or more response questions (e.g., “YES” or “NO”) that determine an action to be taken by the event management system 102. In one example, the response question may include a question about whether a system checkout is desired. If an affirmative response is received, the event management system 102 may determine to transmit the event message to a customer complaint system and / or a product service system. In one example, the response question may include a question about whether an appointment is desired. If an affirmative response is received, the event management system 102 may determine to transmit the event message to a customer complaint system and / or a clinical application system. In a non-limiting embodiment, the response question may include one or more questions generated by a generative and conversational AI platform based on data associated with the event related to the medical device. In a non-limiting embodiment, the response question may be based on the output of the generative and conversational AI platform.

[0101] As shown in FIG. 4 , in step 408, process 400 may include determining a category of the event message. In a non-limiting embodiment, the event management system 102 may determine the category of the event message based on at least one of data associated with the event related to the medical device, data associated with an identifying characteristic of the medical device, or any combination thereof. In a non-limiting embodiment, the category of the event message may be a category associated with a system to which the event management system 102 may transmit the event message. In a non-limiting embodiment, the category may be a category associated with a complaint system, a service system (e.g., a service scheduling system), a hospital information system (e.g., the hospital information system 112), a regulatory reporting system, etc. In a non-limiting embodiment, the event management system 102 may determine the category of the event message from multiple categories of event messages.

[0102] In a non-limiting embodiment, the event management system 102 may determine a category for the event message based on the output of a machine learning model. For example, the event management system 102 may provide data associated with an event related to a medical device and / or data associated with an identifying characteristic of the medical device as input to the machine learning model, and the machine learning model may provide an output based on the input, where the output includes a prediction of a category for the event message.

[0103] In a non-limiting embodiment, the event management system 102 may determine a category for the event message based on an indication included in data associated with the event related to the medical device (e.g., an indication associated with the type of event). For example, the event management system 102 may receive data associated with the event related to the medical device, and the event management system 102 may determine an indication of the category of the event message included in the data associated with the event related to the medical device. The event management system 102 may determine the category based on the indication of the category of the event message.

[0104] Referring again to FIG. 4 , process 400 is described above as including, at step 408, determining a category of the event message. The category may be further described, in non-limiting embodiments, as a category associated with a complaint system, a service system (e.g., a service scheduling system), a hospital information system (e.g., hospital information system 112), a regulatory reporting system, etc. Examples of such complaint systems may include a complaint system associated with a manufacturer of a medical device, such as a fluid infuser (e.g., Bayer Medical Care Inc.), a complaint system associated with a regulatory agency (e.g., the United States Food and Drug Administration (USFDA), the European Medicines Agency (EMA), the Japanese Pharmaceuticals and Medical Devices Agency (PhMDA), or the UK Medicines and Healthcare products Regulatory Agency (MHRA)), etc. Examples of such service systems may include a service system associated with a manufacturer of a medical device, such as a fluid infuser (e.g., Bayer Medical Care, Inc.'s Technical Assistance Center (TAC)), a service system associated with a third party contracted with the medical device manufacturer, etc. Examples of such regulatory reporting systems may include the USFDA's Adverse Event Reporting System (FAERS), the European Union's (EU) Medical Device Vigilance System, the EMA's EudraVigilance System, and the like.

[0105] 4, in step 410, process 400 may include performing an action based on the category of the event message. For example, event management system 102 may perform an action based on the category of the event message. In a non-limiting embodiment, event management system 102 transmits, stores (e.g., records), and / or analyzes the event message based on the category of the event message.

[0106] In non-limiting embodiments, the event management system 102 may transmit the event message to a healthcare provider communication network, a hospital information system (e.g., hospital information system 112), a system for trend analysis related to one or more events related to medical devices, a system associated with a regulatory agency, a communication gateway for further transmission, etc.

[0107] 5A-5D, which are diagrams of non-limiting embodiments or aspects of an implementation 500 relating to a process (e.g., process 400) for event management of a medical device, such as a fluid infuser 504. In some non-limiting embodiments, fluid infuser 504 may be the same as or similar to fluid infuser system 104, fluid infuser system 204, and / or fluid infuser 204A. In non-limiting embodiments or aspects, one or more of the steps of the process may be performed (e.g., completely, partially, etc.) by event management system 102 (e.g., by one or more devices of event management system 102). In non-limiting embodiments or aspects, one or more of the steps of the process may be performed (e.g., completely, partially, etc.) by another device or group of devices separate from or including the event management system 102, such as a fluid injection system (e.g., one or more devices of fluid injection system 104, such as fluid injection system 104), a workstation device (e.g., workstation device 106), a user device (e.g., user device 108), an IoT management system (e.g., one or more devices of IoT management system 110, such as IoT management system 110), and / or a hospital information system (e.g., one or more subsystems of hospital information system 112, such as hospital information system 112).

[0108] 5A , the event management system 102 may receive data associated with an event related to the fluid injector 504 and data associated with an identifying characteristic of the fluid injector 504. For example, the event management system 102 may receive data associated with an event related to the fluid injector 504 from the user device 108, or the event management system 102 may receive data associated with an identifying characteristic of the fluid injector 504 from the IoT management system 110. In a non-limiting embodiment, the event management system 102 may receive the data associated with the event related to the fluid injector 504 via a UI associated with the fluid injector 504 displayed on the user device 108. In a non-limiting embodiment, the IoT management system 110 may provide the data associated with the identifying characteristic of the fluid injector 504 to the event management system 102 based on receiving notification of an event related to the fluid injector 504.

[0109] 5B by reference numeral 510, the event management system 102 may generate an event message. In a non-limiting embodiment, the event management system 102 may generate the event message based on data associated with the event related to the fluid injector 504 and data associated with an identifying characteristic of the fluid injector 504. In a non-limiting embodiment, the event message may include data associated with the event related to the fluid injector 504 and data associated with an identifying characteristic of the fluid injector 504.

[0110] The event management system 102 may provide a response message, as indicated by reference numeral 515 in FIG. 5C . In a non-limiting embodiment, the event management system 102 may provide the response message via a UI displayed on the user device 108. In a non-limiting embodiment, the response message may include information based on the output of the generative and conversational AI platform. In one example, the event management system 102 may generate a response message that includes information based on the output of the generative and conversational AI platform. In a non-limiting embodiment, the generative and conversational AI platform includes at least one of a generative AI model, a machine learning model, a conversational AI model such as a chatbot, or any combination thereof.

[0111] 5D , the event management system 102 may determine a category for the event message. In a non-limiting embodiment, the event management system 102 may determine the category for the event message based on at least one of data associated with the event related to the fluid infuser 504, data associated with an identifying characteristic of the fluid infuser 504, or any combination thereof. In a non-limiting embodiment, the category of the event message may be a category associated with a remote system to which the event management system 102 may transmit the event message. In a non-limiting embodiment, the event management system 102 may determine the category for the event message from multiple categories of event messages.

[0112] As indicated by reference numeral 525 in FIG. 5D , the event management system 102 may perform an action based on the category of the event message. In a non-limiting embodiment, the event management system 102 may determine one remote system of a plurality of remote systems to transmit the event message to based on the category of the event message. In a non-limiting embodiment, the event management system 102 may transmit the event message to a first remote system (e.g., remote system #1) based on the category of the event message. Examples of such remote systems may include a remote service system associated with a manufacturer of a medical device, such as a fluid infuser (e.g., Bayer Medical Care, Inc.'s VirtualCARE® Remote Support, Bayer Medical Care, Inc.'s Technical Assistance Center (TAC)), a remote service system associated with a third party under contract with the medical device manufacturer, etc.

[0113] While the above-described systems, methods, and computer program products have been described in detail for purposes of illustration based on what are currently considered to be the most practical and preferred embodiments, it should be understood that such detail is for that purpose only, and that the disclosure is not limited to the described embodiments or aspects, but on the contrary, is intended to cover modifications and equivalent arrangements within the spirit and scope of the appended claims. For example, it should be understood that the disclosure contemplates that at least one feature of any embodiment or aspect may be combined, to the extent possible, with at least one feature of any other embodiment.

[0114] The following non-limiting example scenarios use the event management system (eg, event management system 102) described herein.

[0115] Scenario 1 - Service Issue. During a patient's MR exam, the technician notices a burning smell around the injector and scanner. The technician stops the exam and presses the alert button on the workstation GUI in the control room. The workstation pops up an input field asking the technician the reason for the call. The technician is able to immediately verbally explain that there is a burning smell in the scan room while filling the injector with fluid. When the technician stops speaking, the system responds by informing them that the injector serial number and scanner combination have been sent to the Bayer service desk and a service technician has been alerted to be dispatched within xx hours. The system responds with a caution not to use the injector until a Bayer service technician inspects it.

[0116] Scenario 2 - Complaint - A technician complains that the volume at the workstation is too loud and would like to contact someone to remedy the situation. The technician presses the alert button on the workstation GUI in the control room. The workstation pops up an input field asking the technician the reason for the call. The technician is able to quickly verbally explain that the noise coming from the workstation when making a selection is extremely loud and annoying. When the technician stops speaking, the system responds by stating that the injector serial number and scanner combination has been sent to the Bayer Technical Assistance Center (TAC) for further review and management.

[0117] Scenario 3 - Adverse Event - A Brazilian site reports an incident from a mobile CT unit and requests checkout of an injector suspected of air injection. The CT technologist presses the alert button on the workstation GUI in the control room. The workstation pops up an input field asking the technologist the reason for the call. The technologist is able to immediately verbally inform the technologist that there was air injection and the resulting artifact in the diagnostic scan, and would like to request checkout of the injector. Once the technologist stops speaking, the system responds via audio / written notification that the event report will be de-identified and shared with hospital administration for review, and that the request for checkout of the injector (the injector serial number and scanner combination) will be forwarded to the Bayer Service and Adverse Events Team (Issue & Complaint Management (ICM) team). Complaint team personnel contact the customer to collect details of the incident and dispatch maintenance personnel to the site. The system responds with a link to digital resources, including a brief video on how to ensure the patient line is free of air.

[0118] Scenario 4 - Complaint - A technician complains that filling a syringe with a spike results in excessive leakage. This is causing delays as additional time is required to remove the spill. The workstation pops up an input field asking the technician the reason for the call. The technician can immediately request verbal assistance. Once the technician stops speaking, the system responds by informing them that the injector serial number and scanner combination have been sent to a TAC representative. The TAC representative triages the information and determines that the customer needs to contact the Clinical Performance Team to adjust the unit's autoload purge volume setting.

[0119] Scenario 5 - Complaint - Diagnostic Imaging Artifact. A customer sees some ringing on their MR scan and suspects it may be caused by the MR injector. The customer calls or types in their injector complaint. The system communicates through either text chat or voice communication and asks diagnostic questions. Based on the responses, the system recommends "debug" steps to the customer and, depending on the results, next steps. If needed, it provides access to human assistance.

[0120] Scenario 6 - Adverse Event - A customer reports a suspected extravasation during a contrast-enhanced CT procedure while the patient is connected to the MEDRAD® Stellant CT Injection System. The technician requests an injector checkout to ensure proper operation. The user presses the alert button on the workstation GUI in the control room. The workstation opens an input field and prompts the user to enter the reason for the call. The technician can immediately verbally notify Bayer of the extravasation and request a system service check by Bayer field service. Once the caller stops speaking, the system responds with a notification that the event report has been identified and that a request for an injector checkout has been forwarded to Bayer Service, which will dispatch field service and the Issue & Complaint Management (ICM) team. Personnel from ICM will follow up with the customer to gather additional event-related details. The system also sends a request to the Clinical Performance Center for clinical application follow-up.

[0121] Scenario 7 - Complaint - A connectivity issue with the integrated system caused the injector to crash, requiring the scanner to be restarted, and the exam to be aborted. A dose was administered and the patient needs to be rescanned. If the injector-scanner interface (ISI) issue is known for this system configuration, the system may consult a database and inform the user what steps to take to remedy the situation. If this is not a known issue, via text chat or voice communication, the system may go through a series of questions and respond to the customer to assist in debugging the system. If a solution is found, this exchange is added to the database for reference in subsequent cases. If no solution is found, the system may recommend contacting the imaging device manufacturer and may send a service alert to the Bayer service center to make them aware of the issue and inform them that a service call may be requested.

[0122] Scenario 8 - Request for Information - "I need help with the P3T protocol. I haven't used it in months and this procedure requires it." is a verbal message transmitted to the system through the injector user interface. The system responds by connecting the user to an online training video and to the appropriate section of the written manual. All of these types of information requests can be handled at the injector via a custom QR code that the injector displays or on the technician's phone.

[0123] Scenario 9 - Request for Assistance - "I have a few things to order" is communicated verbally or otherwise to the injector user interface. The system responds by displaying a triage menu asking what specifically is needed. Once a specific item or items are selected, the system connects the user directly to Bayer Customer Care to order disposables. If the request is for a new injector, the system emails the request to the appropriate sales representative and a confirmation is sent to the user. If the request is for a replacement syringe heater, communication proceeds to Bayer Service for parts shipment or scheduling a visit, depending on the service contract in place. If the request classification is "Other," the user is connected to Bayer Customer Care.

[0124] Scenario 10 - Request for Assistance - "My injector is not working. I need service." is entered into the system through one of the user interfaces. The system checks the service contract in place and if service for that device is currently covered by Bayer, it contacts Bayer service, or if service is handled by a local hospital through Biomade or a third-party service agent, the system contacts the appropriate number, email, or website to forward the service request.

[0125] Scenario 11 - Request leading to Professional Inquiry Request (PIR) - A customer has a question regarding one or more of the following that our employees cannot handle, for example, off-label use of contrast agents or equipment: The user speaks their PIR to the system. The system checks whether an acceptable answer is available. If so, it shares the answer, including references, with the user. It then checks whether the user is satisfied. If there is no acceptable answer or the user is not satisfied with the answer given, it forwards the request to the appropriate medical or R&D personnel for human follow-up.

[0126] In all scenarios, the system may ask the user about their satisfaction with the answers given or actions taken, and their interaction with the system. This information may be used to refine future responses and identify knowledge gaps that may need to be added to the system. [Explanation of symbols]

[0127] 100 Environment 102 Event Management System 104 Fluid Injection System 106 Workstation Equipment 108 User Equipment 110 Internet of Things (IoT) Management Systems 112 Hospital Information Systems 114 Communication Network 200 systems 204 Fluid Injection System 204A Fluid Injector 206 Workstation Equipment 206A Display Unit 208 User Equipment 210 Gateway Equipment 212-1 Medical Provider Communication Network 212-2 Communication Networks 300 equipment 302 Bus 304 processor 306 memory 308 Memory Components 310 Input Component 312 Output Components 314 Communication Interface 400 processes 500 Implementation 504 Fluid Injector

Claims

1. 1. A system for processing information associated with an event related to a medical device, comprising: receiving data associated with an event related to a medical device via a user interface (UI) associated with the medical device; receiving data associated with an identification characteristic of the medical device; generating an event message, the event message including the data associated with the event related to the medical device and the data associated with the identifying characteristic of the medical device; providing a response message via the UI associated with the medical device based on the data associated with the event related to the medical device, the response message including information based on output of a generative and conversational artificial intelligence (AI) platform; determining a category of the event message based on at least one of the data associated with the event related to the medical device, the data associated with the identifying characteristic of the medical device, or any combination thereof; performing an action based on the category of the event message; and at least one processor configured to implement A system comprising:

2. 10. The system of claim 1, wherein the generative and conversational AI platform comprises at least one of a generative AI model, a conversational AI model, or any combination thereof.

3. the at least one processor: generating the response message based on receiving the data associated with the event related to the medical device, wherein when generating the response message, the at least one processor: providing the data associated with the event related to the medical device as input to a generative AI model; determining an output of the generative AI model based on the input, the output including information associated with a potential solution to the event related to the medical device; configured to perform, configured to perform When providing the response message via the UI associated with the medical device, the at least one processor:

10. The system of claim 1, configured to: provide the information associated with the potential solutions for the event related to the medical device.

4. When providing the response message via the UI associated with the medical device, the at least one processor:

10. The system of claim 1, further configured to: provide a prompt for receiving information from a user via the UI associated with the medical device, the prompt including a question associated with the event related to the medical device.

5. When performing the operations, the at least one processor: The system of claim 1 , configured to: transmit the event message based on the category of the event message.

6. When transmitting the event message, the at least one processor: transmitting said event message to a healthcare provider communications network; transmitting the event message to a system for trend analysis relating to one or more events related to the medical device; transmitting said event message to a communication gateway for further transmission; or any combination thereof, The system of claim 5 configured to implement:

7. the at least one processor: capturing data associated with a timestamp related to the event related to the medical device, the data associated with the timestamp comprising: data associated with a time at which the data associated with the event related to the medical device was received via the UI associated with the medical device; data associated with the time at which the malfunction of the medical device occurred; or and any combination thereof. The system of claim 1 , further configured to:

8. the at least one processor: The system of claim 1 , further configured to: provide the UI associated with the medical device on a mobile device.

9. When providing the UI associated with the medical device on the mobile device, the at least one processor:

10. The system of claim 8, further configured to: upon receiving an input prompt on the mobile device, provide the UI associated with the medical device on the mobile device via an application on the mobile device.

10. Upon receiving the data associated with the event related to the medical device, the at least one processor:

10. The system of claim 1, wherein the system is configured to: receive the data associated with the event related to the medical device via a chatbot that interacts with the UI associated with the medical device.

11. Upon receiving the data associated with the event related to the medical device, the at least one processor: receiving audio data from a user via the user interface (UI) associated with the medical device; converting the voice data into text data using a voice-to-text algorithm; using a natural language processing (NLP) algorithm to convert the text data into the data associated with the event related to the medical device; The system of claim 1 configured to implement:

12. 1. A method for processing information associated with an event related to a medical device, comprising: receiving, with at least one processor, data associated with an event related to the medical device via a user interface (UI) associated with the medical device; receiving, with the at least one processor, data associated with an identifying characteristic of the medical device; generating, with the at least one processor, an event message, the event message including the data associated with the event related to the medical device and the data associated with the identifying characteristic of the medical device; using the at least one processor to provide a response message via the UI associated with the medical device based on the data associated with the event related to the medical device, the response message including information based on output of a generative and conversational artificial intelligence (AI) platform; with the at least one processor, determining a category of the event message based on at least one of the data associated with the event regarding the medical device, the data associated with the identifying characteristic of the medical device, or any combination thereof; with the at least one processor, performing an action based on the category of the event message; A method comprising:

13. 13. The method of claim 12, wherein the generative and conversational AI platform comprises at least one of a generative AI model, a conversational AI model, or any combination thereof.

14. generating the response message based on receiving the data associated with the event related to the medical device, wherein generating the response message comprises: providing the data associated with the event related to the medical device as input to a generative AI model; determining an output of the generative AI model based on the input, the output including information associated with a potential solution to the event related to the medical device; Including steps Further comprising: providing the response message via the UI associated with the medical device; 13. The method of claim 12, further comprising providing the information associated with the potential solutions for the event related to the medical device.

15. providing the response message via the UI associated with the medical device; 13. The method of claim 12, comprising: providing a prompt for receiving information from a user via the UI associated with the medical device, the prompt including a question associated with the event regarding the medical device.

16. performing the operation, The method of claim 12 , further comprising transmitting the event message based on the category of the event message.

17. transmitting the event message, transmitting the event message to a healthcare provider communications network; transmitting the event message to a system for trend analysis relating to one or more events related to the medical device; transmitting said event message to a communication gateway for further transmission; or any combination thereof, 17. The method of claim 16, comprising:

18. capturing data associated with a timestamp related to the event related to the medical device, wherein the data associated with the timestamp comprises: data associated with a time at which the data associated with the event related to the medical device was received via the UI associated with the medical device; data associated with the time at which the malfunction of the medical device occurred; or and any combination thereof; 13. The method of claim 12, further comprising:

19. The method of claim 12 , further comprising providing the UI associated with the medical device on the mobile device.

20. providing the UI associated with the medical device on the mobile device, 20. The method of claim 19, comprising providing the UI associated with the medical device on the mobile device via an application on the mobile device based on receiving an input prompt on the mobile device.

21. receiving the data associated with the event related to the medical device; 13. The method of claim 12, comprising receiving the data associated with the event related to the medical device via a chatbot that interacts with the UI associated with the medical device.

22. receiving the data associated with the event related to the medical device; receiving audio data from a user via the user interface (UI) associated with the medical device; converting the voice data to text data using a speech-to-text algorithm; using a natural language processing (NLP) algorithm to convert the text data into the data associated with the event related to the medical device; 13. The method of claim 12, comprising:

23. 1. A computer program product for processing information associated with events related to a medical device, comprising at least one non-transitory computer-readable medium comprising one or more instructions, which when executed by at least one processor, cause the at least one processor to: receiving, via a user interface (UI) associated with a medical device, data associated with an event related to the medical device; receiving data associated with an identification characteristic of the medical device; generating an event message, the event message including the data associated with the event related to the medical device and the data associated with the identifying characteristic of the medical device; providing a response message via the UI associated with the medical device based on the data associated with the event related to the medical device, the response message including information based on output of a generative and conversational artificial intelligence (AI) platform; determining a category of the event message based on at least one of the data associated with the event related to the medical device, the data associated with the identifying characteristic of the medical device, or any combination thereof; performing an action based on the category of the event message; and A computer program product that causes the

24. 24. The computer program product of claim 23, wherein the generative and conversational AI platform includes at least one of a generative AI model, a conversational AI model, or any combination thereof.

25. The one or more instructions cause the at least one processor to: generating the response message based on receiving the data associated with the event related to the medical device, wherein the one or more instructions causing the at least one processor to generate the response message include causing the at least one processor to: providing the data associated with the event related to the medical device as input to a generative AI model; determining an output of the generative AI model based on the input, the output including information associated with a potential solution to the event related to the medical device; To make or generate Further implementation of the The one or more instructions that cause the at least one processor to provide the response message via the UI associated with the medical device may include causing the at least one processor to:

24. The computer program product of claim 23, wherein the computer program product is configured to perform: providing the information associated with the potential solutions for the event related to the medical device.

26. The one or more instructions that cause the at least one processor to provide the response message via the UI associated with the medical device may include causing the at least one processor to:

24. The computer program product of claim 23, further comprising: providing a prompt for receiving information from a user via the UI associated with the medical device, the prompt including a question associated with the event related to the medical device.

27. The one or more instructions causing the at least one processor to perform the operations may include causing the at least one processor to:

24. The computer program product of claim 23, wherein the computer program product is configured to: transmit the event message based on the category of the event message.

28. The one or more instructions for causing the at least one processor to transmit the event message may include causing the at least one processor to: transmitting said event message to a healthcare provider communications network; transmitting the event message to a system for trend analysis relating to one or more events related to the medical device; transmitting said event message to a communication gateway for further transmission; or any combination thereof, 28. The computer program product of claim 27,

29. The one or more instructions cause the at least one processor to: capturing data associated with a timestamp related to the event related to the medical device, the data associated with the timestamp comprising: data associated with a time at which the data associated with the event related to the medical device was received via the UI associated with the medical device; data associated with the time at which the malfunction of the medical device occurred; or and any combination thereof.

24. The computer program product of claim 23, further comprising:

30. The one or more instructions cause the at least one processor to:

24. The computer program product of claim 23, further comprising: providing the UI associated with the medical device on a mobile device.

31. The one or more instructions that cause the at least one processor to provide the UI associated with the medical device on the mobile device may include causing the at least one processor to:

31. The computer program product of claim 30, further comprising: providing the UI associated with the medical device on the mobile device via an application on the mobile device based on receiving an input prompt on the mobile device.

32. The one or more instructions that cause the at least one processor to receive the data associated with the event related to the medical device may include causing the at least one processor to: receiving the data associated with the event related to the medical device via a chatbot that interacts with the UI associated with the medical device.

33. Upon receiving the data associated with the event related to the medical device, the at least one processor: receiving audio data from a user via the user interface (UI) associated with the medical device; converting the voice data into text data using a voice-to-text algorithm; using a natural language processing (NLP) algorithm to convert the text data into the data associated with the event related to the medical device; 24. The computer program product of claim 23 configured to implement:

Images