JP2024512615A - Smart codes in medical applications - Google Patents

Abstract

The present application is directed to a centralized power data management system for managing power data of remote medical devices located at one or more medical facilities. A server is communicatively coupled to a plurality of power cables. Each power cable includes a code device and is configured to electrically couple to and power a respective medical device. A power profile is received from a first code device of a first power cable and includes power data characteristics measuring power delivered to the first medical device while the first medical device performs a medical procedure. The power profile is used to identify a performed medical procedure including one or more numerical operating parameters of the medical procedure. The computer system transmits a message related to the performed medical procedure to a second electronic device for display on a user interface of the second electronic device.

Description

Related Applications This application claims priority to U.S. Provisional Patent Application No. 63/166,169, filed March 25, 2021, entitled "Smart Cords in Medical Applications," filed February 25, 2022. No. 17/681,692, entitled "Smart Cords in Medical Applications," each of which is incorporated herein by reference in its entirety.

TECHNICAL FIELD This application relates generally to centralized power management systems that collect, analyze, and report power usage characteristics of distributed medical devices powered via power cables.

Medical devices are distributed across different medical facilities and often operate independently of other medical devices. Some medical device manufacturers offer medical device usage platforms to collect usage characteristics of medical devices distributed across different medical facilities. However, such device usage platforms are often limited to one or more specific types of medical devices provided by the same manufacturer and rely on direct communication with those medical devices. Usage characteristics are preferably collected after the medical procedure is completed, as real-time data communication consumes local resources, poses a risk of tampering with the ongoing medical procedure, and can impair the performance of the medical procedure. Transferred to device usage platform. However, such delayed data transfers are easily ignored or interrupted, and do not address concerns of leaking privacy-sensitive patient information stored on the medical device.

In order to safely and efficiently manage the usage characteristics of different types of distributed medical devices, it would be beneficial to develop a centralized data management mechanism.

This application relates to the use of a smart cord device between a power outlet and a medical device to collect and report device usage characteristics associated with the medical device while powering the medical device. The form will be explained. A smart cord device is a piece of medical grade power cable that is configured to work with gauges that comply with medical device specifications. In addition, the smart code device has one or more processors and memory that stores instructions to collect power profiles (e.g., power, voltage, and current of a medical device) and to is executed by the processor to report to a centralized power data management platform. The platform applies data analysis algorithms (e.g., including deep learning techniques) to understand the power profile collected from one or more medical devices, and the platform applies data analysis algorithms (e.g., including deep learning techniques) to understand the power profile collected from one or more medical devices and Translate into understandable information about relevant medical procedures. Specifically, the platform determines ranges of device usage parameters and identifies device modes or operating states of the medical device based on the collected power profile. Data is transferred to smart code devices and centralized power sources via secure and encrypted networks (e.g. private cellular networks) without involving the medical device and without affecting the operation of the associated medical procedure. communicated to and from a data management platform.

In one aspect, a data management method is implemented in a server system that hosts a centralized power data management system for multiple remote medical devices located at one or more medical facilities. The method includes communicatively coupling to a plurality of power cables via one or more wide area networks (WANs). Each of the power cables includes a cord device (ie, a smart cord device having one or more processors and memory). Each power cable is electrically coupled to and configured to power a respective one of the plurality of remote medical devices. The plurality of remote medical devices includes a first medical device powered by a first power cable that includes a first cord device. The method further includes receiving a power profile from the first cord device of the first power cable. The power profile includes a plurality of power data characteristics that measure power delivered to the first medical device while the first medical device performs a medical procedure. The method includes the steps of: using a power profile to identify a performed medical procedure, including one or more numerical operating parameters of the performed medical procedure; and displaying the power profile on a user interface of a second electronic device. and sending the message to the second electronic device in order to do so. The message specifies the medical procedure performed and one or more numerical operating parameters. In some embodiments, the second electronic device is the same as the first medical device. In some embodiments, the second electronic device is separate from the first medical device.

According to other aspects of the present application, a computer system (eg, a server system) includes one or more processing units, a memory, and a plurality of programs stored in the memory. The program, when executed by one or more processing units, causes the computer system to perform the method for managing data of a medical device described above.

According to other aspects of the present application, a non-transitory computer-readable storage medium stores a plurality of programs configured for execution by a computer system having one or more processing units. The program, when executed by one or more processing units, causes the computer system to perform the method for managing data of a medical device described above.

The accompanying drawings, which are included to provide a further understanding of the embodiments and are incorporated in and constitute a part of this specification, illustrate the described embodiments and, together with the text of the specification, illustrate the underlying principles. helps explain.

1 is an illustration of an example data management environment for multiple medical machines or devices, according to some embodiments. FIG. 1 is an illustration of an example operating environment for a power cable power cord device, according to some embodiments. FIG. 1 is a block diagram of a power cord device, according to some embodiments. FIG. 1 is a flow diagram of an example process for managing power data for a medical device 102, according to some embodiments. 2 is an illustration of an example power profile collected from a power cord device 106, according to some embodiments. FIG. 2 is a diagram of a flow of power data received, processed, or generated by a power cord server, according to some embodiments. FIG. FIG. 2 is a diagram of one of three example user interfaces presented to a user, according to some embodiments. FIG. 2 is a diagram of one of three example user interfaces presented to a user, according to some embodiments. FIG. 2 is a diagram of one of three example user interfaces presented to a user, according to some embodiments. 1 is a block diagram of an exemplary medical device for performing a medical procedure, according to some embodiments. FIG. 1 is a block diagram of an example client device for presenting information of a medical procedure performed on a separate medical device, according to some embodiments. FIG. 1 is a block diagram of a power cord server 108 for collecting power profiles and providing medical treatment information to a user, according to some embodiments. FIG. FIG. 3 provides a flow diagram of a data management method implemented at a power cord server, according to some embodiments. FIG. 3 provides a flow diagram of a data management method implemented at a power cord server, according to some embodiments. FIG. 3 provides a flow diagram of a data management method implemented at a power cord server, according to some embodiments. FIG. 3 provides a flow diagram of a data management method implemented at a power cord server, according to some embodiments.

Like reference numbers refer to corresponding parts throughout the several views of the drawings.

Reference will now be made in detail to specific embodiments, examples of which are illustrated in the accompanying drawings. In the detailed description that follows, numerous non-limiting specific details are set forth to assist in understanding the subject matter presented herein. However, it will be apparent to those skilled in the art that various alternatives may be used without departing from the scope of the claims and the subject matter may be practiced without these specific details. For example, it will be apparent to those skilled in the art that the subject matter presented herein can be implemented on many types of electronic devices that have digital video capabilities.

Various embodiments of the present application are communicatively coupled to a plurality of power cord devices and provide power to the medical device through the power cord devices during or after the medical device is performing a medical procedure. For centralized power data management platforms configured to collect usage characteristics. Each power cord device is part of a power cable that connects the respective medical device to a power outlet. Such power cord devices facilitate powering the respective medical device and generally do not exchange data directly with the medical device via the power cable. When a medical procedure is performed by a medical device, the power cord device generally cannot access data stored within the medical device. However, a power cord device can detect power usage characteristics associated with a medical procedure (i.e., enable a medical procedure) without knowing what type of medical device or what type of medical procedure was powered by the power cable. The power profile (including the instantaneous current or power provided by the power cable) can be monitored in order to A centralized power data management platform collects power usage characteristics from different types of medical devices and related to different types of medical procedures, analyzes the collected power usage characteristics, and provides analysis results (e.g., medical devices, The data service may cooperate with the power cord device to generate statistics (of users, treatment settings, treatment times, and geographic distribution) and provide analysis results to users of the data service.

Additionally, in some embodiments, firmware running on the power cord's CPU/processor knows some characteristics of the medical device powered by the power cord. The power cord is configured to classify power events locally instead of fully determining treatment characteristics on a remote power cord server. In some situations, this power cord requires firmware specific to the cord device to properly classify power events.

FIG. 1 is an example data management environment 100 for multiple medical machines or devices 102, according to some embodiments. Each medical machine or device 102 (also abbreviated as medical device 102) is configured to perform one or more respective specialized medical procedures. Examples of medical procedures include, but are not limited to, computed tomography (CT scan), radiography, magnetic resonance imaging (MRI scan), ultrasound, endoscopy, echocardiogram (EKG or ECG), intravenous injections, epidural or intra-arterial injections, LASIK surgery, non-invasive cosmetic surgery, invasive cosmetic surgery, and laser surgery. Examples of medical devices 102 include, but are not limited to, artificial kidneys, ventilators, cardiopulmonary bypass devices (i.e., heart-lung machines), dialysis machines, incubators, various laser machines, various gas machines, and various medical imaging devices. machines, and various medical laboratory equipment. Each medical device 102 is connected to a power outlet via a power cable 104 that includes a power cord device 106 and two cable portions extending from opposite ends of the power cord device 106, the power cable 104 connecting the medical device 102 to a power outlet. Provide electricity. In some embodiments, the power cable 104 that includes the power cord device 106 does not provide data to or receive data from the medical device 102. Conversely, in some embodiments, the power cord device 106 is connected wirelessly (e.g., using near field communication (NFC) or Bluetooth communication) or via wire (e.g., to the corresponding power cable 104). (via a cable portion), providing data to or receiving data from the medical device 102. It is noted that the same type of power cable 104 or the same type of power cord device 106 may be used with different types of medical devices 102.

Power cord device 106 is communicatively coupled to power cord server 108 (also referred to as smart cord server 108) via one or more communication networks 110. While the medical device 102 is performing a medical procedure, the corresponding power cord device 106 connected to the medical device 102 generates a power profile 120 that includes a plurality of power data characteristics that measure the power delivered to the medical device 102. Record and report power profile 120 to power cord server 108 via one or more communication networks 110. In some embodiments, power cord device 106 reports power profile 120 in real time while a medical procedure is being performed. In some embodiments, power cord device 106 reports power profile 120 after each medical procedure is completed. In some embodiments, power cord device 106 reports batches of power profiles 120, including one or more power profiles 120, according to a predefined reporting schedule or periodically. In some embodiments, each power cord device 106 is communicatively coupled to the power cord server 108 via a cellular network that does not need to be delegated to any local area network. In this case, once the power cord device 106 is connected to the corresponding medical device 102, the power cord device 106 is configured to report data (e.g., power profile 120) to the power cord server 108 without or with little or no user intervention. be done.

Power cord server 108 enables a centralized data management platform to manage power profiles 120 collected in connection with multiple medical devices 102, which may include more than one device type. After collecting the power profiles 120 from the plurality of power cord devices 106, the power cord server 108 configures these medical Power profile 120 may be analyzed to identify medical procedures performed by device 102 and further statistics of these medical procedures may be generated. The power cord server 108 is then configured to report the medical procedure with one or more numerical operating parameters to the medical device 102 or client device 112 for display on the user interface of the medical device 102 or client device 112. Generates message 130. In some embodiments, message 130 includes a summary of statistics of medical procedures monitored by two or more medical devices 102, and client device 112 receiving message 130 displays the statistics on its own user interface. Can be visualized.

In some embodiments, the code device 106 preprocesses the power profile 120 collected in association with the connected medical device 102. Firmware running on the cord device 106 recognizes several data characteristics of the medical device 102 powered by the corresponding power cord 104. The code device 106 is configured to locally identify device type, device mode, operating state, medical procedure, or power event instead of determining treatment characteristics entirely on the power cord server 108. Preprocessed power profile 120 is provided by power cord server 108 for further profile processing and/or to generate messages sent to other medical devices or client devices using this code data service. be done. In some embodiments, code device 106 is a specialized code device that includes hardware or software modules configured to identify information associated with one or more specific types of medical device 102. .

In some embodiments, the power cord server 108 is configured to support a power cord application (e.g., applications 634A and 634B in FIGS. 6A and 6B), where the power cord application is connected to the medical device 102 or the client device 112. and is configured to enable a user interface for displaying information contained within message 130. The power cord application may be a browser-based application or a dedicated data application. The user interface is configured to receive a user query and present information contained within the message 130 in accordance with the user query. Messages may include alerts, notifications, reports, and/or instructions regarding medical treatment.

In some embodiments, the type of each medical device 102 is not communicated or known to the power cord device 106 when the power cord device 106 is connected to the respective medical device 102. Similarly, in some embodiments, when a power cord device 106 reports a power profile 120 for a medical procedure for each medical device 102, the type of medical procedure is not communicated to the power cord device 106 or is not known. do not have. In some embodiments, power cord device 106 identifies one or more power characteristics within each power profile 120 and derives the type of medical device 102 and/or medical procedure based on the identified power characteristics. and reports the type of medical device 102 and/or medical procedure along with the power profile 120 to the power cord server 108. Alternatively, in some embodiments, power cord server 108 identifies one or more power characteristics within each power profile 120 collected from cord device 106 and identifies the identified power characteristics within power profile 120. The system is configured to derive a type of medical device 102 and/or medical procedure based on the characteristics. In some embodiments, the power cord device 106 or power cord server 108 uses deep learning techniques to determine the type of medical device 102 and/or medical procedure based on the power profile 120 and/or the corresponding power characteristics. configured to determine.

In some embodiments, medical device 102 operates offline and is isolated from any communication network 110 (eg, for purposes of maintaining data security and privacy). Medical device 102 is configured to locally execute a medical device application (eg, application 630A in FIG. 6A). Alternatively, in some embodiments, medical devices 102 communicate with each other via one or more communication networks 110 (e.g., only during a medical procedure or when a procedure is not being performed). communicatively coupled to server 114; Medical devices of the same type are coupled to the same medical device server 114. Different types or brands of medical devices are coupled to separate medical device servers 114. Each medical device server 114 or medical device 102 may operate independently of the power cord server 108 and is unaware of the existence of the power cord device 106. Conversely, in some situations, medical device server 114 or medical device 102 interacts with power cord server 108. Medical device 102 is configured to execute a medical device application (e.g., application 630A in FIG. 6A) in conjunction with respective medical device server 114 for the purpose of controlling medical device 102 to perform a medical procedure. be done. Under some circumstances, this medical device application receives a message 130 from power cord server 108 regarding a medical procedure performed by this medical device 102 or other medical devices 102 and displays message 130 on its user interface. It is also configured as follows. In one example, the medical device application user interface includes an embedded or pop-up window for displaying messages 130 provided by power cord server 108.

Data management environment 100 further includes a plurality of client devices 112 communicatively coupled to at least power cord server 108. Each client device 112 may be, for example, a desktop computer, a tablet computer, or a mobile phone. Each client device 112 may collect data or user input, execute a user application (eg, power cord application 634B in FIG. 6B), or present output on its user interface. The collected data or user input may be processed locally at client device 112 and/or remotely by server 108 or 114. Servers 108 and 114 provide system data (e.g., boot files, operating system images, and user applications) to client device 112 and, in some embodiments, when the user application executes on client device 112. Processing data and user input received from client devices 112. In one example, client device 112 is utilized to communicate with medical device server 114 and remotely control medical procedures performed by medical devices 102 coupled to medical device server 114. In other examples, client device 112 communicates with power cord server 108 to control collection, analysis, and reporting of power usage characteristics of medical device 102.

Servers 108 and 114, client device 112, code device 106, and medical device 102 (if present) are communicatively coupled to each other via one or more communication networks 110, which communicate with these devices. and computers interconnected within data management environment 100. One or more communication networks 110 may include connections such as wires, wireless communication links, or fiber optic cables. Examples of one or more communication networks 110 include a local area network (LAN), a wide area network (WAN), such as the Internet, or a combination thereof. The one or more communication networks 110 may include Ethernet, Universal Serial Bus (USB), FIREWIRE, Long Term Evolution (LTE), Global System for Mobile Communications (GSM), Extended Data GSM Environment (EDGE), Code Division Multiple Access ( CDMA), Time Division Multiple Access (TDMA), Bluetooth, Wi-Fi, Voice over Internet Protocol (VoIP), Wi-MAX, or any other suitable communication protocol. can be implemented using any known network protocol. Connections to one or more communications networks 110 may be made either directly (e.g., using 3G/4G/5G connectivity to a wireless carrier) or through a network interface (e.g., a router, switch, gateway, hub, or intelligent (a dedicated pan-house control node) or any combination thereof. One or more communication networks 110 may represent the Internet, a worldwide collection of networks and gateways that use the Transmission Control Protocol/Internet Protocol (TCP/IP) suite of protocols to communicate with each other. The core of the Internet is a backbone of high-speed data communication lines between major nodes or host computers, consisting of thousands of commercial, government, educational, and other computer systems that route data and messages 130. In some embodiments, all power cord devices 106 are communicatively coupled to a power cord server 108 via a secure, encrypted private cellular network, and the power cord devices 106 are connected to medical devices 102. It is then configured to report data to the power cord server 108 independently from any local wired or wireless network.

In some embodiments, to process the power profile 120 collected by the power cord device 106 (e.g., to identify power characteristics and operating parameters contained within the power profile 120, to identify new device modes, operating states, Deep learning techniques are used in the data management environment 100 to identify a medical procedure, to match a power profile 120 to a medical procedure, to classify a power profile 120, and/or to synthesize associated power characteristics. Applicable. In these deep learning techniques, data processing modules are created based on one or more neural networks to process the power profile 120. These data processing modules may be trained using training data before being applied to process power profile 120. Both model training and data inference are implemented at the power cord server 108 and the results (e.g., messages 130) are delivered to individual client devices 112 or Reported to medical device 102.

FIG. 2A is an example operating environment 200 for a power cord device 106 of a power cable 104, according to some embodiments, and FIG. 2B is a block diagram of a power cord device 106, according to some embodiments. be. The ends of power cable 104 are configured to connect to a power source (eg, a standard wall outlet) and medical device 102, respectively. Power cord device 106 is coupled to power cable 104 and configured to monitor power as power cable 104 transfers power from the power source to medical device 102. Power cable 104 includes two cable sections 104' extending from opposite ends of power cord device 106. The power is recorded as a power profile 120 (eg, current flow is sampled at a predefined sample rate), reported to, and analyzed by the power cord server 108. The analysis results (eg, message 130) are then presented to the user on the user interface of client device 112 or medical device 102.

In some embodiments, power cord device 106 is utilized to gain insight into device usage patterns, treatment settings, physical location, and other characteristics of medical device 102. Power cord server 108 learns how power profile 120 fits the treatment setting or device mode of medical device 102 and converts power profile 120 of medical device 102 into logical data presented in a visual report. do. In some embodiments, power cord server 108 is configured (eg, using deep learning techniques) to recognize power patterns associated with each medical procedure for different medical devices. In some embodiments, the power cord server 108 is configured to remotely manage software components that manipulate, batch, sort, and initiate transmission of data ingested from the microprocessor of the power cord device 106. configured. In some embodiments, power cord server 108 includes a machine learning component to classify characteristics of data across device types and determine that additional power cord devices 106 are added to data management environment 100. . In some embodiments, the power cord device 106 or the power cord server 108 assigns unique power usage characteristics (e.g., using deep learning techniques) to device type, device mode, operating state, and medical procedure settings. A proprietary software program is installed for mapping. In some embodiments, a website platform is deployed to display, sort, correlate, and export post-processed and interpreted data provided by power cord server 108.

Referring to FIG. 2A, the power cord device 106 includes an AC-DC converter (ADC) 202, a relay 204, a battery 206, a battery management system (including a fuel gauge) 208, a power monitor module 210, a flash storage 212, a position module 214 , a cellular module 216 , an antenna 218 , and a connector 220 . ADC 202 is configured to convert an AC power voltage provided by a power source to a DC power voltage for powering the operation of power cord device 106. Relay 204 is configured to receive controls or instructions to enable/disable current flow to medical device 102 or power cord device 106 (eg, emergency shutoff). This control or command may be provided remotely by power cord server 108. Battery 206 is controlled by battery management system 208 to store power. Location module 214 is configured to identify the geographic location of power cord device 106 and may be a Global Positioning System (GPS) or other module capable of providing geolocation information. In one example, the location of code device 106 is determined based on a Wi-Fi basic service set identifier (BSSID) or received signal strength indicator (RSSI). Power monitor module 210 is configured to sample power, voltage, or current values associated with use of medical device 102. Such sampled values form the power profile 120 of the medical device 102 and are digitized and temporarily stored in flash memory 212. Power profile 120 stored in flash memory 212 is transferred to power cord server 108 via one or more communication networks 110. In one example, power profile 120 is transferred over a private cellular network (eg, using cellular module 216) in an encrypted HIPAA compliant format. In other examples, power profile 120 is transferred with information of the geographic location of power cord device 106.

Referring to FIG. 2B, in some embodiments, power cord device 106 communicates with one or more processors 222 to monitor, store, preprocess, and/or transmit collected power profiles. and a memory 226 for storing instructions to be executed by processor 222. Power cord device 106 further includes one or more network interfaces 224, memory 226, and one or more communication buses 228 for interconnecting these components (sometimes referred to as a chipset). In some embodiments, power cord device 106 includes one or more input devices 230 to facilitate user input, such as a touch screen display, touch sensitive input pad, or other input buttons or controls. In some embodiments, power cord device 106 includes one or more output devices 232 that enable presentation of a user interface and display content, including one or more visual displays and light indicators.

Memory 226 includes high speed random access memory such as DRAM, SRAM, DDR RAM, or other random access solid state memory device. In some embodiments, the memory includes one or more magnetic disk storage devices, one or more optical disk storage devices, one or more flash memory devices, or one or more other non-volatile solid state storage devices. Contains non-volatile memory such as devices. In some embodiments, memory 226 includes one or more storage devices located remotely from one or more processing units 222. Memory 226, or alternatively non-volatile memory within memory 226, includes non-transitory computer-readable storage media. In some embodiments, memory 226, or a non-transitory computer-readable storage medium of memory 226, stores the following programs, modules, and data structures, or a subset or superset thereof.
- An operating system 234 that contains procedures for handling various basic system services and performing hardware-dependent tasks.
connecting each power cord device 106 to the power cord server 108 via one or more network interfaces 224 (wired or wireless) and one or more communication networks 110, such as a private encrypted cellular network; network communication module 236.
- A data collection module 238 that collects a power profile 120 that includes a plurality of power data characteristics that measure the power delivered to a medical device coupled to the power cord device 106.
- A data pre-processing module 240 that processes the collected power profile 120. In some embodiments, a recognition method is applied to identify the device type and/or device mode, operating mode, and/or medical procedure of the medical device 102 based on the power profile 120. .
- A data reporting module 242 that reports the collected or preprocessed power profile 120 (e.g., in real time, periodically, or according to a predefined reporting schedule).
·below,
o Power profile 120 captured and preprocessed by power monitor module 210, as well as o Common device settings of power cord device 106 (e.g., serial identification, geographic location, service tier, device model, storage capacity, processing power, code information and settings248, including communication capabilities, etc.)
one or more databases 244 that store code data including one or more of the following:

Each of the elements identified above may be stored in one or more of the aforementioned memory devices and corresponds to a set of instructions for performing the functions described above. The modules or programs (i.e., sets of instructions) identified above need not be implemented as separate software programs, procedures, modules, or data structures, and therefore various subsets of these modules may be implemented in different implementations. may be joined in form or otherwise rearranged. In some embodiments, memory 226 stores a subset of the modules and data structures identified above. In some embodiments, memory 226 stores additional modules and data structures not described above.

FIG. 3 is a flow diagram of an example process 300 for managing power data for a medical device 102, according to some embodiments. Process 300 is jointly performed by power cord device 106, power cord server 108, and an electronic device (eg, medical device 102 or client device 112). Medical device 102 is connected to a power source by a power cable 104 that includes a power cord device 106. Medical device 102 has device modes (eg, an operational mode and an idle mode). The medical device 102 is configured to perform one or more types of medical procedures in an operational mode based on a treatment setting and to switch to an idle mode after a medical procedure or a batch of consecutive medical procedures has been performed. . Medical device 102 includes one or more processors and memory that stores instructions to be executed by the processors. Specifically, medical device 102 is installed with a medical device application (eg, application 630 in FIG. 6A) that is loaded to control each medical procedure based on corresponding treatment settings (328). In some embodiments, a power cord application is also installed (326). While medical device 102 is performing a medical procedure (304), power cord device 106 records power data characteristics associated with the medical procedure in real time according to a sample rate (306). The recorded power data characteristics measure the power delivered to the medical device 102 while the medical device 102 is performing a medical procedure and form a power profile 120 for the medical device 102.

Power cord device 106 reports a power profile 120 corresponding to the medical procedure to power cord server 108 while the medical procedure is being performed or after the medical procedure is completed. After receiving 310 the power profile 120, the power cord server 108 analyzes the power data characteristics of the power profile and determines whether each portion or interval of the power profile is associated with an operating mode or an idle mode of the medical device 102. Determine (312). Power cord server 108 identifies the performed medical procedure, including one or more numerical operating parameters of the performed medical procedure within power profile 120 (314). For example, a particular type of medical procedure may have one or more power characteristics (e.g., a power pulse train), and the power cord server 108 may have one or more power characteristics (e.g., a power pulse train frequency, Identify the numerical operating parameters corresponding to the power pattern, and the average power peak). This determines that a particular type of medical procedure has been performed by the medical device 102 connected to the power cord device 106 reporting the power profile 120 based on the numerical operating parameters. Accordingly, in some embodiments, the power cord server 108 generates (316) a message 130 specifying the performed medical procedure and one or more numerical operating parameters and displays it on the user interface of the electronic device. Message 130 is sent to the electronic device to do so.

In some embodiments, the electronic device that receives message 130 from power cord server 108 is client device 112. Client device 112 installs and runs 320 a power cord application (eg, application 634B in FIG. 6B), which can be a browser-based application or a dedicated data application. A user account is created in the power cord application for a user of data services provided by the power cord server 108 (322). A user interface is displayed on the client device 112 via the power cord application to share messages 130 with users of the data service. Message 130 is displayed on the power cord application user interface (324).

Alternatively, in some embodiments, the electronic device that receives the message 130 from the power cord server 108 is the same medical device 102 that performs the medical procedure, or a separate medical device 102. In some embodiments, the medical device 102 has installed and runs (326) a power cord application (e.g., application 634A in FIG. 6A), which can be a browser-based application or a dedicated data application, and is connected to a power cord server. User accounts are created in the power cord application for users of data services provided by 108. In some embodiments, the medical device 102 is installed with and executes (328) a medical device application (e.g., application 630A in FIG. 6A) for performing a medical procedure using the medical device 102; The medical device application includes a power cord plug-in program (eg, program 632A in FIG. 6A). A user interface presenting the message 130 is displayed (330) on the medical device 102, either directly through the power cord application or through the medical device application's power cord plug-in program.

It is noted that in some embodiments, firmware running on the cord device 106 recognizes certain data characteristics of the medical device 102 powered by the corresponding power cord 104. The code device is configured to locally identify device type, device mode, operating state, medical procedure, or power event instead of fully determining treatment characteristics on the remote power cord server 108. However, a subset of operations 312 and 314 may be implemented locally at power cord device 106. In particular, code device 106 may be customized with hardware or software modules to serve a particular type of medical device 102. Accordingly, in various embodiments of the present application, operations 312 and 314 are optionally implemented entirely by power cord device 106, wholly by power cord server 108, or jointly by cord device 106 and cord server 108. be done.

FIG. 4A is an example power profile 120 collected from a power cord device 106, according to some embodiments, and FIG. 4B is an example power profile 120 received, processed, or generated by a power cord server 108, according to some embodiments. 4 is a flow 400 of the generated power data. This power profile 120 corresponds to a medical procedure implemented by the Ultherapy device manufacturer by Merz North America. The medical device 102 is powered on and sends pulses from the transducer that are applied to the human tissue to tighten the corresponding tissue area by stimulating collagen production. The power profile 120 includes a root mean square (RMS) value of current 402, an RMS value of voltage 404, active power 406, reactive power 408A and 408B, apparent power 410, power factor 412, frequency 414, die temperature 416; and multiple power parameters. A plurality of power parameters 402-416 are plotted as a function of samples or time and optionally associated with a plurality of timestamps. For example, 3000 samples are recorded for each power parameter at a sample rate of 30 samples per minute. In some embodiments, the plurality of power parameters 402-416 are stored in an HTML file and transferred from the power cord device 106 to the power cord server 108. A power cord application (e.g., application 634C in Figure 6C) is run to open the HTML file and visualize the power parameters 402-416, thereby allowing the user to manipulate the power parameters 402-416 (e.g., each power (turn parameters on or off, or expand parts of the power profile).

A subset of the plurality of power parameters 402-416 is substantially stable. For example, the RMS value of the voltage 404 is 120V. Frequency 414 is 60Hz. Die temperature 416 stabilizes at approximately 30°C. It is noted that the power factor 412 is the ratio of the power dissipated by the power cord device 106 to the product of the RMS value of the current 402 and the RMS value of the voltage 404 (i.e., the power delivered to the medical device 102). . Power factor 412 is approximately zero, indicating that the power dissipated by power cord device 106 is negligible compared to the power provided to medical device 102. In addition, reactive power 408 associated with a reactive load is less than real power 406 or apparent power 410. When medical device 102 is powered on and no medical procedure is being performed in idle mode 418, reactive power 408A is substantially stable (eg, having a temporal variation of less than 5%). When a medical procedure is performed in operating mode 420, reactive power 408B increases slightly and has negligible variation compared to the power pulse train 450 observed in active power 406 or apparent power 410.

Power profile 120 includes multiple operations including a subset of system idle states 424A and 424B, system start state 422, therapy start state 426, one or more therapy states 428A and 428B, therapy idle state 430, and power off state 432. correspond to the state. The idle mode 418 of the medical device 102 includes system idle states 424A and 424B, and the operating modes 420 of the medical device 102 include a therapy start state 426, a first therapy state 428A, a therapy idle state 430, and a second therapy state 428B. corresponds to the sequence of A medical procedure for medical device 102 is identified when a subset of multiple operating states is identified. In this example of FIG. 4A, a particular medical procedure is identified following detection of an ordered sequence of a first therapy state 428A, a therapy idle state 430, and a second therapy state 428B. Further, the first and second therapy states 428A and 428B are identified according to the detection of the power pulse trains 450A and 450B, and the therapy idle state 430 is identified according to the corresponding power drop and position between the two power pulse trains 450A and 450B. be identified. Given that a subset of power parameters 402-416 is substantially stable, medical treatment is based on at least one of the remaining power parameters, such as RMS value of current 402, real power 406, and apparent power 410. and at least one of the remaining power parameters optionally identifies each of states 428A, 430, and 428B, their corresponding ordered sequence, and/or a particular medical procedure. , processed using deep learning techniques.

The first treatment state 428A provides a train of power pulses 450A characterized by a power data characteristic 434 (see FIG. 4B) that measures the power delivered to the medical device 102 while the medical device 102 performs a corresponding medical procedure. include. A subset of these power data characteristics 434 are measured from real power 406 and apparent power 410 and include the duration, frequency, power pattern, and average power peak value of power pulse train 450A. Power cord server 108 identifies first treatment state 428A based on the subset of power data characteristics 434 and determines one or more numerical operating parameters 436 (see FIG. 4B) of the performed medical procedure. In one example, the power pattern and frequency of the power pulses may be used to identify the first treatment condition 428A and the corresponding medical procedure. Medical procedure numerical operating parameters 436 include the power level and duration of the medical procedure, which are determined from a subset of power data characteristics 434 and transmitted to users of data services provided by power cord server 108.

Additionally, in some embodiments, each of the plurality of operating states 422-432 is defined according to at least one power threshold 438 (see FIG. 4B) associated with a respective subset of power data characteristics 434. be done. At least one power threshold 438 associated with each of the plurality of operating states 422-432 is determined and adjusted based on deep learning techniques. In some situations, the ordered sequence of states 426-430 in operating mode 420 is initially unknown to power cord system 108 and appears repeatedly in power profiles collected from different medical devices 102. Power cord server 108 applies deep learning techniques to determine one or more power thresholds associated with each of the states in the sequence of states 426-430, or recognizes the sequence of states 426-430. or classify the sequence of states 426, 428A, 430, and 428B as medical procedures.

The plurality of operating states 422-432 are sequentially ordered in power profile 120. In some embodiments, after receiving power profile 120, power cord server 108 divides power profile 120 into multiple power intervals. Each power interval corresponds to a respective one of a plurality of operating states 422-432. For each power interval, power cord server 108 determines (eg, using deep learning techniques) whether the respective power interval includes a power pulse train 450. In accordance with the determination that each power interval includes a power pulse train 450 (e.g., at active power 406 of first treatment state 428A), power cord server 108 determines that each power interval includes a power pulse train 450 as a respective subset of power data characteristics 434 corresponding to each interval. , determining one or more of the duration, pulse pattern, frequency, and average power peak value of the power pulse train. Conversely, following a determination that each power interval does not include a power pulse train 450, power cord server 108 determines average current, average voltage, average active power, and determining one or more of reactive power. For example, the value of reactive power 408A or 408B is a power data characteristic 434 that may be used to determine whether medical device 102 operates in idle mode 418 or operational mode 420.

In some embodiments, for each power interval, a respective subset of power data characteristics 434 corresponding to the respective interval is compared to at least a respective power threshold 438. The first operating state 428A is associated with the first power interval following a determination that the comparison for the first power interval satisfies the association criteria for the first operating state 428A. One or more numerical operating parameters 436 of the performed medical procedure (e.g., the power level of the medical procedure) are associated with each subset of power data characteristics 434 corresponding to the first power interval (e.g., the first power interval). frequency, power pattern, and average power peak value). Further, in some embodiments, each power threshold associated with the first operating state 428A is determined and adjusted based on the first deep learning technique.

1 and 4B, after the power profile 120 is received from the first power cord device 106A, power data characteristics 434 are extracted and the corresponding first medical device 102A type, device mode (i.e., idle mode 418 or operating mode 420), each operating state associated with the respective power interval, the type of medical procedure, and one or more first numerical operating parameters 436 of the medical procedure. . When multiple power profiles 120 are received from two or more power cord devices 106, power cord server 108 may jointly analyze the multiple power profiles 120 and derive using a single power profile 120. provide additional information that cannot be provided.

For example, in some embodiments, the power cord server 108 connects the second medical device 106B of the second power cable 104B to the second medical device 106B while the second medical device 102B is performing the same medical procedure. A second power profile 120' is received that includes a plurality of second power data characteristics 434' measuring power provided to the device 102B. The second power profile 120' is used to identify one or more second numerical operating parameters 436' of the same medical procedure. Message 130 is generated based on first and second numerical operating parameters 436 and 436' of the same medical procedure. In some embodiments, message 130 reports the results of a statistical analysis of numerical operating parameters 436 of multiple medical devices 102, including first and second medical devices 102A and 102B. Additionally, in some embodiments, a therapeutic power signature 440 is determined for the same medical procedure based on at least the first and second numerical operating parameters 436 and 436' and a message transmitted to other electronic devices. 130 includes a therapeutic power signature 440. Examples of therapeutic power signatures include, but are not limited to, the most commonly used power data characteristics and the most effective power data characteristics for medical procedures. In addition, in some embodiments, other electronic devices that receive message 130 from power cord server 108 may determine whether subsequent medical treatment performed by the electronic device is based on treatment power signature 440 received in message 130. configured to coordinate treatment;

Alternatively, in some embodiments, the power cord server 108 receives a plurality of third power profiles 120'' from a plurality of third power cables 106C. each of the plurality of third power supplies measuring the current supplied to the respective third medical device 106C while the respective third medical device 106C is performing the respective third medical procedure; data characteristics 434''. Each of the plurality of third power profiles 120'' includes one or more third numerical operating parameters 436'' of the respective third medical procedure. The message 130 includes one or more first numerical operating parameters 436 of the performed medical procedure and a third numerical operating parameter corresponding to the plurality of third power profiles 120. parameter 436". For example, message 130 may identify the most performed medical procedures or the average procedure time for different medical procedures. In some embodiments, the first power profile 120 and the plurality of third power profiles 120'' are geographically or In accordance with the temporal constraints, message 130 is generated based on geographic or temporal constraints. In one example, geographic distribution 442 is obtained based on an analysis of power profiles 120 and 120" and message 130 is Sent. In one example, message 130 states that the most popular medical procedure during a 5-year period is LASIK surgery, with 23% of all medical procedures performed in Florida during the 5-year period being LASIK surgery. shows.

5A, 5B, and 5C are three example user interfaces 500, 520, and 540 presented to a user, according to some embodiments. Messages 130 generated by power cord server 108 are displayed as part of each of user interfaces 500, 520, and 540. Message 130 may include alerts, notices, reports, or instructions regarding medical treatment. 5A and 5B, the user interface 500 or 520 is configured within a power cord application (e.g., application 634 in FIG. 6A or 6B) executed by an electronic device (e.g., client device 112 or medical device 102). loaded. The power cord application is configured to facilitate monitoring medical procedures performed by medical devices 102 distributed at different medical facilities based on power profiles 120 of those medical procedures. The power cord application may be a browser-based application or a dedicated data application. Each of the power cord application user interfaces 500 and 520 includes a menu area 502 having multiple affordances 504 and an information display area 506. Each affordance 504 corresponds to different content displayed on information display area 506. In response to selecting one of the plurality of affordances 504, the power cord application displays corresponding different content on the information display area 506. For the subset of affordances 504, the corresponding different content corresponds to the message 130 determined based on the collected power profile 120. Some or all of the messages 130 are displayed within a user interface 500 and 520 of a power cord application executed by the electronic device.

The plurality of affordances 504 include one or more of a device overview affordance 504A, a device map affordance 504B, a reporting affordance 504C, a supplies ordering affordance 504D, a device management affordance 504E, a user profile affordance 504F, and an error affordance 504G. In response to selecting device overview affordance 504A, user interface 500 displays information display area 506, as shown in FIG. 5A. The content displayed in the information display area 506 includes a device summary 508 of medical procedures that meet predefined criteria (eg, including time and location restrictions). Device overview 508 is one of: total number of medical procedures (i.e., treatments) 508A, number of users of power data 508B, total treatment time for these medical procedures 508C, number of medical devices 508D, and number of device events 508E. or more than one. In some situations, plot 510 is generated to provide more information about a subset of device summary 508 (eg, number of device events 508E). In this example, plot 510 shows the variation in the number of device events 508E over this month and last month. In some embodiments, additional content 512 is displayed to provide insight into the power profile 120 collected by the power cord server 108. For example, additional content 512 includes a summary of treatment types 512A, a record of recent events 512B, and/or a list of most active physicians 512C.

Among the content displayed in the information display area 506, at least the total treatment time 508C for these medical procedures is associated with the numerical operating parameters 436 of the medical procedures monitored by the power cord server 108. In some embodiments, in response to user selection of other items in device overview 508, user interface 500 displays additional information on information display area 506 (e.g., one or more items received with message 130). is refreshed to display the numerical operating parameters 436). In some embodiments, message 130 may include numerical operating parameters 436 for each medical procedure, but none of the parameters 436 are displayed for each individual procedure or in an aggregated context. Rather, the information display area 506 focuses on displaying a statistical summary of medical procedures collected based on predefined criteria (e.g., displaying the total number of medical procedures 508A and the number of device events 508E). can be applied.

Referring to FIG. 5B, in response to selecting device map affordance 504B, user interface 520 is displayed as shown in FIG. 5B. Information display area 506 displays a map 522 showing the distribution of medical devices 102 from which medical procedure power profiles 120 were collected, and a list 524 of recent location events. Each event in list 524 is described with device identification, event date, event time, device type, and location information. The content displayed in the information display area 506 of the user interface 520 may include numerical operating parameters 436 of the associated medical procedure. In some embodiments not shown in FIG. 5B, the information display area 506 of the user interface 520 includes a subset of numerical operating parameters 436 of the associated medical procedure. For example, in response to selecting one of the recent location events in list 524, user interface 520 selects one or more numerical operating parameters 436 of the medical procedure associated with the selected recent location event. refreshed to display details of the selected recent location event.

Referring to FIG. 5C, user interface 540 is loaded within a medical device application (eg, application 630 in FIG. 6A or 6B) executed by an electronic device (eg, medical device 102). Medical device applications may be executed offline or in conjunction with medical device server 114. A primary function of a medical device application is to facilitate the performance of a medical procedure (eg, before, during, or after the procedure). In this example, the user interface 540 includes a first area 542 for displaying key medical parameters, a second area 544 for adjusting treatment settings, and a third area 544 for visually presenting medical tools. area 546 and a fourth area 548 for directly adjusting some key settings. The medical device application includes a power cord plug-in program (eg, program 632 in FIG. 6A or FIG. 6B) that executes in conjunction with a power cord server 108 that is different from the medical device server 114 associated with the medical device application. The power cord plug-in program is configured to display some or all of the messages 130 received from the power cord server 108 on the medical device application user interface 540. In some embodiments, message 130 is displayed in a dedicated area of user interface 540, such as a fixed area of a medical device application. Alternatively, in some embodiments, such as shown in FIG. 5C, message 130 is overlaid on any of regions 542-548 after a predefined duration or in response to a user action. It is displayed in a pop-up window 550 of the user interface 540 that disappears. In this example, message 130 is a notification that "This device has been used in 100 medical events in the past month and is used more frequently than 90% of devices of its type in the United States."

In some embodiments, a medical device 102 displaying one of the user interfaces 500, 520, or 540 is powered on to power its medical procedure while subscribing to data services provided by the power cord server 108. Code device 106 is used to report its own power profile 120. Conversely, in some embodiments, a medical device 102 displaying any of the user interfaces 500, 520, or 540 subscribes only to data services provided by the power cord server 108. However, medical device 102 does not use power cord device 106 to power its medical procedure or to report its own power profile 120. In addition, in some embodiments not shown, the medical device 102 while still using the power cord device 106 to power its medical procedure or to report its own power profile 120. , does not subscribe to the data service provided by the power cord server 108. Optionally, power cord server 108 is configured to separately use power cord device 106 and subscribe to data services. In some embodiments, power cord server 108 is configured to associate use of power cord device 106 with subscription to data services, thereby automatically providing data services to users of power cord device 106. be done. Power cord server 108 may further extend data services to other subscribers who do not use power cord device 106.

FIG. 6A is a block diagram of an exemplary medical device 102 for performing a medical procedure, according to some embodiments. Medical device 102 typically includes one or more processing units (CPUs) 602A, one or more network interfaces 604A, memory 606A, and interconnects these components (sometimes referred to as a chipset). and one or more communication buses 608A for connecting. Medical device 102 includes one or more user interface devices 610A. User interface device 610A includes one or more devices that facilitate user input, such as a keyboard, mouse, voice command input unit or microphone, touch screen display, touch-sensitive input pad, gesture capture camera, or other input buttons or controls. Including input device 612A. Additionally, in some embodiments, medical device 102 uses a microphone and voice recognition, or a camera and gesture recognition to supplement or replace a keyboard. In some embodiments, the one or more input devices 612A include, for example, one or more cameras, scanners, or photosensor units to capture images of graphic serial codes printed on the electronic device. include. Medical device 102 is capable of presenting user interfaces (e.g., interfaces 500, 520, and 540 in FIGS. 5A-5C) and display content, including one or more speakers and/or one or more visual displays. Also includes one or more output devices 614A. User interface device 610A further includes several transducer portions for performing medical procedures. For example, if medical device 102 is a medical imaging device, input device 612A of medical device 102 includes a medical sensor configured to collect medical information during a medical procedure.

Memory 606A includes high speed random access memory such as DRAM, SRAM, DDR RAM, or other random access solid state memory device. In some embodiments, the memory includes one or more magnetic disk storage devices, one or more optical disk storage devices, one or more flash memory devices, or one or more other non-volatile solid state storage devices. Contains non-volatile memory such as devices. In some embodiments, memory 606A includes one or more storage devices located remotely from one or more processing units 602A. Memory 606A, or alternatively non-volatile memory within memory 606A, includes non-transitory computer-readable storage media. In some embodiments, memory 606A, or a non-transitory computer-readable storage medium of memory 606A, stores the following programs, modules, and data structures, or a subset or superset thereof.
- Operating system 616A, which contains procedures for handling various basic system services and performing hardware-dependent tasks.
each medical device 102 via one or more network interfaces 604A (wired or wireless) and one or more communication networks 110, such as the Internet, other wide area networks, local area networks, metropolitan area networks; A network communication module 618A that connects the device to other devices (e.g., medical device server 114, power cord server 108, client device 112).
Information at each medical device 102 (e.g., graphical user interfaces for applications 626A, widgets, websites and their web pages, and/or a presentation module 620A that enables the presentation of games, audio, and/or video content);
- An input processing module 622A that detects one or more user inputs or interactions from one of the one or more input devices 612A and interprets the detected inputs or interactions.
- A web page for navigating, requesting (e.g., via HTTP), and displaying a website and its web pages, including a web interface for logging into a user account associated with a medical device 102 or other electronic device; Browser module 624A. Web browser module 624A also controls the medical or electronic device, if one is associated with the user account, and edits and reviews settings and data associated with the user account.
- One or more user applications 626A running on the medical device 102.
- A medical procedure module 628A that performs a medical procedure on the medical device 102.
- A medical device application 630A that performs a medical procedure via a medical procedure module 628A. Medical device application 630A includes a power cord plug-in program 632A for receiving and presenting information regarding power usage of different medical devices distributed across different medical facilities within medical device application 630A.
- A power cord application 634A that is specialized for receiving information from the power cord server 108 regarding power usage of different medical devices distributed across different medical facilities and presenting such information within the power cord application 634A.
-Medical device data 636A including:
o Device settings 638A that include common device settings for the medical device 102 (e.g., service layer, device model, storage capacity, processing power, communication capabilities, and/or medical procedure settings).
o User account information for one or more user applications 626A, medical device applications 630A, and power cord applications 634A (e.g., username, security questions, account history data, user preferences, and predefined account settings) 640A.
o Historical medical data 642 associated with medical procedures previously performed by the medical device 102.
o A message 130 specifying a medical procedure and corresponding numerical operating parameters 436. Messages 130 are generated and provided by power cord server 108 based on power profiles 120 collected from various medical devices 102, which may or may not include medical devices 102 themselves.

Each of the elements identified above may be stored in one or more of the aforementioned memory devices and corresponds to a set of instructions for performing the functions described above. The modules or programs (i.e., sets of instructions) identified above need not be implemented as separate software programs, procedures, modules, or data structures, and therefore various subsets of these modules may be implemented in different implementations. may be joined in form or otherwise rearranged. In some embodiments, memory 606A stores a subset of the modules and data structures identified above. In some embodiments, memory 606A stores additional modules and data structures not described above.

FIG. 6B is a block diagram of an exemplary client device 112 for representing information of a medical procedure performed on a separate medical device 102, according to some embodiments. Examples of client devices 112 include, but are not limited to, desktop computers, laptop computers, tablet computers, and mobile phones. Client device 112 typically has one or more processing units (CPUs) 602B, one or more network interfaces 604B, memory 606B, and interconnects these components (sometimes called a chipset). and one or more communication buses 608B for connecting. Client device 112 includes one or more user interface devices 610B. User interface device 610B includes one or more devices that facilitate user input, such as a keyboard, mouse, voice command input unit or microphone, touch screen display, touch-sensitive input pad, gesture capture camera, or other input buttons or controls. input device 612B. Additionally, in some embodiments, medical device 102 uses a microphone and voice recognition, or a camera and gesture recognition to supplement or replace a keyboard. In some embodiments, the one or more input devices 612B include, for example, one or more cameras, scanners, or photosensor units for capturing images of graphic serial codes printed on the electronic device. include. Client device 112 is capable of presenting a user interface (e.g., interfaces 500, 520, and 540 in FIGS. 5A-5C) and display content, including one or more speakers and/or one or more visual displays. Also includes one or more output devices 614B.

Memory 606B includes high speed random access memory such as DRAM, SRAM, DDR RAM, or other random access solid state memory device. In some embodiments, the memory includes one or more magnetic disk storage devices, one or more optical disk storage devices, one or more flash memory devices, or one or more other non-volatile solid state storage devices. Contains non-volatile memory such as devices. In some embodiments, memory 606B includes one or more storage devices located remotely from one or more processing units 602B. Memory 606B, or alternatively non-volatile memory within memory 606B, includes non-transitory computer-readable storage media. In some embodiments, memory 606B, or a non-transitory computer-readable storage medium of memory 606B, stores the following programs, modules, and data structures, or a subset or superset thereof.
- Operating system 616B, which contains procedures for handling various basic system services and performing hardware-dependent tasks.
each client device 112 via one or more network interfaces 604B (wired or wireless) and one or more communication networks 110, such as the Internet, other wide area networks, local area networks, metropolitan area networks; A network communication module 618B that connects the power cord server 108 to other devices (e.g., the power cord server 108, the medical device server 114, and/or the client device 112).
Information (e.g., graphical user interfaces for applications 626B, widgets, websites and their web pages, and/or a presentation module 620B that enables presentation of games, audio, and/or video content);
- An input processing module 622B that detects one or more user inputs or interactions from one of the one or more input devices 612B and interprets the detected inputs or interactions.
- navigate and request (e.g., via HTTP) a website and its web pages, including a web interface for logging into a user account associated with the client device 112 or other medical device or client device; Web browser module 624B to display. Web browser module 624B also controls the medical device or client device, if one is associated with the user account, and edits and reviews settings and data associated with the user account.
one or more user applications 626B executed by the client device 112 (e.g., games, social network applications, smart home applications, and/or other medical or client devices that control and are captured by such devices); other web-based or non-web-based applications for reviewing the data collected).
- A medical device application 630B that controls a medical procedure performed remotely by the medical device 102. Medical device application 630B includes a power cord plug-in program 632B for receiving and presenting information regarding power usage of different medical devices distributed across different medical facilities within medical device application 630B.
- A power cord application 634B that is specialized for receiving information from the power cord server 108 regarding power usage of different medical devices distributed across different medical facilities and presenting such information within the power cord application 634B.
- Client data 636B including:
o Device settings 638B, including common device settings for client device 112 (eg, service layer, device model, storage capacity, processing power, communication capabilities, and/or medical procedure settings).
o User account information 640B for one or more user applications 626B, medical device applications 630B, and power cord applications 634B (e.g., username, security questions, account history data, user preferences, and predefined account settings) ).
o A message 130 specifying a medical procedure and corresponding numerical operating parameters 436. Messages are generated and provided by power cord server 108 based on power profiles 120 collected from various medical devices 102.

Each of the elements identified above may be stored in one or more of the aforementioned memory devices and corresponds to a set of instructions for performing the functions described above. The modules or programs (i.e., sets of instructions) identified above need not be implemented as separate software programs, procedures, modules, or data structures, and therefore various subsets of these modules may be implemented in different implementations. may be joined in form or otherwise rearranged. In some embodiments, memory 606B stores a subset of the modules and data structures identified above. In some embodiments, memory 606B stores additional modules and data structures not described above.

FIG. 6C is a block diagram of a power cord server 108 for collecting power profiles 120 and providing medical treatment information to a user, according to some embodiments. Examples of power cord servers 108 include, but are not limited to, desktop computers, laptop computers, tablet computers, or mobile phones. Power cord server 108 typically includes one or more processing units (CPUs) 602C, one or more network interfaces 604C, memory 606C, and these components (sometimes referred to as chipsets). and one or more communication buses 608C for interconnecting. Power cord server 108 includes one or more user interface devices 610C. The user interface device 610C includes one or more devices that facilitate user input, such as a keyboard, mouse, voice command input unit or microphone, touch screen display, touch-sensitive input pad, gesture capture camera, or other input buttons or controls. Including input device 612C. Additionally, in some embodiments, medical device 102 uses a microphone and voice recognition, or a camera and gesture recognition to supplement or replace a keyboard. In some embodiments, the one or more input devices 612C include, for example, one or more cameras, scanners, or photosensor units for capturing images of graphic serial codes printed on the electronic device. include. Power cord server 108 also includes one or more output devices 614C that enable presentation of a user interface and display content, including one or more speakers and/or one or more visual displays.

Memory 606C includes high speed random access memory such as DRAM, SRAM, DDR RAM, or other random access solid state memory device. In some embodiments, the memory includes one or more magnetic disk storage devices, one or more optical disk storage devices, one or more flash memory devices, or one or more other non-volatile solid state storage devices. Contains non-volatile memory such as devices. In some embodiments, memory 606C includes one or more storage devices located remotely from one or more processing units 602C. Memory 606C, or alternatively non-volatile memory within memory 606C, includes non-transitory computer-readable storage media. In some embodiments, memory 606C, or a non-transitory computer-readable storage medium of memory 606C, stores the following programs, modules, and data structures, or a subset or superset thereof.
- Operating System 616C, which contains procedures for handling various basic system services and performing hardware-dependent tasks.
Power cord server 108 via one or more network interfaces 604C (wired or wireless) and one or more communication networks 110, such as the Internet, other wide area networks, local area networks, metropolitan area networks, etc. a network communication module 618C that connects the power cord device 106 to other devices (e.g., power cord device 106, medical device 102, and/or client device 112).
information (e.g., graphical user interfaces for applications 626C, widgets, websites and their web pages, audio and and/or video content).
- An input processing module 622C that detects one or more inputs or interactions from one of the one or more input devices 612C and interprets the detected inputs or interactions.
Navigating, requesting (e.g., via HTTP), displaying, and associating a website and its web pages with a user account, including a web interface for logging into a user account associated with the power cord server 108; a web browser module 624C that controls predefined criteria (e.g., including time and location restrictions) for the power cord device 106 and edits and reviews settings and data associated with the user account, if any;
One or more user applications 626C executed by the power cord server 108 (e.g., control predefined criteria, such as time and location restrictions, of the power cord device 106, and web-based or non-web-based applications for reviewing captured data).
- (1) a power cord plug-in module 632C that enables display in the medical device application 630 of information regarding power usage of different medical devices 102 distributed across different medical facilities; and/or (2) of the different medical devices 102. a server-side module that includes a power cord application 634C specialized for transmitting information regarding power usage to a client-side power cord application 634A or 634B and presenting such information at the client-side power cord application 634A or 634B; 644.
・Server data 636C including:
o Device settings 638C, including common device settings for power cord server 108 (e.g., service layer, device model, storage capacity, processing power, communication capabilities, and/or medical procedure settings).
o User account information 640C for one or more user applications 626C, power cord plug-in module 632C, and power cord application 634C (e.g., username, security questions, account history data, user preferences, and account settings).
o Power profile data 120 collected from different medical devices 102.
o Power data characteristics 434 extracted from power profile data 120 related to a mode or operating state of medical device 102.
o including, but not limited to, the device type of the medical device 102, one of an operating mode 420 or an idle mode 418, an operating state 422-432, a type of each medical procedure, and a numerical operating parameter 436 for each medical procedure; medical procedure data 646 determined based on power data characteristics 434;
o Power threshold 438 for deriving medical procedure data 646 from power data characteristics 434 extracted from power profile 120.
o A message 130 specifying a medical procedure and corresponding numerical operating parameters 436.

Each of the elements identified above may be stored in one or more of the aforementioned memory devices and corresponds to a set of instructions for performing the functions described above. The modules or programs (i.e., sets of instructions) identified above need not be implemented as separate software programs, procedures, modules, or data structures, and therefore various subsets of these modules may be implemented in different implementations. may be joined in form or otherwise rearranged. In some embodiments, memory 606C stores a subset of the modules and data structures identified above. In some embodiments, memory 606C stores additional modules and data structures not described above.

7A-7D provide a flow diagram of a data management method 700 implemented at power cord server 108, according to some embodiments. In some embodiments, method 700 is managed by instructions stored in a non-transitory computer-readable storage medium and executed by one or more processors of power cord server 108. Each of the operations shown in FIGS. 7A-7D may correspond to instructions stored within the computer memory or computer-readable storage medium (eg, memory 606C in FIG. 6C) of power cord server 108. Computer-readable storage media may include magnetic or optical disk storage devices, solid state storage devices such as flash memory, or other non-volatile memory devices. Computer-readable instructions stored on a computer-readable storage medium may include one or more of source code, assembly language code, object code, or other instruction formats that are interpreted by one or more processors. Some operations in method 700 may be combined and/or the order of some operations may be changed. In some embodiments, method 700 is managed by instructions stored within power cord plug-in module 632B or server-side module 644 for power cord application 634B.

Power cord server 108 hosts a centralized power data management system for multiple remote medical devices 102 located at one or more medical facilities. In this centralized power data management system, a power cord server 108 is communicatively coupled to a plurality of power cables 104 via one or more wide area networks (WANs) 110 (702). Each of the power cables 104 includes a power cord device 106 (704) and is configured to be electrically connected to and power a respective one of the plurality of remote medical devices 102. The plurality of remote medical devices 102 includes a first medical device 102A powered by a first power cable 104A that includes a first cord device 106A (706). In some embodiments, the one or more WANs 110 include a cellular network, and the plurality of power cables 104 connect the power cords to the server via the cellular network without accessing any local network devices or local area networks. 108. In some embodiments, communications over the cellular network are private and encrypted.

Power cord server 108 receives power profile 120 from first cord device 106A (708). Power profile 120 includes a plurality of power data characteristics 434 that measure power delivered to first medical device 102A while first medical device 102A performs a medical procedure (710). In some embodiments, the power profile 120 is streamed in real time from the first cord device 106A of the first power cable 104A while the first medical device 102A is performing the medical procedure (712). . Alternatively, in some embodiments, the power profile 120 is received from the first cord device 106A of the first power cable 104A after the first medical device 102A has completed performing the medical procedure ( 714). Additionally or alternatively, a batch of power profiles from the first code device 106A of the first power cable 104A is received in a single transmission according to a first reporting schedule (e.g., daily or weekly). 716). The batch includes a power profile 120 along with one or more additional power profiles 120 of one or more additional medical procedures, each of which was previously performed on the first medical device 102A. In some embodiments, the power profile 120 is configured such that the power profile 120 of the medical procedure is based on certain predefined reporting criteria (e.g., the average active power 406 reaches a predefined threshold, or the number of pulses detected in the active power 406) is transmitted to the power cord server 108.

After receiving the power profile 120, the power cord server 108 uses the power profile 120 to identify the performed medical procedure, including one or more numerical operating parameters 436 of the performed medical procedure ( 718). In some embodiments, the power profile includes a subset of a system idle state 424, a system wake-up state 422, a therapy initiation state 426, one or more therapy states 428, a therapy idle state 430, and a power off state 432. Corresponds to multiple operating states 422 to 432 (720). Power cord server 108 identifies (722) a subset of multiple operating states 422-432 of the performed medical procedure. Further, in some embodiments, the one or more treatment states 428 include a first treatment state 428A in which the power pulse train 450A is applied (724), and the plurality of power data characteristics 434 are the power pulse train 450A. Includes duration, frequency, power pattern, and average power peak value. Power cord server 108 determines (726) one or more numerical operating parameters 436 of the performed treatment procedure based on the subset of power data characteristics 434 corresponding to first treatment state 428A. Additionally, in some embodiments, each of the plurality of operating states 422-432 is defined according to at least one power threshold 438 associated with a respective subset of power data characteristics 434. Power cord server 108 determines and adjusts at least one power threshold 438 associated with each of the plurality of operating states 422-432 based on deep learning techniques. Additionally, in some embodiments, each of the plurality of operating states 422-432 is recognized or classified from the power profile 120 using deep learning techniques.

Referring to FIG. 4A, in some embodiments, power cord server 108 divides power profile 120 into multiple power intervals (728). For each power interval, power cord server 108 determines whether the respective power interval includes a power pulse train 450 (730). If each power interval includes a power pulse train 450, the system determines one or more of the duration, pulse pattern, frequency, and average power peak value of the power pulse train 450 (732). This is a respective subset of power data characteristics 434 corresponding to a respective interval. If the respective power interval does not include the power pulse train 450, the system determines (734) one or more of average current, average voltage, average active power, and reactive power. This is a respective subset of power data characteristics 434 corresponding to a respective interval.

In some embodiments, for each power interval, power cord server 108 compares a respective subset of power data characteristics 434 corresponding to the respective interval to at least a respective power threshold 438. If the comparison for the first power interval satisfies the first operating state association criteria, the power cord server associates the first operating state with the first power interval and the power data characteristic corresponding to the first power interval. One or more numerical operating parameters 436 of the performed medical procedure are determined based on each subset of 434. Additionally, in some embodiments, each power threshold 438 associated with the first operating state is determined or adjusted based on the first deep learning technique.

Alternatively, in some embodiments, each of the subsets of power intervals (e.g., the intervals corresponding to power pulse trains 450A and 450B in FIG. 4A) may be configured to have a respective power interval in operating mode 420, idle mode 418, Directly analyzed using a deep learning model for classification as one of a plurality of operating conditions 422-432 and/or as one of a plurality of medical procedures. In some embodiments, deep learning models are trained in a supervised manner based on labeled training data profiles 120. In some embodiments, a deep learning model is trained in an unsupervised manner using power profiles 120 collected from medical device 102. For example, as the deep learning model processes more power profiles 120, the deep learning model can more accurately and efficiently classify power intervals.

In some embodiments, one or more numerical operating parameters 436 include one or more first numerical operating parameters. The power cord server 108 measures the power supplied from the second cord device 106B of the second power cable 104 to the second medical device 102' while the second medical device 102' performs the same medical procedure. A second power profile 120' that includes a plurality of second power data characteristics 434' is received (736). The second power profile is used to identify one or more second numerical operating parameters 436' of the same medical procedure (738). Additionally, in some embodiments, the power cord server 108 derives (740) a therapeutic power signature 440 for the same medical procedure based on at least the first and second numerical operating parameters 436 and 436'; A message 130 including a treatment power signature 440 is generated (742) based on the first and second numerical operating parameters of the same medical procedure. In addition, in some embodiments, the second electronic device that receives the message 130 determines whether a subsequent medical procedure is performed by the second electronic device based on the therapeutic power signature 440 received in the message 130. (744).

In some embodiments, power profile 120 includes a first power profile and one or more numerical operating parameters 436 include one or more first numerical operating parameters. The power cord server 108 receives (746) a plurality of third power profiles 120" from a plurality of third power cables 104C. Each of the plurality of third power profiles 120" is connected to a respective third medical a plurality of third power data characteristics 434'' that measure the current supplied to each third medical device 102C while the device 102C is performing a respective third medical procedure. Each of the three power profiles 120" is used to identify (748) a respective third medical procedure, including one or more third numerical operating parameters 436" of the respective third medical procedure. The message 130 is based on one or more first numerical operating parameters 436 of the performed medical procedure and a third numerical operating parameter 436'' corresponding to the plurality of third power profiles 120''. Additionally, in some embodiments, the first power profile 120 and the plurality of third power profiles 120" conform to geographic or temporal constraints (752); Messages 130 are generated based on geographic or temporal constraints.

Power cord server 108 sends message 130 to the second electronic device for display on the second electronic device's user interface (eg, the interface in FIGS. 5A-5C) (754). Message 130 specifies the medical procedure performed and one or more numerical operating parameters 436. In some embodiments, message 130 includes an alert, notification, report, or instruction regarding the medical procedure that was performed (756). In some embodiments, the second electronic device includes the first medical device 102, and the second electronic device is configured to run a power cord application 634A that includes a user interface. Power cord server 108 enables display of message 130 on the user interface of power cord application 634A of first medical device 102 (758). Alternatively, in some embodiments, the second electronic device includes the first medical device 102, the first medical device configured to run a medical device application 630A that includes a user interface. Ru. The power cord server enables display of message 130 on the user interface of medical device application 630A (760). Medical device application 630A is configured to perform a medical procedure. In some embodiments, the medical device application has a power cord plug-in program 632A running on the power cord server 108 to present the message 130.

Alternatively, in some embodiments, the second electronic device (e.g., a mobile phone) is separate from the first medical device 102, and the second electronic device has a power cord that includes a user interface. Configured to run application 634B. Power cord server 108 enables display of messages on the user interface of second electronic device power cord application 634B (762). Power cord application 634B is executed in conjunction with power cord server 108. The second electronic device may have its own medical device application 630B.

Additionally and alternatively, in some embodiments, the second electronic device (e.g., a mobile phone) is separate from the first medical device, and the second electronic device The medical device application 630A is configured to execute a medical device application 630A that includes a user interface to perform a medical procedure. Power cord server 108 enables display of message 130 on a user interface at medical device application 630A of the second electronic device (764). In some embodiments, the medical device application has a power cord plug-in program 632B running on the power cord server 108 to present the message 130.

It is noted that the power cord application is separate from the medical device application 630A that runs in conjunction with the power cord server 108 and is configured to perform the medical procedure. In some embodiments, the medical device application is online while the medical procedure is being performed and is executed in conjunction with a medical device server 114 that is separate from the power cord server 108. In some embodiments, medical device application 630A is offline while the medical procedure is being performed.

In some embodiments, a message is generated according to a second reporting schedule and sent to a second electronic device (766). In some embodiments, if one or more numerical operating parameters of the performed medical procedure meet the second reporting criteria, a message is ad hoc generated and sent to the second electronic device (768 ).

It should be understood that the particular order in which the operations in FIGS. 7A-7D are described is merely exemplary and is not intended to indicate that the described order is the only order in which the operations may be performed. It is. Those skilled in the art will recognize various ways to manage power data as described herein. In addition, it should be noted that the details described above with respect to FIGS. 1-6C are also applicable in a similar manner to the method 700 described above with respect to FIGS. 7A-7D. For the sake of brevity, these details will not be repeated here.

In one or more examples, the described functionality may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functions may be stored on or transmitted as one or more instructions or code on a computer-readable medium and executed by a hardware-based processing unit. Computer-readable media refers to a computer-readable storage medium that corresponds to a tangible medium such as a data storage medium or communication including any medium that facilitates transfer of a computer program from one place to another (e.g. according to a communication protocol). may include a medium. Thus, computer-readable media generally may correspond to (1) non-transitory, tangible computer-readable storage media, or (2) communication media such as a signal or carrier wave. A data storage medium is any device that can be accessed by one or more computers or one or more processors to obtain instructions, code, and/or data structures for implementation of the embodiments described in this application. can be any available medium. A computer program product may include a computer readable medium.

The terminology used in the description of embodiments herein is for the purpose of describing particular embodiments only and is not intended to limit the scope of the claims. As used in the description of the embodiments and the appended claims, the singular forms "a," "an," and "the" include the plural forms unless the context clearly dictates otherwise. is intended. It will also be understood that the term "and/or" as used herein refers to and includes any and all possible combinations of one or more of the associated listed items. The terms "comprising" and/or "comprising", as used herein, specify the presence of the recited feature, element, and/or component, but with one or more other features. It will be further understood that this does not exclude the presence or addition of elements, components and/or groups thereof.

It is also understood that although the terms first and second may be used herein to describe various elements, these elements should not be limited by these terms. Good morning. These terms are only used to distinguish one element from another. For example, a first electrode can be referred to as a second electrode, and a second electrode can be referred to as a first electrode, without departing from the scope of the embodiments. Although the first electrode and the second electrode are both electrodes, they are not the same electrode.

The description of this application is presented for purposes of illustration and description and is not intended to be exhaustive or to limit the invention to the invention in the form disclosed. Many modifications, variations, and alternative embodiments will be apparent to those skilled in the art having the benefit of the teachings presented in the foregoing description and associated drawings. The embodiments are presented in order to best explain the principles of the invention, its practical application, and to enable those skilled in the art to understand the invention with respect to the various embodiments and with various modifications to suit the particular application contemplated. The underlying principles and various embodiments are described to enable you to best utilize them. Therefore, the claims should not be limited to the particular examples of disclosed embodiments. Modifications and other embodiments are intended to be within the scope of the following claims.

100 Data Management Environment
102 medical device, medical machine or device, first medical device, remote medical device
102' Second medical device
102A First Medical Device
102B Second medical device
102C Third medical device
104 Power cable, power cord, second power cable
104A 1st power cable
104B 2nd power cable
104C 3rd power cable
106 Power cord device, cord device
106A power cord device, 1st cord device
106B Second code device
106C 3rd power cable, 3rd medical device
108 power cord server, smart cord server, server, cord server, power cord system
110 Communication Network, Wide Area Network (WAN)
112 Client device
114 Medical device server, server
120 power profiles, power profile data, labeled training data profiles
120' 2nd power profile
120" 3rd power profile
130 messages
200 Operating environment
202 AC-DC converter (ADC)
204 Relay
206 battery
208 Battery Management System
210 Power Monitor Module
212 Flash storage, flash memory
214 position module
216 Cellular Module
218 Antenna
220 connector
222 Processor, processing unit
224 network interface
226 Memory
228 communication bus
230 Input Device
232 Output device
234 Operating System
236 Network Communication Module
238 Data Collection Module
240 Data Preprocessing Module
242 Data Reporting Module
244 Database
248 Code information and settings
402 Root mean square (RMS) value of current, power parameter
404 RMS value of voltage, power parameters
406 Active power, power parameters
408A reactive power, power parameters
408B Reactive power, power parameters
410 Apparent power, power parameters
412 Power factor, power parameters
414 Frequency, power parameters
416 Die temperature, power parameters
418 Idle mode
420 operating mode
422 System start status, operating status
424 System idle
424A System idle state, operating state
424B System idle state, operating state
426 Treatment start state, operating state
428 Treatment status
428A treatment state, first treatment state, operating state
428B Treatment state, second treatment state, operating state
430 Therapy idle state, operating state
432 Power off state, operating state
434 Power data characteristics
434' Second power data characteristic
434" 3rd power data characteristic
436 Numerical operating parameter, first numerical operating parameter
436' Second numerical operating parameter
436" Third numerical operating parameter
438 Power Threshold
440 Treatment Power Signature
442 Geographic distribution
450 power pulse train
450A power pulse train
450B power pulse train
500 User Interface
502 Menu area
504 Affordance
504A Device Overview Affordances
504B Device Map Affordance
504C Reporting Affordance
504D Consumables Order Affordance
505E Device Management Affordances
505F User Profile Affordance
505G Error Affordance
506 Information display area
508 Device Overview
508A Total number of medical procedures (i.e., treatments)
508B Number of users of power data
508C Total treatment time for medical procedures
508D Number of medical devices
508E Number of device events
510 Plot
512 Additional Content
512A Treatment Type
512B Recording the latest events
512C List of Most Active Physicians
520 User Interface
522 maps
524 list
540 User Interface
542 first area, area
544 second realm, realm
546 third realm, realm
548 fourth realm, realm
602A processing unit (CPU), processing unit
602B Processing unit (CPU), processing unit
602C processing unit (CPU), processing unit
604A network interface
604B network interface
604C network interface
606A memory
606B memory
606C memory
608A communication bus
608B communication bus
608C communication bus
610A User Interface Device
610B User Interface Device
610C User Interface Device
612A input device
612B input device
612C input device
614A output device
614B Output Device
614C output device
616A Operating System
616B Operating System
616C Operating System
618A Network Communication Module
618B Network Communication Module
618C Network Communication Module
620A presentation module
620B presentation module
620C presentation module
622A Input Processing Module
622B Input Processing Module
622C Input Processing Module
624A Web Browser Module
624B Web Browser Module
624C Web Browser Module
626A Application, User Application
626B User Application
626C User Application
628A Medical Procedure Module
630 applications, medical device applications
630A applications, medical device applications
630B Medical Device Application
632 programs
632A program, power cord plug-in program
632B power cord plug-in program
632C Power Cord Plug-in Module
634A application, power cord application
634B application, power cord application
634C application, power cord application
636A Medical Device Data
636B Client data
636C server data
638A device settings
638B Device Settings
638C device settings
640A User Account Information
640B User account information
640C User account information
642 Historical Medical Data
644 Server side module
646 Medical treatment data

Claims (25)

A data management method, comprising:
In a server system hosting a centralized power data management system for multiple remote medical devices located in one or more medical facilities,
communicatively coupling to a plurality of power cables via one or more wide area networks (WANs), each of the power cables including a cord device to connect one of the plurality of remote medical devices; each of the plurality of remote medical devices includes a first medical device electrically coupled to and configured to power the plurality of remote medical devices powered by a first power cable including a first cord device; and,
receiving a power profile from the first coded device, the power profile measuring power delivered to the first medical device while the first medical device is performing a medical procedure; including a plurality of power data characteristics to
using the power profile to identify the performed medical procedure, including one or more numerical operating parameters of the performed medical procedure;
sending a message to the second electronic device for display on a user interface of the second electronic device, the message including the medical procedure performed and the one or more numeric values; A data management method comprising steps for specifying operating parameters. The power profile corresponds to a plurality of operating states, including a plurality of a system idle state, a system wake-up state, a therapy start state, one or more therapy states, a therapy idle state, and a power off state, and the power profile The step of identifying a medical procedure that
further comprising identifying a subset of the plurality of operating states of the performed medical procedure;
The method according to claim 1. The one or more treatment states include a first treatment state in which a power pulse train is applied, and the plurality of power data characteristics include a duration, frequency, power pattern, and average power peak value of the power pulse train. The method includes:
further comprising determining the one or more numerical operating parameters of the performed medical procedure based on the subset of power data characteristics corresponding to the first treatment condition;
The method according to claim 2. each of the plurality of operating states is defined according to at least one power threshold associated with the respective subset of power data characteristics, the method comprising:
further comprising determining and adjusting the at least one power threshold associated with each of the plurality of operating states based on deep learning techniques;
The method according to claim 2. using the power profile to identify the medical procedure performed;
dividing the power profile into multiple power intervals;
For each of the power intervals,
determining whether each said power interval includes a train of power pulses;
one or more of the duration, pulse pattern, frequency, and average power peak value of the power pulse train in accordance with the determination that each said power interval includes a power pulse train, and the power data corresponding to each said interval; determining as each subset of the characteristics;
In accordance with a determination that each said power interval does not include a power pulse train, one or more of average current, average voltage, average active power, and reactive power of said power data characteristic corresponding to said respective said interval is determined. and determining a subset of each of the
The method according to claim 1. using the power profile to identify the medical procedure performed;
For each of the power intervals, comparing the respective subset of the power data characteristics corresponding to the respective interval to at least a respective power threshold;
associating the first operating state with the first power interval according to a determination that the comparison for the first power interval satisfies a first operating state association criterion;
determining the one or more numerical operating parameters of the performed medical procedure based on the respective subsets of the power data characteristics corresponding to the first power interval;
6. The method according to claim 5. 7. The method of claim 6, further comprising determining and adjusting the respective power thresholds associated with the first operating state based on a first deep learning technique. the one or more numerical operating parameters include one or more first numerical operating parameters, and the method comprises:
a plurality of second power data characteristics measuring power delivered from a second cord device of a second power cable to said second medical device while said second medical device is performing the same medical procedure; receiving a second power profile comprising;
using the second power profile to identify one or more second numerical operating parameters of the same medical procedure;
the message is generated based on the first and second numerical operating parameters of the same medical procedure;
8. A method according to any one of claims 1 to 7. deriving a therapeutic power signature for the same medical procedure based on at least the first and second numerical operating parameters;
9. The method of claim 8, further comprising: generating the message including the therapy power signature. 10. The second electronic device is configured to adjust a subsequent medical procedure performed by the second electronic device based on the therapeutic power signature received in the message. the method of. the power profile includes a first power profile, the one or more numerical operating parameters include one or more first numerical operating parameters, and the method includes:
receiving a plurality of third power profiles from a plurality of third power cables, each of the plurality of third power profiles being configured to enable a respective third medical device to perform a respective third medical procedure; each of the plurality of third power data characteristics measuring the power delivered to the respective third medical device while performing the step of
using each of the plurality of third power profiles to identify the respective third medical procedure, including one or more third numerical operating parameters of the respective third medical procedure; further comprising a step;
The message is generated based on the one or more first numerical operating parameters of the performed medical procedure and the third numerical operating parameter corresponding to the plurality of third power profiles. ,
11. A method according to any one of claims 1 to 10. 12. The first power profile and the plurality of third power profiles conform to geographic or temporal constraints, and the message is generated based on the geographic or temporal constraints. the method of. 13. The method of any one of claims 1 to 12, wherein the message includes a warning, notification, report, or instruction regarding the performed medical procedure. the second electronic device includes the first medical device, the second electronic device is configured to run a power cord application including the user interface, and the method includes:
further comprising enabling display of the message on the user interface of the power cord application of the first medical device, the power cord application executing in conjunction with the server system to perform the medical procedure. is separate from the medical device application configured to
14. A method according to any one of claims 1 to 13. the second electronic device includes the first medical device, the first medical device is configured to run a medical device application including the user interface, and the method includes:
further comprising enabling display of the message on the user interface of the medical device application, the medical device application configured to perform the medical process;
15. A method according to any one of claims 1 to 14. the second electronic device is separate from the first medical device, the second electronic device is configured to run a power cord application that includes the user interface, and the method includes:
further comprising enabling display of the message on the user interface of the power cord application of the second electronic device, the power cord application being executed in conjunction with the server system;
16. A method according to any one of claims 1 to 15. The second electronic device is separate from the first medical device, and the second electronic device runs a medical device application that includes the user interface to perform one or more medical procedures. The method is configured to perform:
further comprising enabling display of the message on the user interface in the medical device application of the second electronic device;
17. A method according to any one of claims 1 to 16. 18. Any of claims 1-17, wherein the power profile is streamed in real time from the first cord device of the first power cable while the first medical device is performing the medical procedure. The method described in paragraph 1. 18. Any one of claims 1-17, wherein the power profile is received from the first cord device of the first power cable after the first medical device has completed performing the medical procedure. The method described in. A batch of power profiles from the first cord device of the first power cable is received in a single transmission, and the batch includes one or more additional medical procedures. 18. The method according to any one of claims 1 to 17, comprising the power profile along with a power profile, each of the additional actions previously performed on the first medical device according to a first reporting schedule. Method. 21. A method according to any preceding claim, wherein the message is generated and sent to the second electronic device according to a second reporting schedule. 21. The message of claims 1-20, wherein the message is ad hoc generated and transmitted to the second electronic device in accordance with a determination that the one or more numerical operating parameters of the performed medical procedure meet reporting criteria. The method described in any one of the above. The one or more wide area networks (WAN) include a cellular network, and the plurality of power cables connect to the server system via the cellular network without accessing any local network devices or local area networks. 23. A method according to any one of claims 1 to 22, wherein the method is communicatively coupled. one or more processors;
24. A server system comprising: a memory storing one or more programs configured to be executed by the one or more processors, wherein the one or more programs are comprising instructions for carrying out the method according to any one of the preceding paragraphs;
server system. A non-transitory computer-readable medium storing one or more programs configured to be executed by one or more processors of a server system, the one or more programs from claim 1 24. A non-transitory computer-readable medium comprising instructions for performing the method of any one of 23.