Medical health data management method and front-end equipment

Abstract

The present application provides a medical health data management method and front-end device, the method comprising: obtaining health management data sent by the interface of the currently connected medical health device; determining the interface type of the currently connected medical health device according to the encoding rules of the health management data, and determining a matching target data parsing protocol according to the interface type; parsing the health management data through the target data parsing protocol; and sending the parsed health management data to the cloud.

Description

Technical Field

[0001] The present application relates to the technical field of medical health data processing, and in particular to a medical health data management method and front-end equipment. Background Art

[0002] Currently, there are more and more types of medical and health products, and the product forms are various. As a highly targeted product, a certain type of medical and health product is generally designed to measure a certain physiological parameter indicator (such as weight scales, blood pressure monitors, blood oximeters, blood glucose meters, etc.). With the rapid development of Internet of Things technology, the rapid advancement of medical technology, and the upgrading of personal health concepts, the networking, service-oriented and intelligent development of medical and health products is the future development trend. This requires various types of medical and health products to be connected to the network for systematic big data analysis and application.

[0003] As healthcare products become more connected to the Internet of Things (IoT), intelligent, and systematized, they face several challenges in connecting their data to the network. First, different types of healthcare products and manufacturers have different external data interfaces, requiring the design of corresponding hardware interfaces for connection. This is the current solution, but the drawback is that as the number of product types increases, the number of hardware interfaces also increases, increasing the complexity and cost of system hardware design, and limiting hardware design flexibility. Second, data protocols and formats vary between products and manufacturers, requiring corresponding protocol and data parsing. The current solution is to have this parsing work performed by the firmware of the front-end device. When adding new devices, firmware must be developed first and then updated to the front-end device. This approach has the disadvantage of requiring frequent firmware updates, making it more difficult to implement for front-end devices that lack remote upgrade capabilities or are already installed in households. Third, in terms of product software and hardware development and system application design, the current state of product software, hardware, and system architecture, due to the need to adapt to the diversity of front-end user products, requires managing a large number of hardware and firmware versions, resulting in low resource utilization efficiency, difficulty in reducing costs, and a significant amount of duplicated development work and labor costs. Summary of the Invention

[0004] In order to solve the existing technical problems, this application provides a medical health data management method and front-end equipment that can reduce a lot of software and hardware development work, have high product versatility, reduce costs and improve resource utilization.

[0005] To achieve the above objectives, the technical solution of the embodiment of the present application is implemented as follows:

[0006] A medical health data management method, applied to a front-end device, comprising:

[0007] Obtain health management data sent by the interface of the currently connected medical and health equipment;

[0008] Determine the interface type of the currently connected medical and health device according to the coding rules of the health management data, and determine the matching target data parsing protocol according to the interface type;

[0009] Parsing the health management data using the target data parsing protocol;

[0010] The analyzed health management data is sent to the cloud.

[0011] The step of determining the interface type of the currently connected medical and health device according to the coding rules of the health management data and determining the matching target data parsing protocol according to the interface type includes:

[0012] Performing a traversal decoding test on the health management data through a preset interface program module;

[0013] When one of the interface program modules is met, the interface type of the currently connected medical and health device is determined according to the interface program module that meets the requirements;

[0014] A matching target data parsing protocol is determined according to the interface type.

[0015] The method of determining the interface type of the currently connected medical and health device according to the coding rules of the health management data and determining the matching target data parsing protocol according to the interface type further includes:

[0016] When none of the interface program modules meet the requirements, the information is confirmed as an unknown type and reported to the cloud.

[0017] The step of determining the interface type of the currently connected medical and health device according to the coding rules of the health management data and determining the matching target data parsing protocol according to the interface type includes:

[0018] Determine the interface type of the currently connected medical and health device according to the coding rules of the health management data, and determine the matching target data parsing protocol according to the interface type;

[0019] The data interface currently connected to the medical health device is configured, and the data interface is associated with the matching target data parsing protocol.

[0020] Before sending the parsed health management data to the cloud, the method further includes:

[0021] The parsed health management data is pre-processed according to a preset data processing algorithm.

[0022] A front-end device includes a first chip, a second chip and a memory, wherein the memory stores a plurality of preset interface program modules, wherein the first chip obtains health management data sent by the interface of the currently connected medical and health device; determines the interface type of the currently connected medical and health device according to the encoding rules of the health management data, and determines the matching target data parsing protocol according to the interface type; the first chip or the second chip parses the health management data through the target data parsing protocol; and the second chip sends the parsed health management data to the cloud.

[0023] Among them, the front-end device is a gateway, the first chip is a CPLD chip, and the second chip is an ARM chip.

[0024] Among them, the front-end device is an edge computing device, the first chip is an FPGA chip, and the second chip is an ARM chip.

[0025] Among them, the second chip also includes obtaining an interface type selection instruction and reporting the interface type selection instruction to the cloud; the cloud configures the target data interface according to the interface program module that matches the interface type selection instruction; or, obtains the interface program module that matches the interface type selection instruction issued by the cloud, and stores the interface program module in the memory.

[0026] The second chip further includes obtaining an interface type configuration instruction for a target data interface, and the first chip configures the target data interface according to the interface type configuration instruction, and associates the target data interface with a matching data parsing protocol.

[0027] The medical health data management method and front-end device provided in the above embodiments of the present application can connect to medical health devices with various types of interfaces. By obtaining the health management data sent by the interface of the currently connected medical health device, the interface type of the currently connected medical health device is determined according to the encoding rules of the health management data, and the matching target data parsing protocol is determined according to the interface type. The health management data is parsed through the target data parsing protocol, and the parsed health management data is sent to the cloud. In this way, the same front-end device can adapt to medical health devices with various types of interfaces, which can greatly reduce the firmware and hardware upgrade and management costs of the front-end device and meet the data management requirements of diverse medical health devices. BRIEF DESCRIPTION OF THE DRAWINGS

[0028] Figure 1 Schematic diagram of optional application scenarios of a medical and health data management system in one embodiment;

[0029] Figure 2 is a flow chart of a medical health data management method in one embodiment;

[0030] Figure 3 A schematic diagram of the data interface configuration of the front-end device;

[0031] Figure 4 Another schematic diagram of the data interface configuration of the front-end device;

[0032] Figure 5 Another schematic diagram of the data interface configuration of the front-end device;

[0033] Figure 6 A schematic diagram of the working principle of implementing a healthcare data management method for a gateway;

[0034] Figure 7 A schematic diagram illustrating the working principle of implementing a healthcare data management method for edge computing devices;

[0035] Figure 8 A schematic diagram of a system workflow for implementing the medical and health data management method;

[0036] Figure 9 Schematic diagram of the workflow of another system for implementing the medical and health data management method. DETAILED DESCRIPTION

[0037] The technical solution of this application is further elaborated in detail below with reference to the accompanying drawings and specific embodiments.

[0038] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by those skilled in the art to which this application pertains. The terms used herein in the specification of this application are intended only to describe specific embodiments and are not intended to limit the implementation of this application. The term "and / or" as used herein includes any and all combinations of one or more of the associated listed items.

[0039] In the description of this application, it should be understood that the terms "center," "up," "down," "front," "back," "left," "right," "vertical," "horizontal," "top," "bottom," "inside," "outside," and the like, indicating orientations or positional relationships, are based on the orientations or positional relationships shown in the accompanying drawings and are intended only to facilitate the description of this application and simplify the description. They do not indicate or imply that the devices or elements referred to must have a specific orientation, be constructed, or operate in a specific orientation. Therefore, they should not be construed as limiting this application. In the description of this application, unless otherwise specified, "plurality" means two or more.

[0040] In the description of this application, it should be noted that, unless otherwise expressly specified or limited, the terms "mounted," "connected," and "connected" should be understood broadly. For example, they can refer to fixed connections, detachable connections, or integral connections; they can refer to direct connections, indirect connections through an intermediate medium, or internal communication between two components. Those skilled in the art will understand the specific meanings of the above terms in this application based on the specific circumstances.

[0041] See also Figure 1 , which is a schematic diagram of optional application scenarios of the medical and health data management system provided in an embodiment of the present application, including a cloud 30, a front-end device 20 and a medical and health device 10. Among them, the front-end device 20 can be a gateway or an edge computing device. The medical and health device 10 can be various medical and health products designed for measuring a certain physiological parameter indicator, such as a weight scale, a blood pressure monitor, an oximeter, a blood glucose meter, etc. The interface types of medical and health products of different types and brands for measuring different physiological parameters are usually different, such as SPI (Serial Peripheral Interface), IIC (Inter Integrated-Circuit, bus interface), UART (Universal Asynchronous Receiver Transmitter), USB (Universal Serial Bus), etc. The data interface of the front-end device 20 is designed to be programmable to change the hardware interface type (such as SPI, IIC, UART, USB, etc.), and the interface type implementation function package or IP core is stored on the front-end device 20. According to the interface type of different medical and health devices 10 to be connected, the cloud can remotely configure the front-end device 20 and select to run the hardware interface type implementation function package or IP core corresponding to the currently connected medical and health device 10, so that the front-end device 20 hardware can be connected to medical and health devices 10 with various hardware interface types without changing. The data parsing protocols of different types of medical and health devices 10 are designed in the form of protocol packages, which are stored on the front-end device 20 (gateway, edge computing device, etc.). By remotely selecting, adding, and deleting protocol packages on the front-end device 20, the front-end device 20 firmware can be used to parse the data protocol of the connected product without changing it.

[0042] See also Figure 2 , a medical health data management method provided in the embodiment of the present application, which can be applied to Figure 1 The front-end device shown. The medical health data management method may include the following steps:

[0043] S101, obtaining health management data sent by the interface of the currently connected medical and health device.

[0044] The front-end device connects to the medical and health equipment and obtains physiological parameter indicators collected by the medical and health equipment to represent the user's health status. Medical and health equipment can be weight scales, blood pressure monitors, oximeters, blood glucose meters, etc. Correspondingly, health management data can be weight, blood pressure, blood oxygen level, blood glucose level, etc. measured by the medical and health equipment. Different medical and health equipment may have different types of hardware interfaces or different types of wireless communication interfaces. The data interface of the front-end device can be connected to different types of interfaces of different medical and health equipment.

[0045] S103: Determine the interface type of the currently connected medical and health device according to the encoding rules of the health management data, and determine a matching target data parsing protocol according to the interface type.

[0046] Different types of interfaces for different medical and health devices will use different data transmission protocols for data transmission. Before sending the health management data collected by the medical and health devices to the front-end device, the different data transmission protocols will convert the data into data bits according to the corresponding encoding rules. After the front-end device receives the health management data sent by the medical and health device, it will use the matching data parsing protocol according to the interface type of the corresponding medical and health device to parse the health management data to restore the data bits to the original data of the health management data collected by the medical and health device. The front-end device provides a programmable data interface and implements the hardware functions of different types of interfaces into corresponding interface program modules stored in the memory of the front-end device. These interface program modules are selected and controlled by the pin function configuration control program inside the chip.

[0047] For example, front-end devices can implement various types of hardware interfaces through CPLD / FPGA chips. The hardware function implementation of each hardware interface has been made into a program module (the development of the program module is completed in the background) and stored in the internal storage of the chip or the external Flash storage chip. These program modules are selected and controlled by the pin function configuration control program inside the chip. The CPLD / FPGA chip itself has a large number of programmable GPIO interface pins. Through the configuration control program, different GPIO pin signals can be connected to different interface program modules inside the chip, so that different GPIO pins have different hardware data bus functions, and the same GPIO pin can also have different hardware data bus functions.

[0048] For example, the GPIO interface 1 can be configured to be connected to the IIC bus program module inside the chip, so that the GPIO interface 1 has the hardware interface function of the IIC bus, and thus the GPIO interface 1 can be connected to the medical and health equipment with the IIC bus interface; the GPIO interface 2 can be configured to be connected to the SPI bus program module inside the chip, so that the GPIO interface 2 has the hardware interface function of the SPI bus, and thus the GPIO interface 2 can be connected to the medical and health equipment with the SPI bus interface. In another embodiment, the GPIO interface 1 can also be configured to be connected to the IIC bus program module inside the chip, so that the GPIO interface 1 has the hardware interface function of the IIC bus, and thus the GPIO interface 1 can be connected to the medical and health equipment with the IIC bus interface; the GPIO interface 1 can be configured to be connected to the SPI bus program module inside the chip, so that the GPIO interface 1 has the hardware interface function of the SPI bus, and thus the GPIO interface 1 can be connected to the medical and health equipment with the SPI bus interface.

[0049] S105: Parse the health management data using the target data parsing protocol.

[0050] The front-end device configures a corresponding interface program module for the data interface of the medical device connected to the health management device, so that the data interface of the front-end device can adapt to the interface type of the corresponding medical device. When the front-end device receives health management data collected by the medical device, it determines a matching target data parsing protocol based on the corresponding interface program module and parses the health management data to obtain the original data of the health management data collected by the medical device. Through data parsing, the original valid data of the health management data is obtained, and invalid data portions, such as the data packet start code, packet length code, and packet end code, are removed.

[0051] S107, sending the parsed health management data to the cloud.

[0052] The front-end device sends the parsed health management data to the cloud for unified management based on big data.

[0053] In the above embodiment, the terminal device can be connected to medical and health devices with various types of interfaces. By obtaining the health management data sent by the interface of the currently connected medical and health device, the interface type of the currently connected medical and health device is determined according to the encoding rules of the health management data, and the matching target data parsing protocol is determined according to the interface type. The health management data is parsed through the target data parsing protocol, and the parsed health management data is sent to the cloud. In this way, the same front-end device can adapt to medical and health devices with various types of interfaces, thereby greatly reducing the firmware, hardware upgrade and management costs of the front-end device, and meeting the data management requirements of diverse medical and health devices.

[0054] Optionally, determining the interface type of the currently connected medical and health device according to the encoding rules of the health management data, and determining the matching target data parsing protocol according to the interface type, includes:

[0055] Performing a traversal decoding test on the health management data through a preset interface program module;

[0056] When one of the interface program modules is met, the interface type of the currently connected medical and health device is determined according to the interface program module that meets the requirements;

[0057] A matching target data parsing protocol is determined according to the interface type.

[0058] The front-end device is provided with corresponding interface program modules according to various types of interfaces. For example, the interface of the medical and health equipment can be an SPI interface, an IIC interface, a UART interface, or a USB interface. The interface program modules stored in the front-end device may include an SPI interface program module, an IIC interface program module, a UART interface program module, and a USB interface program module. The data interface on the front-end device can be configured to connect to one of the interface program modules, so that the data interface can be connected to the medical and health equipment of that interface type, and obtain and analyze the medical and health data collected by the medical and health equipment.

[0059] Before configuring the data interface of the front-end device, the health management device is connected to the front-end device, and the front-end device obtains the health management data sent by the health management device. The pre-saved interface program module is used to decode and test the health management data in turn. When one of the interface program modules is met, the interface type of the currently connected medical and health device is determined according to the compliant interface program module, and the current data interface connected to the health management device is configured according to the interface type. The data interface accesses the decoding test result to confirm the compliant interface program module, so that the data interface can be connected to the medical and health device of the interface type accordingly, and the matching target data parsing protocol is determined to parse the medical and health data.

[0060] Optionally, determining the interface type of the currently connected medical and health device according to the encoding rules of the health management data, and determining the matching target data parsing protocol according to the interface type, further includes:

[0061] When none of the interface program modules meet the requirements, the information is confirmed as an unknown type and reported to the cloud.

[0062] Before the front-end device configures the data interface, the health management device is connected to the front-end device. The front-end device receives the health management data sent by the health management device and decodes the health management data using pre-stored interface program modules. If none of the interface program modules match, the interface type of the currently connected health management device is determined to be unknown and reported to the cloud. This reporting to the cloud allows for timely notification and manual intervention.

[0063] Optionally, determining the interface type of the currently connected medical and health device according to the encoding rules of the health management data, and determining the matching target data parsing protocol according to the interface type, includes:

[0064] Determine the interface type of the currently connected medical and health device according to the coding rules of the health management data, and determine the matching target data parsing protocol according to the interface type;

[0065] The data interface currently connected to the medical health device is configured, and the data interface is associated with the matching target data parsing protocol.

[0066] Before sending collected health management data to the front-end device, health management devices with different interface types use different encoding rules to encode the health management data. Once the front-end device obtains the health management data, it can identify the corresponding encoding rule to determine the interface type of the health management device. After determining the interface type of the health management device, the front-end device configures the data interface connected to the health management device accordingly, allowing it to access the matching interface program module and determine the matching target data parsing protocol to parse the medical health data.

[0067] In some embodiments, before sending the parsed health management data to the cloud, the method further includes:

[0068] The parsed health management data is pre-processed according to a preset data processing algorithm.

[0069] Front-end devices can use different programmable control chips to implement the interface functions of various types of hardware interfaces. When using chips with greater processing power and more internal resources, the chips can be equipped with data pre-processing functions. After pre-processing, the data is transmitted to the cloud for unified management, which can reduce the amount of uploaded data and alleviate the data processing pressure on the cloud.

[0070] Preprocessing health management data can include data filtering, jitter removal, data statistics, threshold setting for early warning, and data classification. For example, a blood oximeter, for example, sends a data packet every second. For example, the data packet is parsed according to the device manufacturer's data protocol to obtain the valid data in the packet: 11 22 33 44 (corresponding to blood oxygen, respiration, heart rate, and perfusion parameter values). Directly uploading this data to the cloud system would result in frequent communication between the front-end device and the cloud system, consuming data bandwidth and increasing the pressure on the cloud system's data storage and processing. Preprocessing data on the front-end device, such as data filtering to remove jitter; data statistics to calculate parameter changes over a certain period of time, set thresholds, and issue early warnings; and data classification to identify a single parameter as a key indicator, can significantly avoid these issues before uploading the preprocessed data to the cloud. Alternatively, the data processing results can be directly displayed on the front-end device with a user interface.

[0071] On the other hand, the present application also provides a front-end device, including a first chip, a second chip and a memory, wherein the memory stores a plurality of preset interface program modules, the first chip obtains the health management data sent by the interface of the currently connected medical and health device; determines the interface type of the currently connected medical and health device according to the encoding rules of the health management data, and determines the matching target data parsing protocol according to the interface type; the first chip or the second chip parses the health management data through the target data parsing protocol; the second chip sends the parsed health management data to the cloud.

[0072] Among them, the front-end device can be built-in with an interface function configuration control program. According to the interface type of the connected medical and health equipment, various types of hardware interfaces are realized through the CPLD / FPGA chip. The hardware function implementation of each hardware interface has been made into a corresponding interface program module, which is stored in the internal storage of the chip or the external Flash storage chip. The interface program module is selected and controlled by the interface function configuration control program inside the chip. The CPLD / FPGA chip itself can have multiple programmable GPIO interface pins. Through the interface function configuration control program, different GPIO interface pin signals are connected to different interface program modules inside the chip, so that different GPIO pins have different hardware data bus functions, and the same GPIO pin can also have different hardware data bus functions. Figure 3 As shown, the four GPIO interface pin signals can be configured to connect to different interface program modules inside the chip one by one; Figure 4 As shown, the configurable GPIO interface 1 pin is connected to the corresponding interface program module inside the chip according to the interface type of the currently connected medical and health device. When the first chip of the front-end device uses an FPGA chip with stronger processing power and more internal resources, an interface function identification program is added inside the chip. When a medical and health device is connected, the interface function identification program first performs a traversal identification test based on the interface function program module stored on the front-end device. If the identification test is passed, it is automatically connected. If it is an unknown type, it is reported to the cloud system for manual intervention. Figure 5 As shown, when GPIO interface n is connected to a medical and health device of a certain interface type, the interface type identification program inside the FPGA chip automatically tests and compares it according to the existing interface program module. If it meets an existing interface type, the pin function configuration control program automatically selects and runs this type for configuration, thereby realizing automatic connection of the medical and health device and configuring the GPIO interface n. If the test and comparison do not match, it is regarded as an unknown hardware interface type, and the identification result is reported to the cloud system through the ARM chip and then processed manually.

[0073] In one embodiment, see Figure 6, the front-end device is a gateway, the first chip is a CPLD chip, and the second chip is an ARM chip. Among them, the CPLD chip (optional Altera MAX II or MAX V series chip) implements various hardware data interface function modules on the chip, which are used to connect to various medical and health equipment in the form of wired interfaces. The various hardware data interface function modules can be stored in the Flash memory as an independent function package. The ARM chip (optional NXPi.MX6UL or i.MX 6ULL ​​series chip) is used to implement data protocol parsing, simple user interface and user interaction management for connecting to various health management devices. At the same time, it connects to various Internet of Things wireless communication modules and medical and health equipment in the form of various wireless interfaces through its built-in common hardware interfaces (such as UART, IIC, SPI). The data protocol interface function modules of various medical and health equipment are stored in the Flash memory as an independent data protocol package.

[0074] When the gateway connects to medical devices with wired data interfaces, they connect via a CPLD chip. The CPLD chip implements on-chip interface modules for various hardware data bus interfaces, including IIC, SPI, UART, and USB. System control selects which hardware interface function to use. This allows the same hardware pins to connect to various medical devices with different hardware data bus interfaces, leveraging the configurable pinout of the CPLD chip. The CPLD chip transmits raw protocol data received through the hardware interface to the ARM chip for protocol parsing. When the gateway connects to medical devices with wireless data interfaces, they connect via various IoT wireless communication modules, which in turn connect to the ARM chip via various common data interfaces (such as IIC, SPI, and UART). The ARM chip performs data protocol parsing for all connected medical devices. The parsed data for each connected medical device is stored as a separate data protocol packet in Flash memory, which can be accessed, added, deleted, or updated by the system. The ARM chip uploads the parsed raw data from medical and health devices to the system cloud for further application processing. The ARM chip is also responsible for the gateway's interface display and user interaction management.

[0075] When a medical health product with a wireless or wired interface is connected, the cloud will take unified control and send the data analysis protocol and hardware data interface type of the connected medical health product to the gateway. The ARM chip and CPLD chip will automatically adapt to run the corresponding program function modules, and no changes are required to the gateway's hardware and firmware.

[0076] In another embodiment, see Figure 7The front-end device is an edge computing device, the first chip is an FPGA chip, and the second chip is an ARM chip. The FPGA chip (optional Altera Cyclone V series or Xilinx Spartan-3 series chips) implements on-chip interface function modules for various hardware data interfaces for connecting to various medical and health devices with wired interfaces, with the interface function modules of various hardware data interfaces serving as independent IP cores; it implements on-chip data protocol parsing for various medical and health devices, with the data protocol function modules of various products serving as independent data protocol packages; it implements on-chip edge computing preprocessing of the raw health management data collected by the parsed medical and health devices according to a preset algorithm; the program modules for the above functions are stored in the Flash memory. The ARM chip (optional NXP i.MX6DL or i.MX 6Q series chips) implements complex user interfaces and user interaction management, user data management, and edge computing server backend configuration and management.

[0077] When the connected medical and health equipment is a device with a wired data interface, the interface function modules (IP cores) of various hardware data bus interfaces implemented on the FPGA chip, such as the interface function modules that can include IIC interface function modules, SPI interface function modules, UART interface function modules, and USB interface function modules, are controlled by the system to select which hardware interface function to run. By utilizing the configurable characteristics of the FPGA chip pin functions, the same hardware pins can be connected to medical and health equipment with various different hardware data bus interfaces. When the connected medical and health equipment has a wireless data interface, it is connected through various IoT wireless communication modules. The communication module is then connected to the FPGA chip through various commonly used data interfaces (such as IIC interface, SPI interface, UART interface, etc.). Similarly, the hardware pins connected to the communication module are also configured as hardware interface functions that are compatible with the various data interfaces of the communication module (such as IIC, SPI, UART, etc.). The FPGA chip also parses the connected health management data and performs edge computing preprocessing on the parsed raw data according to a preset algorithm, and then transmits the preprocessed data to the ARM chip. The various program modules run by the above FPGA are stored in the Flash memory and can be called, added, subtracted, and updated by the system control. The ARM chip is responsible for the complex user interface and user interaction management of the edge computing device, user data management, local application management, background configuration and management, etc.

[0078] When a medical health device with a wireless or wired interface is connected, the cloud will uniformly control it and push the data analysis protocol, hardware data interface type, and edge computing processing algorithm corresponding to the connected medical health device to the edge computing device. The ARM chip and FPGA chip will automatically adapt to run the corresponding program function modules, and no changes are required to the hardware and firmware of the edge computing device.

[0079] In some embodiments, the second chip also includes obtaining an interface type selection instruction and reporting the interface type selection instruction to the cloud; the cloud configures the target data interface according to an interface program module that matches the interface type selection instruction; or, obtaining an interface program module that matches the interface type selection instruction issued by the cloud, and storing the interface program module in the memory.

[0080] For front-end devices with an operation interface, users can also configure the data interface function of the front-end device through the operation interface of the front-end device. The interface type selection instruction can be that the user selects one of the data interfaces to be configured as the target data interface, and then clicks the button corresponding to the interface function module displayed on the operation interface of the front-end device, such as the IIC interface function module, SPI interface function module, UART interface function module, and USB interface function module. After the front-end device obtains the user's click operation, it determines the currently selected interface function module based on the click operation, and reports the interface type selection instruction of the specified interface function module to the cloud. The cloud configures the target data interface according to the interface program module that matches the interface type selection instruction.

[0081] The interface type selection instruction can also be the interface type input by the user through the operation interface of the front-end device. The front-end device will form the interface type selection instruction with the obtained interface type and report it to the cloud. The cloud determines the interface program module that matches it based on the interface type selection instruction, and sends the matching interface program module to the front-end device through the network. The front-end device stores the interface program module in a local designated area, which can be called when subsequently configuring the data interface connected to medical and health devices with different interface types.

[0082] In some embodiments, the second chip further comprises obtaining an interface type configuration instruction for a target data interface, the first chip configures the target data interface according to the interface type configuration instruction, and associates the target data interface with a matching data parsing protocol.

[0083] The front-end device configures the data interface corresponding to the medical and health equipment with different interface types. This can be triggered by receiving an interface type configuration instruction input by the user, or it can be automatically triggered after the data interface is connected to the medical and health equipment. In this embodiment, the front-end device obtains the interface type configuration instruction for the target data interface input by the user on the operation interface, configures the target data interface according to the interface type configuration instruction, and associates the target data interface with a matching data parsing protocol.

[0084] In order to have a more comprehensive understanding of the medical and health data management method provided by this application, please refer to Figure 8 , below, an optional specific example is used to illustrate the workflow of the system for implementing the medical and health data management method. The front-end device is a gateway, and the gateway includes a CPLD chip and an ARM chip. The medical and health equipment is connected to the gateway. The medical and health equipment is connected through a wired hardware interface, and the CPLD chip of the gateway is used for docking. The CPLD chip implements the interface function modules of various hardware data interfaces on the chip, and selects which hardware interface function module to run through unified control in the cloud. In this way, the configurable characteristics of the CPLD chip pin function are utilized to achieve that the same hardware pin can be connected to products with various hardware data bus interfaces. The hardware GPIO interface of the CPLD chip can be configured through software to transmit the signal received from the hardware GPIO interface to different internal interface function program modules, so that the hardware GPIO interface has the corresponding hardware data bus function. This configuration can be repeated many times. Currently, the ARM chip on the front-end device is used to control this configuration, and the ARM chip is connected to the cloud through the network to realize remote configuration of the front-end device.

[0085] The gateway uses a CPLD chip to automatically adapt to the hardware interface type; an ARM chip is used to parse the data protocol and manage user interactions. In this way, the gateway implements the medical data management method provided in the embodiment of the present application to complete wired or wireless access to medical and health equipment, parse the product data protocol, and upload the parsed product original data to the cloud. The gateway does not further process the data.

[0086] See also Figure 9In another optional specific example, the workflow of a system implementing the medical and health data management method is illustrated. The front-end device is an edge computing device, which includes an FPGA chip and an ARM chip. The FPGA chip implements various hardware data interface functional modules on-chip for connecting to various products with wired interfaces. Each hardware data interface functional module is a separate IP core. Data protocol parsing for various medical and health product interfaces is implemented on-chip. Each product's data protocol functional module is a separate data protocol package. Edge computing pre-processing of the parsed product raw data is performed on-chip according to a preset algorithm. The various hardware interface program modules are developed using a hardware description language (such as VHDL or Verilog HDL) and encapsulated into an IP core. This IP core is stored in the FPGA chip's internal or external memory, and the FPGA chip reads, calls, and executes the program. The various hardware interface program modules are essentially hardware functional implementations for processing electrical signals. For example, they process input electrical signals according to specific clock, timing, data bit composition, data start and end specifications, and so on. For example, the hardware signal characteristics of the IIC interface bus: The IIC interface specification defines the corresponding levels of data bits "0" and "1", the high and low levels corresponding to communication start and end signals, their duration, the corresponding timing relationship between the clock and data lines during communication, and the duration of the high and low levels of the data line corresponding to the response signal during communication. Similarly, for SPI interfaces, UART interfaces, USB interfaces, etc., the hardware signals of the interfaces are defined according to their own specification documents.

[0087] Edge computing devices use FPGA chips to automatically adapt to hardware interface types, parse data protocols, and perform data edge computing. ARM chips are responsible for user interaction management and user data management. In this way, they mainly complete wired or wireless access to medical and health products, parse the data protocols of medical and health equipment, and perform edge computing processing on the parsed raw data according to the preset data processing algorithm. The pre-processed data is uploaded to the cloud, reducing the amount of uploaded data and alleviating the pressure on cloud data processing. The front-end equipment products are highly versatile and reduce a lot of software and hardware development work.

[0088] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any modifications or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in the present application should be included in the scope of protection of the present application. Therefore, the scope of protection of the present application should be based on the scope of protection of the claims.

Claims

1. A medical health data management method, applied to a front-end device, characterized in that: include: Obtain health management data sent by the interface of the currently connected medical and health equipment; Performing a traversal decoding test on the health management data through a preset interface program module; The data interface of the front-end device is designed to be programmable to change the hardware interface type, and the implementation function package or IP core of the interface type is stored on the front-end device; the interface program modules preset in the front-end device include an SPI interface program module, an IIC interface program module, a UART interface program module, and a USB interface program module. According to the interface type of different medical and health devices to be connected, the cloud remotely configures the front-end device and selects to run the implementation function package or IP core of the hardware interface type corresponding to the currently connected medical and health device; When one of the interface program modules is met, the interface type of the currently connected medical and health device is determined according to the interface program module that meets the requirements; Determine the matching target data parsing protocol based on the interface type; wherein the target data parsing protocols corresponding to different interface types are selected, added, and deleted through remote configuration in the cloud; the data parsing protocols of medical and health devices with different data are designed in the form of protocol packages, which are stored on the front-end device; Parsing the health management data using the target data parsing protocol; The analyzed health management data is sent to the cloud.

2. The medical health data management method according to claim 1, wherein: The method further comprises: When none of the interface program modules meet the requirements, the information is confirmed as an unknown type and reported to the cloud.

3. The medical health data management method according to claim 1, wherein: The determining the interface type of the currently connected medical and health device according to the coding rule of the health management data, and determining the matching target data parsing protocol according to the interface type, includes: Determine the interface type of the currently connected medical and health device according to the coding rules of the health management data, and determine the matching target data parsing protocol according to the interface type; The data interface currently connected to the medical health device is configured, and the data interface is associated with the matching target data parsing protocol.

4. The medical health data management method according to claim 1, wherein: Before sending the parsed health management data to the cloud, the method further includes: The parsed health management data is pre-processed according to a preset data processing algorithm.

5. A front-end device, characterized in that: The system comprises a first chip, a second chip and a memory, wherein the memory stores a plurality of preset interface program modules, the first chip obtains the health management data sent by the interface of the currently connected medical and health equipment; the health management data is traversed and decoded by the preset interface program module; the data interface of the front-end device is designed in the form of a programmable change of the hardware interface type, and the implementation function package or IP core of the interface type is stored on the front-end device; the preset interface program modules in the front-end device include SPI interface program module, IIC interface program module, UART interface program module and USB interface program module, and according to the interface type of different medical and health equipment to be connected, the front-end device is remotely configured by the cloud, and the operation is selected. A function package or IP core that implements the hardware interface type corresponding to the currently connected medical and health device; when one of the interface program modules is met, the interface type of the currently connected medical and health device is determined according to the interface program module that meets the requirements; the matching target data parsing protocol is determined according to the interface type; wherein, the target data parsing protocols corresponding to different interface types are selected, added and deleted through remote configuration on the cloud; the data parsing protocols of medical and health devices with different data are designed in the form of protocol packages, and the protocol packages are stored on the front-end device; the first chip or the second chip parses the health management data through the target data parsing protocol; the second chip sends the parsed health management data to the cloud.

6. The front-end device according to claim 5, characterized in that: The front-end device is a gateway, the first chip is a CPLD chip, and the second chip is an ARM chip.

7. The front-end device according to claim 5, characterized in that: The front-end device is an edge computing device, the first chip is an FPGA chip, and the second chip is an ARM chip.

8. The front-end device according to claim 6 or 7, characterized in that: The second chip further includes obtaining an interface type selection instruction and reporting the interface type selection instruction to the cloud; The cloud configures the target data interface according to the interface program module that matches the interface type selection instruction; or, obtains the interface program module that matches the interface type selection instruction issued by the cloud, and stores the interface program module in the memory.

9. The front-end device according to claim 6 or 7, characterized in that: The second chip further includes obtaining an interface type configuration instruction for a target data interface, and the first chip configures the target data interface according to the interface type configuration instruction, and associates the target data interface with a matching data parsing protocol.

Images