阅读说明：本技术 健康数据管理方法、设备及系统 (Health data management method, equipment and system ) 是由 刘朝正 邵广玉 杨雪微 李佳澳 许洋溢 代芙瑛 于 2020-05-29 设计创作，主要内容包括：一种健康数据管理方法、设备及系统,涉及电子技术领域,健康数据管理装置可以对来自不同后台装置的健康数据使用相同的数据格式进行统一存储和统一处理,并且同一种健康类型的健康数据可以具有相同的健康指标标识。从而,使得不同后台装置中的健康数据可以互通,提高了使用健康数据的灵活性和高效性；减小了开发成本,提高了开发效率。并且,基于不同后台装置的健康数据的统一处理使得处理结果的准确性和可靠性提高,同时也提高了用户的使用体验。(A health data management method, equipment and a system relate to the technical field of electronics, wherein a health data management device can uniformly store and uniformly process health data from different background devices in the same data format, and the health data of the same health type can have the same health index identification. Therefore, the health data in different background devices can be communicated, and the flexibility and the high efficiency of using the health data are improved; the development cost is reduced, and the development efficiency is improved. Moreover, the health data based on different background devices are uniformly processed, so that the accuracy and the reliability of the processing result are improved, and the use experience of a user is improved.)

1. A health data management method, comprising:

receiving and storing first health data sent by a first background device, wherein the first health data comprises: a first health index identifier and first data content corresponding to the first health index identifier;

receiving and storing second health data sent by a second background device; wherein the second health data comprises: a second health index identifier and second data content corresponding to the second health index identifier;

wherein the first health data and the second health data have the same data format; in the case that the health type of the first data content and the health type of the second data content are the same, the first health indicator identity and the second health indicator identity are the same; in the case that the health type of the first data content and the second data content are different, the first health indicator identity and the second health indicator identity are different.

2. The health data management method according to claim 1,

before receiving and storing the first health data sent by the first background device, the method further comprises:

registering the first background device according to the received first registration request, and returning first information to the first background device; wherein the first information comprises a first background device identifier and a first background device key; and/or;

before receiving and storing the second health data sent by the second background device, the method further comprises:

registering the second background device according to the received second registration request, and returning second information to the second background device; wherein the second information comprises a second background device identification and a second background device key.

3. The health data management method according to claim 2,

if the health index identifier corresponding to the health type of the first health message is not set, and the health type of the first health message is the health type of the health message which can be acquired by the health data acquisition equipment providing services for the first background device, registering the first background device according to the received first registration request, and further comprising:

generating a first health index identifier corresponding to the health type of the first health message according to the received first registration request;

and/or the presence of a gas in the gas,

if the health index identifier corresponding to the health type of the second health message is not set, and the health type of the second health message is the health type of the health message which can be acquired by the health data acquisition equipment providing services for the second background device, registering the second background device according to the received second registration request, and further comprising:

and generating a second health index identifier corresponding to the health type of the second health message according to the received second registration request.

4. The health data management method of any of claims 1-3, wherein after receiving and storing the second health data sent by the second background device, the method further comprises:

under the condition that the first health index identifier is the same as the second health index identifier and the first user identifier is the same as the second user identifier, performing data processing by combining the first data content and the second data content to obtain a data processing result;

transmitting the data processing result to the first background device; and/or the presence of a gas in the gas,

transmitting the data processing result to the second background device; and/or the presence of a gas in the gas,

and transmitting the data processing result to the display equipment.

5. The health data management method of any of claims 1-3, wherein after receiving and storing the second health data sent by the second background device, the method further comprises:

receiving a first data request from the first background device; wherein the first data request is configured to request health data of a first user, the first data request including the first background device identification and the first background device key;

authenticating the first background device in response to the first data request;

and if the first background device passes the authentication, transmitting the first health data to the first background device.

6. The health data management method as set forth in claim 5, further comprising: and under the condition that the first user identification is the same as the second user identification, if the first background device is authenticated, transmitting the second health data to the first background device.

7. A health data management method, comprising:

receiving first health information which is sent by a first terminal and acquired by first health data acquisition equipment, wherein the first health information comprises first user information and first data content;

generating first health data based on the first health information, a first health index identification which is configured and corresponds to the health type of the first data content and fourth information; wherein the fourth information is configured to indicate a data format of the health data, the first health data comprising: the first user information and the first user identification are configured to represent the same user;

and sending the first health data to a health data management device.

8. The health data management method of claim 7, wherein after transmitting the first health data to the health data management device, the method further comprises:

receiving a first data request from the first terminal; wherein the first data request is configured to request health data of a first user, the first data request including a first background device identification and the first background device key;

sending the first data request to the health data management device;

receiving the first health data from the health data management device.

9. The wellness data management method of claim 8 wherein, in the event that the first user identification is the same as a second user identification of second wellness data, after sending a first data request to the wellness data management device, the method further comprises:

receiving the second health data from the health data management device; wherein the second health data is health data stored by the health data management device from a second background device, and the second health data comprises: and the second user identification, the second health index identification and the second data content corresponding to the second health index identification.

10. A health data management method, comprising:

the health data management device receives a first registration request; wherein the first registration request is configured to indicate to register a first background device;

if the health index identifier corresponding to the health type of the first health message is not set, and the health type of the first health message is the health type of the health message which can be acquired by the health data acquisition equipment which provides services for the first background device, the health data management device generates a first health index identifier according to the received first registration request; wherein the first health indicator identifies a health type configured to identify the first health message;

the first background device receives a first health indicator identification and fourth information, wherein the fourth information is configured to indicate a data format of health data;

the first background device generates first health data based on the first health message, the first health indicator identifier and the fourth information; wherein the first health data comprises a first health indicator identity;

the first background device sends the first health data to the health data management device.

11. The health data management method of claim 10, further comprising:

the health data management device receives a second registration request; wherein the second registration request is configured to indicate to register a second background device;

if the health index identifier corresponding to the health type of the second health message is not set, and the health type of the second health message is the health type of the health message which can be acquired by the health data acquisition equipment providing services for the second background device, the health data management device generates a second health index identifier according to the received first registration request; wherein the second health indicator identifies a health type configured to identify the second health message;

the second background device receives a second health indicator identification and fourth information, wherein the fourth information is configured to indicate a data format of health data;

the second background device generates second health data based on the second health message, the second health indicator identifier and the fourth information; wherein the second health data comprises a second health indicator identification;

the second background device sends the second health data to the health data management device.

12. The health data management method as in claim 11, wherein the method further comprises:

the first background device sends a first data request to the health data management device; wherein the first data request is configured to request health data of a first user, the first data request including the first background device identification and the first background device key;

the health data management device responds to the first data request and authenticates the first background device;

if the first background device passes the authentication, the health data management device transmits the first health data to the first background device;

and under the condition that the first health index identifier is the same as the second health index identifier, if the first background device is authenticated, the health data management device also transmits the second health data to the first background device.

13. A health data management apparatus, comprising:

the receiving and sending unit is configured to receive first health data sent by a first background device; wherein the first health data comprises: the system comprises a first user identifier, a first health index identifier and first data content corresponding to the first health index identifier; further configured to receive second health data sent by a second background device; wherein the second health data comprises: a second user identifier, a second health index identifier and second data content corresponding to the second health index identifier; wherein the first health data and the second health data have the same data format; in the case that the health type of the first data content and the health type of the second data content are the same, the first health indicator identity and the second health indicator identity are the same; in the case that the health type of the first data content and the health type of the second data content are different, the first health indicator identification and the second health indicator identification are different;

a storage unit configured to store the first health data and to store the second health data.

14. The health data management apparatus as set forth in claim 13, wherein the health data management apparatus further comprises a processing unit including an external system management module;

the add-on system management module is configured to:

displaying a first interface, wherein the first interface is provided with a first control;

detecting a first preset operation aiming at a first control on a first interface;

responding to the first preset operation, and displaying a second interface;

receiving information of the first background device input to the second interface to generate a first background device identifier and a first background device key;

and/or the presence of a gas in the gas,

displaying a first interface, wherein the first interface is provided with a first control;

detecting a first preset operation aiming at a first control on a first interface;

responding to the first preset operation, and displaying a second interface;

and receiving the information of the second background device input to the second interface to generate a second background device identifier and a second background device key.

15. The health data management apparatus of claim 14, wherein the processing unit further comprises an metrics management module;

the metric management module configured to:

displaying a third interface, wherein the third interface is provided with a second control;

detecting a second preset operation aiming at a second control of the third interface;

responding to the second preset operation, and displaying a fourth interface;

receiving third information which is input to the fourth interface and related to the health type of the first health information to generate a first health index identification corresponding to the health type of the first health information;

and/or the presence of a gas in the gas,

displaying a third interface, wherein the third interface is provided with a second control;

detecting a second preset operation aiming at a second control of the third interface;

responding to the second preset operation, and displaying a fourth interface;

receiving a fourth message which is input to the fourth interface and related to the health type of the second health information, so as to generate a second health index identification corresponding to the health type of the second health information.

16. The health data management apparatus as set forth in claim 14 or 15, wherein the transceiving unit further comprises a unified data transmission interface and an external interface;

the processing unit configured to: under the condition that the first health index identifier is the same as the second health index identifier and the first user identifier is the same as the second user identifier, performing data processing by combining the first data content and the second data content to obtain a data processing result;

the unified data transfer interface configured to:

transmitting the data processing result to the first background device; and/or the presence of a gas in the gas,

transmitting the data processing result to the second background device;

the external interface is configured to:

and transmitting the data processing result to the display equipment.

17. A background apparatus, comprising:

the first health information acquisition equipment is used for acquiring first health information, wherein the first health information comprises first user information and first data content; further configured to transmit the first health data to a health data management apparatus;

a processing unit configured to: generating first health data based on the first health information, a first health index identification which is configured and corresponds to the health type of the first data content and fourth information; wherein the fourth information is configured to indicate a data format of the health data, the first health data comprising: the first user information and the first user identification are configured to represent the same user.

18. A health data management apparatus, comprising: a processor and a memory; the memory is configured to store computer instructions that, when executed by the processor, cause the health data management apparatus to perform the method of any of claims 1-6.

19. A health data management system, comprising: the health data management device comprises a health data management device and at least two background devices; the health data management device is the health data management device according to any one of claims 13-16, and the first background device according to claim 17.

20. A computer readable storage medium having computer program instructions stored therein, which when executed on a processor, cause the processor to perform: the health data management method of any one of claims 1-6; or, the health data management method as claimed in any one of claims 7 to 9; alternatively, the health data management method as claimed in any one of claims 10-12.

Technical Field

The invention relates to the technical field of electronics, in particular to a health data management method, equipment and system.

Background

Along with the development of society, the health consciousness of people is obviously improved. Currently, a variety of health data collection devices are on the market. Such as a bracelet, a sleep meter, a sports watch, etc. Typically, the health data collected by the health data collection device is stored in a background device that serves it.

Different health data acquisition equipment can correspond to different background devices, and the storage, query and processing rules of different background devices may be different.

Disclosure of Invention

In a first aspect, a health data management method is provided, the method comprising: receiving and storing first health data sent by a first background device, wherein the first health data comprises: the first user identification, the first health index identification and first data content corresponding to the first health index identification; receiving and storing second health data sent by a second background device; wherein the second health data comprises: the second user identification, the second health index identification and second data content corresponding to the second health index identification; the data format of the first health data is the same as that of the second health data; under the condition that the health types of the first data content and the second data content are the same, the first health index identification and the second health index identification are the same; in case the health type of the first data content and the second data content are different, the first health indicator identity and the second health indicator identity are different.

In some embodiments, before receiving and storing the first health data sent by the first background device, the method further comprises: registering the first background device according to the received first registration request, and returning first information to the first background device; the first information comprises a first background device identifier and a first background device key; and/or; before receiving and storing the second health data sent by the second background device, the method further comprises: registering the second background device according to the received second registration request, and returning second information to the second background device; wherein the second information comprises a second background device identification and a second background device key.

In some embodiments, registering the first background device according to the received first registration request includes: displaying a first interface, wherein the first interface is provided with a first control; detecting a first preset operation aiming at a first control on a first interface; responding to the first preset operation, and displaying a second interface; receiving information of the first background device input to the second interface to generate a first background device identifier and a first background device key; and/or registering the second background device according to the received second registration request, including: displaying a first interface, wherein the first interface is provided with a first control; detecting a first preset operation aiming at a first control on a first interface; responding to the first preset operation, and displaying a second interface; and receiving information of the second background device input to the second interface to generate a second background device identifier and a second background device key.

In other embodiments, if the health index identifier corresponding to the health type of the first health message is not set, and the health type of the first health message is a health type of a health message that can be collected by health data collection equipment that provides services for the first background device, registering the first background device according to the received first registration request further includes: generating a first health index identifier corresponding to the health type of the first health message according to the received first registration request; and/or if the health index identifier corresponding to the health type of the second health message is not set, and the health type of the second health message is the health type of the health message which can be acquired by the health data acquisition equipment providing services for the second background device, registering the second background device according to the received second registration request, and further comprising: and generating a second health index identifier corresponding to the health type of the second health message according to the received second registration request.

In still other embodiments, generating, according to the received first registration request, a first health indicator identifier corresponding to the health type of the first health message may include: displaying a third interface, wherein the third interface is provided with a second control; detecting a second preset operation aiming at a second control of a third interface; responding to a second preset operation, and displaying a fourth interface; and receiving a third message which is input to the fourth interface and is related to the health type of the first health message to generate a first health index identification corresponding to the health type of the first health message.

In some embodiments, generating, according to the received second registration request, a second health indicator corresponding to the health type of the second health message may include: displaying a third interface, wherein the third interface is provided with a second control; detecting a second preset operation aiming at a second control of a third interface; responding to a second preset operation, and displaying a fourth interface; and receiving a fourth message which is input to the fourth interface and is related to the health type of the second health message to generate a second health index identification corresponding to the health type of the second health message.

In some embodiments, after receiving and storing the second health data sent by the second background device, the method further comprises: and under the condition that the first health index identification is the same as the second health index identification and the first user identification is the same as the second user identification, combining the first data content and the second data content to perform data processing to obtain a data processing result.

In other embodiments, performing data processing in combination with the first data content and the second data content to obtain a data processing result includes: under the condition that the data types of the first data content and the second data content are both numerical values, carrying out weighted average processing on the first data content and the second data content to obtain a data processing result; or deleting semantically identical parts in the first data content or the second data content under the condition that the data types of the first data content and the second data content are both texts.

In further embodiments, after performing data processing in combination with the first data content and the second data content to obtain a data processing result, the method further comprises: transmitting a data processing result to the first background device; and/or transmitting the data processing result to the second background device; and/or transmitting the data processing result to the display equipment.

In some embodiments, after receiving and storing the second health data sent by the second background device, the method further comprises: receiving a first data request from a first background device; wherein the first data request is configured to request health data of a first user, the first data request comprising a first background device identification and a first background device key; authenticating the first background device in response to the first data request; and if the first background device passes the authentication, transmitting the first health data to the first background device.

In other embodiments, the method further comprises: and under the condition that the first user identification is the same as the second user identification, if the first background device passes the authentication, transmitting second health data to the first background device.

In a second aspect, a health data management method is provided, wherein the method comprises: receiving first health information which is sent by a first terminal and acquired by first health data acquisition equipment, wherein the first health information comprises first user information and first data content; generating first health data based on the first health information, the configured first health index identification corresponding to the health type of the first data content and the fourth information; wherein the fourth information is used for indicating a data format of the health data, and the first health data comprises: the system comprises a first user identifier, first data content and a first health index identifier, wherein the first user information and the first user identifier are used for representing the same user; the first health data is sent to a health data management device.

In some embodiments, after sending the first health data to the health data management device, the method further comprises: receiving a first data request from a first terminal; wherein the first data request is configured to request health data of a first user, the first data request comprising a first background device identification and a first background device key; sending a first data request to a health data management device; first health data is received from a health data management device.

In further embodiments, in the event that the first user identification is the same as the second user identification of the second wellness data, after sending the first data request to the wellness data management device, the method further comprises: receiving second health data from the health data management device; wherein the second health data is the health data stored by the health data management device from the second background device, and the second health data includes: and the second user identification, the second health index identification and second data content corresponding to the second health index identification.

In further embodiments, after receiving the first health data from the health data management device, the method further comprises: the first health data is cached.

In a third aspect, a health data management method is provided, wherein the method includes: the health data management device receives a first registration request; wherein the first registration request is configured to indicate to register the first background device; if the health index identifier corresponding to the health type of the first health message is not set, and the health type of the first health message is the health type of the health message which can be acquired by health data acquisition equipment providing services for the first background device, the health data management device generates the first health index identifier according to the received first registration request; wherein the first health indicator identifies a health type configured to identify the first health message; the first background device receives the first health index identification and fourth information, wherein the fourth information is configured to indicate a data format of health data; the first background device generates first health data based on the first health message, the first health index identifier and the fourth information; wherein the first health data comprises a first health index identifier; the first background device sends first health data to the health data management device;

in some embodiments, the method further comprises: the health data management device receives a second registration request; wherein the second registration request is configured to indicate to register with the second background device; if the health index identifier corresponding to the health type of the second health message is not set, and the health type of the second health message is the health type of the health message which can be acquired by the health data acquisition equipment providing services for the second background device, the health data management device generates the second health index identifier according to the received first registration request; wherein the second health indicator identifies a health type configured to identify the second health message; the second background device receives a second health index identification and fourth information, wherein the fourth information is configured to indicate a data format of the health data; the second background device generates second health data based on the second health message, the second health index identifier and the fourth information; wherein the second health data comprises a second health indicator identity; the second background device sends second health data to the health data management device.

In other embodiments, the method further comprises: the first background device sends a first data request to the health data management device; wherein the first data request is configured to request health data of a first user, the first data request comprising a first background device identification and a first background device key; the health data management device responds to the first data request and authenticates the first background device; if the first background device passes the authentication, the health data management device transmits first health data to the first background device; and under the condition that the first health index identifier is the same as the second health index identifier, if the first background device is authenticated, the health data management device also transmits second health data to the first background device.

In a fourth aspect, a health data management apparatus is provided, wherein the health data management apparatus includes a transceiving unit and a storage unit; the receiving and sending unit is used for receiving first health data sent by the first background device; wherein the first health data comprises: the first user identification, the first health index identification and first data content corresponding to the first health index identification; the receiving and sending unit is also used for receiving second health data sent by a second background device; wherein the second health data comprises: the second user identification, the second health index identification and second data content corresponding to the second health index identification; the data format of the first health data is the same as that of the second health data; under the condition that the health types of the first data content and the second data content are the same, the first health index identification and the second health index identification are the same; under the condition that the health types of the first data content and the second data content are different, the first health index identification and the second health index identification are different; the storage unit is used for: the first health data is stored and the second health data is stored.

In some embodiments, the health data management device further comprises a processing unit, the processing unit comprising an external system management module; the external system management module is used for: displaying a first interface, wherein the first interface is provided with a first control; detecting a first preset operation aiming at a first control on a first interface; responding to the first preset operation, and displaying a second interface; receiving information of the first background device input to the second interface to generate a first background device identifier and a first background device key; and/or displaying a first interface, wherein the first interface is provided with a first control; detecting a first preset operation aiming at a first control on a first interface; responding to the first preset operation, and displaying a second interface; and receiving information of the second background device input to the second interface to generate a second background device identifier and a second background device key.

In other embodiments, the processing unit further comprises an index management module; an index management module to: displaying a third interface, wherein the third interface is provided with a second control; detecting a second preset operation aiming at a second control of a third interface; responding to a second preset operation, and displaying a fourth interface; receiving third information which is input to a fourth interface and related to the health type of the first health information to generate a first health index identification corresponding to the health type of the first health information; and/or displaying a third interface, wherein the third interface is provided with a second control; detecting a second preset operation aiming at a second control of a third interface; responding to a second preset operation, and displaying a fourth interface; and receiving a fourth message which is input to a fourth interface and related to the health type of the second health information to generate a second health index identification corresponding to the health type of the second health information.

In other embodiments, a processing unit to: and under the condition that the first health index identification is the same as the second health index identification and the first user identification is the same as the second user identification, combining the first data content and the second data content to perform data processing to obtain a data processing result.

In other embodiments, the transceiver unit further includes a unified data transmission interface and an external interface; a unified data transfer interface for: transmitting a data processing result to the first background device; and/or transmitting the data processing result to the second background device; an external interface for: and transmitting the data processing result to the display equipment.

In other embodiments, the transceiver unit is further configured to: receiving a first data request from a first background device; wherein the first data request is configured to request health data of a first user, the first data request comprising a first background device identification and a first background device key; a processing unit further to: authenticating the first background device in response to the first data request; and if the first background device passes the authentication, transmitting the first health data to the first background device.

In other embodiments, the unified data transfer interface is further configured to: and under the condition that the first user identification is the same as the second user identification, if the first background device passes the authentication, transmitting second health data to the first background device.

In a fifth aspect, a background device is provided, where the background device includes a transceiver unit and a processing unit; a transceiving unit for: receiving first health information which is sent by a first terminal and acquired by first health data acquisition equipment, wherein the health information comprises first user information and first data content; a processing unit to: generating first health data based on the first health information, the configured first health index identification corresponding to the health type of the first data content and the fourth information; wherein the fourth information is used for indicating a data format of the health data, and the first health data comprises: the system comprises a first user identifier, first data content and a first health index identifier, wherein the first user information and the first user identifier are used for representing the same user; a transceiver unit, further configured to: the first health data is sent to a health data management device.

In some embodiments, the transceiver unit is further configured to: receiving a first data request from a first terminal; wherein the first data request is configured to request health data of a first user, the first data request comprising a background device identification and a background device key; sending a first data request to a health data management device; first health data is received from a health data management device.

In further embodiments, in the case that the first user identity is the same as the second user identity of the second health data, the transceiving unit is further configured to: receiving second health data from the health data management device; wherein the second health data is health data stored by the health data management device from another background device except the background device, and the second health data comprises: and the second user identification, the second health index identification and second data content corresponding to the second health index identification.

In a sixth aspect, a health data management system is provided, which includes: the health data management device comprises a health data management device and at least two background devices; wherein the health data management device is the health data management device according to any one of the third aspect, and the background device is the background device according to any one of the fourth aspect.

In a seventh aspect, a health data management apparatus is provided, including: a processor and a memory; the memory is configured to store computer instructions which, when executed by the processor, cause the health data management apparatus to perform the health data management method according to any one of the first aspect.

In an eighth aspect, a computer-readable storage medium is provided. The computer-readable storage medium stores computer program instructions which, when executed on a computer (e.g. a health data management apparatus), cause the computer to perform one or more steps of the health data management method as described in any one of the first aspects above.

In a ninth aspect, a computer-readable storage medium is provided. The computer-readable storage medium stores computer program instructions which, when run on a processor of a computer (e.g. a backend device), cause the computer to perform one or more steps of the health data management method of any of the second aspects described above.

In a tenth aspect, a computer program product is provided. The computer program product comprises computer program instructions which, when executed on a computer (e.g. a health data management apparatus), cause the computer to perform one or more steps of the health data management method as described in any one of the first aspects above.

In an eleventh aspect, a computer program product is provided. The computer program product comprises computer program instructions which, when executed on a computer (e.g. a backend device), cause the computer to perform one or more steps of the health data management method according to any one of the second aspects above.

In a twelfth aspect, a computer program product is provided. The computer program product comprises computer program instructions which, when executed on a computer, cause the computer to perform one or more steps of the health data management method as described in any one of the above third aspects.

In a thirteenth aspect, a computer program is provided. When the computer program is executed on a computer (e.g. a health data management apparatus), the computer program causes the computer to perform one or more steps of the health data management method as described in any one of the above first aspects.

In a fourteenth aspect, a computer program is provided. When the computer program is executed on a computer (e.g. a backend device), the computer program causes the computer to perform one or more steps of the health data management method as described in any of the second aspects above.

In a fifteenth aspect, a computer program is provided. When executed on a computer, the computer program causes the computer to perform one or more steps of the health data management method as defined in any one of the above third aspects.

Drawings

In order to more clearly illustrate the technical solutions in the present disclosure, the drawings needed to be used in some embodiments of the present disclosure will be briefly described below, and it is apparent that the drawings in the following description are only drawings of some embodiments of the present disclosure, and other drawings can be obtained by those skilled in the art according to the drawings. Furthermore, the drawings in the following description may be regarded as schematic diagrams, and do not limit the actual size of products, the actual flow of methods, the actual timing of signals, and the like, involved in the embodiments of the present disclosure.

FIG. 1A is a block diagram of a health data management system according to an embodiment of the present disclosure;

fig. 1B is a structural diagram of a health data management apparatus according to an embodiment of the present disclosure;

FIG. 2A is a schematic diagram of an interface of a health data management device according to an embodiment of the present disclosure;

FIG. 2B is a schematic diagram of another interface of a health data management device according to an embodiment of the disclosure;

FIG. 2C is a schematic view of another interface of a health data management device according to an embodiment of the disclosure;

FIG. 2D is a schematic diagram of another interface of a health data management device according to an embodiment of the disclosure;

FIG. 2E is a schematic diagram of another interface of a health data management device according to an embodiment of the disclosure;

FIG. 2F is a schematic view of another interface of a health data management device according to an embodiment of the disclosure;

FIG. 2G is a schematic diagram of another interface of a health data management device according to an embodiment of the disclosure;

FIG. 2H is a schematic view of another interface of a health data management device according to an embodiment of the disclosure;

FIG. 2I is a schematic diagram of an indicator of health data provided by an embodiment of the present disclosure;

FIG. 3A is a block diagram of a computer system provided by an embodiment of the present disclosure;

fig. 3B is a flowchart of a health data management method according to an embodiment of the disclosure;

FIG. 4 is a flow chart of another method of health data management provided by embodiments of the present disclosure;

fig. 5A is a flowchart of a method for registering a first background device according to an embodiment of the present disclosure;

fig. 5B is a flowchart of a method for registering a second background device according to an embodiment of the disclosure;

fig. 5C is a flowchart of another method for registering a first background device according to an embodiment of the present disclosure;

fig. 5D is a flowchart of another method for registering a second background device according to an embodiment of the present disclosure;

FIG. 6 is a schematic diagram illustrating data processing results provided by an embodiment of the present disclosure;

FIG. 7 is a flow chart of yet another method for health data management provided by an embodiment of the present disclosure;

FIG. 8 is a flow chart of another method of health data management provided by embodiments of the present disclosure;

FIG. 9 is a flow chart of yet another method for health data management provided by an embodiment of the present disclosure;

FIG. 10 is a flow chart of yet another method of health data management provided by an embodiment of the present disclosure;

FIG. 11 is a flow chart of yet another method for health data management provided by an embodiment of the present disclosure;

FIG. 12 is a flow chart of yet another method of health data management provided by an embodiment of the present disclosure;

fig. 13 is a structural diagram of a background device according to an embodiment of the present disclosure.

Detailed Description

Technical solutions in some embodiments of the present disclosure will be clearly and completely described below with reference to the accompanying drawings, and it is obvious that the described embodiments are only a part of the embodiments of the present disclosure, and not all of the embodiments. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments provided by the present disclosure belong to the protection scope of the present disclosure.

Unless the context requires otherwise, throughout the description and the claims, the term "comprise" and its other forms, such as the third person's singular form "comprising" and the present participle form "comprising" are to be interpreted in an open, inclusive sense, i.e. as "including, but not limited to". In the description of the specification, the terms "one embodiment", "some embodiments", "example", "specific example" or "some examples" and the like are intended to indicate that a particular feature, structure, material, or characteristic associated with the embodiment or example is included in at least one embodiment or example of the present disclosure. The schematic representations of the above terms are not necessarily referring to the same embodiment or example. Furthermore, the particular features, structures, materials, or characteristics described may be included in any suitable manner in any one or more embodiments or examples.

In the following, the terms "first", "second" are used for descriptive purposes only and are not to be understood as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of that feature. In the description of the embodiments of the present disclosure, "a plurality" means two or more unless otherwise specified.

"at least one of A, B and C" has the same meaning as "A, B or at least one of C," each including the following combination of A, B and C: a alone, B alone, C alone, a and B in combination, a and C in combination, B and C in combination, and A, B and C in combination.

"A and/or B" includes the following three combinations: a alone, B alone, and a combination of A and B.

As used herein, the term "if" is optionally to be interpreted to mean "when … …" or "at … …" or "in response to a determination" or "in response to a detection", depending on the context. Similarly, the phrase "if determined … …" or "if [ stated condition or event ] is detected" is optionally to be construed to mean "upon determination … …" or "in response to determination … …" or "upon detection of [ stated condition or event ] or" in response to detection of [ stated condition or event ] ", depending on the context.

The use of "adapted to" or "configured to" herein is meant to be an open and inclusive language that does not exclude devices adapted to or configured to perform additional tasks or steps.

Currently, health data acquired by health data acquisition equipment on the market are generally stored in corresponding background devices. Different health data acquisition equipment can correspond to different background devices, and storage, query and processing rules of different background devices are possibly different, so that the health data stored in different background devices cannot be communicated with each other and are difficult to be processed uniformly, the flexibility and the efficiency of using the data are reduced, the development cost is increased, and the development efficiency is reduced. In addition, because different background devices may have different processing rules for the health data, the results obtained by the user through different background devices may also be different, and the user experience is reduced.

The embodiment of the disclosure provides a health data management system, wherein a health data management device can uniformly store and uniformly process health data from different background devices by using the same data format, and the health data of the same health type can have the same health index identifier. Each background device may provide services for at least one health data collection device, for example, each background device may receive health data from a corresponding health data collection device and perform analysis processing on the health data.

By the health data management system provided by the embodiment of the disclosure, the health data can be uniformly stored and uniformly managed, and the health data in different background devices can be communicated, so that the flexibility and the high efficiency of using the health data are improved; compared with the scheme that various background devices respectively manage the health data in the related technology, the development cost is reduced, the development efficiency is improved, and the labor cost is reduced.

In addition, the unified processing is based on the health data of different background devices instead of the health data of a single background device, namely, the unified processing is based on full data instead of single data, and the result of the unified processing can be transmitted to the background devices for result display, so that the accuracy and reliability of the processing result are improved, and the use experience of a user is improved.

In addition, the health data from different background devices are uniformly stored by using the same data format, so that each background device does not need to store a large amount of health data, the requirement on the memory of the background device is reduced, and the efficiency of the background device is improved.

Exemplarily, fig. 1A shows a schematic structural diagram of a health data management system provided by an embodiment of the present disclosure. Referring to fig. 1A, the health data management system 100 may include a health data management apparatus 101, a background apparatus 102, a terminal 103, and a health data collecting device 104.

The health data management apparatus 101 may also include at least one health data management server, and if a plurality of (at least two) health data management servers are included, the health data management apparatus 101 may be referred to as a server cluster; the health data management apparatus 101 may also be a health data management platform (i.e., a software system). The background device 102 may be a background server or may be an external system (which may be a hardware system or a software system). The health data collection device 104 may be referred to simply as a "collection device" or "device".

In addition, there may be one or more of the background device 102, the terminal 103, and the health data collecting apparatus 104. For example, the background devices may include background device 102-1, background device 102-2, and background device 102-3 as shown in FIG. 1A. The terminals may include terminal 103-1, terminal 103-2, terminal 103-3, terminal 103-4 … …, terminal 103-p-1, terminal 103-p as shown in FIG. 1A. The health data collection devices may include the health data collection device 104-1, the health data collection device 104-2, the health data collection device 104-3, the health data collection device 104-4 … …, the health data collection device 104-n-1, the health data collection device 104-n as shown in FIG. 1A.

Each backend apparatus 102 may provide services to at least one health data collection device 104. For example, the health data collected by the health data collecting device 104 may be transmitted to the corresponding background apparatus 102 through the terminal 103. Each background device may correspond to at least one terminal, for example, referring to fig. 1A, the background device 102-1 corresponds to three terminals, which are a terminal 103-1, a terminal 103-2, and a terminal 103-3, respectively. Each terminal can be connected with at least one background device to carry out information interaction related to the health data. For example, referring to FIG. 1A, terminal 103-4 may be connected with background device 102-2 and background device 102-m. Each terminal can be connected with at least one health data acquisition device so as to transmit the health information acquired by the at least one health data acquisition device to the terminal and transmit the health information to the corresponding background device through the terminal. For example, referring to fig. 1A, the terminal 103-4 may be connected to the health data collecting device 104-5 and the health data collecting device 104-6 to transmit the health information collected by the health data collecting device 104-5 to the background apparatus 102-2 and transmit the health information collected by the health data collecting device 104-6 to the background apparatus 102-3.

For example, the health data collected by the health data collecting device 104 is not limited to be transmitted to the corresponding background device 102 through the terminal 103 shown in fig. 1, and the health data collected by the health data collecting device 104 may also be directly transmitted to the corresponding background device 102.

Different background devices can transmit the health data from different health data acquisition equipment to the health data management device for storage by using a uniform data format. Illustratively, the unified data format may be a json format. As another example, the unified data format may be an XML format. As another example, the unified data format may be a CSV format. Of course, the unified data format may also be other types of data formats, and the specific type of the unified data format is not limited in the embodiments of the present disclosure.

In addition, health data of the same health type (e.g., heartbeat, pulse, etc.) may have the same health index identification. That is, the same health index identifier is set for the same type of health data measured by different health data acquisition devices, and the health index identifier may also be referred to as a health index code. For example, the health indicator of diastolic pressure may be: DE04.10.176.00, the health indicator of systolic blood pressure may be: DE04.10.174.00, the health index marker of the glycated hemoglobin can be: DE04.50.083.00, sleep index code is DE04.60.063.00, etc.; if both the sleep apparatus and the sports watch have sleep data, the health index identifications of the sleep data are the same, so that all the sleep data from the sleep apparatus and the sports watch stored in the health data management device 101 have the same health index identification, which is convenient for the health data management device 101 to uniformly manage the sleep data.

Thus, since the health data management apparatus 101 stores health data using a uniform data format, and health data of the same health type may have the same health index flag; therefore, the health data management device 101 can summarize the health data from different background devices for analysis, which can improve the accuracy and reliability of health data processing and improve the user experience. And compared with the scheme that various background devices respectively manage the health data in the related technology, the unified management of the data greatly reduces the development workload, improves the development efficiency and reduces the labor cost.

In addition, referring to fig. 1B, the health data management apparatus 101 may include a storage unit 111, a transceiving unit 112, and a processing unit 113.

The storage unit 111 may be used to support the health data management apparatus 101 to store program codes and data and the like. For example, the storage unit 111 may store health data provided by the embodiments of the present disclosure. The transceiving unit 112 may be used to receive data (e.g., health data, processing results of health data, etc.) from other devices (e.g., background equipment) and transmit data to other devices. The processing unit 113 may be used for controlling and managing the actions of the health data management apparatus 101, and for example, may be used for supporting the health data management apparatus 101 to execute the steps executed by the storage unit 111 and the transceiver unit 112.

The processing unit 113 includes an external system management module 1011 and an index management module 1012. The health data management device 101 may register (may also be referred to as creating) the background device through the external system management module 1011, and the registration information may include a code of the background device, a name of the background device, a background device identifier, a background device key, a background device introduction, and the like. And after the registration is successful, the external system management module 1011 may return the background device identifier and the background device key corresponding to the background device 102.

The health indexes of various types of health data transmitted by the background device to the health data management device 101 need to be recorded in the index management module 1012, so that the same types of health data from different background devices have the same health index identifier, thereby facilitating the unified management of the health data.

The transceiving unit 112 includes a unified data transmission interface 1013 and an external interface 1014.

The unified data transfer interface 1013 shown in fig. 1B is an interface for transferring data between the background apparatus and the health data management apparatus 101. Through the unified data transmission interface 1013, the health data management apparatus 101 can receive health data with a unified data format from different backend apparatuses 102, and can also send corresponding health data with a unified data format to the backend apparatuses 102 in response to a request of the backend apparatuses 102.

The external interface 1014 is an interface for transmitting data between a device other than the background device and the health data management device 101.

In some implementations, the health data management device 101 can transmit the processing result to the background device 102 through the unified data transmission interface 1013, and then the processing result is transmitted to the corresponding terminal 103 by the background device 102 for display. That is, the terminal 103 may be a front end of the background device 102, and may be configured to receive and display a processing result from the background device 102. One background device 102 may correspond to one or more terminals 103. For simplicity of description, in fig. 1, one background device 102 corresponds to one terminal 103.

In other implementations, the health data management apparatus 101 may also transmit the processing result to the display device for displaying through the external interface 1014. The presentation device may be a device other than the terminal 103 shown in fig. 1A. For example, the display device may be a mobile phone, a tablet computer, a desktop computer, and the like, and the specific type of the display device is not limited in the embodiments of the present disclosure.

In other implementations, the health data management device 101 may also directly provide a presentation page to present the processing results.

It is to be understood that the way of displaying the processing result of the health data by the health data management apparatus 101 is not limited to the above example, and other displaying ways are possible, and the displaying way of the processing result of the health data by the health data management apparatus 101 is not limited in the embodiment of the present disclosure.

In addition, the health data management device 101 may send corresponding health data to the background device 102 in response to a request from the background device 102, and the background device 102 may process the health data and display a processing result through the corresponding terminal 103.

Since the health data management apparatus 101 stores health data using a uniform data format, health data of the same health type (for example, heartbeat, pulse, etc.) has the same health index flag. Thus, when a certain background device 102 requests health data of type b of user a from the health data management device 101, in addition to sending health data of type b of user a received from the background device 102 to the background device 102, the health data management device 101 may also send health data of type b of user a from another background device 102 to the background device 102. Therefore, in addition to the health data of the type b of the user a transmitted to the health data management device 101 by the background device 102, the background device 102 may also receive the health data of the type b of the user a from different background devices 102, so that the background device 102 may perform analysis processing in combination with the health data of the type b of the user a from different background devices 102, which is helpful to improve the accuracy and reliability of the processing result.

Illustratively, the health data management apparatus may have an interactive interface shown in fig. 2A. The interactive interface may also be referred to as a main interface. As shown in FIG. 2A, the interface may include an external system control 111, a device management control 112, and a metric management control 113.

As previously mentioned, each backend apparatus may serve at least one health data collection device, the plurality of health data collection devices may collect a plurality of types of health data, and the health data of the same health type may have the same health indicator identification. Therefore, when the background device is created, in addition to the creation of the background device itself, health data acquisition devices that provide services for the background device and health indicators of health data corresponding to the health data acquisition devices may be created. For example, the external system control 111, the device management control 112, and the index management control 113 shown in fig. 2A may respectively create the background device, the health data acquisition devices that the background device provides services, and the health indexes of the health data corresponding to the health data acquisition devices.

A specific process of creating a background device is explained below. Illustratively, the administrator of the health data management device may click on the add-on system control 111 shown in FIG. 2A, and enter the add-on system interface shown in FIG. 2B. Then, clicking a newly-built external system control 114 in the external system interface, entering the newly-built external system interface shown in fig. 2C, and clicking and storing after inputting the system code, the system name, the current version number and the specific information introduced by the system on the newly-built external system interface, thereby creating a new external system. For example, the input system code, system name, current version number and specific information introduced by the system may be "ecg", "ecg patch", "1.0" and "ecg patch", respectively.

In addition, the health data management device may automatically allocate a system identifier and a system key to the newly created add-on system in response to the click saving operation.

Then, the add-on system interface may automatically display the created add-on system, for example. Further illustratively, the add-on interface does not automatically display the created add-on, which can be queried via the search control 115 shown in FIG. 2B. In addition, for each of the created add-on systems, management can also be performed by viewing, editing, and deleting controls. For example, the user clicks a viewing control corresponding to the external system with the system name "electrocardiogram paste" to enter the external system viewing interface shown in fig. 2D. In the external system viewing interface, in addition to the system code, the system name, the current version number and the specific information of the system introduction, the specific information of the system identifier and the system key automatically allocated to the newly created external system is displayed.

The following describes a specific process for creating the health data collecting device for providing services by the background device. Illustratively, the administrator of the health data management appliance may click on the device management control 112 shown in FIG. 2A, and enter the device management interface shown in FIG. 2E. Then, the add new device control 116 in the device management interface is clicked, the add new device interface shown in fig. 2F is entered, and after the add new device interface inputs the specific information of the device type, the device name, the device identifier, and the like, the new device is clicked and stored, so that a new device can be created.

In addition, as shown in fig. 2E, the device management interface may display the created devices, and may also search the created devices through the query control. Meanwhile, for each created device, management operations can be performed by viewing, editing, and deleting controls.

A specific process of creating a health index of health data corresponding to the health data acquisition device is described below. First, it should be noted that if the health indexes corresponding to all the health types of the health data corresponding to the health data acquisition devices providing services for the newly-built background device are already created in the health management server, that is, the health types related to the health data are already created before, it is not necessary to create them repeatedly. And if the health types which are not created before exist in the health types of the health data corresponding to the health data acquisition equipment which is provided with service by the newly-built background device, creating the health indexes aiming at the health types which are not created.

Illustratively, an administrator of the health data management device may click on the metric management control 113 shown in FIG. 2A, and enter the metric management interface shown in FIG. 2G. Then, click the add-on-indicator control 117 in the indicator management interface, enter the add-on-indicator interface shown in fig. 2H, and click to determine after inputting the specific information of the indicator name, the indicator unit, and the indicator code in the add-on-indicator interface, a new indicator can be created.

In addition, as shown in fig. 2G, the index management interface may display the created index, and may also search the created index through the query control. Meanwhile, for each created index, management operation can be performed by checking, editing and deleting the control.

In addition, as shown in fig. 2G, each index may be divided under different directories and sub-directories by category. For example, the blood index directory includes subdirectories of blood sugar, blood pressure, blood gas parameters, blood chemistry, and the like, wherein specific indexes in the blood pressure subdirectory include diastolic pressure, systolic pressure, mean arterial pressure, peripheral pulse, and the like. Indexes can be added to a directory (or a subdirectory), the directory (or the subdirectory) can be modified, and the directory (or the subdirectory) can be deleted through corresponding adding, modifying and deleting controls of the directory (or the subdirectory). For example, the indicator, the blood pressure subdirectory modified and the blood pressure subdirectory deleted can be respectively added to the blood pressure subdirectory through the adding control 121, the modifying control 122 and the deleting control 123 corresponding to the blood pressure subdirectory shown in fig. 2G.

In looking at the created index, for example, referring to fig. 2I, fig. 2I shows an example of an index named diastolic pressure. Referring to fig. 2I, the diastolic pressure is an index under the category "blood index/blood pressure", and therefore the index of the index is superior to the "blood index/blood pressure". The index is named diastolic pressure and is given in mmHg (millimeters of mercury). The index code (i.e., index identification) is 02.02.001.01. The type is an index, and the options of the index are numbers. The value range type and the reference value type of the index are both range values, wherein the value range is 0-300, and the reference value is 60-89.

For example, the health data management device 101 and the background device 102 in fig. 1 may be implemented by the computer system 300 shown in fig. 3A. Computer system 300 includes at least one processor 310, communication lines 320, memory 330, and at least one communication interface 340.

The processor 310 may be a general-purpose Central Processing Unit (CPU), a microprocessor, an Application Specific Integrated Circuit (ASIC), or one or more ics for controlling the execution of programs in accordance with the present disclosure.

Communication link 320 may include a path to communicate information between the aforementioned components.

Communication interface 340 may be implemented using any device, such as a transceiver, for communicating with other devices or communication networks, such as an ethernet, a Radio Access Network (RAN), a Wireless Local Area Network (WLAN), etc.

The memory 330 may be, but is not limited to, a read-only memory (ROM) or other type of static storage device that may store static information and instructions, a RAM or other type of dynamic storage device that may store information and instructions, an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disk storage, optical disk storage (including compact disc, laser disc, optical disc, digital versatile disc, blu-ray disc, etc.), magnetic disk storage media or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer. The memory may be self-contained and coupled to the processor via a bus. The memory may also be integral to the processor.

The memory 330 is used for storing application program codes for executing the disclosed solution, and the execution is controlled by the processor 310. The processor 310 is configured to execute the application program code stored in the memory 330 to control the computer system 300 to implement the health data management method provided by the following embodiments of the present disclosure. Optionally, the computer-executable instructions in the embodiments of the present disclosure may also be referred to as application program codes, which are not specifically limited in the embodiments of the present disclosure.

In particular implementations, processor 310 may include one or more CPUs, such as CPU0 and CPU1 in fig. 3A, each of which may support multiple virtual CPUs, also referred to as VCPUs, as an embodiment.

In particular implementations, computer system 300 may include multiple processors, such as processor 310 and processor 370 in FIG. 3A, for example, as an embodiment. Each of these processors may be a single-core (single-CPU) processor or a multi-core (multi-CPU) processor. A processor herein may refer to one or more devices, circuits, and/or processing cores for processing data (e.g., computer program instructions).

In particular implementations, computer system 300 may also include an output device 350 and an input device 360, as one embodiment. Output device 350 is in communication with processor 310 and may display information in a variety of ways. For example, the output device 350 may be a Liquid Crystal Display (LCD), a Light Emitting Diode (LED) display device, a Cathode Ray Tube (CRT) display device, a projector (projector), or the like. The input device 360 is in communication with the processor 310 and can accept user input in a variety of ways. For example, the input device 360 may be a mouse, a keyboard, a touch screen device, or a sensing device, among others.

The computer system 300 may be a general purpose communication device or a special purpose communication device. The disclosed embodiments do not limit the type of computer system 300. In a specific implementation, the computer system 300 may be a desktop computer, a laptop computer, a web server, a Personal Digital Assistant (PDA), a mobile phone, a tablet computer, a wireless terminal device, an embedded device, or a device with a similar structure as in fig. 2. The various components of computer system 300 may be deployed simultaneously on the same computer device or on different computer devices located in a distributed system.

In addition, the terminal 103 shown in fig. 1A may be a mobile phone, a tablet computer, a wearable device, an in-vehicle device, an Augmented Reality (AR)/Virtual Reality (VR) device, a notebook computer, an ultra-mobile personal computer (UMPC), a netbook, a Personal Digital Assistant (PDA), and the like, and the specific type of the terminal 103 is not limited in the embodiment of the present disclosure.

The health data collecting device 104 shown in fig. 1A may be a sleep device, a sports watch, a bracelet, a sphygmomanometer, a weight scale, a blood glucose meter, etc., and the specific type of the health data collecting device 104 is not limited in any way by the embodiment of the present disclosure.

For convenience of understanding, the following embodiments of the present disclosure will specifically describe a health data management method provided by the embodiments of the present disclosure by taking a health data management system as an example of a system having a structure shown in fig. 1A, and referring to the drawings.

Referring to fig. 3B, the health data management method may include:

301. the first background device sends first health data to the health data management device, wherein the first health data comprises: the first user identification, the first health index identification and the first data content corresponding to the first health index identification.

The first background device may be any one of the background devices shown in fig. 1A.

The user identification is used for representing different users; that is, the user identifiers corresponding to different users are different. Specifically, the first user identifier is information for characterizing the first user. For example: the first user identification may be one or more of an identification number, a mobile phone number, a micro-signal, a registered user name, etc. of the first user.

The health indicator identifies different types of health data content for characterization. Different types of health data content correspond to different health index identifications. Illustratively, the health indicator of diastolic pressure may be: DE04.10.176.00, the health indicator of systolic blood pressure may be: DE04.10.174.00, the health index marker of the glycated hemoglobin can be: DE04.50.083.00, the index of sleep is DE04.60.063.00, etc.

The data content of the health data may be divided into different types. Illustratively, the types of data content can be classified into three types, numeric, text, and option. When the data content is a number, the data content may include a value range type and a value range, the value range type may be divided into a range value, an enumeration value, a single value, and the like, and the value range specifies a range in which the data may be input. In addition, when the data content is digital, the data content may further include a reference value type and a reference value, the reference value type may also be divided into a range value, an enumeration value, a single value, and the like, and the reference value specifies a normal range value of the data. Where the data content is text, for example, the data content may be a diagnostic report or a treatment regimen, or the like. When the data content is an option, for example, the data content may be a preset option, for example, the data content of the health data in which the eye vision condition of the user is recorded may be one of the following options: a: myopia; b: hyperopia; c: and (4) normal.

Additionally, in some implementations, the first background device may send the encrypted first health data to the health data management device. For example, the first background device may encrypt the first health data by an Advanced Encryption Standard (AES) and send the first health data to the health data management device. Of course, the first background device may also perform encryption transmission on the first health data in other encryption manners, and the embodiment of the disclosure does not limit the specific encryption manner.

302. After receiving the first health data from the first background device, the health data management device stores the first health data.

303. The second background device sends second health data to the health data management device.

The second background device may be any one of the background devices shown in fig. 1A.

Wherein the second health data comprises: the second user identification, the second health index identification and second data content corresponding to the second health index identification; the first health data and the second health data have the same data format. For example: the second user identification may be one or more of an identification number, a mobile phone number, a micro signal, a registered user name, etc. of the second user.

Under the condition that the health types of the first data content and the second data content are the same, the first health index identification and the second health index identification are the same; in case the health type of the first data content and the second data content are different, the first health indicator identity and the second health indicator identity are different. Therefore, the health types of the data contents are different, and the corresponding health index identifications are also different. That is, the health type of the data content has a corresponding relationship with the health indicator.

The first health data and the second health data have the same data format, that is, the first health data and the second health data have a uniform data format. For example, the unified data format is defined by the health data management apparatus 101. Illustratively, the unified data format may be a json format. As another example, the unified data format may be an XML format. Still further, the unified data format may be a CSV format. Of course, the unified data format may also be other types of data formats, and the specific type of the unified data format is not limited in the embodiments of the present disclosure.

For example, where the unified data format may be a json format, examples of health data may be as follows:

wherein, the userId is a user identifier; sys is system code; the gatherType is an input mode, wherein 0 represents that the health data are manually input, and 1 represents that the health data are acquired by health data acquisition equipment; deviceType indicates the device type (i.e., indicates what device the device is); deviceId represents a device unique identification code (e.g., may be a MAC address); datasist represents a health data set; time represents the measurement time of the health data; data represents a specific data item; code represents an index flag (may also be referred to as index code); value represents the value of the index; the valueType indicates the type of value, where 0 indicates a specific value and 1 indicates a reference; dataType denotes a data type, where 0 denotes text, 1 denotes a picture, 2 denotes video, 3 denotes audio, and 4 denotes an external link.

The health data may include at least one of the above fields, and the fields included in the health data sent by different background servers may be partially or completely the same.

In addition, in some implementations, the second background device may send the encrypted second health data to the health data management device, and the specific manner of encryption is not limited in the embodiments of the present disclosure.

304. After receiving the second health data from the second background device, the health data management device stores the second health data.

Steps 301 to 304 are merely exemplary to illustrate the health data management method provided by the embodiment of the present disclosure, and do not limit the specific execution order of the method. For example, in a specific implementation, the steps 301 to 304 may be performed in the order. Alternatively, step 303 and step 304 may be performed first, and then step 301 and step 302 may be performed. Alternatively, step 301 and step 303 may be performed first, and then step 302 and step 304 may be performed. Step 301 and step 303 may be performed simultaneously, and step 302 and step 304 may also be performed simultaneously. The specific execution sequence of steps 301 to 304 is not limited by the embodiment of the present disclosure.

In the scheme described in steps 301-304, the health data management device may receive and store the first health data sent by the first background device and the second health data sent by the second background device. The data format of the first health data is the same as that of the second health data; under the condition that the health types of the first data content and the second data content are the same, the first health index identification and the second health index identification are the same; in case the health type of the first data content and the second data content are different, the first health indicator identity and the second health indicator identity are different. That is, the health data management apparatus stores the health data using a unified data format, and the health data of the same health type has the same health index identification. Therefore, the health data management device can collect the health data from different background devices for analysis and processing, the accuracy and the reliability of health data processing can be improved, and the user experience is improved.

In addition, due to the unified management of the data, compared with the scheme that various background devices respectively manage the health data in the related technology, the development workload is greatly reduced, the development efficiency is improved, and the labor cost is reduced.

In some implementations, in steps 302 and 304 described above, the health data management apparatus may employ the TIDB to store the first health data and the second health data. The TIDB is an open-source distributed newSQL database, can realize automatic horizontal expansion and strong-consistency distributed transactions, is compatible with a mysql protocol, is easy to develop, has high query efficiency, and is suitable for storing a large amount of health data in a health data management device.

Optionally, in some embodiments, referring to fig. 4, before step 301, the method further comprises:

401. the health data management device registers the first background device according to the received first registration request and returns first information to the first background device.

Wherein the first information may include a first background device identification and a first background device key.

That is to say, before first health data is sent to the health data management device by the first background device, the health data management device registers the first background device according to the first registration request, and returns first information to the first background device, so that before data transmission is performed between the first background device and the health data management device, the health data management device can authenticate the legitimacy of the first background device according to the first information, and the security of the data transmission is ensured. Meanwhile, the health data management device registering the first background device is also convenient for the health data management device to manage the first background device, for example, the health data management device may disable the first background device.

In some implementations, referring to fig. 5A, registering, by the health data management device, the first background device according to the received first registration request may include:

501. the health data management device displays a first interface, and the first interface is provided with a first control.

Illustratively, the first interface may be an external system interface as shown in FIG. 2B. The first control may be the newly created add-on system control 114 shown in fig. 2B.

502. The health data management device detects a first preset operation aiming at a first control on a first interface.

Illustratively, the first preset operation may be a single-click, double-click, and long-press operation of the first control. Of course, the first preset operation may be another operation for the first control, which is not limited in this disclosure.

503. The health data management device responds to the first preset operation and displays a second interface.

Illustratively, the second interface may be the newly-built external system interface shown in fig. 2C.

504. The health data management device receives the information of the first background device input to the second interface to generate a first background device identifier and a first background device key.

For example, the information of the first background device may be the specific information of the system code, the system name, the current version number, and the system introduction of the input shown in fig. 2C. Of course, the information of the first background device may also include more or less information, and the embodiment of the disclosure does not limit the type of the information of the first background device.

Accordingly, the first registration request may include the first preset operation for the first control on the first interface and the information of the first background device input to the second interface.

That is, the health data management apparatus may display the second interface based on a first preset operation for the first control on the first interface, and receive information of the first background apparatus input to the second interface to generate the first background apparatus identifier and the first background apparatus key.

For example, the information of the first backend device entered into the second interface may come from a mail sent from an administrator of the first backend device to an administrator of the health data management device. The content of the mail can comprise information such as the type of the first background device, the type of at least one first health data acquisition device which is provided with services by the first background device, and health indexes included by each first health data acquisition device. Therefore, the administrator can complete the registration of the first background device according to the information of the first background device, which is input to the second interface by the mail content, wherein the registration can also be referred to as creation. Of course, the information of the first background device input to the second interface may also have other forms, and the form of the information of the first background device input to the second interface is not limited in the embodiments of the present disclosure.

The first registration information obtained by the health data management device registering the first background device may include a first background device identifier and a first background device key. In addition, the first registration information may further include information such as a name of the first backend device, and a code of the first backend device, and the content of the first registration information is not limited in this disclosure.

In other implementation manners, referring to fig. 5B, if the health index identifier corresponding to the health type of the first health message is not set, and the health type of the first health message is a health type of a health message that can be acquired by health data acquisition equipment that provides services for the first background device, registering the first background device according to the received first registration request may further include: and generating a first health index identifier corresponding to the health type of the first health message according to the received first registration request.

In some implementation manners, generating, according to the received first registration request, a first health indicator identifier corresponding to a health type of the first health message may specifically include:

505. the health data management device displays a third interface, and the third interface is provided with a second control.

Illustratively, the third interface may be the metric management interface shown in FIG. 2G, and the second control may be an add metric control 117 in the metric management interface shown in FIG. 2G.

506. The health data management device detects a second preset operation of a second control of the third interface.

Illustratively, the second preset operation may be a single-click, double-click, or long-press operation of the second control. Of course, the second preset operation may be another operation for the second control, which is not limited in this disclosure.

507. And the health data management device responds to the second preset operation and displays a fourth interface.

Illustratively, the fourth interface may be an increase index interface as shown in FIG. 2H.

508. The health data management device receives a third message which is input to the fourth interface and related to the health type of the first health message, and generates a first health index identification corresponding to the health type of the first health message.

Illustratively, the input third message related to the health type of the first health message may be specific information of index name, index unit, index code shown in fig. 2H. Of course, the input third message related to the health type of the first health message may further include more or less information, and the disclosed embodiment does not limit the type of the input third message related to the health type of the first health message.

That is, the health data management apparatus may display a fourth interface based on a second preset operation of a second control of the third interface, receive a third message related to the health type of the first health message input to the fourth interface, and generate a first health index identifier corresponding to the health type of the first health message.

Optionally, in other embodiments, referring to fig. 4, before step 303, the method may further include:

402. and the health data management device registers the second background device according to the second registration request and returns second information to the second background device.

Wherein the second information may include a second background device identification and a second background device key.

That is to say, before the second background device sends the second health data to the health data management device, the health data management device registers the second background device according to the second registration request, and returns the second information to the second background device, so that before data transmission is performed between the second background device and the health data management device, the health data management device can authenticate the legitimacy of the second background device according to the second information, and the security of the data transmission is ensured. Meanwhile, the health data management device registering the second background device is also convenient for the health data management device to manage the second background device, for example, the health data management device may disable the second background device.

In some implementations, referring to fig. 5C, registering, by the health data management device, the second background device according to the received second registration request may include:

511. the health data management device displays a first interface, and the first interface is provided with a first control.

Illustratively, the first interface may be an external system interface as shown in FIG. 2B. The first control may be the newly created add-on system control 114 shown in fig. 2B. Step 511 may be the same as step 501.

512. The health data management device detects a first preset operation aiming at a first control on a first interface.

Illustratively, the first preset operation may be a single-click, double-click, and long-press operation of the first control. Of course, the first preset operation may be another operation for the first control, which is not limited in this disclosure. Step 512 may be the same as step 502.

513. The health data management device responds to the first preset operation and displays a second interface.

Illustratively, the second interface may be the newly-built external system interface shown in fig. 2C. Step 513 may be the same as step 503.

514. The health data management device receives information of the second background device input to the second interface to generate a second background device identifier and a second background device key.

For example, the information of the second background device may be the specific information of the system code, the system name, the current version number, and the system introduction of the input shown in fig. 2C. Of course, the information of the second background device may also include more or less information, and the embodiment of the disclosure does not limit the type of the information of the second background device.

Accordingly, the second registration request may include the first preset operation for the first control on the first interface and information of the second background device input to the second interface.

That is, the health data management apparatus may display the second interface based on the first preset operation for the first control on the first interface, receive information of the second background apparatus input to the second interface, and generate the second background apparatus identifier and the second background apparatus key.

For example, the information of the second backend device entered to the second interface may come from a mail sent from an administrator of the second backend device to an administrator of the health data management device. The content of the mail may include information such as the type of the second background apparatus, the type of at least one second health data collecting device that the second background apparatus provides services, and a health index included in each second health data collecting device. Therefore, the administrator can input the information of the second background device to the second interface according to the mail content, so that the health data management device can complete the registration of the second background device. Of course, the information of the second background device input to the second interface may also have other forms, and the form of the information of the second background device input to the second interface is not limited in the embodiments of the present disclosure.

The second registration information obtained by the health data management device registering the second background device may include a second background device identifier and a second background device key. In addition, the second registration information may further include information such as a name of the second backend device, and a code of the second backend device, and the content of the second registration information is not limited in this disclosure.

In other implementation manners, referring to fig. 5D, if the health index identifier corresponding to the health type of the second health message is not set, and the health type of the second health message is a health type of a health message that can be acquired by health data acquisition equipment that provides services for the second background device, registering the second background device according to the received second registration request may further include:

and generating a second health index identifier corresponding to the health type of the second health message according to the received second registration request.

In some implementation manners, generating, according to the received second registration request, a second health indicator identifier corresponding to the health type of the second health message may specifically include:

515. the health data management device displays a third interface, and the third interface is provided with a second control.

516. The health data management device detects a second preset operation of a second control of the third interface.

517. And the health data management device responds to the second preset operation and displays a fourth interface.

Step 515 to step 517 may be the same as step 505 to step 507, and are not described herein again.

518. The health data management device receives a fourth message which is input to the fourth interface and related to the health type of the second health message, and generates a second health index identification corresponding to the health type of the second health message.

Illustratively, the fourth message input in relation to the health type of the second health message may be specific information of index name, index unit, index code shown in fig. 2H. Of course, the input fourth message related to the health type of the second health message may further include more or less information, and the type of the input fourth message related to the health type of the second health message is not limited by the embodiments of the present disclosure.

That is, the health data management apparatus may display a fourth interface based on a second preset operation of a second control of the third interface, receive a fourth message related to the health type of the second health message input to the fourth interface, and generate a second health index identifier corresponding to the health type of the second health message.

Further optionally, in some implementations, referring to fig. 4, after step 401 and before step 301, the method may further comprise:

403. the first health data acquisition equipment sends acquired first health information to the first terminal.

Wherein the first health information may include first user information and first data content. The first user information is information indicating a first user. Different users may correspond to different user information.

The first terminal is connected with the first background device. Each background device is provided with at least one corresponding terminal, and the terminal can be used for receiving the health data from the background devices and the processing results thereof and displaying the health data.

404. After receiving the first health information, the first terminal sends the first health information to the first background device.

405. After receiving the first health information, the first background device generates first health data based on the first health information, the configured first health index identification corresponding to the health type of the first data content and the fourth information.

Wherein the fourth information is used to indicate a data format of the health data. The fourth information may be information indicating a data format of the health data configured based on the information from the health data management apparatus. The information for indicating the data format of the health data sent by the health data management device to different background devices may be the same, that is, the health data management device may specify a uniform data format.

The first health data may include: the first user identification, the first data content and the first health index identification. Wherein the first user identifier is obtained based on the first user information in the first health information. The first user information and the first user identification are used to represent the same user. The first health indicator identification is a received health indicator identification corresponding to a health type of the first data content.

That is to say, the first health data collecting device may send the collected first health information to the first terminal, and then the first terminal transmits the first health information to the first background device. After receiving the first health information, the first background device can generate first health data with a uniform data format based on the first health information, the configured first health index identifier corresponding to the health type of the first data content and the fourth information, so that the first health data is uploaded to the health data management device and is uniformly stored and processed by the health data management device.

Further optionally, in some implementations, referring to fig. 4, after step 402 and before step 303, the method may further comprise:

406. and the second health data acquisition equipment sends the acquired second health information to the second terminal.

Wherein the second health information may include the second user information and the second data content. The second user information is information indicating a second user. Different users may correspond to different user information. And the second terminal is connected with the second background device.

407. After receiving the second health information, the second terminal sends the second health information to the second background device.

408. After receiving the second health information, the second background device generates second health data based on the second user information, the second data content, and the corresponding relationship between the health type of the data content and the health index identifier.

The second background device analyzes and packages the second health information based on the second user information and the second data content in the second health information and the corresponding relationship between the health type of the data content and the health index identification, and generates second health data with a uniform data format.

That is to say, the second health data collecting device may send the collected second health information to the second terminal, and then the second health information is transmitted to the second background device by the second terminal. After receiving the second health information, the second background device can generate second health data with a uniform data format based on the second health information and the corresponding relation between the health type of the data content and the health index identifier, so that the second health data is uploaded to the health data management device and is uniformly stored and processed by the health data management device.

Optionally, in other embodiments, referring to fig. 4, after step 304, the health data management method provided in the embodiments of the present disclosure further includes:

409. and under the condition that the first health index mark and the second health index mark are the same, the health data management device performs data processing by combining the first data content and the second data content to obtain a data processing result.

As can be seen from the above, the first health indicator flag and the second health indicator flag are the same, i.e. the first data content of the first health data and the second data content of the second health data are of the same type. That is, in the case where the health type of the data content of the health data is the same, the health data management apparatus can perform data processing in conjunction with the first data content and the second data content, thereby contributing to improvement in accuracy and reliability of the processing result.

Optionally, in some implementations, step 409 may include:

illustratively, in the case that the data types of the first data content and the second data content are both numerical values, the weighted average processing is performed on the first data content and the second data content to obtain a data processing result.

Illustratively, in the case where the data types of the first data content and the second data content are both text, the semantically identical part of the first data content or the second data content is deleted.

Deleting the part with the same semantic meaning in the first data content or the second data content, wherein the semantic meaning can be as follows: only one is reserved for semantically identical parts of the first data content and the second data content.

The data type of the data content may be text, picture, video, audio, external link, etc., and the data type of the data content is not limited in this disclosure. Of course, in the case that the data types of the first data content and the second data content are both numerical values or texts, the specific implementation manner of the step 409 is not limited to the above example, and the embodiment of the present disclosure does not limit the specific implementation manner of the step 409.

Optionally, in another embodiment, after step 409, the method may further include:

410. and the health data management device transmits the data processing result to the first background device.

411. And after receiving the data processing result, the first background device transmits the data processing result to the first terminal.

Optionally, in another embodiment, the method may further include:

412. and the health data management device transmits the data processing result to the second background device.

413. And after receiving the data processing result, the second background device transmits the data processing result to the second terminal.

That is to say, after the health data management device performs data processing in combination with the first data content and the second data content to obtain a data processing result, the health data management device may transmit the data processing result to the first background device or the second background device, so that the first background device or the second background device may display the data processing result to the user through the first terminal and the second terminal connected to each other.

In another embodiment, the method may further comprise:

414. and the health data management device transmits the data processing result to the display equipment.

For example, the health data management apparatus may transmit the data processing result to the display device other than the first background apparatus and the second background apparatus through the external interface.

That is, after the health data management apparatus performs data processing in combination with the first data content and the second data content to obtain the data processing result, the health data management apparatus may transmit the data processing result to a display device other than the first background apparatus and the second background apparatus, so that the data processing result may be displayed to the user through the display device.

In another embodiment, the method may further comprise: and the health data management device displays the data processing result.

That is, the health data management apparatus itself may also directly provide a presentation page so that the user can view the data processing result through the presentation page.

In some implementations, the health data management device can provide a presentation page for partially authorized users so that these users can view the data processing results. For example, the partially authorized user may be a human worker at the first backend device and/or the second backend device. For example, when the background device is a patient information management server of a certain hospital, some authorized users may be doctors working in the hospital. For example, referring to fig. 6, a schematic diagram of a presentation page provided by the health data management device is shown.

Optionally, in some embodiments, referring to fig. 7, after step 304, the method may further include:

701. the first terminal responds to the preset operation of the first terminal user and sends a first data request to the first background device.

The preset operation of the first terminal user can be used for indicating to view the health data of the first user. Illustratively, the preset operation of the first end user may be an operation of the first end user clicking a preset control on a terminal screen. For example, the first terminal user clicks an operation of a health data query button on the terminal screen. Further exemplarily, the preset operation of the first terminal user may be a preset gesture operation of the first terminal user on the terminal screen. For example, a first terminal user draws a circle of gesture operations on the terminal screen. Of course, the preset operation of the first end user may also have other various forms, which is not limited in this disclosure.

The first data request is used for requesting health data of a first user, and the first data request comprises a first background device identification and a first background device key.

For example, when the background device is a mobile health server, the first end user may be a user of a bracelet that provides services to the mobile health server, and the first data request may be for requesting health data of the user of the bracelet.

In some embodiments, the first data request may also be for requesting health data of a user other than the first user. That is, the first data request may be for requesting health data of a plurality of users including the first user.

For example, when the backend device is a patient information management server of a certain hospital, the first end user may be a doctor working in the hospital, and the first data request may be for requesting health data of a plurality of patients managed by the doctor.

702. After receiving the first data request from the first terminal, the first background device sends the first data request to the health data management device.

703. The health data management device authenticates the first background device in response to the first data request.

In particular, the health data management device may authenticate the first background device in response to a first background device identification and a first background device key included in the first data request.

704. And if the health data management device passes the authentication of the first background device, transmitting the first health data to the first background device.

That is to say, when the first background device requests the health data of the first user from the health data management device, the health data management device may authenticate the validity of the first background device according to the first background device identifier and the first background device key included in the first data request, and transmit the first health data after the authentication is passed, thereby ensuring the security of data transmission.

Optionally, after step 704, the method may further comprise:

705. after receiving the first health data, the first background device caches the first health data.

Illustratively, the first health data may be buffered in a queue, e.g., the queue may be a first-in-first-out queue.

Therefore, under the condition that the first background device receives the first data request from the first terminal again, if the first health data is still cached in the first background device, the first background device can directly send the first health data to the first terminal without requesting from the health management server again, and transmission resources and time are saved.

In another embodiment, after step 705, the method further comprises:

706. and under the condition that the first user identification is the same as the second user identification, if the health data management device passes the authentication of the first background device, transmitting second health data to the first background device.

That is, if the first user and the second user are the same user, when the health data management device passes the authentication of the first background device, the health data management device may transmit, to the first background device, second health data from the second background device in addition to the first health data from the first background device. Namely, the background device can acquire the health data uploaded by the background device from the health data management device, and can also acquire the health data uploaded by other background devices, so that the health data in different background devices can be communicated, the flexibility and the efficiency of using the health data are improved, the development cost is reduced, and the development efficiency is improved.

In summary, the present disclosure provides a health data management method applied to a health data management apparatus, and in an embodiment, as shown in fig. 8, the method may include the following steps 801 to 802:

801. receiving and storing first health data sent by a first background device, wherein the first health data comprises: the first user identification, the first health index identification and the first data content corresponding to the first health index identification.

802. Receiving and storing second health data sent by a second background device; wherein the second health data comprises: and the second user identification, the second health index identification and second data content corresponding to the second health index identification.

The data format of the first health data is the same as that of the second health data; under the condition that the health types of the first data content and the second data content are the same, the first health index identification and the second health index identification are the same; in case the health type of the first data content and the second data content are different, the first health indicator identity and the second health indicator identity are different.

In the health data management method, for example, the operation of the health data management device may refer to the operation of the health data management device in the embodiment shown in fig. 3 and the related text descriptions, which are not repeated herein.

In addition, another health data management method is further provided in the embodiments of the present disclosure, and is applied to a first background device, as shown in fig. 9, the method includes the following steps 901 to 903:

901. the method comprises the steps of receiving first health information which is sent by a first terminal and collected by first health data collection equipment, wherein the first health information comprises first user information and first data content.

902. And generating first health data based on the first health information, the configured first health index identification corresponding to the health type of the first data content and the fourth information.

Wherein the fourth information is used for indicating the data format of the health data, and the health data may include various types of health data, including the first health data. The first health data includes: the first user identification, the first data content and the first health index identification. The first user information and the first user identification are used for representing the same user

903. And sending the first health data to a health data management device.

In the health data management method, for example, the operation of the first background device may refer to the operation of the first background device in the embodiment shown in fig. 4 and the related text descriptions, which are not repeated herein.

In addition, another health data management method is further provided in an embodiment of the present disclosure, and referring to fig. 10, the method includes:

1001. the health data management device receives a first registration request.

Wherein the first registration request is configured to indicate to register with the first background device.

1002. If the health index identifier corresponding to the health type of the first health message is not set, and the health type of the first health message is the health type of the health message which can be acquired by the health data acquisition equipment which provides services for the first background device, the health data management device generates the first health index identifier according to the received first registration request.

Wherein the first health indicator identifies a health type configured to identify the first health message.

1003. The first background device receives the first health indicator identification and fourth information configured to indicate a data format of the health data.

1004. The first background device generates first health data based on the first health message, the first health indicator identifier and the fourth information.

Wherein the first health data comprises a first health indicator identity. The first health indicator identifies a health type for identifying the first health data (or, the first health message).

1005. The first background device sends the first health data to the health data management device.

In the health data management method, for example, the operations of the health data management device and the first background device may refer to the operations of the health data management device and the first background device in the embodiments shown in fig. 4 and 7 and the related text descriptions, which are not described herein again.

In some embodiments, referring to fig. 11, the method illustrated in fig. 10 may further include:

1101. the health data management device receives a second registration request.

Wherein the second registration request is configured to indicate to register with the second background device.

1102. If the health index identifier corresponding to the health type of the second health message is not set, and the health type of the second health message is the health type of the health message which can be acquired by the health data acquisition equipment providing services for the second background device, the health data management device generates the second health index identifier according to the received first registration request.

Wherein the second health indicator identifies a health type configured to identify the second health message.

1103. The second background device receives the second health indicator identification and fourth information configured to indicate a data format of the health data.

1104. The second background device generates second health data based on the second health message, the second health indicator identifier and the fourth information.

Wherein the second health data comprises a second health indicator identity.

1105. The second background device sends second health data to the health data management device.

In the health data management method, for example, the operations of the health data management device and the second background device may refer to the operations of the health data management device and the second background device in the embodiments shown in fig. 4 and 7 and the related text descriptions, which are not described herein again.

In other embodiments, referring to fig. 12, the method of fig. 11 may further include:

1201. the first background device sends a first data request to the health data management device.

Wherein the first data request is configured to request health data of the first user, the first data request comprising a first background device identification and a first background device key.

1202. The health data management device authenticates the first background device in response to the first data request.

1203. And if the first background device passes the authentication, the health data management device transmits the first health data to the first background device.

In addition, in the case that the first health indicator flag is the same as the second health indicator flag, after step 1203, the method may further include:

1204. and under the condition that the first health index identifier is the same as the second health index identifier, if the first background device is authenticated, the health data management device also transmits second health data to the first background device.

That is to say, under the condition that the first health index identifier is the same as the second health index identifier, the first background device can acquire the first health data uploaded by the first background device from the health data management device, and also can acquire the second health data uploaded by the second background device, so that the health data in different background devices can be communicated, the flexibility and the efficiency of using the data are improved, the development cost is reduced, and the development efficiency is improved.

The health data management device, the background device, the terminal and the health data acquisition equipment can be called as electronic equipment. It will be appreciated that in order to implement the above-described functions, the electronic device comprises corresponding hardware and/or software modules for performing the respective functions. The exemplary algorithmic steps described in connection with the embodiments disclosed herein may be embodied in hardware or in a combination of hardware and computer software. Whether a function is performed as hardware or computer software drives hardware depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, with the embodiment described, but such implementation decisions should not be interpreted as causing a departure from the scope of the present disclosure.

In this embodiment, the electronic device may be divided into functional modules according to the above method example, for example, each functional module may be divided corresponding to each function, or two or more functions may be integrated into one processing module. The integrated module may be implemented in the form of hardware. It should be noted that the division of the modules in this embodiment is schematic, and is only a logic function division, and there may be another division manner in actual implementation.

In the case of dividing each functional module by corresponding each function, the health data management apparatus provided by the embodiment of the present disclosure may be as shown in fig. 1B. Referring to fig. 1B, the health data management apparatus 101 may include a storage unit 111 and a transceiving unit 112.

The transceiver unit 112 is configured to receive first health data sent by a first background device; wherein the first health data comprises: the first user identification, the first health index identification and the first data content corresponding to the first health index identification.

The transceiver unit 112 is further configured to receive second health data sent by a second background device; wherein the second health data comprises: and the second user identification, the second health index identification and second data content corresponding to the second health index identification. The data format of the first health data is the same as that of the second health data; in case the health type of the first data content and the second data content is the same, the first health indicator identity and the second health indicator identity are the same. In case the health type of the first data content and the second data content are different, the first health indicator identity and the second health indicator identity are different.

The storage unit 111 is used for storing the first health data and storing the second health data.

In some embodiments, the health data management device further comprises a processing unit 113, and the processing unit 113 may comprise an external system management module 1011.

The external system management module 1011 may be used to: displaying a first interface, wherein the first interface is provided with a first control; detecting a first preset operation aiming at a first control on a first interface; responding to the first preset operation, and displaying a second interface; and receiving information of the first background device input to the second interface to generate a first background device identifier and a first background device key.

The external system management module 1011 may also be used to: displaying a first interface, wherein the first interface is provided with a first control; detecting a first preset operation aiming at a first control on a first interface; responding to the first preset operation, and displaying a second interface; and receiving information of the second background device input to the second interface to generate a second background device identifier and a second background device key.

In other embodiments, the processing unit 113 includes an index management module 1012. The metric management module 1012 may be configured to: displaying a third interface, wherein the third interface is provided with a second control; detecting a second preset operation aiming at a second control of a third interface; responding to a second preset operation, and displaying a fourth interface; and receiving third information which is input to the fourth interface and is related to the health type of the first health information to generate a first health index identification corresponding to the health type of the first health information.

The metric management module 1012 may be further configured to: displaying a third interface, wherein the third interface is provided with a second control; detecting a second preset operation aiming at a second control of a third interface; responding to a second preset operation, and displaying a fourth interface; and receiving a fourth message which is input to a fourth interface and related to the health type of the second health information to generate a second health index identification corresponding to the health type of the second health information.

In other embodiments, the processing unit 113 may be configured to: and under the condition that the first health index identification is the same as the second health index identification and the first user identification is the same as the second user identification, combining the first data content and the second data content to perform data processing to obtain a data processing result.

In other embodiments, the transceiver unit 112 further includes a unified data transfer interface 1013 and an external interface 1014.

The unified data transfer interface 1013 may be configured to: and transmitting the data processing result to the first background device. The unified data transfer interface 1013 may also be used to: and transmitting the data processing result to the second background device.

The external interface 1014 may be used to: and transmitting the data processing result to the display equipment.

In other embodiments, the transceiver unit 112 may be further configured to: a first data request is received from a first background device. Wherein the first data request is configured to request health data of the first user, the first data request comprising a first background device identification and a first background device key.

The processing unit 113 may also be configured to: authenticating the first background device in response to the first data request; and if the first background device passes the authentication, transmitting the first health data to the first background device.

In other embodiments, unified data transfer interface 1013 may also be configured to: and under the condition that the first user identification is the same as the second user identification, if the first background device passes the authentication, transmitting second health data to the first background device.

In addition, the health data management device provided by the embodiment of the present disclosure may be as shown in fig. 13. Referring to fig. 13, the background device 102 may include a transceiving unit 1100 and a processing unit 1200.

The transceiving unit 1100 may be configured to: the method comprises the steps of receiving first health information which is sent by a first terminal and collected by first health data collection equipment, wherein the health information comprises first user information and first data content.

The processing unit 1200 may be configured to: generating first health data based on the first health information, the configured first health index identification corresponding to the health type of the first data content and the fourth information; wherein the fourth information is used for indicating a data format of the health data, and the first health data comprises: the first user information and the first user identification are used for representing the same user.

The transceiving unit 1100 may further be adapted to transmit the first health data to the health data management device.

In some embodiments, the transceiver unit 1100 may also be configured to: receiving a first data request from a first terminal; wherein the first data request is configured to request health data of a first user, the first data request comprising a background device identification and a background device key; sending a first data request to a health data management device; first health data is received from a health data management device.

In further embodiments, in case the first user identity is the same as the second user identity of the second health data, the transceiving unit 1100 may be further configured to: receiving second health data from the health data management device; wherein the second health data is health data stored by the health data management device from another background device except the background device, and the second health data comprises: and the second user identification, the second health index identification and second data content corresponding to the second health index identification.

In other embodiments, referring to fig. 13, the backend apparatus 102 may further include a storage unit 1300. The memory unit 1300 may be used to cache the first health data.

Some embodiments of the present disclosure also provide a computer-readable storage medium (e.g., a non-transitory computer-readable storage medium) having stored therein computer program instructions that, when executed on a computer, cause the computer (e.g., a health data management device or a backend device) to perform one or more steps of a health data management method as described in any one of the embodiments above.

By way of example, such computer-readable storage media may include, but are not limited to: magnetic storage devices (e.g., hard Disk, floppy Disk, magnetic tape, etc.), optical disks (e.g., CD (Compact Disk), DVD (Digital Versatile Disk), etc.), smart cards, and flash Memory devices (e.g., EPROM (Erasable Programmable Read-Only Memory), card, stick, key drive, etc.). Various computer-readable storage media described in this disclosure can represent one or more devices and/or other machine-readable storage media for storing information. The term "machine-readable storage medium" can include, without being limited to, wireless channels and various other media capable of storing, containing, and/or carrying instruction(s) and/or data.

Some embodiments of the present disclosure also provide a computer program product. The computer program product comprises computer program instructions which, when executed on a computer (e.g. a health data management device or a backend device), cause the computer to perform one or more steps of the health data management method as described in the above embodiments.

Some embodiments of the present disclosure also provide a computer program. When the computer program is executed on a computer (e.g., a health data management apparatus or a background apparatus), the computer program causes the computer to perform one or more steps of the health data management method as described in the above embodiments.

The beneficial effects of the computer-readable storage medium, the computer program product and the computer program are the same as those of the health data management method according to some embodiments, and are not described herein again.

The above description is only for the specific embodiments of the present disclosure, but the scope of the present disclosure is not limited thereto, and any person skilled in the art will appreciate that changes or substitutions within the technical scope of the present disclosure are included in the scope of the present disclosure. Therefore, the protection scope of the present disclosure shall be subject to the protection scope of the claims.