WO2024183529A1 - Data processing method and apparatus for medical device, electronic device, and medium - Google Patents

Abstract

A data processing method and apparatus for a medical device, an electronic device, and a storage medium. The method is executed by a distributed processing engine, and comprises: acquiring data to be processed and a device identifier, wherein the device identifier is used for identifying a medical device to which said data belongs; and when a target data processing engine matching the device identifier is found from a plurality of initial data processing engines pre-stored in a local database, sending said data to the target data processing engine, wherein the target data processing engine at least comprises a debugged data processing script corresponding to the device identifier, and the data processing script is used for processing said data.

Description

Data processing method, device, electronic device and medium for medical equipment

CROSS-REFERENCE TO RELATED APPLICATIONS

The present disclosure claims priority to the Chinese invention patent application No. 202310207537.4 filed on March 3, 2023, the entire contents of which are incorporated herein by reference.

Technical Field

The present disclosure relates to the field of medical health technology, and in particular to a data processing method, device, electronic device and storage medium for medical equipment.

Background Art

In the era of data-driven healthcare, medical devices (for example, wearable medical devices) as one of the main data interfaces are receiving more and more attention. Medical devices can collect various physiological index data of the human body, process the physiological index data collected by the medical devices, obtain data processing results, and then analyze the data processing results to obtain information with relevant medical significance.

In the related art, usually after collecting the relevant data to be processed of the medical device, a data processing script corresponding to the data to be processed is compiled, and then the data to be processed can be processed based on the data processing script.

In this way, every time a new data processing script is compiled to process the data to be processed, a series of processes such as development, joint debugging, testing, and online release of the data processing script need to be repeatedly introduced, which will make the data processing operation process more cumbersome.

Summary of the invention

The present disclosure aims to solve one of the technical problems in the related art at least to some extent.

To this end, the purpose of the present disclosure is to provide a data processing method, device, electronic device and storage medium for medical equipment.

An embodiment of one aspect of the present disclosure proposes a data processing method for medical devices, which is executed by a distributed processing engine, and includes: obtaining data to be processed and a device identifier, wherein the device identifier is used to identify the medical device to which the data to be processed belongs; if a target data processing engine matching the device identifier is found from multiple initial data processing engines pre-stored in a local database, the data to be processed is sent to the target data processing engine, wherein the target data processing engine includes at least: a debugged data processing script corresponding to the device identifier, and the data processing script is used to process the data to be processed.

An embodiment of another aspect of the present disclosure proposes a data processing method for medical devices, which is executed by a target data processing engine, and the target data processing engine at least includes: a data processing script, and the method includes: receiving data to be processed from a medical device sent by a distributed processing engine, wherein the medical device to which the data to be processed belongs has a device identification; processing the data to be processed according to the data processing script, wherein the data processing script corresponds to the device identification.

An embodiment of another aspect of the present disclosure proposes a data processing device for medical equipment, which is executed by a distributed processing engine, and the device includes: an acquisition module, used to acquire data to be processed and a device identification, wherein the device identification is used to identify the medical device to which the data to be processed belongs; a sending module, used to send the data to be processed to the target data processing engine when a target data processing engine matching the device identification is found from multiple initial data processing engines pre-stored in a local database, wherein the target data processing engine includes at least: a debugged data processing script corresponding to the device identification, and the data processing script is used to process the data to be processed.

An embodiment of another aspect of the present disclosure proposes a data processing device for medical equipment, wherein the target data processing engine at least includes: a data processing script, and the device includes: a receiving module for receiving the data to be processed of the medical equipment sent by the distributed processing engine, wherein the medical equipment to which the data to be processed belongs has a device identification; and a processing module for processing the data to be processed according to the data processing script, wherein the data processing script corresponds to the device identification.

An embodiment of another aspect of the present disclosure provides an electronic device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the program, it implements the data processing method for a medical device as proposed in the embodiment of the first aspect of the present disclosure, or implements the data processing method for a medical device as proposed in the embodiment of the second aspect of the present disclosure.

An embodiment of another aspect of the present disclosure proposes a non-temporary computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the data processing method for a medical device as proposed in the embodiment of the first aspect of the present disclosure, or implements the data processing method for a medical device as proposed in the embodiment of the second aspect of the present disclosure.

An embodiment of another aspect of the present disclosure proposes a computer program product. When an instruction processor in the computer program product executes, it executes the data processing method for a medical device as proposed in the embodiment of the first aspect of the present disclosure, or implements the data processing method for a medical device as proposed in the embodiment of the second aspect of the present disclosure.

Additional aspects and advantages of the present disclosure will be given in part in the following description and in part will be obvious from the following description or learned through practice of the present disclosure.

BRIEF DESCRIPTION OF THE DRAWINGS

The above and/or additional aspects and advantages of the present disclosure will become apparent and easily understood from the following description of the embodiments in conjunction with the accompanying drawings, in which:

FIG1 is a flow chart of a data processing method for medical equipment according to an embodiment of the present disclosure;

FIG2 is a schematic diagram of a process flow of data transmission to be processed proposed in an embodiment of the present disclosure;

FIG3 is a flow chart of a data processing method for medical equipment according to another embodiment of the present disclosure;

FIG4 is a flow chart of a data processing method for medical equipment according to another embodiment of the present disclosure;

FIG. 5 is a flowchart of a data processing method for medical equipment according to an embodiment of the present disclosure. Process diagram;

FIG6 is a schematic diagram of the structure of a data processing device for medical equipment according to an embodiment of the present disclosure;

FIG7 is a schematic diagram of the structure of a data processing device for medical equipment proposed in an embodiment of the present disclosure;

FIG8 shows a block diagram of an exemplary electronic device suitable for implementing embodiments of the present disclosure.

DETAILED DESCRIPTION

Embodiments of the present disclosure are described in detail below, and examples of the embodiments are shown in the accompanying drawings, wherein the same or similar reference numerals throughout represent the same or similar elements or elements having the same or similar functions. The embodiments described below with reference to the accompanying drawings are exemplary and are only used to explain the present disclosure, and should not be construed as limitations on the present disclosure. On the contrary, the embodiments of the present disclosure include all changes, modifications, and equivalents that fall within the spirit and connotation of the appended claims.

It should be noted that the processes of data acquisition, collection, storage, use, and processing in the technical solution disclosed in this disclosure comply with the provisions of relevant laws and regulations and do not violate public order and good morals.

FIG1 is a flow chart of a data processing method for medical equipment proposed in an embodiment of the present disclosure.

It should be noted that the executor of the data processing method for medical equipment in this embodiment is a data processing device for medical equipment, which can be implemented by software and/or hardware. The device can be configured in an electronic device, and the electronic device may include but is not limited to a terminal, a server, etc.

As shown in FIG. 1 , the data processing method for medical equipment is executed by a distributed processing engine, and the distributed processing engine may be, for example, Flink, without limitation.

S101: Acquire data to be processed and a device identifier, where the device identifier is used to identify the medical device to which the data to be processed belongs.

The medical device may specifically be a wearable medical device, and the medical device may specifically be a smart blood pressure meter, a smart blood glucose meter, etc., without limitation.

The data processing method for medical equipment described in the embodiments of the present disclosure can be used to process relevant data of the medical equipment, and the relevant data can specifically be, for example, human body indicator data monitored by the medical equipment for the user (for example, blood pressure data, blood sugar data, without limitation).

The device identifier may be used to identify a unique medical device, and the device identifier may be, for example, the name of the medical device, the serial number of the medical device, etc., without limitation.

In some embodiments, obtaining the data to be processed and the device identification can be to pre-build a data transmission link between the medical device and Flink, and then Flink can obtain the relevant indicator data of the medical device as the data to be processed based on the data transmission link between the medical device and Flink, and obtain the device number of the medical device as the device identification, without limitation.

In an embodiment of the present disclosure, refer to Figure 2, which is a flow chart of the transmission of pending data proposed in an embodiment of the present disclosure. As shown in Figure 2, the data to be processed and the device identification can be obtained by the MQTT Cluster monitoring the medical device, and when the medical device generates the data to be processed, the data to be processed and the device identification are reported to the MQTT Broker in the MQTT Cluster. The MQTT Broker plug-in can be pre-integrated with the Kafka Topic mapping rules in the Kafka Client, so that after obtaining the data to be processed and the device identification reported by the medical device, the data to be processed and the device identification can be mapped to the Kafka Topic in the Kafka Client, and then Flink can obtain the corresponding data to be processed and the device identification from the Kafka Topic.

S102: If a target data processing engine matching the device identifier is found from a plurality of initial data processing engines pre-stored in the local database, the data to be processed is sent to the target data processing engine.

Among them, the target data processing engine at least includes: a debugged data processing script corresponding to the device identifier (the data processing script can be specifically, for example, a (Java Script, JS) script.

Among them, the initial data processing engine is a script engine pre-stored in the local database of the platform to which the distributed processing engine belongs, and is used to process the data to be processed based on the data processing script. The initial data processing engine can be specifically, for example, a JS engine (the main function of the JS engine is to compile and execute scripts in combination with the characteristics of the JS script), and the target data processing engine is the initial data processing engine in the initial data processing engine that is adapted to the data to be processed. The target data processing engine can process the data to be processed based on the data processing script.

It is understandable that in the process of processing the data to be processed based on the data processing script, it is usually necessary to introduce a series of processes such as development, joint debugging, testing, and online release of the data processing script, which will make the data processing process more cumbersome. The debugged data processing script can be directly used to process the data to be processed, thereby effectively simplifying the data processing operation process.

That is to say, in the embodiment of the present disclosure, after obtaining the data to be processed and the device identification, it is possible to search whether there is a target data processing engine corresponding to the device identification in the local database of the platform to which the distributed processing engine belongs, and when a target data processing engine matching the device identification is found from multiple initial data processing engines pre-stored in the local database, the data to be processed is sent to the target data processing engine, and then, the target data processing engine can process the data to be processed based on compiling and executing the data processing script.

In the embodiment of the present disclosure, after determining the target data processing engine corresponding to the device identifier, the data to be processed can be sent to the target data processing engine, and then the target data processing engine can process the data to be processed based on the data processing script to implement the present disclosure. The data processing method for medical equipment described in the embodiment can be specifically referred to in the subsequent embodiments, which will not be described in detail here.

In an embodiment of the present disclosure, by obtaining the data to be processed and the device identification, wherein the device identification is used to identify the medical device to which the data to be processed belongs, and when a target data processing engine matching the device identification is found from multiple initial data processing engines pre-stored in a local database, the data to be processed is sent to the target data processing engine, wherein the target data processing engine at least includes: a debugged data processing script corresponding to the device identification, and the data processing script is used to process the data to be processed. Through the present disclosure, it is possible to directly match the target data processing engine used to process the data to be processed based on the device identification, and because the data processing engine contains a pre-debugged data processing script corresponding to the device identification, there is no need to repeatedly introduce a series of debugging processes such as development, joint debugging, testing, and online release of the data processing script, and then when the data to be processed is sent to the target data processing engine, the target data processing engine can directly complete the processing of the data to be processed based on the compiled data processing script, thereby effectively simplifying the data processing operation process.

FIG3 is a flow chart of a data processing method for medical equipment proposed in another embodiment of the present disclosure.

As shown in FIG3 , the data processing method for medical equipment includes:

S301: When the medical device is registered on the platform to which the distributed processing engine belongs, a candidate device identification of each medical device is obtained.

In the disclosed embodiment, when a certain medical device is introduced, the medical device may be registered on the platform to which the distributed processing engine belongs to obtain a candidate device identification of each medical device.

S302: Obtain a candidate processing script corresponding to each candidate device identifier.

The candidate processing script can be used to process the medical device identified by the corresponding candidate identifier. data to be processed.

After obtaining the candidate device identification of each medical device, the embodiment of the present disclosure can compile a corresponding candidate processing script for each candidate device identification, and then trigger the execution of subsequent data processing methods for the medical device based on the candidate processing script, without limitation.

S303: Storing the candidate processing scripts in a cloud database.

After obtaining the candidate processing script corresponding to each candidate device identifier, the embodiment of the present disclosure can store the candidate processing script in a cloud database, and then, in the subsequent execution of the data processing method for the medical device, support the rapid call of the pre-stored candidate processing script from the cloud database.

S304: Determine the storage address of each candidate processing script in the cloud database.

The storage address of the candidate processing script in the cloud database may be, for example, a resource locator of the candidate processing script in the cloud database, and there is no limitation on this.

That is, after storing the candidate processing scripts in the cloud database, the embodiment of the present disclosure may determine the resource locator of each candidate processing script in the cloud database as the storage address.

S305: Store the storage address in the local database of the platform to which the distributed processing engine belongs.

After determining the storage address of each candidate processing script in the cloud database, the embodiment of the present disclosure may store the storage address in the local database of the platform to which the distributed processing engine belongs.

S306: Allocate index items to the storage addresses stored in the local database.

The index item can be used to obtain the corresponding storage address from the local database.

In the disclosed embodiment, by determining the storage address of each candidate processing script in the cloud database, and storing the storage address in the local database of the platform to which the distributed processing engine belongs, and then assigning an index item to the storage address stored in the local database, since the storage address of the candidate processing script in the cloud database is stored in the local database, the storage resources of the local database can be effectively saved, and by assigning an index item to the storage address stored in the local database, the storage address can be conveniently obtained from the local database.

In some embodiments, assigning an index item to a storage address stored in a local database may be performed by using the last character of the storage address as the index item of the storage address stored in the local database, and there is no limitation to this.

For example, assuming the storage address is "asdgjfkl111", an index item is assigned to the storage address stored in the local database. The last character "1" can be used as the index item of the storage address "asdgjfkl111" in the local database. There is no limitation on this.

Optionally, in some embodiments, assigning an index item to a storage address stored in a local database may be accomplished by configuring a candidate device identifier as an index item of a storage address stored in the local database, and then, during the execution of a data processing method for a medical device, the storage address of a candidate processing script corresponding to the device identifier may be accurately called according to the device identifier.

S307: Acquire the data to be processed and the device identification, wherein the device identification is used to identify the medical device to which the data to be processed belongs.

S308: If a target data processing engine matching the device identifier is found from a plurality of initial data processing engines pre-stored in the local database, the data to be processed is sent to the target data processing engine.

The specific description of S308 can be found in the above embodiment, which will not be repeated here.

In the embodiment of the present disclosure, by obtaining the candidate device identification of each medical device when the medical device is registered on the platform to which the distributed processing engine belongs, and obtaining the candidate processing script corresponding to each candidate device identification, and then storing the candidate processing script in the cloud database, it is possible to support the rapid call of pre-stored candidate processing scripts from the cloud database in the subsequent execution process of the data processing method for the medical device, determine the storage address of each candidate processing script in the cloud database, store the storage address in the local database of the platform to which the distributed processing engine belongs, and then assign index items to the storage addresses stored in the local database. Since the storage addresses of the candidate processing scripts in the cloud database are stored in the local database, the storage resources of the local database can be effectively saved. By assigning index items to the storage addresses stored in the local database, it is possible to facilitate the call from the local database to the local database. The storage address is obtained from the database, and then the data to be processed and the device identification are obtained, the device identification is used to identify the medical device to which the data to be processed belongs, and when a target data processing engine matching the device identification is found from multiple initial data processing engines pre-stored in the local database, the data to be processed is sent to the target data processing engine, wherein the target data processing engine at least includes: a debugged data processing script corresponding to the device identification, the data processing script is used to process the data to be processed, and since the data processing engine contains a pre-debugged data processing script corresponding to the device identification, there is no need to repeatedly introduce a series of debugging processes such as development, joint debugging, testing, and online launch of the data processing script, and then when the data to be processed is sent to the target data processing engine, the target data processing engine can directly complete the processing of the data to be processed based on the compiled data processing script, thereby effectively simplifying the data processing operation process.

FIG. 4 is a flow chart of a data processing method for medical equipment proposed in another embodiment of the present disclosure.

As shown in FIG4 , the data processing method for medical equipment includes:

S401: Obtain the data to be processed and the device identification, wherein the device identification is used to identify the data to be processed. The medical device that processes the data.

The specific description of S401 can be found in the above embodiment and will not be repeated here.

S402: If a target data processing engine matching the device identifier is found from a plurality of initial data processing engines pre-stored in the local database, the target data processing engine is constructed based on the data processing script.

That is to say, in the embodiment of the present disclosure, after obtaining the data to be processed and the device identification, it is possible to search whether there is a target data processing engine corresponding to the device identification in the local database of the platform to which the distributed processing engine belongs, and when the target data processing engine that matches the device identification is not found from the multiple initial data processing engines pre-stored in the local database, the target data processing engine is constructed based on the data processing script, and then, the target data processing engine can process the data to be processed based on compiling and executing the data processing script.

Optionally, in some embodiments, before building a data processing engine based on the data processing script, a target index item corresponding to the device identifier can also be determined from multiple index items in the local database, wherein each index item is used to index a storage address, and based on the storage address indexed from the local database by the target index item, the data processing script is determined from multiple candidate processing scripts stored in the cloud database based on the storage address obtained by the index.

The index item corresponding to the device identifier determined from among the multiple index items in the local database may be referred to as the target index item.

That is to say, in the embodiment of the present disclosure, the target index item corresponding to the device identifier can be determined from the local database, and then the storage address obtained by indexing from the local database based on the target index item can be used to determine the data processing script from multiple candidate processing scripts stored in the cloud database according to the storage address obtained by indexing. In this way, it can be ensured that the acquired data processing script can match the device identifier, so that in the subsequent execution process of the processing method for the medical device, it can be ensured that the constructed data processing engine can Supports processing of data identified by corresponding devices.

Optionally, in some embodiments, a target index item corresponding to a device identifier is determined from multiple index items in a local database. This may be by determining multiple candidate device identifiers from the local database, and determining a candidate device identifier that is identical to the device identifier among the multiple candidate device identifiers, and then using the identical candidate device identifier as the target index item.

That is to say, in the embodiments of the present disclosure, after obtaining the corresponding device identifier, a candidate device identifier that is identical to the device identifier can be determined from multiple candidate device identifiers stored in the local database, and the candidate device identifier that is identical to the device identifier can be used as the target index item. Then, based on the target index item, a storage address can be indexed from the local database, and then, according to the storage address obtained by indexing, a data processing script can be determined from multiple candidate processing scripts stored in the cloud database.

S403: If a target data processing engine matching the device identifier is not found from the multiple initial data processing engines pre-stored in the local database, the target data processing engine is constructed based on the data processing script.

The specific description of S403 can be found in the above embodiment, which will not be repeated here.

In the disclosed embodiment, by obtaining the data to be processed and the device identification, wherein the device identification is used to identify the medical device to which the data to be processed belongs, and determining the search result obtained by searching the data processing engine in the local database, and then determining the target determination method of the data processing engine based on the search result, and determining the data processing engine corresponding to the device identification based on the target determination method, thereby, the data processing engine corresponding to the device identification can be accurately determined based on the target determination method, and then the data to be processed is sent to the data processing engine, thereby, a suitable data processing engine can be provided for the data to be processed, thereby effectively simplifying the data processing operation process and effectively improving the data processing effect.

FIG. 5 is a flowchart of a data processing method for medical equipment according to an embodiment of the present disclosure. Process diagram.

It should be noted that the executor of the data processing method for medical equipment in this embodiment is a data processing device for medical equipment, which can be implemented by software and/or hardware. The device can be configured in an electronic device, and the electronic device may include but is not limited to a terminal, a server, etc.

As shown in Figure 5, the data processing method for medical equipment is executed by a target data processing engine, which at least includes: a data processing script. The target data processing engine can be specifically, for example, a JS engine. Accordingly, the data processing script can be specifically, for example, a JS script, without limitation.

S501: Receive data to be processed of a medical device sent by a distributed processing engine, wherein the medical device to which the data to be processed belongs has a device identifier.

The meanings and descriptions of the terms in this embodiment that are the same as those in the above embodiments can be specifically referred to in the above embodiments and will not be repeated here.

In the embodiment of the present disclosure, the data to be processed of the medical device sent by the distributed processing engine can be received via a data transmission link between the distributed processing engine and the target data processing engine. Then, the data to be processed can be processed by the target data processing engine. For details, please refer to the subsequent embodiments and will not be repeated here.

S502: Process the data to be processed according to a data processing script, wherein the data processing script corresponds to the device identifier.

In the embodiment of the present disclosure, after receiving the data to be processed of the medical device sent by the distributed processing engine, the target data processing engine can process the data to be processed according to the data processing script.

In this embodiment, the data to be processed of the medical device sent by the distributed processing engine is received, wherein the medical device to which the data to be processed belongs has a device identification, and the data to be processed is processed according to the data processing script, wherein the data processing script corresponds to the device identification. Thus, the data processing script can be independently compiled in the target data processing engine, and can support independent operation between multiple engines, effectively avoiding mutual influence between the simultaneous processing of multiple device data, and effectively ensuring the data processing effect.

FIG6 is a schematic diagram of the structure of a data processing device for medical equipment proposed in an embodiment of the present disclosure.

As shown in FIG6 , the data processing device 60 for medical equipment includes:

An acquisition module 601 is used to acquire the data to be processed and the device identification, wherein the device identification is used to identify the medical device to which the data to be processed belongs;

The sending module 602 is used to send the data to be processed to the target data processing engine when a target data processing engine matching the device identifier is found from multiple initial data processing engines pre-stored in the local database, wherein the target data processing engine at least includes: a debugged data processing script corresponding to the device identifier, and the data processing script is used to process the data to be processed.

In some embodiments of the present disclosure, the data processing device 60 for medical equipment is further used to:

When the medical device is registered on the platform to which the distributed processing engine belongs, obtaining a candidate device identifier for each medical device;

Obtaining a candidate processing script corresponding to each candidate device identifier;

The candidate processing scripts are stored in a cloud database.

In some embodiments of the present disclosure, the data processing device 60 for medical equipment is further used to:

Determine the storage address of each candidate processing script in the cloud database;

Storing the storage address in a local database of the platform to which the distributed processing engine belongs;

Assign index entries to storage addresses stored in the local database.

In some embodiments of the present disclosure, the data processing device 60 for medical equipment is further used to:

The candidate device identification is configured as an index item of the storage address stored in the local database.

In some embodiments of the present disclosure, the data processing device 60 for medical equipment is further used to:

Determine a target index item corresponding to the device identifier from a plurality of index items in a local database, wherein each index item is used to index a storage address;

Obtain storage address from local database based on target index item;

According to the storage address obtained by the index, a data processing script is determined from a plurality of candidate processing scripts stored in the cloud database.

In some embodiments of the present disclosure, the data processing device 60 for medical equipment is further used to:

Determine multiple candidate device identifiers from a local database;

Determine a candidate device identifier that is identical to the device identifier among multiple candidate device identifiers;

The same candidate device identifier is used as the target index item.

In some embodiments of the present disclosure, the data processing device 60 for medical equipment is further used to:

If a target data processing engine matching the device identifier is not found from a plurality of initial data processing engines pre-stored in the local database, the target data processing engine is constructed based on the data processing script.

Corresponding to the data processing method for medical equipment provided in the embodiments of FIGS. 1 to 5 above, the present disclosure further provides a data processing device for medical equipment. Since the data processing device for medical equipment provided in the embodiments of the present disclosure is consistent with the data processing method for medical equipment provided in the embodiments of FIGS. 1 to 5 above, The provided data processing method for medical equipment corresponds to the data processing method for medical equipment, so the implementation of the data processing method for medical equipment is also applicable to the data processing device for medical equipment provided in the embodiment of the present disclosure, and will not be described in detail in the embodiment of the present disclosure.

In this embodiment, by obtaining the data to be processed and the device identification, wherein the device identification is used to identify the medical device to which the data to be processed belongs, and when a target data processing engine matching the device identification is found from multiple initial data processing engines pre-stored in a local database, the data to be processed is sent to the target data processing engine, wherein the target data processing engine at least includes: a debugged data processing script corresponding to the device identification, and the data processing script is used to process the data to be processed. Through the present disclosure, it is possible to directly match the target data processing engine used to process the data to be processed based on the device identification, and because the data processing engine contains a pre-debugged data processing script corresponding to the device identification, there is no need to repeatedly introduce a series of debugging processes such as development, joint debugging, testing, and online launch of the data processing script, and then when the data to be processed is sent to the target data processing engine, the target data processing engine can directly complete the processing of the data to be processed based on the compiled data processing script, thereby effectively simplifying the data processing operation process.

FIG. 7 is a schematic diagram of the structure of a data processing device for medical equipment proposed in an embodiment of the present disclosure.

As shown in FIG. 7 , the data processing device 70 for medical equipment includes:

The receiving module 701 is used to receive the to-be-processed data of the medical device sent by the distributed processing engine, wherein the medical device to which the to-be-processed data belongs has a device identification;

The processing module 702 is used to process the data to be processed according to the data processing script, wherein the data processing script corresponds to the device identifier.

Corresponding to the data processing method for medical equipment provided in the embodiments of FIGS. 1 to 5 above, the present disclosure further provides a data processing device for medical equipment. Since the data processing device for medical equipment provided in the embodiments of the present disclosure corresponds to the data processing method for medical equipment provided in the embodiments of FIGS. 1 to 5 above, The implementation of the data processing method is also applicable to the data processing device for medical equipment provided in the embodiment of the present disclosure, and will not be described in detail in the embodiment of the present disclosure.

In the disclosed embodiment, the data to be processed of the medical device sent by the distributed processing engine is received, wherein the medical device to which the data to be processed belongs has a device identification, and the data to be processed is processed according to a data processing script, wherein the data processing script corresponds to the device identification. Thus, the data processing script can be independently compiled in the target data processing engine, and can support independent operation between multiple engines, effectively avoiding mutual influence between the simultaneous processing of data from multiple devices, and effectively ensuring the data processing effect.

In order to implement the above embodiments, the present disclosure also proposes an electronic device, including: a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the program, it implements the data processing method for medical equipment proposed in the above embodiments of the present disclosure.

In order to implement the above embodiments, the present disclosure also proposes a non-temporary computer-readable storage medium on which a computer program is stored. When the program is executed by a processor, it implements the data processing method for medical equipment proposed in the above embodiments of the present disclosure.

In order to implement the above embodiments, the present disclosure further proposes a computer program product. When an instruction processor in the computer program product executes, the data processing method for a medical device proposed in the above embodiments of the present disclosure is executed.

Fig. 8 shows a block diagram of an exemplary electronic device suitable for implementing the embodiments of the present disclosure. The electronic device shown in Fig. 8 is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present disclosure.

As shown in FIG8 , the electronic device is presented in the form of a general-purpose computing device. The components of the electronic device may include, but are not limited to: one or more processors or processing units 16, a system memory 28, and a computer that connects different system components (including the system memory 28 and the processing unit 16). Bus 18.

Bus 18 represents one or more of several types of bus structures, including a memory bus or memory controller, a peripheral bus, a graphics acceleration port, a processor or a local bus using any of a variety of bus structures. For example, these architectures include but are not limited to Industry Standard Architecture (hereinafter referred to as: ISA) bus, Micro Channel Architecture (hereinafter referred to as: MAC) bus, Enhanced ISA bus, Video Electronics Standards Association (hereinafter referred to as: VESA) local bus and Peripheral Component Interconnection (hereinafter referred to as: PCI) bus.

Electronic devices typically include a variety of computer system readable media. These media can be any available media that can be accessed by the electronic device, including volatile and non-volatile media, removable and non-removable media.

The memory 28 may include computer system readable media in the form of volatile memory, such as random access memory (RAM) 30 and/or cache memory 32. The electronic device may further include other removable/non-removable, volatile/non-volatile computer system storage media. By way of example only, the storage system 34 may be used to read and write non-removable, non-volatile magnetic media (not shown in FIG. 8 , commonly referred to as a “hard drive”).

Although not shown in FIG. 8 , a disk drive for reading and writing a removable nonvolatile disk (e.g., a “floppy disk”) and an optical disk drive for reading and writing a removable nonvolatile optical disk (e.g., a compact disc read only memory (CD-ROM), a digital versatile disc read only memory (DVD-ROM), or other optical media) may be provided. In these cases, each drive may be connected to the bus 18 via one or more data medium interfaces. The memory 28 may include at least one program product having a set (e.g., at least one) of program modules configured to perform the functions of the various embodiments of the present disclosure.

A program/utility 40 having a set (at least one) of program modules 42 may be stored, for example, in the memory 28, such program modules 42 including but not limited to an operating system, one or more application programs, other program modules, and program data, each of which or some combination may include an implementation of a network environment. The program modules 42 generally perform the functions and/or methods of the embodiments described in the present disclosure.

The electronic device may also communicate with one or more external devices 14 (e.g., keyboard, pointing device, display 24, etc.), may also communicate with one or more devices that enable a user to interact with the electronic device, and/or communicate with any device that enables the electronic device to communicate with one or more other computing devices (e.g., network card, modem, etc.). Such communication may be performed through an input/output (I/O) interface 22. Furthermore, the electronic device may also communicate with one or more networks (e.g., a local area network (LAN), a wide area network (WAN), and/or a public network, such as the Internet) through a network adapter 20. As shown, the network adapter 20 communicates with other modules of the electronic device through a bus 18. It should be understood that, although not shown in the figure, other hardware and/or software modules may be used in conjunction with the electronic device, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems.

The processing unit 16 executes various functional applications and data processing by running the programs stored in the system memory 28, such as implementing the data processing method for medical equipment mentioned in the above embodiments.

Those skilled in the art will readily appreciate other embodiments of the present disclosure after considering the specification and practicing the invention disclosed herein. The present disclosure is intended to cover any variations, uses, or adaptations of the present disclosure that follow the general principles of the present disclosure and include common knowledge or customary techniques in the art that are not disclosed in the present disclosure. The description and examples are to be considered exemplary only, and the true scope and spirit of the present disclosure are indicated by the following claims.

It should be understood that the present disclosure is not limited to the exact structures that have been described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.

It should be noted that, in the description of the present disclosure, the terms "first", "second", etc. are only used for descriptive purposes and cannot be understood as indicating or implying relative importance. In addition, in the description of the present disclosure, unless otherwise specified, the meaning of "plurality" is two or more.

Any process or method description in a flowchart or otherwise described herein may be understood to represent a module, segment or portion of code that includes one or more executable instructions for implementing the steps of a specific logical function or process, and the scope of the preferred embodiments of the present disclosure includes alternative implementations in which functions may not be performed in the order shown or discussed, including performing functions in a substantially simultaneous manner or in the reverse order depending on the functions involved, which should be understood by those skilled in the art to which the embodiments of the present disclosure belong.

It should be understood that the various parts of the present disclosure can be implemented in hardware, software, firmware or a combination thereof. In the above-mentioned embodiments, multiple steps or methods can be implemented in software or firmware stored in a memory and executed by a suitable instruction execution system. For example, if implemented in hardware, as in another embodiment, it can be implemented by any one of the following technologies known in the art or their combination: a discrete logic circuit having a logic gate circuit for implementing a logic function for a data signal, a dedicated integrated circuit having a suitable combination of logic gate circuits, a programmable gate array (PGA), a field programmable gate array (FPGA), etc.

A person skilled in the art may understand that all or part of the steps in the method for implementing the above-mentioned embodiment may be completed by instructing related hardware through a program, and the program may be stored in a computer-readable storage medium, which, when executed, includes one or a combination of the steps of the method embodiment.

In addition, each functional unit in each embodiment of the present disclosure can be integrated into a processing unit. In the module, each unit may exist physically separately, or two or more units may be integrated into one module. The above-mentioned integrated module may be implemented in the form of hardware or in the form of a software functional module. If the integrated module is implemented in the form of a software functional module and sold or used as an independent product, it may also be stored in a computer-readable storage medium.

The storage medium mentioned above can be a read-only memory, a magnetic disk or an optical disk, etc.

In the description of this specification, the description with reference to the terms "one embodiment", "some embodiments", "example", "specific example", or "some examples" means that the specific features, structures, materials or characteristics described in conjunction with the embodiment or example are included in at least one embodiment or example of the present disclosure. In this specification, the schematic representation of the above terms does not necessarily refer to the same embodiment or example. Moreover, the specific features, structures, materials or characteristics described may be combined in any one or more embodiments or examples in a suitable manner.

Although the embodiments of the present disclosure have been shown and described above, it is to be understood that the above embodiments are illustrative and are not to be construed as limitations of the present disclosure. A person skilled in the art may change, modify, replace and vary the above embodiments within the scope of the present disclosure.

Claims (12)

A data processing method for a medical device, which is executed by a distributed processing engine, the method comprising: Acquire the data to be processed and the device identification, wherein the device identification is used to identify the medical device to which the data to be processed belongs; If a target data processing engine matching the device identifier is found from a plurality of initial data processing engines pre-stored in a local database, the data to be processed is sent to the target data processing engine, wherein the target data processing engine includes at least: a debugged data processing script corresponding to the device identifier, and the data processing script is used to process the data to be processed. The method according to claim 1, wherein the method further comprises: When the medical device is registered on the platform to which the distributed processing engine belongs, obtaining a candidate device identification of each medical device; Obtaining a candidate processing script corresponding to each of the candidate device identifiers; The candidate processing scripts are stored in a cloud database. The method according to claim 2, wherein after storing the candidate processing script in a cloud database, the method further comprises: Determine a storage address of each of the candidate processing scripts in the cloud database; Storing the storage address in a local database of the platform to which the distributed processing engine belongs; An index item is assigned to the storage address stored in the local database. The method of claim 3, wherein the assigning of index items to the storage addresses stored in the local database comprises: The candidate device identification is configured as an index item of the storage address stored in the local database. The method according to claim 3, wherein the method further comprises: Determine a target index item corresponding to the device identifier from a plurality of the index items in the local database, wherein each of the index items is used to index a storage address; Obtaining the storage address from the local database based on the target index item; According to the storage address obtained by the index, the data processing script is determined from the plurality of candidate processing scripts stored in the cloud database. The method of claim 5, wherein determining the target index item corresponding to the device identifier from the plurality of index items in the local database comprises: Determining a plurality of candidate device identifiers from the local database; Determine a candidate device identifier that is identical to the device identifier among the multiple candidate device identifiers; The same candidate device identifier is used as the target index item. The method according to claim 1, wherein the method further comprises: If the target data processing engine matching the device identifier is not found from the plurality of initial data processing engines pre-stored in the local database, the target data processing engine is constructed based on the data processing script. A data processing method for a medical device, which is executed by a target data processing engine, the target data processing engine at least comprising a data processing script, the method comprising: Receiving data to be processed from a medical device sent by a distributed processing engine, wherein the medical device to which the data to be processed belongs has a device identifier; The data to be processed is processed according to the data processing script, wherein the data processing script corresponds to the device identifier. A data processing device for medical equipment, which is executed by a distributed processing engine, comprising: An acquisition module, used for acquiring the data to be processed and a device identification, wherein the device identification is used for identifying the medical device to which the data to be processed belongs; The sending module is used to process multiple initial data pre-stored in the local database When a target data processing engine matching the device identifier is found in the engine, the data to be processed is sent to the target data processing engine, wherein the target data processing engine at least includes: a debugged data processing script corresponding to the device identifier, and the data processing script is used to process the data to be processed. A data processing device for medical equipment, which is executed by a target data processing engine, the target data processing engine at least comprising a data processing script, the device comprising: A receiving module, used for receiving the to-be-processed data of the medical device sent by the distributed processing engine, wherein the medical device to which the to-be-processed data belongs has a device identification; A processing module is used to process the data to be processed according to the data processing script, wherein the data processing script corresponds to the device identifier. An electronic device, comprising: at least one processor; and a memory communicatively coupled to the at least one processor, in, The memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to execute the method described in any one of claims 1 to 7, or execute the method described in claim 8. A non-transitory computer-readable storage medium storing computer instructions, wherein the computer instructions are used to cause the computer to execute the method of any one of claims 1 to 7, or to execute the method of claim 8.