Information management system

Abstract

To provide an information management system which can continuously manage medical data.SOLUTION: An information management system that manages medical data including text data indicating sensing results of biometric information of a user and medical image data of the user captured in a medical institution includes: a first recording unit for recording the text data in a distributed ledger; and a second recording unit for recording the medical image data in a centralized database.SELECTED DRAWING: Figure 2

Description

[Technical Field]

[0001] The present invention relates to an information management system for managing medical data. [Background technology]

[0002] In the medical, pharmaceutical, insurance, and other industries, distributed ledger technologies such as blockchain have been utilized to manage various information about end users who are customers in these industries. For example, Patent Document 1 discloses that medical data such as information obtained by sensing a user's blood pressure, blood sugar level, heart rate, body temperature, etc., electronic medical records, and medical images such as X-ray images, CT images, and MRI images are stored in a blockchain. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Patent No. 6912840 Summary of the Invention [Problem to be solved by the invention]

[0004] However, all past data is stored in the blockchain. Therefore, if medical images are stored in the blockchain as in Patent Document 1, the storage capacity of the computers participating in the blockchain will be quickly consumed. As a result, the system described in Patent Document 1 cannot continuously manage users' medical data.

[0005] The present invention has been made to solve the above-mentioned problems, and has an object to provide an information management system that can continuously manage medical data. [Means for solving the problem]

[0006] The information management system of the present invention is an information management system that manages medical data including text data indicating the sensing results of a user's biometric information and medical image data of the user taken at a medical institution, and is equipped with a first recording unit that records the text data in a distributed ledger and a second recording unit that records the medical image data in a centralized database. [Effects of the Invention]

[0007] In the information management system of the present invention, text data is recorded in a distributed ledger, and medical image data is recorded in a centralized database. In this way, relatively large volumes of medical image data are recorded outside the distributed ledger, so the information management system can continuously manage medical data. [Brief explanation of the drawings]

[0008] [Figure 1] 1 is a schematic configuration diagram showing an information management system according to a first embodiment. [Figure 2] 1 is a functional block diagram showing an information management system according to a first embodiment. [Figure 3] FIG. 2 is a functional block diagram showing a data utilization unit according to the first embodiment. [Figure 4] FIG. 4 is a diagram for explaining the processing of a token management unit according to the first embodiment. [Figure 5] 4 is a flowchart showing an AI diagnostic process in the information management system according to the first embodiment. [Figure 6] 10 is a flowchart showing a token issuing process in the information management system according to the first embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0009] Embodiment 1 FIG. 1 is a schematic configuration diagram showing an information management system 100 according to a first embodiment. The information management system 100 is a system for managing medical data acquired from users. As shown in FIG. 1, the information management system 100 includes an information processing device 1 and a hybrid cloud 2. The information processing device 1 transmits or receives medical data between the hybrid cloud 2 and external devices and systems, such as a user terminal 11, a business operator terminal 12, an electronic medical record system 13, and medical devices 14, which will be described later. Medical data is a general term for data indicating a user's health condition and various data used to estimate the user's health condition. The information management system 100 also has a function of providing economic rebates to users who provide medical data.

[0010] The information processing device 1 is, for example, a server device, and includes one or more processors such as a central processing unit (CPU) or a graphics processing unit (GPU), and a memory. The processor realizes various functions by reading and executing computer programs stored in the memory.

[0011] The hybrid cloud 2 is a storage medium that combines a distributed ledger such as a blockchain 21 and a centralized database 22. The blockchain 21 is a chronological arrangement of data groups, each with a specific data structure called a block. The blockchain 21 functions as a ledger that continuously stores the information recorded in each block. In addition to the information to be stored in the blockchain 21, each block contains information about the previous block and a nonce. The nonce is information used to detect tampering. When a new block is added to the blockchain 21, processing is performed according to a specific consensus algorithm in which multiple nodes 21a participate. Each of the multiple nodes 21a stores a copy of the blockchain 21 through processing according to the consensus algorithm. The blockchain 21 is a so-called private chain, managed, for example, by a pharmaceutical company.

[0012] The centralized database 22 is, for example, a cloud-type database. The centralized database 22 is a so-called scalable server, and can increase its storage area in accordance with an increase in the amount of data to be stored.

[0013] The user terminal 11, the business operator terminal 12, the electronic medical record system 13, and the medical equipment 14 are connected to the information processing device 1 via a network NW such as the Internet or a dedicated network line so as to be able to communicate with the information processing device 1.

[0014] The user terminal 11 is a communication device such as a smartphone, tablet, or personal computer owned by a user. A dedicated application for the user to access the functions of the information management system 100 and an authentication application provided by a business operator are installed on the user terminal 11.

[0015] The business operator terminal 12 is a communication device such as a server device or a personal computer owned by a business operator such as a medical institution, a pharmaceutical company, or an insurance company. The business operator terminal 12 may also be a communication device such as a smartphone, a tablet, or a personal computer owned by an individual or an organization that holds a sporting event or the like. A dedicated application for the business operator to access the functions of the information management system 100 is installed on the business operator terminal 12.

[0016] The electronic medical record system 13 is a system for providing electronic medical records created at a medical institution to an external device. The electronic medical record includes the details of the examination, diagnosis, and prescription medication of the user who is a patient, as well as images taken at the medical institution. The medical device 14 is a device installed at the medical institution, and is, for example, a device for taking X-ray images, CT images, or MRI images of the user's body.

[0017] 2 is a functional block diagram showing the information management system 100 according to Embodiment 1. The operation of the device that records medical data and the recording process of the information processing device 1 will be described with reference to FIG.

[0018] The user terminal 11 transmits event data related to events managed by the authentication application to the information processing device 1. The authentication application is an application that has been authenticated by clearing standards set in advance by the provider of this system. The events managed by the authentication application are intended to manage the user's health. Specifically, the events are intended to contribute to maintaining the user's health or recovering from illness by having the user participate in set behavioral content. For example, wearing a wearable sensor 11a for health status monitoring by a medical institution is an example of such an event.

[0019] If the event involves wearing the wearable sensor 11a, the duration of the event is set to be indefinite. The event data also includes sensing data indicating the sensing results of the user's biological information. The sensing data is measured, for example, by the wearable sensor 11a attached to the user's body. The sensed data is, for example, the patient's respiratory rate, heart rate, and body temperature. The wearable sensor 11a communicates wirelessly with the user terminal 11 and transmits the sensing data to the user terminal 11 at predetermined intervals (for example, every 10 minutes). The user terminal 11, which has received the sensing data from the wearable sensor 11a, transmits the event data (sensing data) to the information processing device 1 at predetermined intervals (for example, every 10 minutes).

[0020] The electronic medical record system 13 transmits electronic medical record data to the information processing device 1. The medical device 14 transmits medical image data such as X-ray images, CT images, and MRI images to the information processing device 1. The medical device 14 uses a common standard for medical images, such as DICOM (Digital Imaging and Communications in Medicine), when transmitting the medical image data.

[0021] The information processing device 1 has a control device 31 and a storage device 32. The control device 31 is a processor, and has a first recording unit 41, a second recording unit 42, a data utilization unit 43, and a token management unit 44. Here, the first recording unit 41 and the second recording unit 42, which are related to the recording of medical data, will be described. The storage device 32 stores various information necessary for the operation of the control device 31, and is, for example, a hard disk, an EEPROM (Electrically Erasable Programmable ROM), a flash memory, or the like.

[0022] The first recording unit 41 acquires event data via the user terminal 11. The event data is expressed as text data. Specifically, the sensing data included in the event data indicates the sensing content and the sensing results using character information and numeric information. Furthermore, the first recording unit 41 acquires data expressed as text data from the electronic medical record data received from the electronic medical record system 13. The first recording unit 41 records the acquired text data in the blockchain 21.

[0023] The second recording unit 42 acquires medical image data expressed as image data from the electronic medical record data received from the electronic medical record system 13. The second recording unit 42 also acquires medical image data received from the medical device 14. The second recording unit 42 records the acquired medical image data in the centralized database 22.

[0024] The sensing data is assigned the terminal ID of the device that performed the sensing, the electronic medical record data is assigned a medical record ID, and the medical image data provided by the medical device is assigned an image ID. The storage device 32 stores the association between the terminal ID, the medical record ID, and the image ID for identifying the user using the information management system 100. The administrator of the information management system 100 can determine whether the association between each ID is correct by checking an audit log, which records the processing on the information management system 100 and the data movement associated with the processing. In this case, the system administrator may use dedicated software for tracking the audit log. The audit log is checked, for example, at predetermined intervals or when an incident occurs. If an error in the association between IDs is discovered, the association is corrected and the impact is confirmed. The first recording unit 41 assigns a user ID to the text data to be recorded. The second recording unit 42 records the user ID together with the medical image data.

[0025] Fig. 3 is a functional block diagram showing a data utilization unit 43 according to the first embodiment. The utilization of data recorded in the hybrid cloud 2 will be described with reference to Fig. 3. Note that Fig. 3 does not show the first recording unit 41, the second recording unit 42, and the token management unit 44 of the control device 31. The data utilization unit 43 transmits medical data to the business operator terminal 12, and as shown in Fig. 3, includes a disclosure setting unit 431, a data providing unit 432, and a diagnosis unit 433.

[0026] The disclosure setting unit 431 sets medical data that is or is not available to the data providing unit 432 and the diagnosis unit 433 based on the disclosure range specified by the user via the user terminal 11. Specifically, when the disclosure setting unit 431 receives the setting of the disclosure range from the user terminal 11, it stores it in the storage device 32 as an access permission list AL. The access permission list AL records, for each business operator identified by, for example, a business operator ID, which type of medical data is or is not accessible to which user ID. The access permission list AL also records, for each user, which type of medical data is or is not accessible to which user ID. The user can specify the disclosure range of their own medical data from a specification screen displayed on the user terminal 11 using a dedicated application for the user.

[0027] In response to a request from the business operator terminal 12, the data providing unit 432 provides medical data within the range of access permitted in the access permission list AL set by the disclosure setting unit 431. An example of a specific access restriction will be described. A request from the business operator terminal 12 includes, for example, request content indicating the medical data requested to be disclosed, as well as a digital signature generated using a secret key (private key). The private key is issued in pair with a public key by a dedicated application for the business operator installed in the business operator terminal 12, and is managed together with the public key on the dedicated application for the business operator. In addition, wallet addresses are stored in the storage device 32 as a correspondence table CL, linked to the business operator ID or user ID. The wallet address is a character string generated using a one-way function for the public key.

[0028] When sending a request, the business operator terminal 12 sends a public key in addition to the request with a digital signature. When the data providing unit 432 receives the request, it uses the digital signature and the public key to verify that the transmitted data has not been tampered with, and then identifies the wallet address based on the public key. The data providing unit 432 then identifies the business operator ID of the business operator using the business operator terminal 12 based on the correspondence table CL, and provides only the medical data for which access is permitted in the access permission list AL. The access permission list AL and the correspondence table CL may be stored in the blockchain 21.

[0029] The diagnosis unit 433 diagnoses the user's health condition using AI (Artificial Intelligence). Hereinafter, a diagnosis using AI will be referred to as AI diagnosis. The diagnosis unit 433 performs AI diagnosis using the trained model LM1 or the trained model LM2 according to the input medical data. The trained model LM1 and the trained model LM2 are stored in advance in the storage device 32, for example.

[0030] First, the trained model LM1 is a trained model that has been trained in advance by machine learning or deep learning using training data to output diagnostic result information that estimates the user's current health condition or the user's future health condition (e.g., 18 hours from now). The trained model LM1 receives text data recorded in the blockchain 21 as input and outputs a diagnostic result of the health condition. The diagnostic result is expressed, for example, by a disease classification code and a degree of urgency. The disease classification code is, for example, the International Classification of Diseases.

[0031] The diagnosis unit 433 inputs text data acquired from the blockchain 21 into the trained model LM1 and acquires a diagnosis result about the user's health condition, which is the output of the trained model LM1. The diagnosis unit 433 then outputs the acquired diagnosis result to the provider terminal 12 used by the medical institution. If the event involves wearing the wearable sensor 11a, the diagnosis unit 433 performs an AI diagnosis of the user's current health condition and the user's future health condition using the trained model every predetermined first hour. The first hour is, for example, a time set to synchronize the timing at which the event data is acquired and recorded with the timing at which the AI ​​diagnosis is performed, and is, for example, 10 minutes.

[0032] However, the diagnosis unit 433 may perform AI diagnosis using the trained model LM1 based on instructions from a medical institution. The text data used to input the trained model LM1 is limited to data that is accessible in the access permission list AL set by the disclosure setting unit 431. The method of access restriction is the same as the method described in relation to the data provision unit 432.

[0033] Second, the trained model LM2 is a trained model that has been trained in advance by deep learning or the like to output diagnostic result information that estimates the user's current health condition. The trained model LM2 is a convolution neural network (CNN). The trained model LM2 receives medical image data recorded in the centralized database 22 as input and outputs a diagnostic result of the health condition. The diagnostic result is expressed, for example, by a disease classification code and a degree of urgency.

[0034] The diagnosis unit 433 inputs medical image data acquired from the centralized database 22 into the trained model LM2 and acquires a diagnosis result on the user's health condition, which is the output of the trained model LM2. The diagnosis unit 433 then outputs the acquired diagnosis result to the operator terminal 12 used by the medical institution. The diagnosis unit 433 performs AI diagnosis using the trained model LM2 based on instructions from the medical institution. The medical image data used to input the trained model LM2 is limited to data that is accessible in the access permission list AL set by the disclosure setting unit 431. The method of access restriction is the same as the method described in relation to the data providing unit 432.

[0035] The business operator terminal 12 receives the requested medical data from the data providing unit 432 of the information management system 100. Furthermore, if the business operator managing the business operator terminal 12 is a medical institution, the business operator terminal 12 receives the diagnosis result of the user's health condition based on the processing of the diagnosis unit 433.

[0036] 4 is a diagram for explaining the processing of the token management unit 44 according to the first embodiment. The operator terminal 15 is a terminal among the business operator terminals 12 that is owned by the operator of the authentication application. When a predetermined condition is satisfied, the operator terminal 15 instructs the token management unit 44 to issue a token. For example, when the event duration is set to be indefinite, as in the case of the wearable sensor 11a, the operator terminal 15 instructs the token management unit 44 to issue a token when a predetermined second time period (for example, one day) has elapsed.

[0037] The token management unit 44 determines whether the user has achieved the event based on the event data recorded in the blockchain 21. If it is determined that the user has achieved the event, the token management unit 44 issues tokens on the blockchain 21. The destination of the tokens is the wallet address of the user who achieved the event. The token management unit 44 determines the amount of tokens to be issued to the user based on the type of event and the achievement status of the event. For example, if the event involves wearing the wearable sensor 11a, the achievement status of the event is evaluated based on the wearing rate of the wearable sensor 11a. The wearing rate of the wearable sensor 11a can be determined by the amount of event data during the second time period. If the wearing rate of the wearable sensor 11a is equal to or greater than a predetermined threshold, the token management unit 44 determines that the event has been achieved. If the wearing rate of the wearable sensor 11a is less than the predetermined threshold, the token management unit 44 determines that the event has not been achieved. The token management unit 44 issues more tokens as the wearing rate of the wearable sensor 11a increases, and conversely, issues less tokens as the wearing rate of the wearable sensor 11a decreases.

[0038] In response to a request from the user terminal 11, the token management unit 44 causes the user terminal 11 to display the tokens recorded in the user's wallet address based on the correspondence table CL and the user ID. In addition, in response to a request from the user terminal 11, the token management unit 44 accepts the use of the tokens recorded in the user's wallet address. An example of a specific process will be described. In addition to the request content, a digital signature generated using a private key is attached to the request from the user terminal 11. The private key is issued in pair with a public key by a dedicated application for the user installed in the user terminal 11, and is managed together with the public key on the dedicated application for the user.

[0039] When sending a request, the user terminal 11 sends a public key in addition to the request with a digital signature. When the data providing unit 432 receives the request, it uses the digital signature and the public key to verify that the transmitted data has not been tampered with, and then identifies a wallet address based on the public key. The data providing unit 432 then identifies the user ID of the user using the user terminal 11 based on the correspondence table CL, and accepts the display and use of tokens for the wallet address whose correspondence is indicated in the correspondence table CL. Note that the access permission list AL may set not only the permission to access the medical data described above, but also the permission to view and use tokens transmitted to the wallet address. In this case, the data providing unit 432 restricts the display and use of tokens for the wallet address based on the settings in the access permission list AL.

[0040] Tokens can be converted into cash using, for example, a known algorithm. The token management unit 44 may convert tokens into cash only when a predetermined amount of tokens has been accumulated. A user can check the tokens recorded in a wallet address and apply for token use from, for example, an application screen displayed on the user terminal 11 using a dedicated user application.

[0041] FIG. 5 is a flowchart showing the AI ​​diagnostic process in the information management system 100 according to the first embodiment. Here, the example illustrates a case in which the event is the wearing of the wearable sensor 11a, and diagnosis is performed using the trained model LM1 with event data (sensing data from the wearable sensor 11a) as text data stored in the blockchain 21 as input. As shown in FIG. 5, first, when the event data is transmitted from the user terminal 11 (step S1), the first recording unit 41 of the information processing device 1 records the event data in the blockchain 21 (step S2). Thereafter, the diagnosis unit 433 determines whether a first time has elapsed (step S3). If the first time has not elapsed (step S3: NO), the diagnosis unit 433 waits for the recording of the event data from the user terminal 11. If the first time has elapsed (step S3: YES), the diagnosis unit 433 inputs the event data into the trained model to obtain a diagnosis result regarding the user's current health state or future health state (step S4). Then, the diagnosis unit 433 outputs the diagnosis result to the provider terminal 12, and the diagnosis result is confirmed by a medical institution (step S5). In this way, by periodically performing AI diagnosis using event data (sensing data from wearable sensor 11a) acquired every hour, medical institutions can monitor the user's health condition and determine whether the user currently has any illnesses or whether they will have any illnesses in the future.

[0042] FIG. 6 is a flowchart showing a token issuance process in the information management system 100 according to the first embodiment. Here, a case where the event is wearing the wearable sensor 11a will be described as an example. As shown in FIG. 6, first, when event data (sensing data of the wearable sensor 11a) is transmitted from the user terminal 11 (step S11), the first recording unit 41 of the information processing device 1 records the event data in the blockchain 21 (step S12). Thereafter, the operator terminal determines whether a second time has elapsed (step S13). If the second time has not elapsed (step S13: NO), the operator terminal waits to issue an instruction to issue a token until the second time has elapsed. If the second time has elapsed (step S13: YES), the operator terminal issues an instruction to issue a token (step S14), and the token is issued by the token issuing unit of the information processing device 1 (step S15).

[0043] In the above description, the event is the wearing of the wearable sensor 11a. However, the administrator of the authentication application can set various other actions as events for the purpose of managing or improving the user's health or conducting surveys and research.

[0044] Specifically, for the purpose of managing the user's health, the execution of a medication plan designated by a medical institution may be set as an event. For the purpose of conducting surveys and research, the execution of a clinical trial plan designated by a medical institution or pharmaceutical company may be set as an event. Furthermore, for the purpose of improving the user's health, activities in a sports club, for example, may be set as an event.

[0045] For example, if the event is the execution of a medication plan specified by a medical institution, the event data transmitted from the user terminal 11 to the information processing device 1 is a medication record consisting of the date and time of medication and the details of medication. The user can input the medication record, for example, from an input screen displayed on the user terminal by an authentication application. The medication record is text data consisting of character information and numeric information. Furthermore, the event continues for a treatment period previously set by the medical institution. In this case, the operator terminal 15 instructs the token management unit 44 to issue a token when a predetermined third time (for example, one day) or the treatment period has elapsed.

[0046] The token management unit 44 calculates the user's medication adherence as a quantitative index. For example, it evaluates the degree to which the recorded medication record deviates from the medication plan. The token management unit 44 determines that the event has been achieved if the index based on medication adherence is equal to or greater than a predetermined threshold. Furthermore, the token management unit 44 determines that the event has not been achieved if the index based on medication adherence is less than a predetermined threshold. The token management unit 44 evaluates the achievement of the event most highly when the medication record completely complies with the medication plan, and evaluates the achievement of the event less highly as the deviation between the medication record and the medication plan increases.

[0047] Furthermore, for example, if the event is the execution of a clinical trial plan designated by a medical institution or pharmaceutical company, the token management unit 44 determines that the event has been achieved when participation in the clinical trial is approved by the medical institution or pharmaceutical company running the clinical trial. Approval for participation in the clinical trial is achieved, for example, when a user applies for participation via an authentication application on the user terminal 11 and the application for participation is approved by the operator terminal 16.

[0048] For example, the token management unit 44 evaluates the achievement status of the event at the end of the clinical trial higher the longer the clinical trial schedule, and conversely, the shorter the clinical trial schedule, the lower the achievement status of the event at the end of the clinical trial.

[0049] For example, if the event is an activity of a sports club, the token management unit 44 determines that the event has been accomplished when the user reads a two-dimensional code such as a QR code (registered trademark, omitted hereafter) generated by the individual or group hosting the club via an authentication application on the user terminal 11. The right to generate a QR code can be obtained by, for example, applying to be the event host in the authentication application. The user terminal 11 that reads the QR code can instruct the token management unit 44 to issue a token using the function of the authentication application.

[0050] For example, the token management unit 44 evaluates the achievement status of the event higher the longer the activity time in the sports club, and conversely, the shorter the activity time in the sports club, the lower the achievement status of the event.

[0051] Note that a user can select from various authentication applications according to his or her interests and install them on the user terminal. Furthermore, multiple types of authentication applications may be installed, or one authentication application may be related to multiple events.

[0052] As described above, in the information management system 100 of the first embodiment, text data is recorded in the distributed ledger, and medical image data is recorded in the centralized database 22. In this way, since medical image data, which has a relatively large capacity, is recorded outside the distributed ledger, the information management system 100 can continuously manage medical data.

[0053] Furthermore, according to the first embodiment, by using the hybrid cloud 2, it is possible to perform AI diagnosis using both text data and medical image data. In this case, regardless of the size of the data, the text data is recorded in the blockchain 21 and the medical image data is recorded in the centralized database 22. Therefore, depending on the type of data used in the AI ​​diagnosis, the diagnosis unit 433 communicates with either the blockchain 21 or the centralized database 22. In other words, when performing AI diagnosis, the diagnosis unit 433 does not need to communicate with both the blockchain 21 and the centralized database 22, and therefore data acquisition and analysis can be performed efficiently.

[0054] Furthermore, according to the first embodiment, by awarding tokens to users who participate in an event, it is possible to motivate users to participate in the event. Therefore, by collecting more medical data to be used for AI analysis, it is possible to perform more accurate AI diagnosis. In addition, even if a large amount of medical data is collected, the information management system 100 can continuously manage the medical data because the medical image data, which has a relatively large capacity, is recorded outside the distributed ledger.

[0055] Furthermore, by collecting more medical data, AI can predict the likelihood of a user becoming ill in the future. Therefore, by cooperating with insurance companies and other parties on the predicted data of a user's likelihood of illness, it will be possible to reduce insurance premiums.

[0056] Furthermore, according to the first embodiment, the access permission list AL sets the authority of the ID of the business or user corresponding to the wallet address identified using a pair of private key and public key issued on a user's or business's dedicated application. This makes it possible to block access from unauthorized third parties to the blockchain 21 and centralized database 22 of the hybrid cloud 2, thereby preventing tampering with recorded information such as medical data or tokens.

[0057] The above is a description of the embodiments of the present invention, but the present invention is not limited to the configurations of the above embodiments and various modifications are possible within the scope of the technical concept. For example, the specific configuration of the information processing device 1 of embodiment 1 is not particularly limited. Each function of the information processing device 1 may be executed by a plurality of servers, personal computers, etc. Furthermore, some of the functions of the information processing device 1 may be realized by software installed in the user terminal 11, medical device 14, and provider terminal 12.

[0058] Furthermore, while users have been compensated with tokens for achieving certain events, other means of economic return may be used. For example, information indicating the status of event achievement may be linked to insurance companies. This may allow for reductions in life insurance premiums, etc. [Explanation of symbols]

[0059] 1 Information processing device, 2 Hybrid cloud, 11 User terminal, 11a Wearable sensor, 12 Operator terminal, 13 Electronic medical record system, 14 Medical device, 15 Operator terminal, 21 Blockchain, 21a Node, 22 Centralized database, 31 Control device, 32 Storage device, 41 First recording unit, 42 Second recording unit, 43 Data usage unit, 44 Token management unit, 100 Information management system, 431 Disclosure setting unit, 432 Data provision unit, 433 Diagnosis unit.

Claims

1. An information management system that manages medical data including text data indicating a sensing result of a user's biological information and medical image data of the user taken at a medical institution, a first recording unit that records the text data in a distributed ledger; a second recording unit for recording the medical image data in a centralized database. Information management system.

2. A token management unit that issues tokens on the distributed ledger when the user achieves an event aimed at managing or improving the user's health or conducting research and studies. The information management system according to claim 1 .

3. The token management unit determines the amount of tokens to be issued to the user based on the type of the event and the achievement status of the event. The information management system according to claim 2 .

4. a diagnosis unit that inputs the medical data recorded in the distributed ledger or the centralized database into a trained model that outputs a diagnosis result about the user's health condition, inputs the medical data acquired from the distributed ledger or the centralized database, acquires a diagnosis result about the user's health condition as an output, and outputs the diagnosis result to a communication device used by the medical institution; 4. The information management system according to claim 1.

5. a disclosure setting unit that receives a setting of the disclosure range of the medical data from the user; 4. The information management system according to claim 1.

Images