Healthcare data management system, healthcare data management method, and healthcare data management program

The healthcare data management system addresses the challenge of rewarding all stakeholders in healthcare data sharing by incorporating a reward distribution unit that compensates users, manufacturers, and data holders, ensuring a comprehensive incentive structure for data sharing.

JP2025077255AActive Publication Date: 2025-05-19IMOBILE
View PDF 4 Cites 0 Cited by

Patent Information

Application Number
JP2023189318
Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
Filing Date
2023-11-06
Publication Date
2025-05-19
Estimated Expiration
2043-11-06

AI Technical Summary

Technical Problem

Existing technologies face challenges in distributing rewards to manufacturers and holders of devices that acquire healthcare data, as well as to holders of the healthcare data itself, beyond just rewarding the users providing the data.

Method used

A healthcare data management system that includes a storage unit for associating manufacturer IDs with device IDs, a healthcare data reception unit for receiving and storing user and device IDs with the healthcare data, a provision unit for providing the data, and a reward distribution unit that distributes rewards to users, manufacturers, and data holders based on the provided healthcare data.

Benefits of technology

Enables the distribution of rewards to all stakeholders involved in providing healthcare data, including users, manufacturers, and data holders, thereby incentivizing the sharing of healthcare data while ensuring proper compensation for all parties.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 2025077255000001_ABST
    Figure 2025077255000001_ABST
Patent Text Reader

Abstract

To provide new technique for distributing rewards by providing healthcare data related to medical treatment / health.SOLUTION: A healthcare data management system 0 comprises a storage unit, a healthcare data reception unit, a provision unit, and a reward distribution unit. The storage unit stores, in association with each other, a device ID of a device that acquires health care data relating to medical treatment / health of a user, and a manufacturer ID of a manufacturer that supplies the device. The healthcare data reception unit receives the health care data, the user ID of the user, and the device ID of the device that has acquired the healthcare data, and then associates the user ID and the device ID with the healthcare data, and stores them in the storage unit. The provision unit provides health care data to a person who wants to use the healthcare data. The reward distribution unit distributes rewards to the manufacturer having the manufacturer ID and the user having the user ID associated with the provided healthcare data.SELECTED DRAWING: Figure 1
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to a healthcare data management system, a healthcare data management method, and a healthcare data management program.

Background Art

[0002] Conventionally, there has been a technology that provides data related to a user's medical care and health to a third party, and the user who provides the data receives a reward.

[0003] For example, Patent Document 1 discloses a technology in which a user provides data related to medical care and health, and a reward is distributed to the user in exchange for the provision of the personal data.

Prior Art Documents

Patent Documents

[0004]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0005] In order for a user to provide data related to medical care and health to a third party, cooperation from a person other than the user, particularly a manufacturer that supplies a device for acquiring healthcare data related to medical care and health, is also indispensable. However, with the technology of Patent Document 1, while it is possible to distribute a reward to the user, it is difficult to distribute a reward to the manufacturer that supplies the device.

[0006] The present invention has been made in view of the above circumstances, and an object thereof is to provide a new technology for distributing rewards for providing healthcare data related to medical care and health.

Means for Solving the Problems

[0007] In order to solve the above problems, the present invention provides a healthcare data management system for managing healthcare data related to a user's medical and health conditions, comprising: The healthcare data management system includes a storage unit, a healthcare data reception unit, a provision unit, and a reward distribution unit. The storage unit stores by associating a manufacturer ID of a manufacturer that supplies a device for acquiring healthcare data related to a user's medical and health conditions with a device ID of the device. The healthcare data reception unit receives the healthcare data, a user ID of the user, and a device ID of a device that has acquired the healthcare data, associates the user ID and the device ID with the healthcare data, and stores the associated data in the storage unit. The provision unit provides the healthcare data to a person who wishes to use the healthcare data. The reward distribution unit distributes rewards to the user corresponding to the user ID associated with the provided healthcare data and the manufacturer corresponding to the manufacturer ID.

[0008] In addition, in order to solve the above problems, the present invention provides a healthcare data management method executed by a healthcare data management system for managing healthcare data related to a user's medical and health conditions, comprising: The healthcare data management system includes a storage unit, a healthcare data reception unit, a provision unit, and a reward distribution unit. A step of the storage unit storing by associating a manufacturer ID of a manufacturer that supplies a device for acquiring healthcare data related to a user's medical and health conditions with a device ID of the device. A step of the healthcare data reception unit receiving the healthcare data, a user ID of the user, and a device ID of a device that has acquired the healthcare data, associating the user ID and the device ID with the healthcare data, and storing the associated data in the storage unit. A step of the provision unit providing the healthcare data to a person who wishes to use the healthcare data. The step of the reward distribution unit distributing a reward to the user with the user ID and the manufacturer with the manufacturer ID associated with the provided healthcare data.

[0009] Also, in order to solve the above problems, the present invention is a healthcare data management program for managing healthcare data related to a user's medical and health conditions, causing a computer having a storage unit to function as a healthcare data reception unit, a provision unit, and a reward distribution unit, wherein the storage unit stores by associating a manufacturer ID of a manufacturer that supplies a device for acquiring healthcare data related to a user's medical and health conditions with the device ID of the device, the healthcare data reception unit receives the healthcare data, the user ID of the user, and the device ID of the device that acquired the healthcare data, associates the user ID and the device ID with the healthcare data, and stores the data in the storage unit, the provision unit provides the healthcare data to a person who wants to use the healthcare data, and the reward distribution unit distributes a reward to the user with the user ID and the manufacturer with the manufacturer ID associated with the provided healthcare data.

[0010] With such a configuration, it is possible to distribute a reward to a manufacturer that supplies a device that has acquired a user's healthcare data.

[0011] In a preferred form of the present invention, the storage unit stores by associating a healthcare data holder ID representing the holder of the healthcare data with the healthcare data, and the reward distribution unit further distributes the reward to the holder represented by the healthcare data holder ID associated with the provided healthcare data.

[0012] With such a configuration, it is possible to distribute a reward to a holder who holds a user's healthcare data.

[0013] In a preferred embodiment of the present invention, the healthcare data management system further comprises an opt-in information receiving unit, The opt-in information receiving unit receives opt-in information indicating whether to provide the healthcare data to those who want to use the healthcare data, associates the opt-in information with the healthcare data and / or the user ID, and stores the associated information in the storage unit. The providing unit further provides the healthcare data based on the opt-in information.

[0014] With such a configuration, the user can select whether to provide their own healthcare data to those who want to use it.

[0015] In a preferred embodiment of the present invention, the healthcare data management system further comprises a transmission opt-in information receiving unit. The transmission opt-in information receiving unit receives transmission opt-in information indicating whether to transmit the healthcare data to the healthcare data receiving unit.

[0016] With such a configuration, the user can determine whether to transmit their own healthcare data.

[0017] In a preferred embodiment of the present invention, the storage unit further stores user attributes, which are the attributes of the user, associated with the user ID. The reward distribution unit distributes the reward based on the user attributes associated with the user ID.

[0018] With such a configuration, it is possible to distribute rewards according to the attributes of the user associated with the healthcare data.

[0019] In a preferred embodiment of the present invention, the healthcare data management system further comprises a usage request receiving unit. The usage request receiving unit receives a request to use healthcare data that includes usage restriction information, which is information for restricting the use of the healthcare data. The providing unit further provides healthcare data with usage restrictions, including information that restricts the use of the healthcare data under the conditions of the usage restriction information, based on the usage request.

[0020] By adopting such a configuration, the expiration date for the use of healthcare data can be set.

[0021] In a preferred form of the present invention, the healthcare data reception unit further receives an electronic contract that contracts for the distribution of the remuneration between the user and / or the holder and the person who wants to use the healthcare data, and stores it in the storage unit linked to at least one of the healthcare data, the user ID, the device ID, or the healthcare data holder ID.

[0022] By adopting such a configuration, the remuneration generated from the user's healthcare data can be regarded as a claim.

[0023] To solve the above problems, a healthcare data management system for managing healthcare data related to a user's medical and health conditions, The healthcare data management system includes a storage unit, a healthcare data reception unit, a providing unit, a providing opt-in information reception unit, and a remuneration distribution unit. The storage unit stores by associating the device ID of a device that acquires healthcare data related to a user's medical and health conditions with the manufacturer ID of the manufacturer that supplies the device, and further stores by associating the healthcare data holder ID representing the holder of the healthcare data with the healthcare data. The healthcare data reception unit receives the healthcare data, the user ID of the user, the device ID of the device that acquired the healthcare data, and the healthcare data owner ID of the healthcare data, associates the user ID with information for identifying the healthcare data, and stores it in the blockchain network system. Further, the device ID and the healthcare data owner ID are associated with the information for identifying the healthcare data and stored in the storage unit or the blockchain network system. The provision opt-in information reception unit receives provision opt-in information indicating whether the healthcare data can be provided to those who want to use the healthcare data, associates the provision opt-in information with the information for identifying the healthcare data and / or the user ID, and stores it in the storage unit or the blockchain network system. The provision unit provides the healthcare data to those who want to use the healthcare data based on the provision opt-in information. The reward distribution unit distributes rewards to the user represented by the user ID associated with the provided healthcare data, the manufacturer represented by the manufacturer ID, and the owner represented by the healthcare data owner ID associated with the provided healthcare data.

[0024] With such a configuration, it is possible to prevent the falsification of healthcare data and the like.

Advantages of the Invention

[0025] According to the present invention, it is possible to provide a new technology for distributing rewards by providing healthcare data related to medical care and health.

Brief Description of the Drawings

[0026]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Mode for Carrying Out the Invention

[0027] Hereinafter, the healthcare data management system of the present invention will be described with reference to the drawings. Preferred embodiments are shown in the drawings. However, the present invention can be implemented in many different forms and is not limited to the embodiments described herein.

[0028] For example, in this embodiment, the configuration, operation, etc. of the healthcare data management system will be described, but the same effects can also be achieved by the method, apparatus, computer program, etc. executed. The program in this embodiment may be provided as a computer-readable non-transitory recording medium, may be provided so as to be downloadable from an external server, or the program may be started on an external computer in order to implement its function at the client terminal (so-called cloud computing).

[0029] Also, in this embodiment, the "section" may include, for example, a combination of hardware resources implemented by a circuit in a broad sense and information processing of software that can be specifically realized by these hardware resources. In this embodiment, the "information" is represented, for example, by a physical value of a signal value representing voltage or current, the high and low of a signal value as a set of binary bits composed of 0 or 1, or a quantum superposition (so-called quantum bit), and communication and calculation can be executed on a circuit in a broad sense.

[0030] A circuit in a broad sense is a circuit realized by appropriately combining a circuit, circuitry, a processor, a memory, etc. That is, it includes a CPU (Central Processing Unit), a GPU (Graphics Processing Unit), an LSI (Large Scale Integration), an ASIC (Application Specific Integrated Circuit), an FPGA (Field-Programmable Gate Array), etc.

[0031] <System Overview> FIG. 1 is a block diagram showing the configuration of a healthcare data management system according to this embodiment. As shown in FIG. 1, the healthcare data management system 0 includes a healthcare data management device 1, a device 2, and a medical institution device 3. The healthcare data management device 1 is configured to be communicable with the device 2 and the medical institution device 3 via a communication network NW.

[0032] In this embodiment, the communication network NW is an IP (Internet Protocol) network, but there is no limitation on the type of communication protocol, and further, there is no limitation on the type and scale of the network.

[0033] The healthcare data management device 1 is a device that collectively manages healthcare data acquired by a user in various locations and ways. As the healthcare data management device 1, it is possible to use a computer for a general-purpose server, a personal computer, etc. Also, it is possible to configure the healthcare data management device 1 using a plurality of computers.

[0034] Device 2 acquires healthcare data related to the user's medical and health conditions. As Device 2, for example, an information processing device such as a personal computer, smartphone, tablet terminal, IoT (Internet of Things) device, etc. can be used. For example, when Device 2 is a smartphone, the user can acquire healthcare data via the downloaded application. Also, for example, when Device 2 is an IoT device that can acquire healthcare data, it can directly acquire the healthcare data and transmit it to the healthcare data management device 1.

[0035] The medical institution device 3 acquires healthcare data related to the user's medical and health conditions. The medical institution generates healthcare data, for example, by means of CT scans, X-rays, and the entry of medical records (clinical records) by doctors. The medical institution device 3 acquires the healthcare data generated at the medical institution.

[0036] The healthcare data management system 0 may further include a device for generating healthcare data. Examples of the device for generating healthcare data include the device of a medical institution where there is a doctor, the device of a person who provides an application for acquiring healthcare data via a smartwatch, etc., and the device of a person who created that application. The device for generating healthcare data may be configured to be communicable with the healthcare data management device 1 via the communication network NW, or may be configured to be communicable only with Device 2 or the medical institution device 3.

[0037] <Hardware Configuration> Figure 2 is a hardware configuration diagram. As shown in Figure 2(a), the information processing device 10 (healthcare data management device 1) has a processing unit 101, a storage unit 102, and a communication unit 103, which are used to exert the functions of each part and each process. Also, as shown in Figure 2(b), the terminal device 9 (Device 2) has a processing unit 91, a storage unit 92, a communication unit 93, an input unit 94, and an output unit 95, which are used to exert the functions of each part and each process.

[0038] The processing unit 101 and the processing unit 91 have a processor such as a CPU (Central Processing Unit) capable of executing an instruction set, and execute an OS (Operating System) and a healthcare data management program (in the case of the healthcare data management device 1) or a healthcare data acquisition program (in the case of the device 2), etc.

[0039] The storage unit 102 and the storage unit 92 have a volatile memory such as a RAM (Random Access Memory) capable of storing an instruction set and a non-volatile recording medium such as an HDD (Hard Disk Drive) or an SSD (Solid State Drive) capable of recording an OS, etc. The storage unit 102 of the information processing device 10 stores a healthcare data management program and various information described later. The storage unit 92 of the terminal device 9 stores a healthcare data acquisition program, etc.

[0040] The communication unit 103 and the communication unit 93 have an interface for physically connecting to a network, execute communication control with the network, and communicate with other information processing devices 10 and terminal devices 9. The input unit 94 has an operation input device capable of input processing such as a touch panel or a keyboard, a voice input device capable of voice input such as a microphone, and a sensor for acquiring healthcare data, etc. The output unit 95 has a display device capable of display processing such as a display and a voice output device such as a speaker.

[0041] The device for generating healthcare data also has a hardware configuration as shown in Fig. 2(a) or (b).

[0042] <Functional component elements> As shown in FIG. 3, the healthcare data management device 1 includes a healthcare data reception unit 11, an offer opt-in information reception unit 12, a provision unit 13, a reward distribution unit 14, and a usage request reception unit 15. The device 2 includes a healthcare data acquisition unit 21, a user information reception unit 22, a transmission unit 23, a personal information anonymization unit 24, and a transmission opt-in information reception unit 25. The medical institution device 3 includes a healthcare data generation unit 31, a user information reception unit 32, a transmission unit 33, a personal information anonymization unit 34, and a transmission opt-in information reception unit 35.

[0043] The arrangement of these functional components is an example, and a part of the functional configuration of the healthcare data management device 1 may be arranged in one or more devices configured to be communicable with the medical institution device 3, the device 2, or the healthcare data management device 1. Similarly, a part of the functional configuration of the device 2 may be arranged in one or more devices configured to be communicable with the healthcare data management device 1 or the device 2. Also, a part of the functional configuration of the medical institution device 3 may be arranged in one or more devices configured to be communicable with the healthcare data management device 1 or the medical institution device 3.

[0044] The device that generates healthcare data may include some or all of the functional configurations provided in the healthcare data management device 1, the device 2, or the medical institution device 3.

[0045] The healthcare data management device 1 stores device information, manufacturer information, healthcare data owner information, anonymized user information, healthcare data, offer opt-in information, and accessor information in the storage unit. The device 2 stores the user ID and transmission opt-in information in the storage unit. The medical institution device 3 stores user information and healthcare data in the storage unit.

[0046] The storage unit for storing information may be a blockchain network system. For example, a part of the information stored in the healthcare data management device 1, such as a user ID, a value that can identify an individual only within the healthcare data management device 1, and healthcare data, may be stored in the blockchain. In addition to this, it is conceivable that the blockchain network stores information for identifying healthcare data. When the healthcare data is an MRI image or the like, the information for identifying the healthcare data may be a URL representing the storage location of the image. Also, a healthcare data ID associated with the healthcare data can be considered as information for identifying the healthcare data, and the healthcare data stored in a storage unit that is not a blockchain network can be referred to using this healthcare data ID. A blockchain is composed of a chain of data called blocks. Since each block contains information on the hash value of the previous block, if any block is tampered with, an inconsistency occurs in the chain relationship. Also, it has the property that a large number of nodes cannot perform such unauthorized tampering processes or block deletions. When information is transmitted to the blockchain network system, the information is stored in the block.

[0047] The arrangement of each data is also an example, and part or all of the data stored in the storage unit of the healthcare data management device 1 may be stored in one or more devices configured to be communicable with the medical institution device 3, the device 2, or the healthcare data management device 1. Similarly, part or all of the data stored in the storage unit of the device 2 may be stored in one or more devices configured to be communicable with the healthcare data management device 1 or the device 2. Also, part or all of the data stored in the storage unit of the medical institution device 3 may be stored in one or more devices configured to be communicable with the healthcare data management device 1 or the medical institution device 3.

[0048] <Data Configuration> FIG. 4 is an example of the data configuration stored in the database in the present embodiment. The user information is information as shown in FIG. 4(a) in which information related to the user such as the user's name, date of birth, age, gender, pre-existing medical conditions, and reward receipt information is associated with a user ID for identifying an individual. The user ID may be any value as long as it cannot be identified by an unspecified number of people. For example, a personal number or the like can be considered, but it may also be a value that can identify an individual only within the healthcare data management device 1. A value that can identify an individual only within the healthcare data management device 1 may be, for example, a value obtained by hashing a personal number and a date of birth using a hash function (personal hash value). The information related to the user is stored in the storage unit of the device 2 of the user or the medical institution device 3 in the medical institution where the user visits. As information related to the user, information that can be used for analyzing the tendency of diseases and / or information that can be used for calculating the rewards to be distributed, such as age, gender, and types of pre-existing medical conditions, can be considered. The reward receipt information is information for distributing rewards and can be anything as long as it is, for example, the account of the payment means designated by the user to receive the reward. In FIG. 4(a), since a bank account is associated, it represents receiving the reward by transferring money to that account. In addition to this, the reward receipt information may be various settlement accounts, accounts for various points obtained when using a credit card, wallet addresses for receiving cryptocurrency, and the like.

[0049] Healthcare data is information related to the medical and health conditions of users, such as the information shown in FIGS. 4(b) to 4(d) associated with a user ID. Examples of healthcare data include a user's vital data (biological information such as pulse, blood pressure, respiration, body temperature, etc.), height, weight, daily step count, daily sleep duration, types of underlying diseases, types of regularly taken medications, types of allergies, medical history, and the like. Furthermore, healthcare data may be information acquired or generated by medical institutions or the like. For example, information acquired by devices of medical institutions, information related to doctor consultations generated by medical institutions or the like may be considered. In the healthcare data shown in FIGS. 4(b) and 4(c), a device ID for identifying the device used to acquire it is further associated. Additionally, the date and time when the healthcare data was acquired is associated with the healthcare data. The healthcare data shown in FIG. 4(d) is information generated and acquired by a doctor in a medical institution, and further, a healthcare data holder ID for identifying the holder who possesses it is associated. Also, it may be information acquired by a device of a medical institution, in which case, a device ID is further associated. Healthcare data is stored in at least one of the storage units of the healthcare data management device 1, the device 2, or the medical institution device 3. The healthcare data holder may be a medical institution that generated the healthcare data, a company that possesses (actually acquired) the healthcare data, or the like. Furthermore, information for identifying the healthcare data, such as a healthcare data ID, may be associated with the healthcare data shown in FIGS. 4(b) to 4(d).

[0050] The anonymized user information is information that cannot identify the user's personal information. For example, it is information such as shown in FIG. 5(a) where user attributes such as the user's age, gender, types of underlying diseases, etc. are associated with the user ID. Since the anonymized user information has been processed so that the user's personal information cannot be identified, it is stored in the storage unit of the healthcare data management device 1.

[0051] Device information is information such as that shown in Fig. 5(b) in which a device ID is associated with a manufacturer ID for identifying the manufacturer that supplies the device. Since the manufacturer that distributes the reward is specified by the device information, the device information is stored in the storage unit of the healthcare data management device 1. In the present embodiment, an IoT device and a smartphone or the like cooperate to function as device 2, and the device ID is an ID for identifying an IoT device that cooperates with the smartphone. When a plurality of IoT devices cooperate with one smartphone, different device IDs are assigned to each IoT device.

[0052] Manufacturer information is information such as that shown in Fig. 5(c) in which a manufacturer ID is associated with reward receipt information and the like. Since the method by which the manufacturer of the manufacturer ID receives the reward is determined by the manufacturer information, the manufacturer information is stored in the storage unit of the healthcare data management device 1.

[0053] Healthcare data owner information is information such as that shown in Fig. 5(d) in which a healthcare data owner ID is associated with reward receipt information and the like. Since the method by which the owner represented by the healthcare data owner ID receives the reward is determined by the healthcare data owner information, the healthcare data owner information is stored in the storage unit of the healthcare data management device 1.

[0054] Transmission opt-in information is information such as that shown in Fig. 5(e) in which a device ID is associated with transmission permission information indicating whether or not the healthcare data acquired by the device may be registered in the healthcare data management device 1. Since transmission permission information is associated with each device that acquires healthcare data, the transmission opt-in information is stored in the storage unit of device 2.

[0055] Provided opt-in information is information like FIG. 5(f) in which provision permission information indicating whether it is possible to provide a user's healthcare data to research institutions, pharmaceutical companies, etc. that wish to conduct research using the healthcare data obtained by that device is associated with the device ID. In addition to this, it is conceivable that provision permission information is associated with the healthcare data. The healthcare data management device 1 stores the provided opt-in information in its storage unit in order to determine whether it is possible to provide the healthcare data to research institutions, pharmaceutical companies, etc. based on the provided opt-in information.

[0056] Access person information is information like FIG. 5(g) in which the password of the account is associated with the account ID of a person who can search for and / or acquire healthcare data within the healthcare data management device 1. Since the access person information is information of a person who can search for and / or acquire healthcare data within the healthcare data management device 1, it is stored in the storage unit of the healthcare data management device 1.

[0057] In this embodiment, the device 2 is an IoT device, a smartphone, etc., and by using a dedicated application to cooperate with a plurality of IoT devices, the healthcare data obtained from the IoT devices can be transmitted to the healthcare data management device 1. In addition to this, a case where the device 2 is a smartphone, acquires healthcare data via an application, the device ID is an ID for identifying the application, and the manufacturer ID is an ID for identifying the manufacturer that supplies the application is also conceivable. Also, in this embodiment, the healthcare data holder is a medical institution that generates a user's medical record (medical chart), etc., and the healthcare data holder ID is an ID for identifying that medical institution.

[0058] <Flowchart of the process> FIG. 6 is a flowchart of the processing in the present embodiment. First, in step S601, a person concerned performs pre-registration with the healthcare data management device 1. The person concerned is a user who acquires healthcare data using a device, a user who has a healthcare institution generate healthcare data, a healthcare institution that acquires and holds healthcare data, a company that holds healthcare data, an institution or company that conducts research or the like using healthcare data, a device manufacturer, etc., and is a person related to the acquisition or use of healthcare data.

[0059] Hereinafter, the registration in S601 will be specifically described. The pre-registration of a user is for a person who conducts research or the like using healthcare data to send to the healthcare data management device 1 the provision opt-in information for the user to provide their own healthcare data, the consent to receive a reward when the healthcare data is used, and the consent to the related regulations. The user can set the provision opt-in information for each IoT device that acquires healthcare data. For example, the user can make settings such as not providing the healthcare data acquired from a weighing scale (provision available: no) and providing the healthcare data acquired from a blood pressure monitor (provision available: yes). Specifically, the provision opt-in information for the healthcare data acquired from each IoT device is set via a dedicated application, and the provision opt-in information is associated with each device ID and stored in the storage unit. Further, the healthcare data management device 1 stores the received consent in the storage unit.

[0060] The pre-registration of a healthcare institution is for the healthcare institution to send to the healthcare data management device 1 the consent to anonymize the personal information of the user by removing it and provide the generated healthcare data when the healthcare institution will generate, acquire, and there is consent from the user (the provision opt-in information has been received from the user) in the future, and the consent to receive a reward when the healthcare data is used, and the consent to the related regulations. The healthcare data management device 1 stores the received consent in the storage unit.

[0061] The prior registration of a person who holds healthcare data means that when the holder holds and accumulates the user's past healthcare data and obtains the user's consent, the holder anonymizes the user's personal information by removing it and provides the healthcare data to be held and accumulated, and also that the holder receives a reward when the healthcare data is used. It is for the holder to send the consent to the relevant agreement regarding this to the healthcare data management device 1. The healthcare data management device 1 stores the received consent in the storage unit.

[0062] The prior registration of an institution or enterprise that conducts research, etc. using healthcare data means that the institution or enterprise sends the consent to the relevant agreement regarding the use of healthcare data and the payment of rewards to the healthcare data management device 1, and further obtains the access method to the healthcare data possessed by the healthcare data management device 1. The acquisition of the access method specifically means that the institution or enterprise that conducts research, etc. obtains an account for searching and / or acquiring the healthcare data in the healthcare data management device 1, and can access the healthcare data by logging in using the account. Specifically, the healthcare data management device 1 issues an account ID and stores it in the storage unit of the healthcare data management device 1 as accessor information, enabling the person to log in to the account, and stores the received consent in the storage unit.

[0063] The prior registration of a manufacturer that supplies a device means that the manufacturer sends the consent regarding the use of healthcare data, the relevant agreement regarding receiving a reward, and the reward receipt information to the healthcare data management device 1, and further sends the device ID supplied by the manufacturer. The healthcare data management device 1 stores the received consent in the storage unit as device information and manufacturer information.

[0064] In step S602, the health care data of the user is acquired, and the health care data management device 1 registers the health care data. The health care data of the user is acquired via the device 2 or the medical institution device 3 and registered in the health care data management device 1. It is registered only when the user consents to register it in the health care data management device 1. Also, the health care data registered in the health care data management device 1 by the person who holds the health care data may be the health care data consented to by the user. Further, since the health care data is registered in the health care data management device 1, it is expected to function as a backup device in case the data in the medical institution is lost or deleted. The medical records of the medical institution are defined to have a preservation obligation period of 5 years, so the data will not be deleted during that period, but after that, data deletion is recognized. Even in such a case where the data is deleted, as long as the health care data management device 1 permanently stores the health care data, it can be used as data for research purposes. In addition to this, when the health care data is registered in the health care data management device 1, as a result, the user can view and manage the health care data that was discretely (in various medical institutions, applications, etc.) arranged in a unified manner. Furthermore, if the user desires, the unified managed health care data can be viewed by a specific medical institution or the like.

[0065] The device 2 or the medical institution device 3 transmits the acquired health care data to the health care data management device 1, and the health care data management device 1 stores it in the storage unit.

[0066] For example, device 2 transmits the healthcare data obtained by a device associated with "Yes" as transmission opt-in information to the healthcare data management device 1. Since transmission opt-in information is associated with each device, each time healthcare data is obtained, the obtained healthcare data may be transmitted to the healthcare data management device 1. Also, device 2 may transmit the healthcare data to the healthcare data management device 1 at a specified time. Further, device 2 transmits the provided opt-in information received from the user to the healthcare data management device 1.

[0067] On the other hand, for example, when a medical institution device 3 generates healthcare data such as a medical record (clinical record) by a doctor's input, further, the healthcare data is generated by obtaining and inputting from a patient (user) whether the generated healthcare data can be transmitted to the healthcare data management device 1. Further, at that time, by obtaining from the user the provided opt-in information indicating whether the healthcare data can be provided to those who want to use the healthcare data and having a doctor or the like input it, the healthcare data associated with the provided opt-in information can be generated and transmitted to the healthcare data management device 1. When the medical institution device 3 obtains healthcare data, it is conceivable that each time, the doctor or the like inputs by obtaining from the user whether the healthcare data can be transmitted and / or provided to generate the healthcare data.

[0068] In step S603, the healthcare data management device 1 provides the healthcare data to those who want to use the healthcare data. It is provided only when the user consents to the provision of the healthcare data. In step S604, the healthcare data management device 1 distributes rewards based on the utilized healthcare data.

[0069] When consent to the provision of healthcare data is confirmed by providing opt-in information and the healthcare data management device 1 provides healthcare data to a person who wishes to use the healthcare data, an electronic contract may be automatically concluded with that person. By this electronic contract, a right to a claim against the intangible healthcare data (the right of three parties, namely the user, the manufacturer, the user, and medical institutions other than the manufacturer, to receive consideration for the use of the data of the person who wishes to use the healthcare data) is generated, and this claim shall be subject to inheritance even in the case of the death, etc. of an individual (user).

[0070] <Schematic image diagram> Figure 7 is a schematic image diagram of the healthcare data management system according to the present embodiment. The user acquires his / her own healthcare data via device 2 (the application of his / her own smartphone) (see (A)). Device 2 transmits the healthcare data to the healthcare data management device 1 (see (B)). The healthcare data management device 1 receives a request for the use of healthcare data (see (C)). The healthcare data management device 1 provides healthcare data to the person who has received the request for use (see (D)). The healthcare data management device 1 receives a reward from the person who wishes to use the healthcare data (see (E)). The healthcare data management device 1 distributes the reward to the user and the manufacturer of the device (see (F)).

[0071] <Device> The healthcare data acquisition unit 21 acquires healthcare data related to the medical and health conditions of the user.

[0072] The user information reception unit 22 receives user information which is information about the user. Examples of user information include the user's name, date of birth, age, gender, underlying diseases, reward receipt information, etc. User information also includes user attributes such as age, gender, and types of underlying diseases.

[0073] The transmission unit 23 transmits the healthcare data acquired by the healthcare data acquisition unit 21, the user ID of the healthcare data, and the device ID of the device that acquired the healthcare data to the healthcare data management device 1. Further, the transmission unit 23 may transmit the user information received by the user information reception unit 22 to the healthcare data management device 1 by associating it with the user ID.

[0074] The personal information anonymization unit 24 performs a process to prevent personal information from being identified in the healthcare data acquired by the healthcare data acquisition unit 21 and / or the user information received by the user information reception unit 22. Specifically, for example, anonymized user information is generated by encrypting or deleting information that can identify personal information such as name, date of birth, and remuneration receipt information from the user information. The transmission unit 23 transmits anonymized user information associating user attributes such as the user's age, gender, and type of disease, for which personal information cannot be identified, with the user ID to the healthcare data reception unit 11.

[0075] The transmission opt-in information reception unit 25 receives transmission opt-in information from the user indicating whether the healthcare data acquired by the healthcare data acquisition unit 21 can be transmitted to the healthcare data reception unit 11. Specifically, the transmission opt-in information reception unit 25 receives transmission opt-in information, which is opt-in information regarding integrating and managing its own healthcare data. When the user agrees to integrate and manage their own healthcare data, the transmission unit 23 transmits the healthcare data to the healthcare data reception unit 11. The transmission opt-in information may be stored in the storage unit of the device 2. For example, by associating the transmission opt-in information for each device ID, the transmission unit 23 can transmit the healthcare data acquired from the device with the device ID based on the transmission opt-in information associated with the device ID. Further, when the user agrees to integrate and manage their own healthcare data, the transmission opt-in information reception unit 25 may receive from the user offer opt-in information indicating whether the healthcare data can be provided to those who want to use the healthcare data.

[0076] On the other hand, when the transmission opt-in information reception unit 25 receives information from the user indicating that the user does not consent to the integration and management of their own healthcare data, the transmission unit 23 does not transmit the user's healthcare data to the healthcare data management device 1. In this case, the user's healthcare data may be stored in the storage unit of the device 2.

[0077] <Medical institution device> The healthcare data generation unit 31 receives information acquired at a medical institution, generates healthcare data, and stores it in the storage unit of the medical institution device 3. Examples of healthcare data generated at a medical institution include CT scans, X-rays, medical records (clinical records), etc. For example, a medical record is generated by receiving information entered by a doctor at a medical institution and stored as healthcare data in the storage unit of the medical institution device 3.

[0078] The user information reception unit 32 receives user information in the same manner as the user information reception unit 22. The user information reception unit 32 may store the received user information in the storage unit of the medical institution device 3.

[0079] The transmission unit 33 transmits the healthcare data acquired by the healthcare data generation unit 31, the user ID of the healthcare data, and the healthcare data holder ID of the holder who holds the healthcare data to the healthcare data management device 1. Examples of the healthcare data holder ID include a value obtained by hashing the insurance medical institution code of a medical institution. In addition, the transmission unit 33 may transmit the user information received by the user information reception unit 32 linked to the user ID to the healthcare data management device 1. Furthermore, when a user ID has been generated in advance by the device 2, the transmission unit 33 reads the user ID into the medical institution device 3 and transmits the healthcare data etc. linked to the read user ID.

[0080] The personal information concealment unit 34 conceals the received information, similar to the personal information concealment unit 24. The transmission unit 33 transmits the anonymized user information, in which the user information has been anonymized, to the healthcare data reception unit 11.

[0081] The transmission opt-in information reception unit 35 receives, from the user, transmission opt-in information indicating whether the healthcare data acquired by the healthcare data generation unit 31 can be transmitted to the healthcare data reception unit 11, similar to the transmission opt-in information reception unit 25.

[0082] <Healthcare Data Management Device> The healthcare data reception unit 11 receives the information transmitted by the transmission unit 23 and / or the transmission unit 33, and stores the received information in the storage unit. For example, the healthcare data reception unit 11 receives healthcare data, the user ID of the user, and the device ID of the device that acquired the healthcare data, associates the user ID and the device ID with the healthcare data, and stores them in the storage unit. In addition to this, the healthcare data reception unit 11 receives healthcare data, the user ID of the user, and the healthcare data holder ID representing the holder who holds the healthcare data, associates the user ID and the healthcare data holder ID with the healthcare data, and stores them in the storage unit.

[0083] The healthcare data reception unit 11 further receives an electronic contract that contracts for the distribution of rewards between the user and / or the healthcare data holder and the person who wants to use the healthcare data, and stores it in the storage unit associated with at least one of the healthcare data, user ID, device ID, or healthcare data holder ID. The electronic contract refers to a contract concluded by recording electronic data (electronic signature, time stamp, etc.) on an electronic file. For example, it is a contract that promises that when the healthcare data of the user and / or the healthcare data held by the healthcare data holder is provided and / or used, the person who provided and / or used the healthcare data pays a reward. Also, the electronic contract may be a contract that promises that when the healthcare data is provided and / or used between the manufacturer of the device used for obtaining the healthcare data and the person who wants to use the healthcare data, the manufacturer of the device used for obtaining the healthcare data is paid a reward. By this contract, the user, the manufacturer who supplies the device, or the healthcare data holder acquires the right to receive the distributed reward. Specifically, the healthcare data reception unit 11 concludes an electronic contract by receiving the electronic signatures of the user and / or the healthcare data holder, etc. who are the parties, and the person who wants to use the healthcare data. In addition to this, the healthcare data reception unit 11 may conclude an electronic contract by receiving an electronic signature (a method in which a third party who is not a party attaches an electronic signature based on the instructions of the party). Furthermore, the healthcare data reception unit 11 may receive an electronic contract with a time stamp attached.

[0084] The provision opt-in information reception unit 12 receives provision opt-in information indicating whether or not to provide healthcare data from the transmission unit 23 and / or the transmission unit 33 to the person who wants to use the healthcare data, and stores the provision opt-in information associated with the healthcare data and / or the user ID in the storage unit. Specifically, the provision opt-in information reception unit 12 receives the provision opt-in information, which is the opt-in information for providing its own healthcare data and receiving a reward, from the person who wants to use the healthcare data.

[0085] The providing unit 13 provides healthcare data to those who want to use the healthcare data. Also, when the storage unit of the healthcare data management device 1 stores the providing opt-in information, based on the providing opt-in information, it provides the healthcare data of the users who consent to the providing. For example, by associating the providing opt-in information for each device ID, the providing unit 13 can provide the healthcare data acquired from the device with the corresponding device ID based on the providing opt-in information associated with the device ID. The providing unit 13 can provide the healthcare data associated with "Yes" as the providing opt-in information.

[0086] The reward distribution unit 14 distributes rewards to the user with the user ID and the manufacturer with the manufacturer ID associated with the provided healthcare data. By associating the manufacturer ID with the device ID as shown in Fig. 5(b), and further associating the user ID and the device ID with the healthcare data as shown in Fig. 4(b), the user ID and the manufacturer ID can be referred to from the healthcare data. Also, the reward distribution unit 14 distributes rewards to the holder represented by the healthcare data holder ID associated with the provided healthcare data. By associating the reward receiving information with the healthcare data as shown in Fig. 4(d), the healthcare data holder ID can be referred to from the healthcare data.

[0087] Specifically, the reward distribution unit 14 calculates the amount to be distributed to each. As a calculation method, a method that increases the distribution amount for the user can be considered. Furthermore, a calculation method that increases the distribution amount according to the user's attributes can also be considered. For example, if a certain user has a rare disease, since it has rarity compared to other healthy users, the distribution amount of the reward calculated by the reward distribution unit 14 for the user with rare attributes will be increased. In this way, for data with high rarity value, methods such as market value calculation can be considered. By the storage unit storing the anonymized user information as shown in Fig. 5(a) linked to the user ID, the reward distribution unit 14 can calculate the amount to be distributed by referring to the user attributes linked to the user ID from the healthcare data. In addition to this, the reward distribution unit 14 may calculate the reward amount to be distributed based on the balance between demand and supply. For example, while a certain infectious disease is suddenly spreading worldwide and the number of infected people in the country is not so large, in order for domestic research institutions, companies, etc. to develop a new drug for the domestic market against this infectious disease, healthcare data of domestic infected people with low supply is required. Furthermore, when many domestic research institutions, companies, etc. want to develop a new drug, the demand for healthcare data of the infected people with this infectious disease is high and the supply is low. In this way, when demand is high and supply is low, the reward distribution unit 14 increases the distribution amount for the user to enhance the motivation of the user to provide healthcare data. Also, it can be considered to increase the reward received from those who want to use healthcare data with high demand and low supply. By doing so, the reward distribution unit 14 can ultimately distribute more rewards to the user.

[0088] The reception unit 15 for requests receives a request for the use of healthcare data including usage restriction information which is information for restricting the use of healthcare data. Various criteria for restricting the use of healthcare data can be considered for the usage restriction information. For example, as the usage restriction information, available period information which is information representing the period during which the healthcare data can be used can be considered. The available period information may be received from a person who wants to use the healthcare data, and is the period during which the healthcare data can be used. The usage fee to be paid by the user may be determined according to the length (period) until that period. In addition to this, as the usage restriction information, available times information which is information representing the number of times the healthcare data can be used can be considered. The available times information may be received from a person who wants to use the healthcare data, and is the number of times the healthcare data can be used (downloaded, etc.). The usage fee to be paid by the user may be determined according to that number of times.

[0089] The provision unit 13 may provide healthcare data with usage restrictions including information for restricting the use of healthcare data under the conditions of the usage restriction information based on the usage request received by the reception unit 15 for requests. For example, when the usage restriction information is available period information, a time invalidation function may be added to the healthcare data so that it cannot be viewed after a certain period. Also, for medical institutions, research institutions, etc. that use the data, the use may be restricted by concluding a confidentiality obligation for the data and a contract for disposal / non - use after the data expiration date. Furthermore, the confidentiality obligation for the data and the contract for disposal / non - use after the data expiration date may be made as an electronic contract, and the information may be stored in the storage unit. In addition to this, when the usage restriction information is available times information, a usage invalidation function may be added to the healthcare data so that it cannot be used after a certain number of uses (downloads, etc.). Also, for medical institutions, research institutions, etc. that use the data, the use may be restricted by concluding a confidentiality obligation for the data and a contract stating that use exceeding the number of data uses is not allowed. Furthermore, the confidentiality obligation for the data and the contract stating that use exceeding the number of data uses is not allowed may be made as an electronic contract, and the information may be stored in the storage unit.

[0090] The reward distributed to users and the like may be paid as a usage fee by those who provided the healthcare data. The usage fee may be determined according to the usage period, or may be a part of the sales (e.g., 3% etc.) based on the findings obtained by those who provided the healthcare data due to such usage. By those who provided the healthcare data (users of the healthcare data) paying a part of the sales as a usage fee (reward), various persons can use the healthcare data. Since users of healthcare data can pay a success reward (usage fee) when they succeed in commercialization using the data, for example, researchers with poor financial strength such as individual research departments can also conduct research using the data.

[0091] As described above, according to the configuration of the present invention, a new technology for distributing rewards by providing healthcare data related to medical care and health can be provided.

Explanation of Signs

[0092] 0 Healthcare data management system 1 Healthcare data management device 11 Healthcare data reception unit 12 Opt-in information reception unit for provision 13 Provision unit 14 Reward distribution unit 15 Usage request reception unit 2 Device 21 Healthcare data acquisition unit 22 User information reception unit 23 Transmission unit 24 Personal information anonymization unit 25 Opt-in information reception unit for transmission 3 Medical institution device 31 Healthcare data generation unit 32 User information reception unit 33 Transmission unit 34 Personal information anonymization unit 35 Opt-in information reception unit for transmission NW Communication network

Claims

1. A healthcare data management system for managing healthcare data related to a user's medical and health conditions, The health care data management system includes a storage unit, a health care data receiving unit, a providing unit, and a reward distribution unit. the storage unit stores a device ID of a device that acquires healthcare data related to the medical care and health of a user in association with a manufacturer ID of a manufacturer that supplies the device; the healthcare data receiving unit receives the healthcare data, a user ID of the user, and a device ID of a device that has acquired the healthcare data, and associates the healthcare data with the user ID and the device ID and stores the healthcare data in the storage unit; the providing unit provides the health care data to a person who wishes to use the health care data; The reward distribution unit distributes rewards to the user of the user ID and the manufacturer of the manufacturer ID associated with the provided healthcare data. Healthcare data management system.

2. The storage unit stores the healthcare data in association with a healthcare data owner ID representing an owner of the healthcare data, The reward distribution unit further distributes the reward to a holder represented by the healthcare data holder ID associated with the provided healthcare data. The healthcare data management system of claim 1 .

3. The health care data management system further includes an opt-in information providing unit, the provision opt-in information receiving unit receives provision opt-in information indicating whether the health care data is to be provided to a person who wishes to use the health care data, and associates the provision opt-in information with the health care data and / or a user ID and stores the information in the storage unit; The providing unit further provides the health care data based on the provision opt-in information. The healthcare data management system of claim 2 .

4. The health care data management system further includes a transmission opt-in information receiving unit, the transmission opt-in information receiving unit receives transmission opt-in information indicating whether or not the healthcare data can be transmitted to the healthcare data receiving unit; The healthcare data management system of claim 3 .

5. The storage unit further stores user attributes, which are attributes of the user, in association with the user ID. The reward distribution unit distributes the reward based on a user attribute associated with the user ID. The healthcare data management system of claim 1 .

6. The health care data management system further includes a usage request receiving unit, the use request receiving unit receives a use request for the health care data including use restriction information that is information restricting use of the health care data; The providing unit further provides restricted health care data including information restricting use of the health care data under conditions included in the usage restriction information based on the use request. The healthcare data management system of claim 1 .

7. The healthcare data receiving unit further receives an electronic contract for a sharing of the reward between the user and / or the owner and a person who wishes to use the healthcare data, and stores the electronic contract in the storage unit in association with at least one of the healthcare data, the user ID, the device ID, or the healthcare data owner ID. The healthcare data management system of claim 2 .

8. A healthcare data management system for managing healthcare data related to a user's medical and health conditions, The health care data management system includes a storage unit, a health care data receiving unit, a providing unit, a providing opt-in information receiving unit, and a reward distribution unit; the storage unit stores a device ID of a device that acquires healthcare data related to the medical care and health of a user in association with a manufacturer ID of a manufacturer that supplies the device, and further stores the healthcare data in association with a healthcare data owner ID representing an owner of the healthcare data; the healthcare data receiving unit receives the healthcare data, the user ID of the user, the device ID of the device that acquired the healthcare data, and the healthcare data owner ID of the healthcare data, links the user ID to information for identifying the healthcare data and stores it in a block chain network system, and further links the device ID and the healthcare data owner ID to information for identifying the healthcare data and stores them in the storage unit or the block chain network system; The provision opt-in information receiving unit receives provision opt-in information indicating whether or not the health care data is to be provided to a person who wishes to use the health care data, and associates the provision opt-in information with information for identifying the health care data and / or a user ID and stores the information in a storage unit or the blockchain network; The providing unit provides the health care data to a person who wishes to use the health care data based on the provision opt-in information, The reward distribution unit distributes rewards to a user of the user ID associated with the provided healthcare data, a manufacturer of the manufacturer ID, and an owner represented by the healthcare data owner ID associated with the provided healthcare data. Healthcare data management system.

9. A healthcare data management method executed by a healthcare data management system that manages healthcare data related to a user's medical care and health, comprising: The health care data management system includes a storage unit, a health care data receiving unit, a providing unit, and a reward distribution unit. a step of storing, in the storage unit, a device ID of a device that acquires healthcare data related to the medical care and health of a user, in association with a manufacturer ID of a manufacturer that supplies the device; the health care data receiving unit receiving the health care data, a user ID of the user, and a device ID of a device that has acquired the health care data, and storing the health care data in the storage unit in association with the user ID and the device ID; a step of the providing unit providing the health care data to a person who wishes to use the health care data; The reward distribution unit distributes rewards to the user of the user ID and the manufacturer of the manufacturer ID associated with the provided healthcare data. Healthcare data management methods.

10. A healthcare data management program for managing healthcare data relating to a user's medical and health conditions, A computer having a storage unit is caused to function as a healthcare data receiving unit, a providing unit, and a reward distributing unit; the storage unit stores a device ID of a device that acquires healthcare data related to the medical care and health of a user in association with a manufacturer ID of a manufacturer that supplies the device; the healthcare data receiving unit receives the healthcare data, a user ID of the user, and a device ID of a device that has acquired the healthcare data, and associates the healthcare data with the user ID and the device ID and stores the healthcare data in the storage unit; the providing unit provides the health care data to a person who wishes to use the health care data; The reward distribution unit distributes rewards to the user of the user ID and the manufacturer of the manufacturer ID associated with the provided healthcare data. Healthcare Data Management Program.

Citation Information

Patent Citations

  • Skin state measurement care system and skin care device

    JP2017027618A

  • Data distribution control device, data distribution control method, and data distribution control program

    JP2020129311A

  • Data management device and data management method

    WO2022185471A1

  • Provision of Personal Data Market

    JP2016511890A