Control method, program and control device

A smart contract on a distributed ledger ensures medical treatments align with patient intentions by recording and executing decisions from patient-doctor consultations, addressing verification and accountability issues.

JP7595031B2Active Publication Date: 2024-12-05PANASONIC INTELLECTUAL PROPERTY CORP OF AMERICA
View PDF 6 Cites 0 Cited by

Patent Information

Application Number
JP2021567241
Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
Priority Date
2019-12-27
Filing Date
2020-12-11
Publication Date
2024-12-05
Estimated Expiration
2040-12-11

AI Technical Summary

Technical Problem

Existing methods fail to verify whether medical treatments are decided and implemented in consideration of a patient's wishes when they are unable to express their intentions, leading to uncertainty and accountability issues.

Method used

A control method using a smart contract on a distributed ledger that records and executes medical treatment decisions based on patient-doctor consultations, incorporating biological information and diagnosis results to ensure treatments align with the patient's prior intentions.

Benefits of technology

Ensures that medical treatments are reliably verified to have been decided and implemented in accordance with the patient's expressed intentions, enhancing transparency and accountability.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007595031000001
    Figure 0007595031000001
  • Figure 0007595031000002
    Figure 0007595031000002
  • Figure 0007595031000003
    Figure 0007595031000003
Patent Text Reader

Abstract

A control method according to the present invention is to be used in a system. A smart contract, which has been transformed into a program so as to be able to execute medical treatment determination acquired as a result of consent between a patient and a doctor, is stored in a distributed register. The method involves: acquiring (S205) condition transaction data that includes biological information of a patient obtained from a sensor; acquiring (S210) opinion transaction data including information about a doctor's diagnosis result regarding the biological information; and executing (S211, S212) the smart contract on the basis of the diagnosis result and the biological information included in the acquired condition transaction data and the opinion transaction data, and outputting medical treatment proposal information that is acquired by executing the smart contract and that is about a medical treatment to be performed for the patient.
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] The present disclosure relates to a control method, a program, and a control device using blockchain technology. [Background technology]

[0002] For example, Patent Document 1 proposes a medical decision support system that assigns an evaluation to known medical facts accumulated in a server and selects the most effective medical proposal based on the evaluation.

[0003] Here, a medical fact may be, for example, a medical diagnosis, a medical finding, a medication, a medical history, an ancillary suggestion, a laboratory evaluation, a medical validity, a medical conclusion, a medical procedure, a medical instruction, a medical report, a medical question, a symptom, a group of symptoms, a text block, or a nutritional recommendation. A medical fact may also be, for example, an exercise suggestion, a care suggestion, a rehabilitation suggestion, a genetic aspect, a histological finding, a physiological process, a pathophysiological process finding, a quality indicator, a treatment recommendation, a therapy recommendation, a process suggestion, a medical research suggestion, a patient questionnaire, or a specialized questionnaire survey. A medical fact may be any combination of these.

[0004] Furthermore, for example, Patent Document 2 proposes a method for sharing and managing medical information, including a patient's prior declaration of intent, via the Internet while taking into consideration reliability and privacy.

[0005] However, the methods proposed in the above Patent Documents 1 and 2 only allow medical treatment to be determined under circumstances in which the patient himself / herself is able to express his / her will. In other words, under circumstances in which the patient is unable to express his / her will, medical treatment cannot be determined taking into account the patient's will.

[0006] In response to this, there is a method of using a living will or POLST, which reflects the patient's prior will, to determine medical treatment that takes into account the patient's will in a situation where the patient is unable to express their will themselves (for example, Non-Patent Document 1). Here, POLST is an abbreviation for Physician Orders for Life-Sustaining Treatment. POLST is a written instruction by a doctor regarding medical treatment, including resuscitation treatment, in the final stage of a patient's life, and includes a DNAR (Do Not Attempt Resuscitate), which is a do-not-attempt resuscitate instruction. Then, a doctor can make a decision on the medical treatment to be performed, such as whether or not to perform cardiopulmonary resuscitation, for a patient facing a "life-threatening disease" based on the POLST. Note that if there is a special instruction in the DNAR not to perform cardiopulmonary resuscitation when the heart or breathing stops due to terminal cancer, the doctor can omit cardiopulmonary resuscitation in accordance with the DNAR. [Prior art documents] [Patent documents]

[0007] [Patent Document 1] Special Publication No. 2016-516231 [Patent Document 2] Special Publication No. 2015-507282 [Non-patent literature]

[0008] [Non-Patent Document 1] "Physician Orders for Life-sustaining Treatment (POLST) and Do Not Attempt Resuscitation (DNAR) Orders" https: / / www.jsicm.org / pdf / DNAR20161216_kangae_02.pdf (2020 / 03 / 13) Summary of the Invention [Problem to be solved by the invention]

[0009] However, even if the POLST disclosed in Non-Patent Document 1 is used, it is not possible to verify whether medical treatment has been decided and carried out taking into account the patient's wishes in a situation where the patient is unable to express his or her own wishes. In other words, when the patient is actually in a situation where he or she is unable to express his or her wishes, it is not possible to verify that the patient's wishes reflected in advance in the POLST or the like have been taken into account in the actual medical treatment.

[0010] For this reason, in such circumstances, if medical treatment is performed that ignores the patient's wishes, it is impossible to verify its appropriateness, nor is it clear who is responsible for the treatment.

[0011] The present disclosure has been made in consideration of the above-mentioned circumstances, and aims to provide a control method, program, and control device that can verify whether medical procedures have been decided and carried out taking into account the patients' prior wishes. [Means for solving the problem]

[0012] In order to achieve the above-mentioned objective, the control method of the present disclosure is a control method in a system, in which a smart contract programmed to be able to execute a medical treatment decision obtained as a result of discussion between a patient and a doctor is stored in a distributed ledger, the control method acquires first transaction data including biometric information of the patient obtained from a sensor, acquires second transaction data including information regarding the doctor's diagnosis result for the biometric information, executes the smart contract based on the biometric information and the diagnosis result included in the acquired first transaction data and second transaction data, and outputs medical suggestion information regarding the medical treatment to be performed on the patient obtained by executing the smart contract.

[0013] These comprehensive or specific aspects may be realized by a system, an integrated circuit, a computer program, or a recording medium such as a computer-readable CD-ROM, or may be realized by any combination of a system, a method, an integrated circuit, a computer program, and a recording medium. Effect of the Invention

[0014] The control method and the like disclosed herein aim to provide a control method, program, and control device that can verify whether medical procedures have been decided and carried out taking into account the patient's prior expressed wishes. [Brief description of the drawings]

[0015] [Figure 1] FIG. 1 is a diagram showing the overall configuration of a medical treatment management system according to an embodiment. [Diagram 2] FIG. 2 is a block diagram illustrating an example of a configuration of a patient terminal according to the embodiment. [Diagram 3] FIG. 3 is an explanatory diagram showing the data structure of a blockchain. [Figure 4] FIG. 4 is a block diagram illustrating an example of a configuration of a doctor terminal according to an embodiment. [Diagram 5] FIG. 5 is a diagram illustrating an address configuration in a blockchain network stored in a distributed ledger according to an embodiment. [Figure 6] FIG. 6 is a diagram conceptually showing a data structure of the third transaction data according to the embodiment. [Figure 7] FIG. 7 is a diagram conceptually illustrating a data structure of the physical transaction data according to the embodiment. [Figure 8] FIG. 8 is a diagram conceptually showing a data structure of opinion transaction data according to an embodiment. [Figure 9] FIG. 9 is a diagram conceptually showing an algorithm of the medical decision support smart according to the embodiment. [Figure 10]FIG. 10 is a diagram conceptually illustrating an algorithm of the medical decision support smart contract according to the first embodiment. [Figure 11] FIG. 11 is a diagram conceptually illustrating an algorithm of the medical decision support smart contract according to the second embodiment. [Figure 12] FIG. 12 is a block diagram illustrating an example of a configuration of a server device according to the embodiment. As illustrated in FIG. [Figure 13A] FIG. 13A is a diagram showing an overview of the operation of the medical treatment management system according to the embodiment up to storing a patient's declaration of intent in a distributed ledger. [Figure 13B] Figure 13B is a diagram showing an overview of the operations up to verifiably recording whether medical procedures have been decided and implemented in accordance with the patient's wishes, which are stored in the distributed ledger of the medical procedure management system of this embodiment. [Figure 14] FIG. 14 is a diagram showing a sequence from generation of a medical decision support smart contract to operation by the medical treatment management system according to the embodiment. [Figure 15] FIG. 15 is a diagram showing a sequence from when a medical decision support smart contract according to an embodiment is executed to when the results of a medical procedure are recorded. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0016] A control method of one embodiment of the present disclosure is a control method in a system, in which a smart contract programmed to execute a medical treatment decision obtained as a result of discussion between a patient and a doctor is stored in a distributed ledger, the control method acquires first transaction data including biometric information of the patient obtained from a sensor, acquires second transaction data including information regarding the doctor's diagnosis result for the biometric information, executes the smart contract based on the biometric information and the diagnosis result included in the acquired first transaction data and second transaction data, and outputs medical suggestion information regarding the medical treatment to be performed on the patient obtained by executing the smart contract.

[0017] In this way, a smart contract that takes into account the patient's prior wishes and uniquely determines the medical treatment proposal based on the patient's condition, etc., can be made to propose medical treatment in a situation where the patient is unable to express their own wishes. This makes it possible to compare the medical treatment actually performed with the medical treatment proposed by the smart contract at a later date. This makes it possible to verify whether the medical treatment was decided and performed while taking into account the patient's prior wishes.

[0018] In addition, for example, before acquiring the first transaction data and the second transaction data, third transaction data including the smart contract generated based on the medical treatment decision obtained as a result of consultation between the patient and the doctor may be acquired, and a block including the third transaction data may be stored in the distributed ledger.

[0019] This allows the smart contract to be generated and stored in the distributed ledger, taking into account the patient's prior wishes.

[0020] Here, for example, the third transaction data may include a signature for verifying the authenticity of the third transaction data.

[0021] Also, for example, the smart contract may be a program having a description including a conditional expression for executing the medical treatment decision using the first transaction data and the second transaction data as input values.

[0022] Also, for example, the first transaction data and the second transaction data include a contract address indicating an address of the smart contract.

[0023] Furthermore, for example, fourth transaction data including medical procedure result information, which is information regarding the medical procedure performed by the doctor on the patient, may be acquired, and the medical procedure result information may be linked to the medical suggestion information and stored in the distributed ledger.

[0024] This allows for a more reliable comparison of the medical procedures actually performed with those proposed by the smart contract by storing the actual medical procedures in a distributed ledger, thereby making it possible to verify whether the medical procedures were decided and performed in accordance with the patients' prior wishes.

[0025] Here, for example, the biological information may be information indicating cardiac arrest, the diagnosis result may be information indicating no trauma, and the medical suggestion information may be information indicating that the medical procedure to be performed on the patient is cardiopulmonary resuscitation.

[0026] The distributed ledger may also be built on a blockchain platform.

[0027] Moreover, a control device according to one embodiment of the present disclosure is a control device having a processor, a memory, and a distributed ledger, wherein the distributed ledger stores a smart contract programmed to execute a medical treatment decision obtained as a result of discussion between a patient and a doctor, the processor acquires first transaction data including biometric information of the patient obtained from a sensor, the processor acquires second transaction data including information regarding the doctor's diagnosis result for the biometric information, the processor uses the memory to execute the smart contract based on the biometric information and the diagnosis result included in the acquired first transaction data and the second transaction data, and the processor outputs medical suggestion information regarding the medical treatment to be performed on the patient obtained by executing the smart contract.

[0028] Hereinafter, the embodiments will be described with reference to the drawings. Note that each of the embodiments described below shows a preferred specific example of the present disclosure. In other words, the numerical values, shapes, materials, components, arrangement and connection forms of the components, steps, and order of steps shown in the following embodiments are merely examples and are not intended to limit the present disclosure. The present disclosure is specified based on the description of the claims. Therefore, among the components in the following embodiments, components that are not described in the independent claims showing the highest concept of the present disclosure are described as components that are not necessarily required to achieve the objectives of the present disclosure but constitute a more preferred form.

[0029] (Embodiment) First, the system configuration of the present disclosure will be described.

[0030] [1. System configuration] The medical treatment management system disclosed herein records the patient's wishes in a highly reliable and transparent distributed ledger built on a blockchain platform, and has a smart contract on the blockchain autonomously determine a medical treatment that takes into account the patient's prior wishes and output it as medical proposal information. In addition, the medical treatment management system disclosed herein links the determined medical treatment with the medical procedure performed by the doctor and records it in the distributed ledger. This makes it possible to verify with high reliability whether the doctor decided and performed the medical treatment that took into account the patient's prior wishes.

[0031] Hereinafter, a medical treatment management system according to an embodiment will be described with reference to the drawings.

[0032] [1.1 Overall configuration of medical treatment management system 1] FIG. 1 is a diagram showing the overall configuration of a medical treatment management system 1 according to the present embodiment.

[0033] 1, the medical treatment management system 1 includes one or more patient terminals 10, one or more doctor terminals 20, and one or more server devices 30. These are connected via a communication network 40.

[0034] One or more patient terminals 10, one or more doctor terminals 20, and one or more server devices 30 are connected to a storage device having a distributed ledger in which transaction data and blocks of the blockchain are electronically recorded. One or more patient terminals 10, one or more doctor terminals 20, and one or more server devices 30 may be connected to the storage device via a communication network 40, or may be provided internally as a storage unit.

[0035] In this way, one or more patient terminals 10, one or more doctor terminals 20, and one or more server devices 30 form a blockchain network.

[0036] [1.2 Configuration of patient terminal 10] The patient terminal 10 is, for example, a terminal such as a PC (Personal Computer) used by a patient, but is not limited to this. The patient terminal 10 may be a server, not limited to a terminal, as long as it has a distributed ledger, can configure a blockchain network, and can be used by a patient or can directly communicate with a patient.

[0037] FIG. 2 is a block diagram showing an example of the configuration of the patient terminal 10 according to the present embodiment.

[0038] As shown in FIG. 2, the patient terminal 10 includes a communication unit 101, a sensor information acquisition unit 102, a smart contract generation unit 103, a blockchain control unit 104, a display unit 105, and a memory unit 106.

[0039] <Communication Department 101> The communication unit 101 communicates with the doctor terminal 20 and the server device 30 via the communication network 40. The communication unit 101 also communicates with input devices such as a keyboard and a microphone used by the patient.

[0040] The communication unit 101 acquires, for example, text data and voice data input by operation by the patient, and acquires data input by the patient interactively with the display unit 105 .

[0041] <Sensor information acquisition unit 102> The sensor information acquisition unit 102 acquires sensor information, which is information from a group of sensors connected to the patient terminal 10, via the communication unit 101. Here, the sensor information is information used to indicate the condition of a patient and is information indicating medical facts. The sensor information may be biological information of the patient obtained from the group of sensors. The biological information indicates vital data of the patient, such as the patient's heart rate, blood glucose level, cognitive function evaluation, and respiratory rate.

[0042] The sensor information acquisition unit 102 transmits the acquired sensor information to the smart contract generation unit 103, the blockchain control unit 104, the display unit 105, or the memory unit 106 depending on the content of the sensor information.

[0043] <Smart contract generation unit 103> The smart contract generation unit 103 generates a medical decision support smart contract based on the medical treatment decision obtained as a result of the consultation between the patient and the doctor. Here, the smart contract is a program that can be executed on the blockchain and returns a unique output for a unique input value. The medical decision support smart contract is a smart contract that is programmed to be executable based on the medical treatment decision obtained as a result of the consultation between the patient and the doctor. When executed, the medical decision support smart contract can output medical proposal information regarding the medical treatment to be performed on the patient.

[0044] In this embodiment, the smart contract generation unit 103 generates a medical decision support smart contract by programming an algorithm of the medical decision support smart contract using data such as the medical proposal subset acquired via the communication unit 101. Then, the smart contract generation unit 103 transmits the generated medical decision support smart contract to the blockchain control unit 104. Note that the medical proposal subset is data indicating a combination of medical procedures that can be proposed.

[0045] Here, we describe an example of a method for generating a medical decision support smart contract.

[0046] First, the smart contract generation unit 103 acquires data such as a medical proposal subset from the server device 30 via the communication unit 101. Next, the smart contract generation unit 103 acquires data indicating the contents of the medical decision support smart contract input by the patient interactively with the display unit 105 while the patient and the doctor are discussing with each other, and generates a medical decision support smart contract based on the medical proposal subset. More specifically, the smart contract generation unit 103 derives a conditional expression for making a judgment on the input value, a constant constituting the conditional expression, and variables and constants corresponding to the input and output results of the conditional expression, using the derived conditional expression, variables, and constants as inputs, and edits them into a program that is executable on the blockchain and returns a unique output for a unique input value, thereby generating a medical decision support smart contract.

[0047] In this embodiment, the smart contract generation unit 103 generates a binary program including a conditional expression written in Solidity, which is a script language executable on an Ethereum-based blockchain, and an access method to the derived constants and variables. The smart contract generation unit 103 then transmits the generated binary program to the blockchain control unit 104 as a medical decision support smart contract.

[0048] <Blockchain control section 104> The blockchain control unit 104 controls the formation of a blockchain network, the generation of transaction data, the synchronization of distributed ledgers, and the execution of a consensus algorithm. The blockchain control unit 104 also controls the storage of each control result in the storage unit 106.

[0049] In this embodiment, the blockchain control unit 104 generates transaction data including sensor information such as biological information of a patient obtained from a sensor received from the sensor information acquisition unit 102. Also, for example, the blockchain control unit 104 generates transaction data including a medical decision support smart contract generated by the smart contract generation unit 103. In the following, transaction data including sensor information such as biological information of a patient obtained from a sensor is referred to as transaction data indicating a patient's condition or condition transaction data. Also, transaction data including a medical decision support smart contract is referred to as third transaction data. When generating condition transaction data, the blockchain control unit 104 includes a contract address indicating the address of the medical decision support smart contract in the destination address. Details will be described later.

[0050] Here, the data structure of the blockchain will be described.

[0051] FIG. 3 is an explanatory diagram showing the data structure of a blockchain.

[0052] A blockchain is a set of blocks, which are units of record, connected in a chain. Each block contains multiple transaction data and the hash value of the immediately preceding block. Specifically, block B2 contains the hash value of the previous block B1. A hash value calculated from the multiple transaction data contained in block B2 and the hash value of block B1 is included in block B3 as the hash value of block B2. In this way, by connecting blocks in a chain while including the contents of the previous block as a hash value, tampering with the connected transaction data is effectively prevented.

[0053] If past transaction data is changed, the block's hash value will be different from before the change, and in order to make the altered block appear correct, all blocks after it would have to be recreated, which is a very difficult task in reality.

[0054] Next, we will explain the example of choosing Ethereum, which is based on the implementation of smart contracts, as the blockchain platform.

[0055] The blockchain control unit 104 controls the formation of a blockchain network by establishing peer-to-peer communication in accordance with a specified blockchain protocol.

[0056] The blockchain control unit 104 also receives binary data of the medical decision support smart contract generated by the smart contract generation unit 103, and generates transaction data including this as content data. The blockchain control unit 104 also receives sensor information generated by the smart contract generation unit 103, and generates transaction data including this. Note that, although details will be described later, when generating transaction data, the blockchain control unit 104 includes the blockchain address linked to the patient terminal 10 as the destination address. Then, the blockchain control unit 104 stores (records) the generated transaction data in the distributed ledger of the patient terminal 10.

[0057] In this way, the blockchain control unit 104 controls the generation of transaction data. The generated transaction data is transmitted and received between addresses in the blockchain network. The generated transaction data further includes a signature unique to the blockchain control unit 104 or the patient terminal 10.

[0058] In addition, the blockchain control unit 104 executes a consensus algorithm to reach an agreement on the validity of the generated transaction data, and when the validity is agreed upon, records a block including the transaction data in the distributed ledger. In this embodiment, the blockchain control unit 104 executes the consensus algorithm to confirm incorporation into a block, and records the block in the distributed ledger.

[0059] Incidentally, in Ethereum and other systems, a smart contract is a code that is deployed on the blockchain. For this reason, the transaction data, including the binary data of the smart contract, can be sent to a null address to deploy the smart contract. Deploying a smart contract means deploying the smart contract program, which is the actual form of the smart contract, on the blockchain network. Meanwhile, transaction data, including information for executing the smart contract or information to be left as history, is broadcast and stored in the distributed ledger via a consensus algorithm.

[0060] In this embodiment, the blockchain control unit 104 broadcasts the newly generated transaction data to the doctor terminal 20 and the server device 30, which are other nodes constituting the blockchain network. Then, the blockchain control unit 104 synchronizes with all the nodes constituting the blockchain network and stores the newly generated transaction data in the distributed ledger. In addition, the blockchain control unit 104 executes a consensus algorithm between all the nodes constituting the blockchain network to determine whether to incorporate the newly generated transaction data into a block and confirm it.

[0061] In this way, the blockchain control unit 104 stores a block including the third transaction data in the distributed ledger, and the third transaction data includes a signature to prove the authenticity of the third transaction data.

[0062] <Display section 105> The display unit 105 acquires text data and voice data input by the patient's operation, etc., and interactively displays the data input by the patient. The display unit 105 may further function as an interface equipped with an input device (not shown).

[0063] In addition, the display unit 105 uses data such as the medical suggestion subset acquired via the communication unit 101 to display questions, etc., to help the patient decide in advance, in consultation with the doctor, what their wishes are regarding medical treatment in a situation where the patient is unable to express their wishes.

[0064] Furthermore, the display unit 105 displays the medical treatment obtained as a result of a consultation between the patient and the doctor, and displays the contents of the medical decision support smart contract generated by the smart contract generation unit 103 in a form that can be understood by users such as patients. Note that the display unit 105 is not limited to visual display, and may convey the display contents to the user audibly or tactilely.

[0065] <Storage section 106> The memory unit 106 stores the sensor information acquired by the sensor information acquisition unit 102, the medical decision support smart contract generated by the smart contract generation unit 103, text data input by the patient's operation, voice data, and data input by the patient.

[0066] 1 having a distributed ledger. In this case, a distributed ledger area is partitioned in the storage unit 106, and the distributed ledger is stored in the distributed ledger area.

[0067] [1.3 Configuration of doctor terminal 20] The doctor terminal 20 is, for example, a terminal such as a PC used by a doctor, but is not limited to this. The doctor terminal 20 may be a server, not limited to a terminal, as long as it has a distributed ledger, can configure a blockchain network, and can be used by a doctor or can directly communicate with a doctor.

[0068] FIG. 4 is a block diagram showing an example of the configuration of the doctor terminal 20 according to the present embodiment.

[0069] As shown in FIG. 4, the doctor terminal 20 includes a communication unit 201, a doctor's opinion generating unit 202, a blockchain control unit 203, a display unit 204, and a storage unit 205.

[0070] <Communications Department 201> The communication unit 201 communicates with the patient terminal 10 and the server device 30 via the communication network 40. The communication unit 201 also communicates with input devices such as a keyboard and a microphone used by a doctor.

[0071] The communication unit 201 acquires, for example, text data and voice data input by operation by the doctor, and acquires data input by the doctor interactively with the display unit 204 .

[0072] <Doctor's opinion generating unit 202> The doctor's opinion generating unit 202 generates a doctor's opinion based on the data input by the doctor's operation, etc. The doctor's diagnosis includes the above-mentioned medical facts.

[0073] In this embodiment, the doctor's opinion generating unit 202 generates information on the doctor's diagnosis result for the patient's biological information obtained from the sensor. More specifically, the doctor's opinion generating unit 202 generates the doctor's diagnosis result for the biological information acquired from the patient terminal 10. The doctor's opinion generating unit 202 converts the generated doctor's diagnosis result into a format described in numbers or equal signs in accordance with the medical decision support smart contract. The doctor's opinion generating unit 202 transmits the converted doctor's diagnosis result to the blockchain control unit 203 as information on the doctor's diagnosis result.

[0074] Furthermore, the doctor's opinion generating unit 202 generates medical procedure result information, which is information on the medical procedure performed by the doctor on the patient, as the doctor's opinion, based on data input by the doctor's operation or the like.

[0075] <Blockchain Control Unit 203> The blockchain control unit 203 controls the formation of a blockchain network, the generation of transaction data, the synchronization of distributed ledgers, and the execution of a consensus algorithm. The blockchain control unit 203 also controls the storage of each control result in the storage unit 205.

[0076] In this embodiment, the blockchain control unit 203 generates transaction data including information on the doctor's diagnosis result generated by the doctor's opinion generating unit 202. Also, for example, the blockchain control unit 203 generates transaction data including medical procedure result information generated by the smart contract generating unit 103. In the following, transaction data including information on the doctor's diagnosis result is referred to as transaction data indicating the doctor's opinion or opinion transaction data. Also, transaction data including medical procedure result information is referred to as medical procedure implementation result transaction data. When generating opinion transaction data, the blockchain control unit 203 includes a contract address indicating the address of the medical decision support smart contract in the destination address. Details will be described later.

[0077] Other controls by the blockchain control unit 203 are similar to those of the blockchain control unit 104 in the patient terminal 10, so detailed explanations will be omitted here.

[0078] <Display section 204> The display unit 204 acquires text data and voice data input by the doctor's operation, etc., and interactively displays the data input by the doctor. The display unit 204 may further function as an interface equipped with an input device (not shown).

[0079] Furthermore, the display unit 204 may display questions displayed by the patient terminal 10 in synchronization with the patient terminal 10, using data such as the medical suggestion subset acquired via the communication unit 101. As described above, the questions displayed by the patient terminal 10 are questions to the patient to determine the patient's prior expression of intent regarding medical treatment in a situation in which the patient is unable to express his or her intent.

[0080] <Storage section 205> The storage unit 205 stores the doctor's opinion generated by the doctor's opinion generating unit 202, text data input by the doctor's operation or the like, voice data, and data input by the patient.

[0081] 1 having a distributed ledger. In this case, a distributed ledger area is partitioned in the storage unit 205, and the distributed ledger is stored in the distributed ledger area.

[0082] [1.4 Address structure in blockchain network] FIG. 5 is a diagram showing an address configuration in a blockchain network held in a distributed ledger according to this embodiment.

[0083] A blockchain address is information given to each node constituting a blockchain network, and is information that can uniquely identify the node. The patient address 11 shown in FIG. 5 is a blockchain address given to the patient terminal 10. Similarly, the doctor address 21 shown in FIG. 5 is a blockchain address given to the doctor terminal 20, and the server address 31 is a blockchain address given to the server device 30.

[0084] On the other hand, the medical decision support contract address 32 shown in Fig. 5 is a unique address given to the medical decision support smart contract deployed on the blockchain network. If the unique address can be referenced, the medical decision support smart contract can be executed.

[0085] In addition, the address configuration shown in Figure 5 indicates that the patient address 11, doctor address 21, server address 31, and medical decision support contract address 32 are stored in the distributed ledger and can be used when generating transaction data.

[0086] [1.5 Data structure of transaction data] In this embodiment, the transaction data includes a destination address, a source address, and content data, but may take a different form as long as it includes this information.

[0087] 6 is a diagram conceptually illustrating the data structure of the third transaction data according to the present embodiment. The third transaction data is transaction data including a medical decision support smart contract, and is generated by the blockchain control unit 104 of the patient terminal 10. As described above, the medical decision support smart contract is a program having a description including a condition formula for executing a medical treatment decision using the condition transaction data and the opinion transaction data as input values.

[0088] As shown in FIG. 6, the third transaction data includes a destination address, content data, and a source address. The destination address and source address both include the patient address 11. This is because in Ethereum and the like, transaction data needs to be sent to a null address to deploy a smart contract. The content data also includes a medical decision support smart contract binary program, i.e., a medical decision support smart contract generated as a binarized program. Note that the content data does not have to be a binary program as long as it is a programmed medical decision support smart contract.

[0089] The patient terminal 10 generates the third transaction data having such a data structure and transmits it to itself, thereby deploying the medical decision support smart contract on the blockchain network. Note that the content data of the third transaction data further includes a signature (not shown) for verifying the authenticity of the first transaction data.

[0090] Next, we will explain the data structure of the transaction data that is input to the medical decision support smart contract, i.e., the transaction data indicating the patient's condition and the transaction data indicating the doctor's opinion. Hereinafter, the transaction data indicating the patient's condition and the transaction data indicating the doctor's opinion will be referred to as condition transaction data and opinion transaction data.

[0091] FIG. 7 is a diagram conceptually showing the data structure of the physical transaction data according to the present embodiment.

[0092] As shown in FIG. 7, the condition transaction data includes a destination address, content data, and a source address. The destination address includes a medical decision support contract address 32, and the source address includes a patient address 11. The content data includes information indicating the patient's condition and a signature of the patient terminal 10, which is the source. The information indicating the patient's condition is, for example, a medical fact indicating the patient's condition, such as the patient's vital data. The signature is used to prove the authenticity of the condition transaction data. The signature may be, for example, a digest value indicating the patient's condition encrypted with a private key. In this case, the public key may be stored separately in a distributed ledger and made public.

[0093] The patient terminal 10 generates condition transaction data with such a data structure and transmits it to the medical decision support contract address 32.

[0094] FIG. 8 is a diagram conceptually showing the data structure of the opinion transaction data according to the present embodiment.

[0095] As shown in FIG. 8, the opinion transaction data includes a destination address, content data, and a source address. The destination address includes a medical decision support contract address 32, and the source address includes a doctor address 21. The content data includes information indicating the doctor's opinion and a signature of the doctor terminal 20, which is the sender. The information indicating the doctor's opinion is, for example, the doctor's diagnosis result on the patient's condition, and may further include an opinion for executing the medical decision support smart contract on the medical fact indicating the patient's condition. The signature is used to prove the authenticity of the opinion transaction data. The signature may be, for example, a digest value of a value indicating the doctor's opinion encrypted with a private key. In this case, the public key may be stored separately in a distributed ledger and made public.

[0096] The doctor terminal 20 generates opinion transaction data of such a data structure and transmits it to the medical decision support contract address 32.

[0097] The medical decision support smart contract can be executed by sending such condition transaction data and opinion transaction data to the medical decision support contract address 32. This allows the medical decision support smart contract to output medical suggestion transaction data including medical suggestion information regarding the medical procedure to be performed on the patient.

[0098] Although not shown, the medical suggestion transaction data includes a destination address, content data, and a sender address. The content data includes medical suggestion information, and the destination address includes a doctor address 21. The sender address includes a medical decision support contract address 32 or a blockchain address of a node that executed the medical decision support smart contract.

[0099] Next, an overview of the algorithm of the medical decision support smart contract according to this embodiment will be described.

[0100] [1.6 Medical decision support smart contract algorithm] FIG. 9 is a diagram conceptually showing an algorithm of the medical decision support smart system according to this embodiment.

[0101] As described above, the medical decision support smart contract is a smart contract programmed to execute a medical treatment decision obtained as a result of consultation between a patient and a doctor. When executed, medical proposal information regarding the medical treatment to be performed on the patient is output. Here, executing a medical treatment decision obtained as a result of consultation between a patient and a doctor means determining and outputting a medical treatment to be performed on a patient taking into consideration the patient's prior will in a situation where the patient himself / herself is unable to express his / her will. In other words, the medical decision support smart contract is a smart contract programmed to determine a medical treatment to be performed on a patient taking into consideration the patient's prior will in a situation where the patient himself / herself is unable to express his / her will, and output it as medical proposal information when executed.

[0102] More specifically, as shown in FIG. 9, the algorithm of the medical decision support smart contract includes condition branches such as those shown in conditions 0 to 2, and variables / constants indicating combinations of medical procedures such as those shown in medical proposal subsets 1-1 to 2-2 selected by the conditions. The algorithm of the medical decision support smart contract also includes a conditional expression in which condition transaction data indicating the condition of a patient in a situation where the patient cannot express his / her own will and opinion transaction data indicating the doctor's opinion thereon are input. Furthermore, the algorithm of the medical decision support smart contract also includes a conditional expression in which the validity of the signature included in these transaction data is confirmed and the like is advanced to the above conditions 0 to 2. The algorithm of the medical decision support smart contract also includes a conditional expression in which medical proposal information regarding the medical procedures to be performed on the patient is derived as one output when these transaction data are input.

[0103] In other words, as shown in Fig. 9, the algorithm of the medical decision support smart contract includes an input step of the above two pieces of transaction data, and a signature verification step of verifying the signatures included in each of the above two pieces of transaction data. In addition, the algorithm of the medical decision support smart contract includes a selection step of a medical suggestion subset based on three condition branches represented by conditions 0 to 2, and an output step of medical suggestion information.

[0104] Next, we will explain the processing flow of the medical decision support smart contract algorithm.

[0105] First, when the patient's condition transaction data and the doctor's opinion transaction data are sent to the medical decision support contract address 32, the input step of the medical decision support smart contract is executed. In the input step, information indicating the patient's condition contained in the condition transaction data and information indicating the doctor's opinion contained in the opinion transaction data are held in a format in which they are assigned to variables.

[0106] Next, the medical decision support smart contract executes a signature verification step. In the signature verification step, it is verified whether the signature for certifying the authenticity of the transaction data registered as a constant in the medical decision support smart contract matches the signature included in the content data of the condition transaction data and the opinion transaction data. The registered signature, which is the signature for certifying the authenticity of the transaction data, is registered as a constant when the medical decision support smart contract is deployed.

[0107] In the signature confirmation step, the next selection step is executed only if the verification result shows that the registered signature matches the signature included in the content data of the condition transaction data and the opinion transaction data, i.e., the input signature. On the other hand, if the verification result shows that the registered signature does not match the input signature, the process is interrupted and the variables of the medical decision support smart contract are initialized. In other words, the execution of the medical decision support smart contract is stopped. The patient terminal 10 and the doctor terminal 20 may be notified that the execution of the medical decision support smart contract has been stopped. In this case, the medical decision support smart contract may generate alert transaction data including the patient address 11 and the doctor address 21 and indicating that the execution has been stopped.

[0108] In the medical suggestion subset selection step, one medical suggestion subset is selected from the multiple medical suggestion subsets registered in advance according to a condition formula registered in advance in the medical decision support smart contract. The condition formula registered in advance in the medical decision support smart contract is a condition formula for executing a medical treatment decision obtained as a result of a consultation between the patient and the doctor. When content data included in the condition transaction data and the opinion transaction data are substituted into this condition formula, one medical suggestion subset is selected.

[0109] In the example shown in Fig. 9, two cases are selected by each of the three conditional branches indicated by conditions 0 to 2. Therefore, there are three conditional expressions pre-registered in the medical decision support smart contract, and there are four pre-registered multiple medical suggestion subsets.

[0110] In the medical proposal information output step, medical proposal transaction data is generated and output, the content data of which includes medical proposal information indicating one medical proposal subset selected in the selection step. Here, the medical decision support smart contract generates medical proposal transaction data including the doctor address 21 as the destination address and the medical decision support contract address 32 as the source address.

[0111] The medical suggestion subset included in the content data of the medical suggestion transaction data is shared with the doctor via the doctor terminal 20, and the doctor performs medical treatment in accordance with this medical suggestion subset.

[0112] The medical decision support smart contract may further include a step of recording the medical implementation results. Also, the step of recording the medical implementation results may be described in a smart contract different from the medical decision support smart contract. Regardless of which smart contract is used, first, the signature of the medical suggestion transaction data and the transaction data indicating the medical procedure performed by the doctor based on the medical suggestion subset may be confirmed, as in the above signature confirmation step. Then, the medical suggestion subset indicated in the medical suggestion transaction data and the medical procedure performed by the doctor may be linked and recorded (stored) in the distributed ledger.

[0113] Example 1 Next, we will explain the case where a subset of medical procedures based on the current POLST format, which is the result of mutual discussion between the patient and the doctor, is pre-registered in the medical decision support smart contract.

[0114] Fig. 10 is a diagram conceptually illustrating an algorithm of the medical decision support smart contract according to Example 1. Fig. 10 conceptually illustrates an algorithm in which a medical procedure subset in accordance with the current POLST format is selected by executing the medical decision support smart contract.

[0115] First, when the patient's condition transaction data and the doctor's opinion transaction data are sent to the medical decision support contract address 32, the input step of the medical decision support smart contract is executed. In the input step, information indicating the patient's condition in a situation where the patient is unable to express his or her own will and information indicating the doctor's opinion about the patient in that situation are held as input values.

[0116] Next, the medical decision support smart contract executes a signature verification step to verify the authenticity of the input values ​​by verifying whether the registered signature matches the input signature included in the content data of each of the condition transaction data and opinion transaction data.

[0117] Next, the medical decision support smart contract executes a selection step. If the patient's condition indicates cardiac arrest, the medical proposal subset is selected according to the medical procedure previously agreed upon by the patient and the doctor depending on whether or not the condition indicates the influence of trauma, with reference to the pre-conditions. For example, if the patient is in cardiac arrest and the doctor's opinion is that the patient is not affected by trauma, the medical proposal subset is selected to "perform full CPR." Also, for example, if the patient is in cardiac arrest and the doctor's opinion is that the patient will have severe aftereffects from trauma, the medical proposal subset is selected to perform mild "CPR."

[0118] On the other hand, if the patient's condition indicates that he / she is not in cardiac arrest, the medical proposal subset is selected according to the medical treatment previously agreed upon by the patient and the doctor depending on whether or not he / she will have severe after-effects, with reference to the pre-conditions. For example, if the patient is not in cardiac arrest and the doctor's opinion indicates that the patient will have severe after-effects, "pain relief treatment" is selected as the medical proposal subset. Also, for example, if the patient is not in cardiac arrest and the doctor's opinion indicates that the patient will not have severe after-effects, "medical treatment including invasive medical care" is selected as the medical proposal subset.

[0119] Each medical procedure subset preregistered in the medical decision support smart contract holds a unique identifier, and the medical procedure indicated by the selected medical procedure subset can be identified by this identifier. Therefore, the medical decision support smart contract only needs to transmit the identifier indicating the selected medical procedure subset to the output step.

[0120] In the output step, medical suggestion transaction data is generated and output, the content data of which includes an identifier indicating one medical suggestion subset selected in the selection step as medical suggestion information.

[0121] This enables a doctor to perform a medical procedure based on the medical suggestion subset represented in the medical suggestion transaction data, thereby enabling the doctor to perform a medical procedure that takes into account the patient's prior wishes.

[0122] The medical decision support smart contract may further include a step of recording the medical treatment results (not shown). In this case, transaction data is issued with the doctor address 21 as the sender address and the medical treatment results as content data. In the recording step, the medical decision support smart contract may link an identifier indicating one selected medical proposal subset with the medical treatment results and record them in the distributed ledger.

[0123] Example 2 Next, a case will be described in which a medical procedure subset based on the current living will format as a medical procedure obtained as a result of a consultation between a patient and a doctor is registered in advance in the medical decision support smart contract. Note that the following description will not be repeated in the same manner as in the first embodiment.

[0124] Fig. 11 is a diagram conceptually illustrating an algorithm of the medical decision support smart contract according to Example 2. Fig. 11 conceptually illustrates an algorithm for selecting a medical procedure subset in accordance with the current living will format by executing the medical decision support smart contract.

[0125] First, when the patient's condition transaction data and the doctor's opinion transaction data are sent to the medical decision support contract address 32, the input step of the medical decision support smart contract is executed. In the input step, information indicating the patient's condition in a situation where the patient is unable to express his or her own will and information indicating the doctor's opinion about the patient in that situation are held as input values.

[0126] Next, the medical decision support smart contract executes a signature verification step to verify the authenticity of the input values ​​by verifying whether the registered signature matches the input signature included in the content data of each of the condition transaction data and opinion transaction data.

[0127] Next, the medical decision support smart contract executes a selection step. If the patient's condition indicates that he or she is unlikely to regain consciousness, the medical decision support smart contract refers to the pre-conditions and selects a medical proposal subset that corresponds to the medical treatment previously agreed upon by the patient and the doctor depending on the presence or absence of trauma and visceral damage.

[0128] For example, if the patient is not expected to regain consciousness and the doctor has indicated that the patient has no external injuries or internal organ damage, the medical suggestion subset "Perform all cardiopulmonary resuscitation" is selected. Also, if the patient is not expected to regain consciousness and the doctor has indicated that the patient has no external injuries but internal organ damage, the medical suggestion subset "Request for continuous nutritional support via gastrostomy" is selected.

[0129] For example, if the patient is not expected to regain consciousness and the doctor has determined that the patient has external injuries but no internal organ damage, the medical suggestion subset "request for hydration via drip" is selected. For example, if the patient is not expected to regain consciousness and the doctor has determined that the patient has external injuries and internal organ damage, the medical suggestion subset "request for natural death without hydration or nutrition" is selected.

[0130] In the above first and second embodiments, the processing flow of the algorithm of the medical decision support smart contract based on the current POLST form and the current living will form has been described, but this is not limited to this.

[0131] The medical decision support smart contract may further include a process flow for selecting the content of the medical procedure according to the fee of the medical procedure. Also, the medical decision support smart contract may further include a process flow for referencing the insurance money or the patient's own account balance when performing the process flow for selecting the content of the medical procedure according to the fee of the medical procedure.

[0132] [1.7 Server configuration] FIG. 12 is a block diagram showing an example of the configuration of the server device 30 according to the present embodiment.

[0133] As shown in Fig. 12, the server device 30 includes a communication unit 301, a storage unit 302, a blockchain control unit 303, a database unit 304, and a working memory 305. The server device 30 can be realized by a processor executing a predetermined program using the memory. Each component will be described below.

[0134] <Communication Unit 301> The communication unit 301 communicates medical facts with the patient terminal 10 and the doctor terminal 20 via the communication network 40. The communication unit 301 may also cause the server device 30 to record the medical facts received in the storage unit 302.

[0135] In this embodiment, the communication unit 301 acquires, for example, third transaction data or condition transaction data including the medical decision support smart contract from the patient terminal 10. The communication unit 301 also acquires opinion transaction data or medical procedure implementation result transaction data from the doctor terminal 20. The communication unit 301 also transmits medical proposal transaction data output by the medical decision support smart contract to the doctor terminal 20.

[0136] <Storage section 302> The storage unit 302 stores, for example, medical suggestion transaction data output by the medical decision support smart contract. The storage unit 302 also stores the control results of the blockchain control unit 303.

[0137] The storage unit 302 may be the storage device shown in Fig. 1 having a distributed ledger. In this case, a distributed ledger area may be partitioned in the storage unit 302, and the distributed ledger may be stored in the distributed ledger area. The storage unit 302 may also have a working memory 305. In this case, the storage unit 302 may have a working memory area partitioned.

[0138] <Blockchain Control Unit 303> The blockchain control unit 303 controls the formation of a blockchain network, the generation of transaction data, the synchronization of distributed ledgers, and the execution of a consensus algorithm. The blockchain control unit 303 also controls the storage of each control result in the storage unit 302.

[0139] In this embodiment, the blockchain control unit 303 executes the medical decision support smart contract based on the patient's biometric information included in the condition transaction data and the doctor's diagnosis result for the patient's biometric information included in the opinion transaction data. In addition, the blockchain control unit 303 outputs suggested information on the medical treatment to be performed on the patient obtained from the medical decision support smart contract by executing the medical decision support smart contract.

[0140] In addition, the blockchain control unit 303 executes a consensus algorithm and stores the medical procedure implementation result transaction data obtained from the doctor terminal 20 in the distributed ledger.

[0141] Furthermore, the blockchain control unit 303 links the medical procedure implementation result transaction data acquired from the doctor terminal 20 with the medical proposal transaction data output by the medical decision support smart contract. More specifically, the blockchain control unit 303 stores information linking the medical procedure implementation result included in the medical procedure implementation result transaction data with the medical proposal subset included in the medical proposal transaction data in the storage unit 302. Note that the blockchain control unit 303 may execute a smart contract other than the medical decision support smart contract to store the information linking the medical procedure implementation result with the medical proposal subset in the distributed ledger.

[0142] Other controls by the blockchain control unit 303 are similar to those of the blockchain control unit 104 in the patient terminal 10, so detailed explanations will be omitted here.

[0143] <Database section 304> The database unit 304 functions as a database of medical facts. The database unit 304 may record medical information such as medical receipt data as medical facts.

[0144] Furthermore, the database unit 304 transmits data indicating a combination of medical procedures that can be proposed among the medical facts as a medical proposal subset to the patient terminal 10 and the doctor terminal 20 via, for example, the communication unit 301. The database unit 304 manages the medical facts indicated in the content data included in the transaction received by the blockchain control unit 303, and stores them in the storage unit 302.

[0145] <Working Memory 305> The working memory 305 is a memory that functions as an on-memory of the server device 30. The working memory 305 reads blocks recorded in the distributed ledger and stores the smart contract to operate the smart contract. The working memory 305 may store a contract address that indicates the smart contract.

[0146] In this embodiment, the working memory 305 may hold a medical decision support contract address 32, which is a contract address pointing to the medical decision support smart contract. Furthermore, the working memory 305 may hold a medical decision support smart contract in an operating state.

[0147] [1.8 Operation of the medical treatment management system] Next, an overview of the operation of the medical treatment management system 1 configured as above will be described.

[0148] FIG. 13A is a diagram showing an overview of the operation of the medical treatment management system 1 according to this embodiment up to storing a patient's declaration of intent in a distributed ledger.

[0149] First, in step S1, the medical treatment management system 1 allows the patient and the doctor to consult on medical treatment. More specifically, the medical treatment management system 1 allows the patient and the doctor to consult on medical treatment according to the patient's wishes in a situation where the patient is unable to express his or her own wishes.

[0150] In this embodiment, the patient terminal 10 acquires a medical procedure subset based on, for example, the current POLST format, and displays questions for determining the patient's prior will regarding medical procedures in a situation where the patient is unable to express his or her will. The patient decides on a medical procedure that is in line with the patient's will in a situation where the patient is unable to express his or her own will, in consultation with the doctor, by answering questions displayed on the patient terminal 10. The decided medical procedure is the medical procedure decision that the patient expressed his or her prior will as a result of consultation between the patient and the doctor.

[0151] Next, in step S2, the medical treatment management system 1 generates a medical decision support smart contract based on the result of the medical treatment consultation in step S2. More specifically, the medical treatment management system 1 generates a medical decision support smart contract that is programmed to be able to execute the medical treatment decision obtained as a result of consultation between the patient and the doctor.

[0152] Next, in step S3, the medical treatment management system 1 operates the medical decision support smart contract generated in step S2. More specifically, the medical treatment management system 1 operates the medical decision support smart contract by storing the medical decision support smart contract generated in step S2 in a distributed ledger and deploying it.

[0153] In this way, the medical treatment management system 1 stores the patient's expression of intent in the distributed ledger by storing and running a medical decision support smart contract, which is programmed to be able to execute medical treatment decisions reached through discussion between the patient and the doctor, in the distributed ledger.

[0154] FIG. 13B is a diagram showing an overview of the operations up to verifiably recording whether medical treatment has been decided and implemented in accordance with the patient's wishes, which are stored in the distributed ledger of the medical treatment management system 1 according to this embodiment.

[0155] First, in step S4, it is assumed that an incident occurs in which the patient requires medical treatment. Here, the occurrence of an incident means that the patient who has discussed medical treatment with the doctor in step S1 requires medical treatment and a situation has arisen in which it is necessary to use the medical treatment management system 1, such as when the patient's vital data is abnormal. In this case, the medical treatment management system 1 generates condition transaction data including the patient's sensor information and opinion transaction data including information regarding the doctor's diagnosis of the patient's vital information.

[0156] Next, in step S5, the medical decision support smart contract is executed. More specifically, the medical treatment management system 1 executes the medical decision support smart contract by storing the condition transaction data and opinion transaction data generated in step S4 in the distributed ledger.

[0157] Next, in step S6, the medical decision support smart contract outputs a medical treatment proposal to the patient as an execution result. More specifically, the medical decision support smart contract receives the condition transaction data and the opinion transaction data as inputs, and outputs uniquely determined proposal information regarding the medical treatment to be performed on the patient.

[0158] Next, in step S7, the doctor performs the medical treatment on the patient based on the proposed information on the medical treatment to be performed on the patient output in step S6. The doctor inputs information on the medical treatment performed on the patient to the medical treatment management system 1 as the result of the medical treatment.

[0159] Finally, in step S8, the results of the medical treatment performed in step S7 are recorded. More specifically, the medical treatment management system 1 stores the results of the medical treatment performed in step S7 in the distributed ledger in association with the proposed information on the medical treatment to be performed on the patient output in step S6.

[0160] In this way, the medical treatment management system 1 can ensure the reliability and resistance to tampering with the medical treatment process that reflects the patient's wishes. In other words, the medical treatment management system 1 records the medical treatment decision, including the patient's wishes, and the results of the medical treatment based on the medical treatment decision result in a referable manner in a blockchain that is extremely difficult to tamper with. This makes it possible to verify whether the medical treatment was decided and carried out taking into account the patients' prior wishes.

[0161] [1.8.1 Deployment sequence of medical decision support smart contract] Next, a sequence from generating a medical decision support smart contract in the medical treatment management system 1 to deploying it will be described.

[0162] FIG. 14 is a diagram showing a sequence from generation of a medical decision support smart contract by the medical treatment management system 1 according to this embodiment until it is put into operation.

[0163] First, the server device 30 transmits a medical suggestion subset (S101). In this embodiment, the server device 30 transmits the medical suggestion subset indicating a combination of medical facts and medical procedures in accordance with a living will form or a POLST form used for expressing the patient's prior will.

[0164] Next, the patient and the doctor use the patient terminal 10 and the doctor terminal 20 to make a consultation on medical treatment (S102). Here, the medical treatment decision used for generating the medical decision support smart contract, that is, the medical treatment decision expressed in advance by the patient himself, is decided by consultation between the patient and the doctor. In this embodiment, the patient terminal 10 asks the patient questions while showing a combination of medical facts and medical treatments in accordance with a living will form or a POLST form, and the patient decides on the medical treatment decision by answering the questions while consulting with the doctor. Note that the patient terminal 10 generates a medical decision support smart contract based on the decided medical treatment decision while performing the process of deciding the medical treatment decision. Details are as described in step S1 of FIG. 13A, so the explanation here is omitted.

[0165] Next, the patient terminal 10 and the doctor terminal 20 judge whether the consultation in step S102 has ended (S103).

[0166] In step S103, when it is determined that the consultation in step S102 has ended (Yes in S103), the doctor terminal 20 transmits the signature of the doctor terminal 20 (S104).

[0167] Next, the patient terminal 10 acquires the signature of the doctor terminal 20 transmitted in step S104 (S105).

[0168] Next, the patient terminal 10 generates a medical decision support smart contract based on the medical treatment decision obtained as a result of the consultation between the patient and the doctor in step S102 (S106). In this embodiment, the patient terminal 10 generates (a draft of) the medical decision support smart contract along with the medical treatment decision by the patient in the consultation in step S102. For this reason, the patient terminal 10 programs the medical decision support smart contract as, for example, a binary program in order to complete the generation of the medical decision support smart contract by acquiring the signature of the doctor terminal 20.

[0169] Next, the patient terminal 10 generates third transaction data including the medical decision support smart contract generated in step S106 (S107). In this embodiment, the patient terminal 10 generates third transaction data including the medical decision support smart contract generated as a binary program in content data, and the patient address 11 in the destination address and source address, as shown in Fig. 6, for example.

[0170] Next, the patient terminal 10 deploys the medical decision support smart contract in the blockchain network configured by the patient terminal 10 (S109) by sending the third transaction data generated in step S107 to itself (S108).

[0171] Next, the doctor terminal 20 and the server device 30 acquire the third transaction data that has been deployed and transmitted in step S109 (S110).

[0172] Next, the patient terminal 10, the doctor terminal 20, and the server device 30 are synchronized. More specifically, the patient terminal 10, the doctor terminal 20, and the server device 30 each execute a consensus algorithm, incorporate the third transaction data acquired in step S110 into a block, and store the block in the distributed ledger.

[0173] Next, the patient terminal 10, the doctor terminal 20, and the server device 30 run a medical decision support smart contract (S112).

[0174] [1.8.2 Execution sequence of medical decision support smart contract] Next, we will explain the sequence from when the medical decision support smart contract is executed in the medical treatment management system 1 to when medical suggestions are output and the results of the medical treatment performed by the doctor are recorded.

[0175] FIG. 15 is a diagram showing a sequence from when the medical decision support smart contract according to this embodiment is executed to when the results of the medical procedure are recorded.

[0176] First, the patient terminal 10 acquires sensor information such as biological information of the patient (S201). Specifically, the patient terminal 10 acquires sensor information such as biological information of the patient from, for example, the patient or a monitor device attached to the patient.

[0177] Next, the patient terminal 10 checks whether the patient's vital signs are abnormal based on the sensor information acquired in step S201 (S202).

[0178] If the patient's vital signs are abnormal in step S202 (Yes in S202), the patient terminal 10 generates condition transaction data including sensor information of the patient indicating the patient's condition (S203). Note that Yes in step S202, i.e., the patient's vital signs are abnormal, corresponds to the case of an incident occurring in step S4 in Fig. 13B described above. In this embodiment, the patient terminal 10 generates condition transaction data including the patient's condition and the signature of the patient terminal 10 in the content data, the medical decision support contract address 32 in the destination address, and the patient address 11 in the source address, as shown in Fig. 7, for example.

[0179] Next, the patient terminal 10 transmits the condition transaction data generated in step S203 to the doctor terminal 20 and the server device 30 by broadcasting it (S204).

[0180] Next, the doctor terminal 20 and the server device 30 acquire the condition transaction data (S205).

[0181] Next, the doctor terminal 20 checks whether the doctor's diagnosis result for the patient's condition included in the condition transaction data has been acquired (S207).

[0182] When the diagnosis result is acquired in step S207 (Yes in S207), the doctor terminal 20 generates opinion transaction data including information on the doctor's diagnosis result for the above-mentioned patient's biological information indicating the doctor's opinion (S209). In this embodiment, the doctor terminal 20 generates opinion transaction data including the doctor's opinion and the signature of the doctor terminal 20 in the content data, the medical decision support contract address 32 in the destination address, and the doctor address 21 in the source address, as shown in Fig. 8, for example.

[0183] Next, the doctor terminal 20 transmits the opinion transaction data generated in step S208 to the server device 30 (S209).

[0184] Next, the server device 30 transfers the condition transaction data transmitted in step S209 to the patient terminal 10 (S210). The doctor terminal 20 may transmit the opinion transaction data generated in step S208 to the patient terminal 10 and the server device 30 by broadcasting it. In this case, step S210 is not performed.

[0185] Next, the patient terminal 10, the doctor terminal 20, and the server device 30 execute a consensus algorithm (S211). More specifically, when the patient terminal 10, the doctor terminal 20, and the server device 30 verify that the condition transaction data and the opinion transaction data are valid transaction data (i.e., validity), they generate a block including them. Then, the patient terminal 10, the doctor terminal 20, and the server device 30 store the block including the condition transaction data and the opinion transaction data in their respective distributed ledgers. Then, the patient terminal 10, the doctor terminal 20, and the server device 30 input the condition transaction data and the opinion transaction data incorporated in the block to the medical decision support smart contract that is stored in the distributed ledger, written out to the working memory, and in operation. As a result, the medical decision support smart contract is executed using the condition transaction data and the opinion transaction data as input values.

[0186] Next, the server device 30 acquires the output of the medical decision support smart contract (S212).

[0187] Next, the server device 30 transmits the medical treatment proposal transaction data acquired in step S212 to the doctor terminal 20 (S213).

[0188] Next, the doctor terminal 20 acquires the medical proposal transaction data transmitted in step S213 (S214). The doctor using the doctor terminal 20 performs a medical procedure on the patient based on the proposal information included in the acquired medical proposal transaction data. The doctor then inputs information about the medical procedure performed on the patient to the doctor terminal 20 as the result of the medical procedure. Note that the server device 30 and the doctor terminal 20 may separately record the acquired medical proposal transaction data in a distributed ledger together with the patient terminal 10.

[0189] Next, the doctor terminal 20 checks whether the results of the medical procedure have been acquired (S215).

[0190] When the medical procedure implementation result is acquired in step S215 (Yes in S215), the doctor terminal 20 generates medical procedure implementation result transaction data including the medical procedure implementation result (S216).

[0191] Next, the doctor terminal 20 transmits the medical procedure implementation result transaction data generated in step S216 to the server device 30 (S218).

[0192] Next, the server device 30 transfers the medical procedure implementation result transaction data transmitted in step S218 to the patient terminal 10 (S219). The doctor terminal 20 may transmit the medical procedure implementation result transaction data generated in step S216 to the patient terminal 10 and the server device 30 by broadcasting it. In this case, step S219 is not performed.

[0193] Next, the patient terminal 10, the doctor terminal 20, and the server device 30 execute a consensus algorithm (S220). More specifically, when the patient terminal 10, the doctor terminal 20, and the server device 30 each verify that the medical procedure implementation result transaction data is valid transaction data (i.e., validity), they each generate a block including the medical procedure implementation result transaction data. Then, the patient terminal 10, the doctor terminal 20, and the server device 30 each store the block including the medical procedure implementation result transaction data in their respective distributed ledgers.

[0194] Next, the server device 30 records the medical suggestion information and the implementation result of the medical procedure in association with each other from the medical procedure implementation result transaction data and the medical suggestion transaction data stored in the distributed ledger (S221). It is assumed that a smart contract for recording the medical suggestion information and the implementation result of the medical procedure in association with each other is stored in the distributed ledger and written out to the working memory and is operated. In this case, the server device 30 may input the medical procedure implementation result transaction data incorporated in the block to the smart contract. As a result, the smart contract is executed using the medical procedure implementation result transaction data and the medical suggestion transaction data as input values, and the medical suggestion information and the implementation result of the medical procedure are recorded in association with each other.

[0195] [1.10 Effects, etc.] As described above, according to the control method and the like disclosed herein, all information including medical facts regarding the decision on medical treatment in a situation where the patient himself / herself cannot express his / her will can be recorded in the distributed ledger. Furthermore, according to the control method and the like disclosed herein, the medical decision support smart contract, which uniquely determines the proposal of medical treatment based on the patient's condition, etc., taking into account the patient's prior will, is made to propose medical treatment in a situation where the patient himself / herself cannot express his / her will. This makes it difficult to tamper with all information including the medical decision support smart contract, i.e., all information related to the decision on medical treatment in a situation where the patient himself / herself cannot express his / her will, so it can be verified whether the medical treatment was decided and implemented taking into account the patients' prior will. Furthermore, by making all the information difficult to tamper with using the distributed ledger, it is possible to prevent attacks by unauthorized manipulation of medical information, so it can be verified with high reliability whether the medical treatment was decided and implemented taking into account the patients' prior will.

[0196] (Other variations) Although the present disclosure has been described based on the above-mentioned embodiments, the present disclosure is not limited to the above-mentioned embodiments. The following cases are also included in the present disclosure.

[0197] (1) In the above embodiment, the patient terminal 10 has been described as having one blockchain control unit, but this is not limited to the above. The patient terminal 10 may have multiple blockchain control units, or, for example, a monitor device connected to the patient terminal 10 may have a blockchain control unit. In addition, a configuration in which these are combined may be used.

[0198] (2) In the above embodiment, the blockchain network is configured with one patient terminal 10, one doctor terminal 20, and one server device 30. However, the present invention is not limited to this. For example, the blockchain network may be configured with multiple patient terminals 10, multiple doctor terminals 20, and multiple server devices. The blockchain network may be configured with a combination of one patient terminal 10, multiple doctor terminals 20, and multiple server devices.

[0199] (3) In the above embodiment, the server device 30 has the database unit 304. However, the present invention is not limited to this. For example, a single database unit 304 may be divided and included in multiple server devices 30.

[0200] (4) In the above embodiment, the patient terminal 10 is described as generating the medical decision support smart contract, but this is not limited to the above. The patient terminal 10 may generate the medical decision support smart contract in cooperation with the doctor terminal 20, or the doctor terminal 20 may generate the medical decision support smart contract in cooperation with the patient terminal 10. In this case, the signatures of the patient terminal 10 and the doctor terminal 20 may be required as a multisig signature to issue transaction data including the medical decision support smart contract.

[0201] (5) In the above embodiment, Ethereum is used as a blockchain infrastructure for constructing a distributed ledger, i.e., a blockchain platform, but the present invention is not limited to this. For example, any platform that allows smart contracts to be written on a blockchain, such as Hyperledger Fabric, may be used, and the type of platform is not limited.

[0202] (6) In the above embodiment, the development language for smart contracts is Solidity, which is an Ethereum development language, but the invention is not limited to this. Any development language that allows smart contracts to be written in the selected blockchain platform may be used.

[0203] (7) In the above embodiment, the data format of the smart contract included in the transaction data is binary data, but the data format is not limited to binary data. For example, the data format may be any data format that can be executed by the selected blockchain platform, such as an application binary interface.

[0204] (8) In the above embodiment, the medical facts are transmitted and received in the form of being included in the transaction data, but this is not limiting. Any form may be used as long as the patient terminal 10, the doctor terminal 20, and the server device 30 can communicate with each other. The medical facts may be transmitted and received, for example, using file transportation in P2P, or through communication on the web.

[0205] (9) In the above embodiment, the input to the medical decision support smart contract is described as being the condition transaction data sent by the patient terminal 10 and the opinion transaction data sent by the doctor terminal 20, but is not limited thereto. For example, the doctor terminal 20 may acquire the condition transaction data generated by the patient terminal 10, and the input may be opinion transaction data that summarizes the patient's condition included in the condition transaction data. Note that the input to the medical decision support smart contract is described as being the condition transaction data and the opinion transaction data, but data division of the transaction data is not specified. If the algorithm in the medical decision support smart contract supports it, one transaction data such as the condition transaction data may be divided into two or more and input.

[0206] (10) In the above embodiment, the input to the medical decision support smart contract is described as the condition transaction data transmitted by the patient terminal 10 and the opinion transaction transmitted by the doctor terminal 20, but this is not limited thereto. The smart contract including the medical decision support smart contract may refer to data recorded in a distributed ledger including other smart contracts. The other smart contract may be, for example, a smart contract that describes the patient's own will information, or a smart contract that describes the patient's family information. The other smart contract may be a smart contract that describes a third party's decision in the manner of the medical decision support smart contract. The other smart contract may be a smart contract that describes not only medical care during life but also responses at the time of death, including organ donation, in the manner of the medical decision support smart contract. The other smart contract may further be a smart contract that combines these. In these cases, it is sufficient that the conditions of the smart contract or transaction to be referenced are described in advance in the smart contract.

[0207] (11) In the above embodiment, in the signature verification process in the medical decision support smart contract, if the signature included in the transaction data is an unauthorized signature, the process is interrupted. However, this is not limited to the above. In this case, the medical decision support smart contract may generate and transmit to the patient terminal 10, the doctor terminal 20, and / or the server device 30 transaction data indicating that an unauthorized signature was included in the transaction data. In addition, the medical decision support smart contract may perform the above interruption process together with the process of generating and transmitting transaction data indicating that an unauthorized signature was included in the transaction data.

[0208] (12) Each device in the above embodiments is specifically a computer system composed of a microprocessor, a ROM, a RAM, a hard disk unit, a display unit, a keyboard, a mouse, etc. A computer program is recorded in the RAM or the hard disk unit. Each device achieves its function by the microprocessor operating in accordance with the computer program. Here, the computer program is composed of a combination of multiple instruction codes that indicate commands for a computer to achieve a specified function.

[0209] (13) In each of the above embodiments, some or all of the constituent elements may be configured from a single system LSI (Large Scale Integration). The system LSI is a super multi-function LSI manufactured by integrating multiple components on a single chip, and specifically, is a computer system including a microprocessor, ROM, RAM, etc. A computer program is recorded in the RAM. The system LSI achieves its functions by the microprocessor operating in accordance with the computer program.

[0210] Furthermore, each of the components constituting each of the above devices may be individually implemented as a single chip, or some or all of them may be included in a single chip.

[0211] In addition, although we refer to it as a system LSI here, it may also be called an IC, LSI, super LSI, or ultra LSI depending on the degree of integration. Also, the method of integration is not limited to LSI, but may be realized by a dedicated circuit or a general-purpose processor. It is also possible to use an FPGA (Field Programmable Gate Array) that can be programmed after the LSI is manufactured, or a reconfigurable processor that can reconfigure the connections and settings of the circuit cells inside the LSI.

[0212] Furthermore, if a new integrated circuit technology that can replace LSI appears due to the progress of semiconductor technology or a derivative technology, it is possible to integrate the functional blocks using that technology. The application of biotechnology is also a possibility.

[0213] (14) A part or all of the components constituting each of the above devices may be composed of an IC card or a single module that is detachable from each device. The IC card or the module may be a computer system composed of a microprocessor, a ROM, a RAM, etc. The IC card or the module may include the above-mentioned ultra-multifunction LSI. The microprocessor operates according to a computer program, so that the IC card or the module achieves its function. The IC card or the module may be tamper-resistant. The present disclosure may be the above-mentioned method. Also, the present disclosure may be a computer program that realizes these methods by a computer, or a digital signal consisting of the computer program.

[0214] Furthermore, the present disclosure may be a computer program or a digital signal recorded on a computer-readable recording medium, such as a flexible disk, a hard disk, a CD-ROM, an MO, a DVD, a DVD-ROM, a DVD-RAM, a BD (Blu-ray (registered trademark) Disc), a semiconductor memory, etc. Also, the present disclosure may be a digital signal recorded on such a recording medium.

[0215] In addition, the present disclosure may involve transmitting the computer program or the digital signal via a telecommunications line, a wireless or wired communication line, a network such as the Internet, data broadcasting, or the like.

[0216] The present disclosure may also provide a computer system having a microprocessor and a memory, the memory storing the computer program, and the microprocessor operating in accordance with the computer program.

[0217] Moreover, the program or the digital signal may be recorded on the recording medium and transferred, or the program or the digital signal may be transferred via the network or the like, so that the program or the digital signal may be implemented by another independent computer system. The above-mentioned embodiments and the above-mentioned modified examples may be combined with each other. [Industrial Applicability]

[0218] The present disclosure can be used for control methods, programs, and control devices, for example, for systems that securely manage and share medical facts, including patient decision-making and diagnostic results for patients, and manage all medical treatment data so that it can be verified after the fact. [Explanation of symbols]

[0219] 1 Medical Treatment Management System 10 Patient terminal 11 Patient Address 20 Doctor's terminal 21 Doctor's Address 30 Server device 31 Server Address 32 Medical Decision Support Contract Address 40 Communication Network 101, 201, 301 Communications Department 102 Sensor information acquisition unit 103 Smart Contract Generation Unit 104, 203 Blockchain control section 105, 204 Display section 106, 205, 302 Storage section 202 Doctor's Opinion Generation Department 303 Blockchain Control Section 304 Database Department 305 Working Memory

Claims

1. A control method in a system, comprising: The smart contract, which is programmed to execute medical treatment decisions made through consultation between patients and doctors, is stored in a distributed ledger. The control method includes: acquiring first transaction data including biometric information of the patient obtained from a sensor; acquiring second transaction data including information regarding a diagnosis result of the doctor with respect to the biological information; Executing the smart contract based on the biometric information and the diagnosis result included in the acquired first transaction data and the acquired second transaction data; outputting medical suggestion information regarding a medical procedure to be performed on the patient, the medical suggestion information being obtained by executing the smart contract; Control methods.

2. Before acquiring the first transaction data and the second transaction data, Obtaining third transaction data including the smart contract generated based on the medical treatment decision obtained as a result of consultation between the patient and the doctor; storing a block including the third transaction data in the distributed ledger; The control method according to claim 1 .

3. The third transaction data includes a signature for verifying authenticity of the third transaction data. The control method according to claim 2 .

4. The smart contract is a program having a description including a conditional expression for executing the medical treatment judgment using the first transaction data and the second transaction data as input values. The control method according to any one of claims 1 to 3.

5. The first transaction data and the second transaction data are A contract address indicating the address of the smart contract; The control method according to any one of claims 1 to 4.

6. moreover, Obtaining fourth transaction data including medical procedure result information, which is information regarding the medical procedure performed by the doctor on the patient; The medical treatment result information is linked to the medical suggestion information and stored in the distributed ledger. The control method according to any one of claims 1 to 5.

7. The biological information is information indicating cardiac arrest, The diagnosis result is information indicating no trauma, The medical suggestion information is information indicating that the medical procedure to be performed on the patient is cardiopulmonary resuscitation. The control method according to any one of claims 1 to 6.

8. The distributed ledger is built on a blockchain platform. The control method according to any one of claims 1 to 7.

9. acquiring first transaction data including biometric information of the patient obtained from a sensor; acquiring second transaction data including information regarding a doctor's diagnosis of the biological information; Executing a smart contract that is programmed to be executable to determine a medical treatment decision made as a result of a discussion between the patient and the doctor based on the biological information and the diagnosis result contained in the acquired first transaction data and the acquired second transaction data, the smart contract being stored in a distributed ledger; outputting medical suggestion information regarding a medical procedure to be performed on the patient, the medical suggestion information being obtained by executing the smart contract; A program that a computer runs.

10. A control device having a processor, a memory, and a distributed ledger, The distributed ledger stores a smart contract that is programmed to execute medical treatment decisions made as a result of consultation between a patient and a doctor, The processor acquires first transaction data including biometric information of the patient obtained from a sensor; The processor acquires second transaction data including information regarding a diagnosis result of the doctor for the biological information; The processor executes the smart contract using the memory based on the biometric information and the diagnosis result included in the acquired first transaction data and the acquired second transaction data; The processor outputs medical suggestion information regarding a medical treatment to be performed on the patient, the medical suggestion information being obtained by executing the smart contract. Control device.

Citation Information

Patent Citations

  • Method and system for managing personal health records using telemedicine and health monitoring device functions.

    JP2015507282A

  • Method for calculating a score of a medical proposal as support for medical decision-making

    JP2016516231A

  • System and Method for a Distributed Autonomous Medical Economy Platform

    JP2018533103A

  • System and method utilizing facial recognition with online (social) network to access casualty health information in an emergency situation

    US20190035492A1

  • Smart device

    US20190361917A1