Smart codes for medical applications

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

Technical Field

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

[0002] This application generally relates to a centralized power management system that collects, analyzes, and reports the power usage characteristics of distributed medical devices powered via a power cable.

Background Art

[0003] Medical devices are distributed across different medical facilities and often operate independently of other medical devices. Some medical device manufacturers provide medical device usage platforms to collect the 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. Since real-time data communication consumes local resources, poses a risk of tampering with ongoing medical procedures, and may degrade the performance of medical procedures, usage characteristics are preferably collected after the medical procedure is completed and transferred to the device usage platform. However, such delayed data transfers can easily be ignored or interrupted and also do not address concerns about leakage of private and confidential patient information stored on medical devices.

Summary of the Invention

Problems to be Solved by the Invention

[0004] To safely and efficiently manage the usage characteristics of different types of distributed medical devices, it is beneficial to develop a centralized data management mechanism. [Means for solving the problem]

[0005] This application describes embodiments relating to the use of a smart code device between a power outlet and a medical device to collect and report device usage characteristics related to a medical device while powering the medical device. The smart code device is part of a medical-grade power cable configured to operate with gauges compliant with the specifications of the medical device. In addition, the smart code device has one or more processors and memory for storing instructions, which are executed by the processors to collect power profiles (e.g., power, voltage, and current of the medical device) and report them to a centralized power data management platform. The platform applies data analysis algorithms (e.g., including deep learning techniques) to understand the power profiles collected from one or more medical devices and translates the power profiles into easily understandable information about the medical device and associated medical procedures for the parties involved. Specifically, based on the collected power profiles, the platform determines the range of device usage parameters and identifies the device mode or operating state of the medical device. The data is communicated between the smart code device and the centralized power data management platform via a secure, encrypted network (e.g., a private cellular network) without involving the medical device and without affecting the operation of the associated medical procedures.

[0006] In one embodiment, the data management method is implemented in a server system hosting a centralized power data management system for a plurality of remote medical devices located in one or more medical facilities. The method includes the step of being communicatively coupled to a plurality of power cables via one or more wide area networks (WANs). Each power cable includes a code device (i.e., a smart code device having one or more processors and memory). Each power cable is configured to be electrically coupled to and power supply to one of the plurality of remote medical devices. The plurality of remote medical devices include a first medical device powered by a first power cable containing a first code device. The method further includes the step of receiving a power profile from the first code device of the first power cable. The power profile includes a plurality of power data characteristics that measure the power supplied to the first medical device while the first medical device is performing a medical procedure. The method further includes the step of using the power profile to identify a medical procedure performed, which includes one or more numerical operating parameters of the medical procedure performed, and the step of sending a message to a second electronic device for display on the user interface of the second electronic device. 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 different from the first medical device.

[0007] According to another aspect of this application, a computer system (e.g., a server system) includes one or more processing units, memory, and a plurality of programs stored in memory. When executed by one or more processing units, the programs cause the computer system to perform a method for managing the medical device data described above.

[0008] According to another aspect of this application, a non-temporary computer-readable storage medium stores a plurality of programs configured for execution by a computer system having one or more processing units. When executed by one or more processing units, the programs cause the computer system to perform the methods for managing the medical device data described above.

[0009] To provide a further understanding of the embodiments, the accompanying drawings, which are included and incorporated herein and constitute part of this specification, illustrate the embodiments described and, together with the text of the specification, help to illustrate the underlying principles. [Brief explanation of the drawing]

[0010] [Figure 1] This is a diagram illustrating an exemplary data management environment for multiple medical machines or devices, according to several embodiments. [Figure 2A] This is a diagram illustrating an exemplary operating environment for a power cord device of a power cable, according to several embodiments. [Figure 2B] This is a block diagram of a power cord device according to several embodiments. [Figure 3] This is a flowchart illustrating an exemplary process for managing power data for a medical device 102, according to several embodiments. [Figure 4A] This is a diagram of exemplary power profiles collected from the power cord device 106 according to several embodiments. [Figure 4B] This diagram illustrates the flow of power data received, processed, or generated by a power cord server in several embodiments. [Figure 5A] This is a diagram of one of three exemplary user interfaces presented to the user, according to several embodiments. [Figure 5B] This is a diagram of one of three exemplary user interfaces presented to the user, according to several embodiments. [Figure 5C]This is a diagram of one of three exemplary user interfaces presented to the user, according to several embodiments. [Figure 6A] This is a block diagram of an exemplary medical device for performing medical procedures, according to several embodiments. [Figure 6B] This is a block diagram of an exemplary client device for presenting information on medical procedures performed in separate medical devices, according to several embodiments. [Figure 6C] This is a block diagram of a power cord server 108 for collecting power profiles and providing medical treatment information to a user, according to several embodiments. [Figure 7A] This diagram provides flowcharts of data management methods implemented in a power cord server according to several embodiments. [Figure 7B] This diagram provides flowcharts of data management methods implemented in a power cord server according to several embodiments. [Figure 7C] This diagram provides flowcharts of data management methods implemented in a power cord server according to several embodiments. [Figure 7D] This diagram provides flowcharts of data management methods implemented in a power cord server according to several embodiments. [Modes for carrying out the invention]

[0011] Throughout several figures in the drawing, similar reference numbers refer to the corresponding parts.

[0012] Here, the example will be given in detail by referring to the specific embodiment shown in the accompanying drawings. In the following detailed description, numerous non-limiting specific details will be given to help in understanding the subject matter presented herein. However, it will be apparent to those skilled in the art that various alternatives can be used without departing from the claims and that the subject matter can be implemented 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 having digital video capabilities.

[0013] Various embodiments of this application relate to a centralized power data management platform configured to be communicatively coupled to a plurality of power cord devices and to collect power usage characteristics of medical devices via these power cord devices while the medical devices are performing or after performing medical procedures. Each power cord device is part of a power cable that connects each medical device to a power outlet. Such power cord devices facilitate the power supply to each medical device and generally do not exchange data directly with the medical devices via the power cable. When a medical procedure is performed by a medical device, the power cord devices generally cannot access data stored within the medical device. However, the power cord devices can monitor power usage characteristics associated with a medical procedure (i.e., a power profile including instantaneous current or power provided by the power cable to enable the medical procedure) without knowing what kind of medical device or what type of medical procedure was powered by the power cable. A centralized power data management platform can collaborate with power cord devices to collect power usage characteristics from different types of medical devices and related to different types of medical procedures, analyze the collected power usage characteristics, generate analysis results (e.g., statistics on medical devices, users, treatment settings, procedure time, and geographical distribution), and provide the analysis results to users of its data service.

[0014] In addition, in some embodiments, firmware operating on the CPU / processor of the power cord knows some of the characteristics of the medical device powered by the power cord. The power cord is configured to locally classify power events instead of completely determining treatment characteristics on a remote power cord server. In some situations, this power cord requires firmware specific to its code device to properly classify power events.

[0015] Figure 1 shows an exemplary data management environment 100 for multiple medical machines or devices 102 in several 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 scans), radiography, magnetic resonance imaging (MRI scans), ultrasound, endoscopy, echocardiography (EKG or ECG), intravenous infusion, epidural infusion, or intra-arterial infusion, 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., cardiopulmonary bypass machines), dialysis machines, incubators, various laser machines, various gas machines, various medical imaging machines, and various medical laboratory equipment. Each medical device 102 is connected to a power outlet via a power cable 104, which includes a power cord device 106 and two cable portions extending from both ends of the power cord device 106, and the power cable 104 provides power to the medical device 102. In some embodiments, the power cable 104, including 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 provides data to or receives data from the medical device 102 wirelessly (e.g., using near-field communication (NFC) or Bluetooth communication) or via a wire (e.g., via the cable portion of the corresponding power cable 104). It should be 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.

[0016] The power cord device 106 is communicatively coupled to a power cord server 108 (also referred to as a 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 records a power profile 120 that includes a plurality of power data characteristics that measure the power supplied to the medical device 102, and reports the power profile 120 to the power cord server 108 via one or more communication networks 110. In some embodiments, the power cord device 106 reports the power profile 120 in real time while the medical procedure is being performed. In some embodiments, the power cord device 106 reports the power profile 120 after each medical procedure is completed. In some embodiments, the power cord device 106 reports a batch of power profiles 120 that include 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 commissioned to any local area network. In this case, when the power cord device 106 is connected to the corresponding medical device 102, it is configured to report data (e.g., the power profile 120) to the power cord server 108 without user intervention or with little user intervention.

[0017] The power cord server 108 enables a centralized data management platform to manage power profiles 120 collected in relation to multiple medical devices 102, which may include two or more device types. After collecting power profiles 120 from multiple power cord devices 106, the power cord server 108 can analyze the power profiles 120 to identify medical procedures performed by these medical devices 102, including one or more numerical operating parameters, device modes, and / or the operating state of the medical procedures performed, and can further generate statistics for these medical procedures. The power cord server 108 then generates a message 130 to report medical procedures having 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. In some embodiments, the message 130 includes a summary of statistics for medical procedures monitored by two or more medical devices 102, and the client device 112 receiving the message 130 can visualize the statistics on its own user interface.

[0018] In some embodiments, the code device 106 preprocesses power profiles 120 collected in relation to the connected medical device 102. Firmware operating on the code 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 fully determining the treatment characteristics on the power cord server 108. The preprocessed power profiles 120 are provided by the power cord server 108 for further profiling and / or to generate messages to be sent to other medical devices or client devices using this code data service. In some embodiments, the code device 106 is a specialized code device comprising a hardware or software module configured to identify information associated with one or more specific types of medical devices 102.

[0019] In some embodiments, the power cord server 108 is configured to support a power cord application (e.g., applications 634A and 634B in Figures 6A and 6B), which runs on a medical device 102 or a client device 112 and is configured to enable a user interface for displaying information contained within a message 130. The power cord application may be a browser-based application or a dedicated data application. The user interface is configured to receive user queries and present information contained within a message 130 according to the user queries. Messages may include warnings, notices, reports, and / or instructions regarding medical procedures.

[0020] In some embodiments, when the power cord device 106 is connected to each medical device 102, the type of each medical device 102 is not communicated to or known to the power cord device 106. Similarly, in some embodiments, when the power cord device 106 reports a power profile 120 relating to a medical procedure for each medical device 102, the type of medical procedure is not communicated to or known to the power cord device 106. In some embodiments, the power cord device 106 identifies one or more power features within each power profile 120, derives the type of medical device 102 and / or medical procedure based on the identified power features, 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, the power cord server 108 is configured to identify one or more power features within each power profile 120 collected from the cord device 106 and derive the type of medical device 102 and / or medical procedure based on the identified power features within the power profile 120. In some embodiments, the power cord device 106 or power cord server 108 is configured to use deep learning techniques to determine the type of medical device 102 and / or medical procedure based on the power profile 120 and / or corresponding power features.

[0021] In some embodiments, the medical device 102 operates offline and is isolated from any communication network 110 (for example, for the purpose of maintaining data security and privacy). The medical device 102 is configured to run a medical device application (e.g., application 630A in Figure 6A) locally. Alternatively, in some embodiments, the medical device 102 is communicably coupled to a respective medical device server 114 via one or more communication networks 110 (e.g., only during or when no medical procedure is being performed). Medical devices of the same type are coupled to the same medical device server 114. Medical devices of different types or brands 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 be unaware of the presence of the power cord device 106. Conversely, in some situations, the medical device server 114 or medical device 102 interacts with the power cord server 108. The medical device 102 is configured to run a medical device application (e.g., application 630A in Figure 6A) in cooperation with its respective medical device server 114 for the purpose of controlling the medical device 102 in order to perform medical procedures. Under certain circumstances, the medical device application is also configured to receive messages 130 from the power cord server 108 regarding medical procedures performed by the medical device 102 or other medical devices 102, and to display the messages 130 on its user interface. In one example, the user interface of the medical device application includes an embedded window or pop-up window for displaying the messages 130 provided by the power cord server 108.

[0022] The data management environment 100 further includes a plurality of client devices 112 that are communicatively coupled to at least a 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 can collect data or user input, run a user application (e.g., the power cord application 634B in Figure 6B), or present output on its user interface. The collected data or user input may be processed locally on the client device 112 and / or remotely by the server 108 or 114. The servers 108 and 114 provide system data (e.g., boot files, operating system images, and user applications) to the client device 112 and, in some embodiments, process the data and user input received from the client device 112 when the user application is run on the client device 112. In one example, the client device 112 communicates with a medical device server 114 and is used to remotely control medical procedures performed by a medical device 102 coupled to the medical device server 114. In another example, the client device 112 communicates with the power cord server 108 to control the collection, analysis, and reporting of the power usage characteristics of the medical device 102.

[0023] Servers 108 and 114, client device 112, code device 106, and medical device 102 (if present) are connected to each other in a communicative manner via one or more communication networks 110, the medium used to provide communication links between these devices and computers interconnected within the 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 local area networks (LANs), wide area networks (WANs) such as the Internet, or a combination thereof. One or more communication networks 110 may be implemented using any known network protocol, including a variety of wired or wireless protocols such as Ethernet, Universal Serial Bus (USB), FireWire, Long-Term Evolution (LTE), Global System for Mobile Communications (GSM), Enhanced 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. Connection to one or more communication networks 110 may be established directly (e.g., using 3G / 4G / 5G connectivity to a wireless carrier), via a network interface (e.g., a router, switch, gateway, hub, or intelligent dedicated whole-house control node), or via any combination thereof. One or more communication networks 110 may represent the Internet, a global collection of networks and gateways that use the Transmission Control Protocol / Internet Protocol (TCP / IP) suite of protocols to communicate with one another. The heart of the internet is the backbone of high-speed data communication lines between major nodes or host computers, consisting of thousands of commercial, government, educational, and other computer systems routing data and messages.In some embodiments, all power cord devices 106 are communicably coupled to a power cord server 108 via a secure, encrypted private cellular network and are configured to report data to the power cord server 108 independently of any local wired or wireless network after the power cord devices 106 are connected to the medical device 102.

[0024] In some embodiments, deep learning techniques are applied in the data management environment 100 to process the power profiles 120 collected by the power cord device 106 (for example, to identify power features and operating parameters contained within the power profiles 120, to identify new device modes, operating states, and medical procedures, to match the power profiles 120 with medical procedures, to classify the power profiles 120, and / or to synthesize the relevant power characteristics). In these deep learning techniques, a data processing module is created based on one or more neural networks to process the power profiles 120. These data processing modules can be trained with training data before being applied to process the power profiles 120. Both model training and data inference are implemented in the power cord server 108, and the results (e.g., message 130) are reported to individual client devices 112 or medical devices 102 for review by users of the data management service provided by this data management environment 100.

[0025] Figure 2A is an exemplary operating environment 200 for a power cord device 106 for a power cable 104 according to several embodiments, and Figure 2B is a block diagram of the power cord device 106 according to several embodiments. Both ends of the power cable 104 are configured to connect to a power source (e.g., a standard wall outlet) and a medical device 102, respectively. The power cord device 106 is coupled to the power cable 104 and is configured to monitor power as the power cable 104 transmits power from the power source to the medical device 102. The power cable 104 includes two cable portions 104' extending from both ends of the power cord device 106. Power is recorded as a power profile 120 (e.g., current flow is sampled at a predefined sample rate), reported to a power cord server 108, and analyzed by the power cord server 108. The analysis results (e.g., message 130) are then presented to the user on the user interface of the client device 112 or the medical device 102.

[0026] In some embodiments, the power cord device 106 is used to gain insights into device usage patterns, treatment settings, physical location, and other characteristics of the medical device 102. The power cord server 108 learns how the power profile 120 fits the treatment settings or device modes of the medical device 102 and converts the power profile 120 of the medical device 102 into logical data presented in a visual report. In some embodiments, the power cord server 108 is configured to recognize power patterns associated with each medical treatment of different medical devices (e.g., using deep learning techniques). 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. In some embodiments, the power cord server 108 includes machine learning components for classifying data characteristics across device types and determining whether additional power cord devices 106 are added to the data management environment 100. In some embodiments, the power cord device 106 or power cord server 108 is fitted with a proprietary software program to map unique power usage characteristics to device type, device mode, operating state, and medical procedure settings (e.g., using deep learning techniques). In some embodiments, a website platform is deployed to display, sort, associate, and export the post-processed and interpreted data provided by the power cord server 108.

[0027] Referring to Figure 2A, the power cord device 106 includes one or more of the following: 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, flash storage 212, a location module 214, a cellular module 216, an antenna 218, and a connector 220. The ADC 202 is configured to convert the AC power supply voltage provided by the power supply to a DC power supply voltage for powering the operation of the power cord device 106. The relay 204 is configured to receive control or commands and enable / disable the flow of current to the medical device 102 or the power cord device 106 (e.g., emergency shutoff). This control or command may be provided remotely by the power cord server 108. The battery 206 is controlled by the battery management system 208 for storing power. The location module 214 is configured to identify the geographic location of the power cord device 106 and may be a Global Positioning System (GPS) or other module that can provide geolocation information. In one example, the location of the cord device 106 is determined based on the Wi-Fi Basic Service Set Identifier (BSSID) or the Received Signal Strength Indicator (RSSI). The power monitor module 210 is configured to sample power, voltage, or current values ​​related to the use of the medical device 102. Such sampled values ​​form a power profile 120 of the medical device 102, which is digitized and temporarily stored in flash memory 212. The power profile 120 stored in flash memory 212 is transferred to the power cord server 108 via one or more communication networks 110. In one example, the power profile 120 is transferred over a private cellular network (e.g., using a cellular module 216) in an encrypted HIPAA-compliant format. In another example, the power profile 120 is transferred along with information about the geographical location of the power cord device 106.

[0028] Referring to Figure 2B, in some embodiments, the power cord device 106 includes one or more processors 222 and a memory 226 that stores instructions to be executed by the processors 222 to monitor, store, preprocess, and / or transmit the collected power profile. The power cord device 106 further includes one or more network interfaces 224, the memory 226 and one or more communication buses 228 for interconnecting these components (sometimes called a chipset). In some embodiments, the power cord device 106 includes one or more input devices 230 that facilitate user input, such as a touchscreen display, a touch-sensitive input pad, or other input buttons or controls. In some embodiments, the power cord device 106 includes one or more output devices 232 that enable the presentation of a user interface and display content, including one or more visual displays and light indicators.

[0029] Memory 226 includes high-speed random-access memory such as DRAM, SRAM, DDR RAM, or other random-access solid-state memory devices. In some embodiments, memory includes non-volatile memory such as 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. In some embodiments, memory 226 includes one or more storage devices located remotely from one or more processing units 222. Memory 226, or alternatively, the non-volatile memory within memory 226, includes a non-temporary computer-readable storage medium. In some embodiments, memory 226, or the non-temporary computer-readable storage medium of memory 226, stores the following programs, modules, and data structures, or subsets or supersets thereof: • An operating system 234 that handles various basic system services and includes procedures for performing hardware-dependent tasks. A network communication module 236 connects 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. A data acquisition module 238 collects a power profile 120 which includes multiple power data characteristics that measure the power supplied to a medical device coupled to a power cord device 106. A data preprocessing module 240 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 reports the collected or pre-processed power profiles 120 (for example, in real time, periodically, or according to a predefined reporting schedule). ·below, ○Power profile 120 captured and pre-processed by the power monitor module 210, and Code information and settings 248, including common device settings for power cord device 106 (e.g., serial identification, geographical location, service layer, device model, memory capacity, processing power, communication capabilities, etc.) One or more databases 244 that store code data containing one or more of the following.

[0030] 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 do not need to be implemented as separate software programs, procedures, modules, or data structures, and therefore various subsets of these modules may be combined or otherwise rearranged in various embodiments. 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.

[0031] Figure 3 is a flowchart of an exemplary process 300 for managing power data for a medical device 102, according to several embodiments. Process 300 is carried out jointly by a power cord device 106, a power cord server 108, and an electronic device (e.g., medical device 102 or client device 112). The medical device 102 is connected to a power source by a power cable 104, which includes the power cord device 106. The medical device 102 has device modes (e.g., operating mode and idle mode). Based on the treatment setting, the medical device 102 is configured to perform one or more types of medical procedures in operating mode, and to switch to idle mode after the medical procedures or batches of consecutive medical procedures have been performed. The medical device 102 includes one or more processors and memory that stores instructions to be executed by those processors. Specifically, the medical device 102 has a medical device application installed (e.g., application 630 in Figure 6A) which is loaded to control each medical procedure based on the corresponding treatment setting (328). In some embodiments, a power cord application is also installed (326). While the medical device 102 is performing a medical procedure (304), the power cord device 106 records power data characteristics associated with the medical procedure in real time according to the sample rate (306). The recorded power data characteristics measure the power supplied to the medical device 102 while it is performing the medical procedure and form the power profile 120 of the medical device 102.

[0032] The power cord device 106 reports a power profile 120 corresponding to a medical procedure to the power cord server 108 while the medical procedure is being performed or after the medical procedure is completed. After receiving the power profile 120 (310), the power cord server 108 analyzes the power data characteristics of the power profile and determines whether each part or interval of the power profile is related to the operating mode or idle mode of the medical device 102 (312). The power cord server 108 identifies the medical procedure performed, including one or more numerical operating parameters of the medical procedure performed in the power profile 120 (314). For example, a certain type of medical procedure has one or more power features (e.g., a power pulse train), and the power cord server 108 identifies the numerical operating parameters corresponding to the power features of the medical procedure in the power profile (e.g., the frequency, power pattern, and average power peak of the power pulse train). Based on the numerical operating parameters, it is determined that a particular type of medical procedure was performed by the medical device 102 connected to the power cord device 106 reporting the power profile 120. Therefore, in some embodiments, the power cord server 108 generates a message 130 (316) specifying the medical procedure performed and one or more numerical operating parameters, and transmits the message 130 to the electronic device for display on the user interface of the electronic device.

[0033] In some embodiments, the electronic device that receives message 130 from the power cord server 108 is a client device 112. The client device 112 has a power cord application installed and runs it (for example, application 634B in Figure 6B), which may be a browser-based application or a dedicated data application (320). A user account is created in the power cord application for users of the data services provided by the power cord server 108 (322). The user interface is displayed on the client device 112 via the power cord application to share message 130 with users of the data services. Message 130 is displayed on the user interface of the power cord application (324).

[0034] 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 a power cord application installed and runs (e.g., application 634A in Figure 6A), which may be a browser-based application or a dedicated data application (326), and a user account is created in the power cord application for users of the data services provided by the power cord server 108. In some embodiments, the medical device 102 has a medical device application installed and runs (e.g., application 630A in Figure 6A) for performing medical procedures using the medical device 102 (328), and the medical device application includes a power cord plug-in program (e.g., program 632A in Figure 6A). The user interface presenting the message 130 is displayed on the medical device 102 either directly through the power cord application or through the power cord plug-in program in the medical device application (330).

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

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

[0037] A subset of several power parameters 402-416 is substantially stable. For example, the RMS value of voltage 404 is 120V. The frequency 414 is 60Hz. The die temperature 416 is stable at approximately 30°C. It should be 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 current 402 and the RMS value of voltage 404 (i.e., the power supplied to the medical device 102). The power factor 412 is approximately 0, indicating that the power dissipated by the power cord device 106 is negligible compared to the power supplied to the medical device 102. In addition, the reactive power 408 associated with the reactive load is smaller than the active power 406 or apparent power 410. When the medical device 102 is powered on and no medical procedure is being performed in idle mode 418, the reactive power 408A is substantially stable (e.g., with a time variation of less than 5%). When a medical procedure is performed in operating mode 420, the reactive power 408B increases slightly and has negligible fluctuations compared to the power pulse train 450 observed in the active power 406 or apparent power 410.

[0038] The power profile 120 corresponds to a subset of operating states, including system idle states 424A and 424B, system start state 422, treatment start state 426, one or more treatment states 428A and 428B, treatment idle state 430, and power-off state 432. The idle mode 418 of the medical device 102 includes system idle states 424A and 424B, and the operating mode 420 of the medical device 102 corresponds to the sequence of treatment start state 426, first treatment state 428A, treatment idle state 430, and second treatment state 428B. A medical procedure of the medical device 102 is identified when a subset of the multiple operating states is identified. In this example in Figure 4A, a specific medical procedure is identified according to the detection of an ordered sequence of the first treatment state 428A, treatment idle state 430, and second treatment state 428B. Furthermore, the first and second treatment states 428A and 428B are identified according to the detection of power pulse trains 450A and 450B, and the treatment idle state 430 is identified according to the corresponding power drop and the position between the two power pulse trains 450A and 450B. Assuming that a subset of power parameters 402-416 is substantially stable, a medical procedure is determined based on at least one of the remaining power parameters, such as the RMS value of the current 402, the active power 406, and the apparent power 410, and at least one of the remaining power parameters is optionally processed using deep learning techniques to identify each of the states 428A, 430, and 428B, their corresponding ordered sequences, and / or a specific medical procedure.

[0039] A first treatment state 428A includes a power pulse train 450A characterized by power data characteristics 434 (see Figure 4B) that measure the power supplied to the medical device 102 while the medical device 102 performs the corresponding medical procedure. A subset of these power data characteristics 434 are measured from the active power 406 and apparent power 410 and include the duration, frequency, power pattern, and average power peak value of the power pulse train 450A. The power cord server 108 identifies the first treatment state 428A based on the subset of power data characteristics 434 and determines one or more numerical operation parameters 436 (see Figure 4B) of the medical procedure performed. In one example, the power pattern and frequency of the power pulses may be used to distinguish the first treatment state 428A from the corresponding medical procedure. The numerical operation parameters 436 of the medical procedure include the power level and duration of the medical procedure, which are determined from the subset of power data characteristics 434 and transmitted to the user of the data service provided by the power cord server 108.

[0040] In addition, in some embodiments, each of the multiple operating states 422-432 is defined according to at least one power threshold 438 (see Figure 4B) associated with each subset of power data characteristics 434. The at least one power threshold 438 associated with each of the multiple operating states 422-432 is determined and adjusted based on deep learning techniques. In some situations, an ordered sequence of states 426-430 in operating mode 420 is initially unknown to the power cord system 108 and repeatedly appears in power profiles collected from different medical devices 102. The 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, recognize the sequence of states 426-430, or classify the sequence of states 426, 428A, 430, and 428B as a medical procedure.

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

[0042] In some embodiments, for each power interval, each subset of the power data characteristics 434 corresponding to each interval is compared with at least each power threshold 438. The first operating state 428A is associated with the first power interval according to the 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 medical procedure performed (e.g., power level of the medical procedure) are determined based on each subset of the power data characteristics 434 corresponding to the first power interval (e.g., frequency, power pattern, and average power peak value of the first power interval). Furthermore, in some embodiments, each power threshold associated with the first operating state 428A is determined and adjusted based on a first deep learning technique.

[0043] Referring to Figures 1 and 4B, after a power profile 120 is received from the first power cord device 106A, power data characteristics 434 are extracted and used to determine the type of the corresponding first medical device 102A, the device mode (i.e., idle mode 418 or operating mode 420), each operating state associated with each 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, the power cord server 108 jointly analyzes the multiple power profiles 120 to provide additional information that cannot be derived using a single power profile 120.

[0044] For example, in some embodiments, the power cord server 108 receives a second power profile 120' from the second cord device 106B of the second power cable 104B, which includes a plurality of second power data characteristics 434' that measure the power supplied to the second medical device 102B while the second medical device 102B is performing the same medical procedure. The second power profile 120' is used to identify one or more second numerical operating parameters 436' for the same medical procedure. Message 130 is generated based on the first and second numerical operating parameters 436 and 436' for the same medical procedure. In some embodiments, message 130 reports the results of a statistical analysis of the numerical operating parameters 436 for a plurality of medical devices 102, including the first and second medical devices 102A and 102B. Furthermore, in some embodiments, a therapeutic power signature 440 is determined for the same medical procedure based on at least first and second numerical operating parameters 436 and 436', and a message 130 sent to other electronic devices includes the 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 a medical procedure. In addition, in some embodiments, other electronic devices that receive the message 130 from the power cord server 108 are configured to adjust subsequent medical procedures performed by the electronic devices based on the therapeutic power signature 440 received in the message 130.

[0045] 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 profiles 120" includes each of a plurality of third power data characteristics 434" that measure the current supplied to each third medical device 106C while each third medical device 106C is performing each third medical procedure. Each of the plurality of third power profiles 120" is used to identify each third medical procedure, including one or more third numerical operating parameters 436" for each third medical procedure. A message 130 is generated based on one or more first numerical operating parameters 436 of the medical procedure performed and the third numerical operating parameters 436" corresponding to the plurality of third power profiles 120. For example, the message 130 may identify the most frequently performed medical procedure or the average procedure time for different medical procedures. In some embodiments, the first power profile 120 and a plurality of third power profiles 120'' conform to geographical or temporal limitations (e.g., targeting medical procedures within a geographical area and within a defined duration), and the message 130 is generated based on these geographical or temporal limitations. In one example, a geographical distribution 442 is obtained based on an analysis of the power profiles 120 and 120'' and is transmitted along with the message 130. In one example, the message 130 indicates that the most popular medical procedure during a five-year period was LASIK surgery, and that 23% of all medical procedures performed in Florida during the five-year period were LASIK surgery.

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

[0047] Multiple affordances 504 include one or more of the following: device overview affordance 504A, device map affordance 504B, reporting affordance 504C, consumable order affordance 504D, device management affordance 504E, user profile affordance 504F, and error affordance 504G. In response to the selection of device overview affordance 504A, the user interface 500 displays an information display area 506, as shown in Figure 5A. The content displayed in the information display area 506 includes a device overview 508 of medical procedures that meet predefined criteria (e.g., time and location restrictions). The device overview 508 may include one or more of the following: 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. In some situations, a plot 510 is generated to provide more information about a subset of the device summary 508 (e.g., the number of device events 508E). In this example, plot 510 shows the variation in the number of device events 508E over the current and previous months. In some embodiments, additional content 512 is displayed to provide insights about the power profile 120 collected by the power cord server 108. For example, the additional content 512 includes a summary of treatment types 512A, a record of the most recent events 512B, and / or a list of the most active physicians 512C.

[0048] Of the content displayed in the information display area 506, at least the total treatment time 508C for these medical procedures is associated with numerical operation parameters 436 of the medical procedures monitored by the power cord server 108. In some embodiments, in response to a user selection of other items in the device overview 508, the user interface 500 is refreshed on the information display area 506 to display additional information (e.g., one or more numerical operation parameters 436 received with message 130). In some embodiments, message 130 may include numerical operation 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 may focus on displaying a statistical overview 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).

[0049] Referring to Figure 5B, in response to the selection of device map affordance 504B, the user interface 520 is displayed as shown in Figure 5B. The information display area 506 displays a map 522 showing the distribution of medical devices 102 from which the medical procedure power profile 120 was collected, and a list 524 of recent location events. Each event in the list 524 is described along 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 Figure 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 the selection of one of the recent location events in the list 524, the user interface 520 is refreshed to display details of the selected recent location event, including one or more numerical operating parameters 436 of the medical procedure associated with the selected recent location event.

[0050] Referring to Figure 5C, the user interface 540 is loaded within a medical device application (e.g., application 630 in Figure 6A or 6B) executed by an electronic device (e.g., medical device 102). The medical device application may run offline or in conjunction with the medical device server 114. The primary function of the medical device application is to facilitate the execution of medical procedures (e.g., 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, a third area 546 for visually representing medical tools, and a fourth area 548 for directly adjusting several key settings. The medical device application includes a power cord plug-in program (e.g., program 632 in Figure 6A or 6B) that runs in conjunction with a power cord server 108, separate 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 user interface 540 of the medical device application. In some embodiments, the messages 130 are displayed in a dedicated area of ​​the user interface 540, such as a fixed area of ​​the medical device application. Alternatively, in some embodiments, as shown in Figure 5C, the messages 130 are overlaid on one of areas 542-548 and displayed in a pop-up window 550 of the user interface 540 that disappears after a predefined duration or in response to user action. In this example, the message 130 is a notification stating, "This device has been used in 100 medical events in the past month, which is more frequent than 90% of devices of the same type in the United States."

[0051] In some embodiments, a medical device 102 displaying one of the user interfaces 500, 520, or 540 uses a power cord device 106 to power its medical procedure and reports its own power profile 120, while also subscribing to data services provided by a power cord server 108. Conversely, in some embodiments, a medical device 102 displaying one of the user interfaces 500, 520, or 540 subscribes only to data services provided by the power cord server 108. However, the medical device 102 does not use the 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 does not subscribe to data services provided by the power cord server 108, while still using the power cord device 106 to power its medical procedure or to report its own power profile 120. Optionally, the power cord server 108 is configured to handle the use of the power cord device 106 and the subscription to data services separately. In some embodiments, the power cord server 108 is configured to associate the use of the power cord device 106 with a subscription to a data service, thereby automatically providing the data service to the user of the power cord device 106. The power cord server 108 can further extend the data service to other subscribers who do not use the power cord device 106.

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

[0053] Memory 606A includes high-speed random-access memory such as DRAM, SRAM, DDR RAM, or other random-access solid-state memory devices. In some embodiments, the memory includes non-volatile memory such as 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. In some embodiments, memory 606A includes one or more storage devices located remotely from one or more processing units 602A. Memory 606A, or alternatively, the non-volatile memory within memory 606A, includes a non-temporary computer-readable storage medium. In some embodiments, memory 606A, or the non-temporary computer-readable storage medium of memory 606A, stores the following programs, modules, and data structures, or subsets or supersets thereof: • Operating system 616A, which handles various basic system services and includes procedures for performing hardware-dependent tasks. A network communication module 618A that connects each medical device 102 to other devices (e.g., medical device server 114, power cord server 108, client device 112) 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, or metropolitan area networks. Presentation module 620A that enables the presentation of information (e.g., graphical user interfaces, widgets, websites and their web pages for applications 626A, as well as games, audio, and / or video content) in each medical device 102 via one or more output devices 614A (e.g., displays or speakers). An input processing module 622A that detects one or more user inputs or interactions from one or more input devices 612A and interprets the detected inputs or interactions. A web browser module 624A that navigates, requests, and displays (e.g., via HTTP) 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. The web browser module 624A also controls the medical device or electronic device if it is associated with a user account, and edits and reviews the settings and data associated with the user account. • One or more user applications 626A executed in the medical device 102. • Medical procedure module 628A that performs medical procedures on medical device 102. • A medical device application 630A that performs medical procedures via a medical procedure module 628A. The medical device application 630A includes a power cord plug-in program 632A for receiving and presenting information regarding the power usage of different medical devices distributed across different medical facilities within the medical device application 630A. A power cord application 634A is dedicated to receiving information from a power cord server 108 regarding the 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 the following: ○ Device configuration 638A, which includes common device settings for the medical device 102 (e.g., service layer, device model, memory capacity, processing power, communication capabilities, and / or medical procedure settings). ○ User account information 640A 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). ○History medical data 642 associated with medical procedures previously performed by the medical device 102. ○Message 130 specifying a medical procedure and corresponding numerical operating parameters 436. Message 130 is generated and provided by the power cord server 108 based on power profiles 120 collected from various medical devices 102, which may or may not include the medical device 102 itself.

[0054] 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 do not need to be implemented as separate software programs, procedures, modules, or data structures, and therefore various subsets of these modules may be combined or otherwise rearranged in various embodiments. 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.

[0055] Figure 6B is a block diagram of an exemplary client device 112 for representing information on a medical procedure performed in a separate medical device 102, according to several embodiments. Examples of the client device 112 include, but are not limited to, desktop computers, laptop computers, tablet computers, and mobile phones. The client device 112 typically includes one or more processing units (CPUs) 602B, one or more network interfaces 604B, memory 606B, and one or more communication buses 608B for interconnecting these components (sometimes called chipsets). The client device 112 includes one or more user interface devices 610B. The user interface devices 610B include one or more input devices 612B that facilitate user input, such as a keyboard, mouse, voice command input unit or microphone, touchscreen display, touch-sensitive input pad, gesture capture camera, or other input buttons or controls. Furthermore, in some embodiments, the medical device 102 uses a microphone and voice recognition, or a camera and gesture recognition, to supplement or replace the keyboard. In some embodiments, 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 an electronic device. The client device 112 also includes one or more output devices 614B that enable the presentation of a user interface (e.g., interfaces 500, 520, and 540 in Figures 5A to 5C) and display content, including one or more speakers and / or one or more visual displays.

[0056] Memory 606B includes high-speed random-access memory such as DRAM, SRAM, DDR RAM, or other random-access solid-state memory devices. In some embodiments, the memory includes non-volatile memory such as 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. In some embodiments, memory 606B includes one or more storage devices located remotely from one or more processing units 602B. Memory 606B, or alternatively, the non-volatile memory within memory 606B, includes a non-temporary computer-readable storage medium. In some embodiments, memory 606B, or the non-temporary computer-readable storage medium of memory 606B, stores the following programs, modules, and data structures, or subsets or supersets thereof: • Operating System 616B, which handles various basic system services and includes procedures for performing hardware-dependent tasks. A network communication module 618B that connects each client device 112 to other devices (e.g., power cord server 108, medical device server 114, and / or 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, etc. Presentation module 620B that enables the presentation of information (e.g., graphical user interfaces, widgets, websites and their web pages for applications 626B, as well as games, audio, and / or video content) to each client device 112 via one or more output devices 614B (e.g., displays or speakers). An input processing module 622B that detects one or more user inputs or interactions from one or more input devices 612B and interprets the detected inputs or interactions. A web browser module 624B that navigates, requests, and displays (e.g., via HTTP) a website and its web pages, including a web interface for logging into a client device 112 or other medical devices or user accounts associated with the client device. The web browser module 624B also controls, if the medical device or client device is associated with a user account, and edits and reviews the settings and data associated with the user account. • One or more user applications 626B executed by the client device 112 (e.g., games, social networking applications, smart home applications, and / or other web-based or non-web-based applications for controlling medical devices or client devices and reviewing data captured by such devices). • A medical device application 630B controls medical procedures performed remotely by a medical device 102. The medical device application 630B includes a power cord plug-in program 632B for receiving and presenting information regarding the power usage of different medical devices distributed across different medical facilities within the medical device application 630B. • Power cord application 634B is dedicated to receiving information from power cord server 108 regarding the power usage of different medical devices distributed across different medical facilities, and presenting such information within power cord application 634B. • Client data 636B including the following: ○ Device configuration 638B, which includes common device settings for client device 112 (e.g., service layer, device model, storage capacity, processing power, communication capabilities, and / or medical treatment settings). ○ 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). ○Message 130 specifying a medical procedure and corresponding numerical operating parameters 436. The message is generated and provided by the power cord server 108 based on power profiles 120 collected from various medical devices 102.

[0057] 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 do not need to be implemented as separate software programs, procedures, modules, or data structures, and therefore various subsets of these modules may be combined or otherwise rearranged in various embodiments. 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.

[0058] Figure 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 several embodiments. Examples of the power cord server 108 include, but are not limited to, desktop computers, laptop computers, tablet computers, or mobile phones. The power cord server 108 typically includes one or more processing units (CPUs) 602C, one or more network interfaces 604C, memory 606C, and one or more communication buses 608C for interconnecting these components (sometimes called chipsets). The power cord server 108 includes one or more user interface devices 610C. The user interface devices 610C include one or more input devices 612C that facilitate user input, such as a keyboard, mouse, voice command input unit or microphone, touchscreen display, touch-sensitive input pad, gesture capture camera, or other input buttons or controls. Furthermore, in some embodiments, the medical device 102 uses a microphone and voice recognition, or a camera and gesture recognition, to supplement or replace the keyboard. In some embodiments, 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 electronic devices. The power cord server 108 also includes one or more output devices 614C that enable the presentation of a user interface and display content, including one or more speakers and / or one or more visual displays.

[0059] Memory 606C includes high-speed random-access memory such as DRAM, SRAM, DDR RAM, or other random-access solid-state memory devices. In some embodiments, the memory includes non-volatile memory such as 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. In some embodiments, memory 606C includes one or more storage devices located remotely from one or more processing units 602C. Memory 606C, or alternatively, the non-volatile memory within memory 606C, includes a non-temporary computer-readable storage medium. In some embodiments, memory 606C, or the non-temporary computer-readable storage medium of memory 606C, stores the following programs, modules, and data structures, or subsets or supersets thereof: • Operating System 616C, which handles various basic system services and includes procedures for performing hardware-dependent tasks. A network communication module 618C that connects the power cord server 108 to other devices (e.g., power cord device 106, medical device 102, and / or client device 112) 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, or metropolitan area networks. Presentation module 620C enables the presentation of information (e.g., graphical user interfaces, widgets, websites and their web pages, audio and / or video content for applications 626C) in each power cord server 108 via one or more output devices 614C (e.g., displays or speakers). An input processing module 622C that detects one or more inputs or interactions from one or more input devices 612C and interprets the detected inputs or interactions. A web browser module 624C that navigates, requests, displays (e.g., via HTTP) a website and its web pages, including a web interface for logging into a user account associated with the power cord server 108, controls predefined criteria (e.g., time and location restrictions) for the power cord device 106 if associated with a user account, and edits and reviews settings and data associated with the user account. • One or more user applications 626C executed by the power cord server 108 (for example, web-based or non-web-based applications for controlling predefined criteria such as time and location restrictions for power cord devices 106 and for reviewing data captured by such power cord devices 106). (1) A power cord plug-in module 632C that enables the display of information regarding the power usage of different medical devices 102 distributed across different medical facilities in a medical device application 630, and / or (2) a server-side module 644 that includes a power cord application 634C that is specialized for transmitting information regarding the power usage of different medical devices 102 to a client-side power cord application 634A or 634B and for presenting such information in the client-side power cord application 634A or 634B. Server data 636C, including the following: Device configuration 638C, which includes common device settings for the power cord server 108 (e.g., service layer, device model, storage capacity, processing power, communication capabilities, and / or medical procedure settings). ○ 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 predefined account settings). ○Power profile data 120 collected from different medical devices 102. ○Power data characteristics 434 extracted from power profile data 120 in relation to the mode or operating state of the medical device 102. ○Medical procedure data 646 determined based on power data characteristics 434, including, but not limited to, the device type of the medical device 102, one of the operating mode 420 or idle mode 418, operating states 422-432, the type of each medical procedure, and numerical operating parameters 436 for each medical procedure. ○Power threshold 438 for deriving medical treatment data 646 from power data characteristics 434 extracted from power profile 120. Message 130 specifies the medical procedure and the corresponding numerical operation parameter 436.

[0060] 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 do not need to be implemented as separate software programs, procedures, modules, or data structures, and therefore various subsets of these modules may be combined or otherwise rearranged in various embodiments. 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.

[0061] Figures 7A to 7D provide flowcharts of data management methods 700 implemented in a power cord server 108 according to several embodiments. In some embodiments, the method 700 is managed by instructions stored in a non-temporary computer-readable storage medium and executed by one or more processors of the power cord server 108. Each of the operations shown in Figures 7A to 7D may correspond to instructions stored in the computer memory or computer-readable storage medium (e.g., memory 606C in Figure 6C) of the power cord server 108. The computer-readable storage medium 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 the computer-readable storage medium may include source code, assembly language code, object code, or one or more other instruction formats interpreted by one or more processors. Some operations in the 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 in a server-side module 644 for the power cord plug-in module 632B or the power cord application 634B.

[0062] The power cord server 108 hosts a centralized power data management system for a plurality of remote medical devices 102 located in one or more medical facilities. In this centralized power data management system, the power cord server 108 is communicably 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 one of each 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 which includes a first cord device 106A (706). In some embodiments, one or more WANs 110 include a cellular network, and the plurality of power cables 104 are communicably coupled to the power cord server 108 via the cellular network without accessing any local network devices or local area networks. In some embodiments, communication via the cellular network is private and encrypted.

[0063] The power cord server 108 receives a power profile 120 from the first cord device 106A (708). The power profile 120 includes a number of power data characteristics 434 that measure the power supplied to the first medical device 102A while the first medical device 102A is performing 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 a 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, batches of power profiles from the first cord device 106A of the first power cable 104A are received in a single transmission according to a first reporting schedule (e.g., daily or weekly) (716). A batch includes a power profile 120 along with one or more additional power profiles 120 for one or more additional medical procedures, each of which has been previously performed in the first medical device 102A. In some embodiments, the power profile 120 is sent to the power cord server 108 according to a determination that the power profile 120 for a medical procedure meets certain predefined reporting criteria (e.g., the average active power 406 reaches a predefined threshold, or a predefined number of pulses are detected in the active power 406).

[0064] After receiving the power profile 120, the power cord server 108 uses the power profile 120 to identify the medical procedure performed, including one or more numerical operating parameters 436 of the medical procedure performed (718). In some embodiments, the power profile corresponds to a plurality of operating states 422-432, including a subset of the system idle state 424, system startup state 422, treatment start state 426, one or more treatment states 428, treatment idle state 430, and power off state 432 (720). The power cord server 108 identifies a subset of the plurality of operating states 422-432 of the medical procedure performed (722). Furthermore, in some embodiments, one or more treatment states 428 include a first treatment state 428A to which a power pulse train 450A is applied (724), and the plurality of power data characteristics 434 include the duration, frequency, power pattern, and average power peak value of the power pulse train 450A. The power cord server 108 determines one or more numerical operating parameters 436 of the treatment procedure performed based on a subset of power data characteristics 434 corresponding to a first treatment state 428A (726). In addition, in some embodiments, each of the plurality of operating states 422-432 is defined according to at least one power threshold 438 associated with each subset of power data characteristics 434. The power cord server 108 determines and adjusts the at least one power threshold 438 associated with each of the plurality of operating states 422-432 based on deep learning techniques. In addition, 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.

[0065] Referring to Figure 4A, in some embodiments, the power cord server 108 divides the power profile 120 into a plurality of power intervals (728). For each power interval, the power cord server 108 determines whether each power interval contains a power pulse train 450 (730). If each power interval contains 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). These are respective subsets of the power data characteristics 434 corresponding to each interval. If each power interval does not contain a power pulse train 450, the system determines one or more of the average current, average voltage, average active power, and reactive power (734). These are respective subsets of the power data characteristics 434 corresponding to each interval.

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

[0067] Alternatively, in some embodiments, each of a subset of power intervals (e.g., intervals corresponding to power pulse trains 450A and 450B in Figure 4A) is directly analyzed using a deep learning model to classify each power interval as an operating mode 420, an idle mode 418, one of several operating states 422-432, and / or one of several medical procedures. In some embodiments, the deep learning model is trained in a supervised manner based on labeled training data profiles 120. In some embodiments, the deep learning model is trained in an unsupervised manner using power profiles 120 collected from medical devices 102. For example, as the deep learning model processes more power profiles 120, it can classify power intervals more accurately and efficiently.

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

[0069] In some embodiments, the 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 a plurality of third power profiles 120" from a plurality of third power cables 104C (746). Each of the plurality of third power profiles 120" includes each of a plurality of third power data characteristics 434" that measure the current supplied to each third medical device 102C while each third medical device 102C is performing each third medical procedure. Each of the plurality of third power profiles 120" includes one or more third numerical operating parameters 436" for each third medical procedure. and used to identify each third medical procedure (748). Message 130 is generated based on one or more first numerical operating parameters 436 of the medical procedure performed and third numerical operating parameters 436" corresponding to a plurality of third power profiles 120" (750). In addition, in some embodiments, the first power profile 120 and the plurality of third power profiles 120" are subject to geographical or temporal limitations (752), and message 130 is generated based on geographical or temporal limitations.

[0070] The power cord server 108 sends a message 130 to the second electronic device for display on the user interface of the second electronic device (e.g., the interface in Figures 5A to 5C) (754). The message 130 specifies the medical procedure performed and one or more numerical operating parameters 436. In some embodiments, the message 130 includes a warning, notification, report, or instruction regarding the medical procedure 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, which includes a user interface. The power cord server 108 enables the display of the message 130 on the user interface of the power cord application 634A of the first medical device 102 (758). Alternatively, in some embodiments, the second electronic device includes the first medical device 102, and the first medical device is configured to run a medical device application 630A, which includes a user interface. The power cord server enables the display of message 130 on the user interface of the medical device application 630A (760). The 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 that runs on the power cord server 108 to present message 130.

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

[0072] Additionally and alternatively, in some embodiments, a second electronic device (e.g., a mobile phone) is separate from the first medical device, and the second electronic device is configured to run a medical device application 630A, which includes a user interface, for performing one or more medical procedures. The power cord server 108 enables the display of messages 130 on the user interface in the 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 that is run on the power cord server 108 to present messages 130.

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

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

[0075] It should be understood that the specific sequence of operations described in Figures 7A to 7D is merely illustrative and not intended to indicate that the described sequence is the only sequence in which the operations can be performed. Those skilled in the art will recognize the various methods of managing power data as described herein. In addition, it should be noted that the details described above with respect to Figures 1 to 6C are also applicable in a similar manner to method 700 described above with respect to Figures 7A to 7D. For the sake of brevity, these details will not be repeated here.

[0076] In one or more examples, the described functions may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functions may be stored as one or more instructions or codes on a computer-readable medium, or transmitted through a computer-readable medium and executed by a hardware-based processing unit. The computer-readable medium may include computer-readable storage media corresponding to tangible media such as data storage media, or communication media including any medium that facilitates the transfer of computer programs from one location to another (e.g., according to a communication protocol). Thus, the computer-readable medium may generally correspond to (1) non-temporary tangible computer-readable storage media, or (2) communication media such as signals or carrier waves. The data storage medium may be any available medium that can be accessed by one or more computers or one or more processors to obtain instructions, codes, and / or data structures for implementation of the embodiments described in this application. A computer program product may include computer-readable media.

[0077] The terms used in the description of embodiments herein are for the sole purpose of describing specific embodiments and are not intended to limit the scope of the claims. Where used in the description of embodiments and the appended claims, the singular forms “a,” “an,” and “the” are intended to include the plural form unless the context explicitly indicates otherwise. Where used herein, the terms “and / or” refer to and encompass all possible combinations of one or more of the enumerated items relating to the invention. Where used herein, the terms “equipped with” and / or “equipped with” specify the presence of the described features, elements, and / or components, but are not intended to exclude the presence or addition of one or more other features, elements, components, and / or groups thereof.

[0078] The terms "first" and "second" may be used herein to describe various elements, but it will be understood that these elements should not be limited by these terms. These terms are used solely to distinguish one element from another. For example, without departing from the scope of the embodiment, the first electrode may be called the second electrode, and the second electrode may be called the first electrode. The first electrode and the second electrode are both electrodes, but they are not the same electrode.

[0079] The description in this application is presented for illustrative and explanatory purposes and is not intended to be exhaustive or to limit the invention to the disclosed forms. Many modifications, variations, and alternative embodiments will be apparent to those skilled in the art who benefit from the teachings presented in the foregoing description and the associated drawings. The embodiments are described to best illustrate the principles and practical applications of the invention and to enable those skilled in the art to understand the invention in various embodiments and to best utilize the underlying principles and various embodiments by making various modifications to suit a particular intended use. Accordingly, the claims should not be limited to specific examples of the disclosed embodiments. Modifications and other embodiments are intended to be included within the scope of the appended claims. [Explanation of Symbols]

[0080] 100 Data Management Environments 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 First power cable 104B Second power cable 104C Third power cable 106 Power cord devices, cord devices 106A Power Cord Device, First Cord Device 106B Second Code Device 106C Third Power Cable, Third Medical Device 108 Power cord servers, smart cord servers, servers, cord servers, power cord systems 110 Communication networks, wide area networks (WANs) 112 Client Devices 114 Medical device server, server 120 power profiles, power profile data, labeled training data profiles 120' Second power profile 120" Third 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 connectors 222 processors, processing units 224 Network Interfaces 226 memory 228 Communications Bus 230 Input Devices 232 Output Devices 234 Operating Systems 236 Network Communication Module 238 Data Acquisition Modules 240 Data Preprocessing Modules 242 Data Reporting Module 244 Databases 248 Code Information and Settings 402 Root Mean Square (RMS) value of current, power parameters 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 Modes 422 System startup status, operating status 424 System Idle State 424A System idle state, operating state 424B System idle state, operating state 426 Treatment initiation state, operating state 428 Treatment status 428A Treatment status, first treatment status, operating status 428B Treatment status, Second treatment status, Operating status 430 Treatment idle state, operating state 432 Power off state, operating state 434 Power Data Characteristics 434' Second power data characteristics 434" Third power data characteristic 436 Numerical operation parameters, first numerical operation parameter 436' Second numerical operating parameter 436" Third numerical operating parameter 438 Power threshold 440 Therapeutic Power Signatures 442 Geographic distribution 450 Power Pulse Train 450A Power Pulse Train 450B Power Pulse Train 500 User Interfaces 502 Menu Area 504 Affordances 504A Device Overview Affordances 504B Device Map Affordance 504C Report Affordances 504D Consumables Order Affordance 505E Device Management Affordances 505F User Profile Affordances 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 Record of the latest events 512C List of the most active doctors 520 User Interface 522 Maps 524 List 540 User Interface 542 First region, region 544 Second area, area 546 Third area, area 548 The fourth area, area 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 Communications Bus 608B Communications Bus 608C Communications 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 Display 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 Treatment Module 630 applications, medical device applications 630A applications, medical device applications 630B Medical Device Applications 632 Programs 632A Program, Power Cord Plug-in Program 632B Power Cord Plug-in Program 632C Power Cord Plug-in Module 634A applications, power cord applications 634B applications, power cord applications 634C applications, power cord applications 636A Medical Device Data 636B Client Data 636C Server Data 638A Device Settings 638B Device Configuration 638C Device Configuration 640A User Account Information 640B User Account Information 640C User Account Information 642 Medical History Data 644 Server-side pages 646 Medical Treatment Data

Claims

1. A data management method, In a server system that hosts a centralized power data management system for multiple remote medical devices located in one or more medical facilities, A step of communicatingly coupling to a plurality of power cables via one or more wide area networks (WANs), each of which power cables includes a cord device and is configured to be electrically coupled to and power supply to one of the plurality of remote medical devices, the plurality of remote medical devices including a first medical device powered by a first power cable including a first cord device, A step of receiving a first power profile from the first coding device, wherein the first power profile includes a plurality of power data characteristics that measure the power supplied to the first medical device while the first medical device is performing a medical procedure, A step of using the first power profile to identify the medical procedure performed, including the type of the first medical device, the type of medical procedure performed, and one or more numerical operating parameters of the medical procedure performed; A step of sending a message to a second electronic device for display on the user interface of the second electronic device, wherein the message specifies the medical procedure performed and one or more numerical operating parameters used to coordinate subsequent medical procedures related to the second electronic device. A data management method that includes this.

2. The first power profile corresponds to a plurality of operating states, including a system idle state, a system startup state, a treatment start state, one or more treatment states, a treatment idle state, and a power-off state, and the step of identifying the medical procedure performed is, The step further includes identifying a subset of the plurality of operating states of the medical procedure performed, The method according to claim 1.

3. The one or more treatment states include a first treatment state to which a power pulse train is applied, the plurality of power data characteristics include the duration, frequency, power pattern, and average power peak value of the power pulse train, and the method is The step further includes determining one or more numerical operating parameters of the medical procedure performed based on a subset of the power data characteristics corresponding to the first treatment state, The method according to claim 2.

4. Each of the plurality of operating states is defined according to at least one power threshold associated with each subset of the power data characteristics, and the method is The process further includes 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.

5. The step of using the first power profile to identify the medical procedure performed is: The steps include dividing the first power profile into a plurality of power intervals, For each of the aforementioned power intervals, A step of determining whether each of the aforementioned power intervals includes a power pulse train, The steps include determining, in accordance with the determination that each of the aforementioned power intervals includes a power pulse train, one or more of the duration, pulse pattern, frequency, and average power peak value of the power pulse train as respective subsets of the power data characteristics corresponding to each of the aforementioned intervals, The steps include determining, in accordance with the determination that each of the aforementioned power intervals does not contain a power pulse train, one or more of the average current, average voltage, average active power, and reactive power as the respective subsets of the power data characteristics corresponding to each of the aforementioned intervals. Including, The method according to claim 1.

6. The step of using the first power profile to identify the medical procedure performed is: For each of the power intervals, the step of comparing each subset of the power data characteristics corresponding to each interval with at least each power threshold, The steps include associating the first operating state with the first power interval, in accordance with the determination that the comparison with the first power interval satisfies the association criteria for the first operating state, The steps include determining one or more numerical operating parameters of the medical procedure performed based on the respective subsets of the power data characteristics corresponding to the first power interval, and Including, The method according to claim 5.

7. The method according to claim 6, further comprising the step of determining and adjusting the respective power thresholds associated with the first operating state based on a first deep learning technique.

8. The one or more numerical operating parameters include one or more first numerical operating parameters, and the method is The steps include receiving a second power profile from a second cord device of a second power cable, which includes a plurality of second power data characteristics that measure the power supplied to the second medical device while the second medical device is performing the same medical procedure, The steps include using the second power profile to identify one or more second numerical operating parameters of the same medical procedure, and It further includes, The message is generated based on the first and second numerical operating parameters of the same medical procedure. The method according to any one of claims 1 to 7.

9. The steps include deriving a therapeutic power signature for the same medical procedure based on at least the first and second numerical operating parameters, The steps of generating the message including the therapeutic power signature and The method according to claim 8, further comprising:

10. The method according to claim 9, wherein the second electronic device is configured to coordinate the subsequent medical procedure performed by the second electronic device based on the therapeutic power signature received in the message.

11. The method according to claim 8, wherein the first power profile and the second power profile conform to geographical or temporal limitations, and the message is generated based on the geographical or temporal limitations.

12. The method according to any one of claims 1 to 11, wherein a batch of power profiles from the first cord device of the first power cable is received in a single transmission, and the batch comprises the first power profile together with one or more additional power profiles of one or more additional medical procedures, each of which has been previously performed in the first medical device according to a first reporting schedule.

13. The message is generated based on one or more numerical operating parameters of the medical procedure performed by the first medical device and multiple numerical operating parameters of the medical procedure performed by one or more additional medical devices. The second electronic device is the first medical device and is configured to receive the message for display on the user interface and to perform the medical procedure described above based on the message. The method according to any one of claims 1 to 12.

14. One or more processors, A memory that stores one or more programs configured to be executed by the one or more processors and A server system comprising, wherein one or more programs include instructions for performing the method described in any one of claims 1 to 13, Server system.

15. A non-temporary computer-readable medium for storing one or more programs configured to be executed by one or more processors of a server system, wherein the one or more programs include instructions for performing the method according to any one of claims 1 to 13.

Images