KR102220183B1 - Apparatus and method for managing health data - Google Patents

Abstract

In a method for a terminal to manage health data, terminal information for identifying the terminal and medical device information for measuring health data are input into a management server linked with the terminal, and the health data measured by the medical device is received from the management server. Information including a security type indicating storage in the first memory or a second memory accessible by at least one designated user may be received, and health data may be stored in the first memory or the second memory based on the security type.

Description

Device and method for health data management {APPARATUS AND METHOD FOR MANAGING HEALTH DATA}

The present invention relates to health data, and more particularly to an apparatus and method for health data management.

As interest in health care continues to increase every year, the need for health data management is also gradually increasing. In addition, in recent years, as the number of smartphone users has increased rapidly, demand for a service that allows smartphone users to manage their health data through smartphones is increasing.

Accordingly, by applying Near Field Communication (NFC) technology, health data measured through medical devices such as weight scales, blood pressure monitors, blood glucose meters, electrocardiograms, blood analyzers, etc. are converted into information technology (IT) devices such as smartphones. The service that the user manages his/her own health data by delivering to is currently being used. In addition, the demand for the service is expected to continue to increase with the increase in smartphone penetration.

On the other hand, depending on the type of health data, there are data that do not matter to whom it is disclosed, while there are data that must be disclosed only to specific groups such as medical staff. However, as health data is currently open to anyone to share, personal health data is shared with others other than medical staff, leading to problems such as Internet exposure of personal information and inappropriate use of personal health data by hiring companies. I can. In addition, if the smartphone in which the health data is stored is lost, a problem may occur in personal health data management.

Therefore, there is a need for a way to solve the above problems in managing health data.

The present invention provides an apparatus and method for classifying and managing health data according to security types.

A method according to an embodiment is a method for a terminal to manage health data, the process of inputting terminal information for identifying the terminal and medical device information for measuring health data into a management server linked to the terminal, and the A process of receiving, from the management server, information including a security type instructing to store the health data measured by the medical device in a first memory or a second memory accessible by at least one designated user, and the security type Based on this, a process of storing the health data in the first memory or the second memory may be included.

A method according to another embodiment is a method of managing health data by a management server interlocked with a terminal, the process of receiving terminal information for identifying the terminal and medical device information for measuring health data from the terminal, and the A process of checking whether a security type instructing to store health data measured by a medical device in a first memory or a second memory accessible by at least one designated user is registered in the management server, and the security type is the management When registered in the server, the process of generating information including the security type and transmitting the information to the terminal may be included.

An apparatus according to an embodiment is a terminal for managing health data, comprising: a first memory; a second memory accessible by at least one designated user; and a medical device that measures terminal information and health data for identifying the terminal. Information including a transmission unit for transmitting device information to a management server interlocked with the terminal, and a security type instructing from the management server to store health data measured by the medical device in the first memory or the second memory And a receiving unit configured to receive and receive the health data from the medical device, and a control unit configured to instruct to store the health data in the first memory or the second memory based on the security type.

An apparatus according to another embodiment is a management server for managing health data, comprising: a receiving unit for receiving terminal information for identifying the terminal and medical device information for measuring health data from the terminal; and health data measured by the medical device A control unit for checking whether a security type instructing to store the data in a first memory or a second memory accessible by at least one designated user is registered in the management server, and when the security type is registered in the management server, It may include a management unit that generates information including the security type, and a transmission unit that transmits the generated information to the terminal.

The present invention proposes a method of classifying and managing health data according to security types, and through this, there is an effect of solving a problem caused by sharing health data requiring security to others.

1 is a diagram showing an example of a security type table for classifying security types for each medical device;
2 is a diagram illustrating an example of a security type table for classifying security types by health data measurable in medical devices;
3 is a diagram showing a procedure for storing and managing health data in a user terminal according to the first embodiment of the present invention;
4 is a diagram showing a procedure for storing and managing health data in a user terminal according to a second embodiment of the present invention;
5 is a diagram showing a procedure for sharing health data requiring security between a user terminal and a hospital server according to an embodiment of the present invention;
6 is a flow chart showing an operation of a user terminal for storing and managing health data according to an embodiment of the present invention;
7 is a flowchart showing the operation of a management server for storing and managing health data according to an embodiment of the present invention;
8 is a flow chart showing an operation of a hospital server sharing health data requiring security with a user terminal according to an embodiment of the present invention;
9 is a device diagram showing the configuration of a user terminal for storing and managing health data according to an embodiment of the present invention;
10 is an apparatus diagram showing the configuration of a management server for storing and managing health data according to an embodiment of the present invention;
11 is an apparatus diagram showing the configuration of a hospital server for sharing health data requiring security with a user terminal according to an embodiment of the present invention.

Hereinafter, preferred embodiments of the present invention will be described in detail with reference to the accompanying drawings. Further, in describing the present invention, when it is determined that a detailed description of a related known function or configuration may unnecessarily obscure the subject matter of the present invention, a detailed description thereof will be omitted. In addition, terms to be described later are terms defined in consideration of functions in the present invention, which may vary depending on the intention or custom of users or operators. Therefore, the definition should be made based on the contents throughout this specification.

In an embodiment of the present invention to be described later, when a user terminal purchases a medical device and stores health data measured through the medical device, a method of storing and managing the corresponding data in different memories according to the security type of the health data is provided. Suggest. In other words, it is proposed to store and manage the data in different memories depending on whether the health data is general data that does not matter to whom it is disclosed or whether it is security data that should be disclosed only to a specific group such as medical staff.

In addition, in an embodiment of the present invention to be described later, the following security type table is proposed in order to store and manage health data in different memories according to security types. The security type table may be issued so that the security type can be classified by medical device or measured health data.

1 is a diagram illustrating an example of a security type table for classifying security types for each medical device.

Referring to FIG. 1, the user terminal 160 purchases a medical device for measuring its own health status through the management server 130, for example, a weight scale, a blood pressure monitor, a blood glucose meter, an electrocardiogram, a blood analyzer, etc., and a management server ( 130) issues and manages a security type table 100 corresponding to each of the medical devices. Here, the user terminal 160 is assumed to be a smart phone, but the user terminal 160 may be any other IT device other than a smart phone. In addition, the medical device is an application program running on a smart phone. Assume that you purchase through the sensor shop of (application). Here, the sensor shop is a vendor that sells medical devices and is managed by the management server 130.

The security type table 100 is a table indicating security types such as health data measured by a medical device, such as weight, blood pressure, blood sugar, electrocardiogram, and blood analysis results, and is a table code 102 and a slot number (slot #). 104), a vendor identifier (ID) 106, a usage code 108, and a security type code 110.

The table code 102 represents a code for identification of the security type table 100, the slot # 104 represents the slot number of slots constituting the flash memory, and the manufacturer ID 106 is Represents an ID for identifying the manufacturer of the flash memory.

Here, the slots constituting the flash memory may have different uses for each manufacturer, and the use code 108 indicates the use of each of the slots. That is, '0x01' indicates that slot #0 that constitutes manufacturer A's flash memory and slot #N that constitutes manufacturer N's flash memory is used to store movie-related data, and '0x11' constitutes manufacturer B's flash memory. Slot #2 is used to store medical data, that is, health data, '0x1A' indicates that slot #2 of the manufacturer C's flash memory is used to store game-related data, and '0x20' 'Indicates that slot #3 of the manufacturer D's flash memory is used to store e-book related data.

The security type code 110 represents a security type of health data measured through a medical device. In other words, '00' indicates that the measured health data type corresponds to general data, so it is to be saved in open mode, and '10' indicates that the measured health data type corresponds to security data, so that it is stored in close mode. . The open mode is a mode instructing to store the corresponding health data in an open memory, for example, a Universal Subscriber Identifier Module (USIM) chip so that anyone can share the health data, and the closed mode specifies the corresponding health data. This mode is instructed to store in a memory set to be secured so that only a group can share, for example, an enhanced media ID (EMID) flash memory. In other words, the close mode can fundamentally block external access by storing health data in a secure memory so that information stored in the memory cannot be shared before inputting a unique ID.

It is assumed that the security type table 100 is generated corresponding to the blood analysis system as an example, and at this time, the security type code 110 of the health data indicated by the use code 108 '0x11' is the code '10' indicating the closed mode. Is set. Accordingly, the user terminal 160, which has received the security type table 100 from the management server 130, stores the blood analysis result measured through the blood analyzer in a memory set with security.

On the other hand, the management server 130 manages a plurality of flash memories that are uniquely configured for each manufacturer, and the flash memory 150 shows the flash memory configuration of the manufacturer B as an example. The flash memory 150 is composed of N slots, for example, slot #0 for storing movie-related data, slot #1 for storing e-book-related data, and slot #2 for storing medical-related data, Of course, the data stored in each slot may be set differently for each manufacturer.

2 is a diagram illustrating an example of a security type table for classifying security types by health data measurable in medical devices.

Referring to FIG. 2, the user terminal 260 purchases a medical device for measuring its own health status through the management server 230, and the management server 260 provides a security type table 200 corresponding to each of the medical devices. ) Is issued and managed. In FIG. 2, unlike in FIG. 1, it is assumed that one medical device can measure a plurality of health data, and therefore, the security type table 200 is used to classify security types by health data that can be measured by the medical device. Is written.

Herein, the user terminal 260 is assumed to be a smart phone, but the user terminal 260 may be any other IT device other than a smart phone. In addition, it is assumed that the medical device is purchased through a sensor shop of an application program running on a smartphone.

The security type table 200 is a table indicating the security type of health data measured by a medical device, and a table code 202, slot # 204, a manufacturer ID 206, a use code 208, and a security type code It includes information such as 210.

The table code 202 represents a code for identification of the security type table 200, the slot # 204 represents the slot number of the slots constituting the flash memory, and the manufacturer ID 206 represents the It represents the ID to identify the manufacturer.

Here, the slots constituting the flash memory may have different uses for each manufacturer, and the use code 208 indicates the use of each of the slots. That is, '0x01' indicates that slot #0 that constitutes manufacturer A's flash memory and slot #N that constitutes manufacturer N's flash memory is used to store movie-related data, and '0x11' constitutes manufacturer B's flash memory. Slot #2 is used to store medical-related data, that is, health data, '0x1A' indicates that slot #2 of the manufacturer C's flash memory is used to store game-related data, and '0x20' is the manufacturer. It indicates that slot #3 of D's flash memory is used to store e-book related data.

The security type code 210 represents a security type of each of a plurality of health data measured through a medical device. That is, '00' indicates that the measured health data type corresponds to general data and thus is stored in open mode, and '10' indicates that the measured health data type corresponds to security data and thus is stored in closed mode. Here, assuming that the medical device corresponding to the security type table 200 measures blood pressure, blood analysis, and weight, the security type code 210 is '00' indicating that the blood pressure and weight measured by the medical device are stored in an open mode. And the blood analysis result is set to '10', indicating that it is to be saved in the closed mode. Accordingly, the user terminal 260, which has received the security type table 200 from the management server 230, stores the health data measured through the medical device in an open memory or a memory set with security according to the type. That is, the user terminal stores blood pressure and weight among health data measured through medical devices in a USIM chip corresponding to a public memory so that anyone can share it, and the blood analysis results are set security so that only a specific group can share it. Save in EMID memory corresponding to memory.

On the other hand, the management server 230 manages a plurality of flash memories that are uniquely configured for each manufacturer, and the flash memory 250 shows the flash memory configuration of the manufacturer B as an example. The flash memory 250 is composed of N slots, for example, slot #0 for storing movie-related data, slot #1 for storing e-book-related data, and slot #2 for storing medical-related data, Of course, the data stored in each slot may be set differently for each manufacturer.

3 is a diagram illustrating a procedure of storing and managing health data in a user terminal according to the first embodiment of the present invention.

Referring to FIG. 3, the hospital server 306 sets the security type code of the medical device 304 linked to itself and transmits it to the medical device 304 (step 310). The security type code is registered in the interlocked management server 302 (step 312).

Here, a case in which the hospital server 306 sets the security type code of the medical device 304 has been described as an example, but the security type code may be directly set by the medical device 304 and transmitted to the management server 302. Although not shown, the hospital server 306 manages a personal health record (PHR) server, and the personal health record server may be located outside or inside the hospital server 306. In addition, the security type code may be set by the personal health record server and transmitted to the management server 302.

The user terminal 300, for example, a smart phone, executes an application program to purchase a medical device through a sensor shop (step 314), and inputs the user terminal number and the purchased medical device information to the management server 302. (Step 316) Here, the user terminal number is information for identifying the user terminal and may be a phone number, a serial number, a preset user password, or the like.

Since the management server 302 knows the security type code for the medical device 304 in advance as described in steps 310 and 312, the medical device information is input and issues a corresponding security type table (step 318). ) The security type table is issued to be mapped to the user terminal number, and since the security type table has been described in FIGS. 1 and 2, a detailed description of the security type table is omitted here. The security type table is issued corresponding to the medical device, and when the medical device measures only one health data, the security type table as shown in FIG. 1 is issued, and when the medical device measures a plurality of health data, The security type table as shown in Fig. 2 is issued.

The management server 302 transmits the security type table to the user terminal 300, and transmits the user terminal number received in step 316 and the table code of the security type table to the hospital server 306 (step 320). Step 321) The hospital server 306 stores the user terminal number and table code (Step 323).

Thereafter, when the medical device 304 measures the health data (step 324), the measured health data is wired or wirelessly transmitted to the user terminal 300 (step 326), and the user terminal 300 receives the security data in step 320. In the type table, a security type code indicating the security type of health data measured from the medical device 304 is checked (step 322).

The user terminal 300 stores the received health data in the memory according to the security type code checked in step 322 (step 328). That is, the user terminal 300 determines the security type of the health data measured from the medical device 304. If the indicated security type code is '00', it is confirmed that the measured health data is general data to be stored in an open mode, and the health data is stored in the USIM chip so that anyone can share it. On the other hand, when the security type code is '10', the user terminal 300 confirms that the health data measured by the medical device 304 is security data to be stored in the closed mode, and stores the health data only by a specific group such as a medical staff. Save it to EMID flash memory so it can be shared.

As described above, when the user terminal 300 stores health data measured through the medical device 304, general data is stored in the USIM chip and the security data is stored in the EMID flash memory according to the security type code indicated in the security type table. Thus, external access to health data that requires security is fundamentally blocked. In addition, the security type table is issued by the management server 302, and the security type code required for issuing the security type table may be set by the medical device 304, the hospital server 306, or a personal health record server.

4 is a diagram illustrating a procedure of storing and managing health data in a user terminal according to a second embodiment of the present invention.

Referring to FIG. 4, a user terminal 400, for example a smart phone, executes an application program to purchase a medical device 404 through a sensor shop (step 410), and the user terminal number and the above The purchased medical device information is input (step 412). Here, the user terminal number is information for identifying the user terminal, and may be a phone number, a serial number, a preset user password, or the like.

Since the management server 402 does not know the security type code for the medical device 404, it transmits the user terminal number and the medical device information to the hospital server 406 in order to obtain the security type code (step 414). The hospital server 406 sets the security type code of the medical device 404 corresponding to the received medical device information, issues a security type table corresponding to the medical device 404 (step 416), and Save the table code of the table (step 417).

Since the security type table has been described in FIGS. 1 and 2, detailed description of the security type table is omitted here. The security type table is issued corresponding to the medical device, and when the medical device measures only one health data, the security type table as shown in FIG. 1 is issued, and when the medical device measures a plurality of health data, The security type table as shown in Fig. 2 is issued. In addition, although not shown, the hospital server 406 manages a personal health record server, and the personal health record server may be located outside or inside the hospital server 406. In addition, the security type code may be set by the personal health record server.

The hospital server 406 transmits the security type table to the management server 402 (step 418), and the management server 402 transmits the received security type table to the user terminal 400. (step 420) the user terminal In the security type table, 400 checks a security type code indicating the security type of health data measured from the medical device 404 (step 422).

Thereafter, when the medical device 404 measures the health data (step 424), the measured health data is wired or wirelessly transmitted to the user terminal 400 (step 426), and the user terminal 400 is the security type checked in step 422. The health data received according to the code is stored in the memory. That is, if the security type code indicating the security type of the health data measured from the medical device 404 is '00', the user terminal 400 confirms that the measured health data is general data to be stored in an open mode, and It stores the data on a USIM chip that anyone can share. On the other hand, when the security type code is '10', the user terminal 400 confirms that the health data measured by the medical device 404 is security data to be stored in the closed mode, and stores the health data only by a specific group such as a medical staff. Store it in shared EMID flash memory.

As described above, when the user terminal 400 stores health data measured through the medical device 404, general data is stored in the USIM chip and security data is stored in the EMID flash memory according to the security type code indicated in the security type table. Thus, external access to health data that requires security is fundamentally blocked. In addition, the security type table is issued by the hospital server 402, and the security type code required for issuance of the security type table may be set by the hospital server 406 or a personal health record server.

In FIGS. 3 and 4, when the health data measured through a medical device is data requiring security, a method in which the user terminal stores the health data in the EMID flash memory so that only a specific group such as medical staff can share it. Explained. Hereinafter, a method of sharing health data stored in the EMID flash memory by the user terminal with a specific group such as a medical staff, for example, a hospital server will be described with reference to FIG. 5.

5 is a diagram illustrating a procedure for sharing health data requiring security between a user terminal and a hospital server according to an embodiment of the present invention.

5, a patient visits the hospital and tags the user terminal 500 to the hospital server 506 (step 510), and the hospital server 506 includes a user terminal number and a user terminal 500. The table code of the managed security type table is detected (step 512).

Although not shown, at this time, the hospital server 506 checks whether the checked table code matches a pre-stored table code, and saves the security data stored in the EMID flash memory of the user terminal only when the checked table code matches a pre-stored table code. You can share. The hospital server 506 already knows the table code of the security type table mapped to the user terminal, and the pre-stored table code means the table code of the security type table mapped to the user terminal. Here, it is assumed that the detected table code matches a previously stored table code.

That is, when the table code detected in step 512 matches the previously stored table code, the hospital server 506 sends a security data request message requesting sharing of security data stored in the EMID flash memory of the user terminal 500. ). (Step 514) The user terminal 500 transmits the secure data stored in the EMID flash memory to the hospital server 506 through a secure data response message to the secure data request message (Step 516). The user terminal 500 and the hospital server 506 share the security data stored in the EMID flash memory through steps 514 and 516. The hospital server 506 updates the health data of the user terminal 500 according to the shared health data (step 520).

However, if the table code detected in step 512 does not match the previously stored table code, the hospital server 506 cannot share the security data stored in the EMID flash memory of the user terminal 500.

6 is a flowchart illustrating an operation of a user terminal for storing and managing health data according to an embodiment of the present invention.

6, in step 602, a user terminal, for example, a smart phone, executes an application program to purchase a medical device through a sensor shop, and proceeds to step 604 to input the user terminal number and medical device information to the management server. Here, the user terminal number is information for identifying the user terminal and may be a phone number, a serial number, a preset user password, or the like.

In step 606, the user terminal receives the security type table from the management server, and proceeds to step 608 to check the security type code of the security type table. The security type code is a code indicating whether the data measured by the medical device purchased in step 602 is general data to be stored in open mode or secure data to be stored in closed mode.

In step 608, the user terminal receives the measured health data from the medical device purchased in step 603. In step 612, the user terminal stores the received health data according to the security type code checked in step 608. That is, if the security type code checked in step 608 is '00', the user terminal stores the measured health data in the USIM chip so that anyone can share it, and if the security type code is '10', the measured health data is stored with the medical staff. It is stored in EMID flash memory so that only the same specific group can share it.

7 is a flowchart illustrating an operation of a management server for storing and managing health data according to an embodiment of the present invention.

Referring to FIG. 7, in step 702, the management server receives a user terminal number and information about a medical device purchased by the user terminal from the user terminal. In step 704, the management server checks whether a security type code for the health data measured by the medical device is registered, and if the security type code is registered, proceeds to step 706 and based on the registered security type code. Issue a security type table mapped to the user terminal number. Thereafter, in step 708, the management server transmits the security type table to the user terminal. The case in which the security type code is registered as a result of checking in step 704 corresponds to a case in which the management server described in FIG. 3 knows the security type code for the medical device in advance.

On the other hand, if the security type code is not registered as a result of checking in step 704, the management server proceeds to step 710 and transmits the user terminal number and medical device information to the hospital server. In step 712, the management server receives a security type table issued and transmitted from the hospital server. The case in which the security type code is not registered as a result of the check in step 704 corresponds to the case where the management server described in FIG. 4 does not know the security type code for the medical device.

8 is a flowchart illustrating an operation of a hospital server sharing health data requiring security with a user terminal according to an embodiment of the present invention.

Referring to FIG. 8, in step 802, the hospital server tags the user terminal and proceeds to step 804 to detect the user terminal number of the user terminal and the table code of the security type table managed by the user terminal.

In step 806, the hospital server checks whether the detected table code matches a previously stored table code. Here, the pre-stored table code means a table code of a security type table mapped to the user terminal.

As a result of the check in step 806, if the table code detected in step 804 matches the previously stored table code, the hospital server proceeds to step 808 and transmits a security data request message requesting sharing of the security data stored in the EMID flash memory of the user terminal. do. In step 810, the hospital server receives the security data stored in the EMID flash memory through a security data response message, and proceeds to step 812 to update the health data of the user terminal.

However, if the table code detected in step 804 does not match the previously stored table code as a result of the check in step 806, the hospital server cannot share the security data stored in the EMID flash memory with the user terminal.

9 is an apparatus diagram showing the configuration of a user terminal for storing and managing health data according to an embodiment of the present invention.

Referring to FIG. 9, the user terminal 900 includes a receiving unit 910, a control unit 920, a first storage unit 930, a second storage unit 940, and a transmission unit 950.

When purchasing a medical device, the user terminal 900 transmits the user terminal number and medical device information through the transmission unit 950 and inputs it to the management server, and receives the security type table from the management server through the reception unit 910. . Here, the user terminal number is information for identifying the user terminal and may be a phone number, a serial number, a preset user password, or the like.

When the security type table is transmitted from the receiving unit 910, the control unit 920 checks the security type code of the security type table. Thereafter, when the health data is transmitted from the receiving unit 910, the controller 920 controls the first and second memories 930 according to the previously identified security type code. That is, when the health data is transmitted from the receiving unit 910, the controller 920 stores the health data in a USIM chip that can be shared by anyone when the previously identified security type code is '00', and when the security type code is '10' Control to store the health data in an EMID flash memory that can be shared only by a specific group such as medical staff.

10 is an apparatus diagram showing the configuration of a management server for storing and managing health data according to an embodiment of the present invention.

Referring to FIG. 10, the management server 1000 includes a reception unit 1010, a control unit 1020, a management unit 1030, a memory 1040, and a transmission unit 1050.

When the receiving unit 1010 of the management server 1000 inputs the user terminal number and the medical device information purchased by the user terminal from the user terminal, the security type code of the security type table mapped to the user terminal through the control unit 1020 Check if it is registered in the memory 1040. At this time, if the security type code is registered in the memory 1040, a security type table is issued through the management unit 1030 and transmitted to the user terminal through the transmission unit 1050. In addition, the user terminal number and the table code of the security type table are transmitted to the hospital server through the transmission unit 1050.

Meanwhile, if the security type code is not registered in the memory 1040, the user terminal number and medical device information are transmitted to the hospital server through the transmitter 1050. Thereafter, the security type table transmitted from the hospital server is received through the receiving unit 1010, and the received security type table is transmitted to the user terminal through the transmitting unit 1050.

11 is an apparatus diagram showing the configuration of a hospital server for sharing health data requiring security with a user terminal according to an embodiment of the present invention.

Referring to FIG. 11, the hospital server 1100 includes a control unit 1110, a transmission unit 1120, a reception unit 1030, and a memory 1140.

The reception unit 1130 of the hospital server 1100 checks the user terminal number and table code through the control unit 1110 when the user terminal is tagged and the table code of the user terminal number and the security type table managed by the user terminal is input.

In addition, the control unit 1110 checks whether the checked table code matches a pre-stored table code, that is, a table code of a security type table mapped to the user terminal, and if the checked table code matches a pre-stored table code, the transmission unit 1120 Through this, a security data request message requesting sharing of security data stored in the EMID flash memory of the user terminal is transmitted.

Thereafter, a security data response message is received in response to the security data request message through the reception unit 1130, and security data stored in the EMID flash memory of the user terminal is received together with the security data response message. The received security data is transmitted to the memory 1140, and the hospital server 1100 updates the health data of the user terminal stored in the memory 1140.

Meanwhile, although specific embodiments have been described in the detailed description of the present invention, various modifications are possible without departing from the scope of the present invention. Therefore, the scope of the present invention is limited to the described embodiments and should not be defined, and should be defined by the scope of the claims and equivalents as well as the scope of the claims to be described later.

In addition, it will be appreciated that the apparatus and method for managing health data according to an embodiment of the present invention can be realized in the form of hardware, software, or a combination of hardware and software. Any such software, for example, whether erasable or rewritable, may be a volatile or nonvolatile storage device such as a storage device such as a ROM, or a memory device such as a RAM, memory chip, device or integrated circuit, for example. Or, for example, it may be optically or magnetically recordable, such as a CD, DVD, magnetic disk or magnetic tape, and stored in a storage medium readable by a machine (eg, a computer). The graphic screen update method of the present invention may be implemented by a computer or portable terminal including a control unit and a memory, and the memory is a machine suitable for storing a program or programs including instructions for implementing the embodiments of the present invention. You can see that it is an example of a readable storage medium.

Accordingly, the present invention includes a program including code for implementing the apparatus or method described in any claim of the present specification, and a machine (computer, etc.) readable storage medium storing such a program. Further, such a program may be transferred electronically through any medium, such as a communication signal transmitted through a wired or wireless connection, and the present invention suitably includes equivalents thereto.

In addition, the device for health data management according to an embodiment of the present invention may receive and store the program from a program providing device connected by wire or wirelessly. The program providing device provides a program including instructions for the graphic processing device to perform a preset content protection method, a memory for storing information necessary for the content protection method, and wired or wireless communication with the graphic processing device. It may include a communication unit to perform, and a control unit for automatically transmitting a request from the graphic processing device or a corresponding program to the transmission and reception device.

Claims (15)

In the method for the terminal to manage health data,
Transmitting terminal information for identifying the terminal and medical device information for measuring health data to a first server interlocked with the terminal;
Receiving, from the first server, information including a security type instructing to store the health data in a first memory or a second memory accessible by at least one designated user; And
And storing the health data in the first memory or the second memory based on the security type,
The security type is a health data management method that is set based on at least one of the terminal information, the medical device information, and the health data.
delete The method of claim 1,
The security type is included in a security type table, and the security type table includes a table code for identification of the security type table, slot numbers of slots constituting the first memory and the second memory, the first memory and the Health data management method further comprising at least one of an identifier for identifying a manufacturer of the second memory and a use code indicating a use of each of the slots.
The method of claim 1,
When one health data is measured by the medical device, the security type is set based on the medical device, and when two or more types of health data are measured by the medical device, the security type is measured by the medical device. Health data management method established based on health data.
The method of claim 1,
The security type table including the security type is received from the first server or a second server interlocked with the first server, and when the security type table is received from the first server, the security type is the medical device or Health data management method that is set in the second server and registered in the first server, and the security type is set in the second server when the security type table is received from the second server.
The method of claim 1,
When the table code of the security type table including the security type matches the table code of the security type table mapped to the terminal information, the health data stored in the second memory is shared from a second server linked to the first server. Receiving a request for; And
The health data management method further comprising transmitting the health data stored in the second memory to the second server.
The method of claim 1,
The terminal information health data management method including at least one of a phone number, a serial number, and a preset password of the terminal.
In the terminal for managing health data,
A transceiver; And
And a control unit connected to the transmission/reception unit,
The control unit,
Transmitting terminal information for identifying the terminal and medical device information for measuring health data to a first server interlocked with the terminal through the transceiver,
Receiving information including a security type instructing to store the health data in a first memory or a second memory accessible by at least one designated user, from the first server through the transceiver,
It is configured to instruct to store the health data in the first memory or the second memory based on the security type, and the security type is set based on at least one of the terminal information, the medical device information, and the health data Terminal.
The method of claim 8,
Terminal further comprising at least one of the first memory and the second memory.
delete The method of claim 8,
The security type is included in a security type table, and the security type table includes a table code for identification of the security type table, slot numbers of slots constituting the first memory and the second memory, the first memory and the A terminal further comprising at least one of an identifier for identifying a manufacturer of the second memory and a usage code indicating a use of each of the slots.
The method of claim 8,
When one health data is measured by the medical device, the security type is set based on the medical device, and when two or more types of health data are measured by the medical device, the security type is measured by the medical device. Terminal set based on health data.
The method of claim 8,
The security type table including the security type is received from the first server or a second server interlocked with the first server, and when the security type table is received from the first server, the security type is the medical device or The terminal is set in the second server and registered in the first server, and the security type is set in the second server when the security type table is received from the second server.
The method of claim 8,
When the table code of the security type table including the security type coincides with the table code of the security type table mapped to the terminal information, the control unit transmits the data from the second server interlocked with the first server to the A terminal receiving a request for sharing health data stored in a second memory and transmitting health data stored in the second memory to the second server.
The method of claim 8,
The terminal information includes at least one of a phone number, a serial number, and a preset password of the terminal.

Images