Medical Systems and Computer Programs

Abstract

To provide a medical system and computer program that can improve convenience in the prescription of medicine.SOLUTION: In a management system in which an electronic prescription management device, a history management system, a medical system, a medicine management system, and a user terminal communicate via a network, the medical system for issuing data of an electronic prescription related to medicine prescribed to a patient includes: an issuing section 362 that instructs the history management system for recording a history of transfer of a token to issue the token that is information of a transfer target related to the electronic prescription; and a transfer control section 363 that instructs the history management system to transfer the token to a terminal of a person to receive the medicine.SELECTED DRAWING: Figure 3

Description

[Technical field]

[0001] The present invention relates to techniques used in formulating pharmaceutical products. [Background technology]

[0002] In recent years, technology has been proposed to digitize medical records prepared by doctors (see, for example, Patent Document 1). For example, in 2017, such electronic medical record technology was adopted in nearly 50% of general hospitals and general clinics, and has improved the efficiency of medical care. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2020-113004 A Summary of the Invention [Problem to be solved by the invention]

[0004] However, with regard to prescribing medicines, although the Ministry of Health, Labour and Welfare published the final report of a demonstration project toward the full-scale operation of electronic prescriptions in 2018, convenience is not necessarily sufficient. In view of the above circumstances, an object of the present invention is to provide a technique capable of improving convenience in prescribing pharmaceuticals. [Means for solving the problem]

[0005] One aspect of the present invention is a medical system that includes an issuing unit that issues electronic prescription data for medicines prescribed for a patient and instructs a history management system that records the history of the transfer of the token to issue a token, which is information about the object of transfer related to the electronic prescription, and a transfer control unit that instructs the history management system to transfer the token to a terminal of a person receiving the medicine.

[0006] One aspect of the present invention is the above-mentioned medical system, wherein the history management system is configured using a blockchain.

[0007] One aspect of the present invention is the above-mentioned medical system, wherein the transfer control unit instructs the history management system to transfer the token to a terminal among the terminals that has been authenticated by an authentication and authorization system that performs authentication using authentication information.

[0008] One aspect of the present invention is the above-mentioned information system, wherein the transfer control unit instructs the history management system to transfer the token to an agent terminal, which is one of the terminals to which the token has been transferred from a user terminal used by the patient.

[0009] One aspect of the present invention is the medical system described above, wherein the history management system records information indicating that the token has been handed over to the agent terminal.

[0010] One aspect of the present invention is the above medical system, wherein the token includes a hash value of the electronic prescription data.

[0011] One aspect of the present invention is a computer program for causing a computer to function as the above-mentioned medical system. Effect of the Invention

[0012] The present invention makes it possible to improve convenience in prescribing pharmaceuticals. [Brief description of the drawings]

[0013] [Figure 1] FIG. 1 is a schematic block diagram showing a system configuration of a first embodiment of a management system 100 of the present invention. [Diagram 2] FIG. 2 is a schematic block diagram showing a specific example of the functional configuration of the electronic prescription management device 10. [Diagram 3]2 is a schematic block diagram showing a specific example of the functional configuration of a medical system 30. FIG. [Figure 4] 2 is a schematic block diagram showing a specific example of the functional configuration of a medicine management system 40. FIG. [Diagram 5] 2 is a schematic block diagram showing a specific example of the functional configuration of a user terminal 50. FIG. [Figure 6] 1 is a sequence chart showing a specific example of the processing flow when an electronic prescription is issued. [Figure 7] 11 is a sequence chart showing a specific example of the processing flow when an electronic prescription token is transferred from the medical system 30 to the user terminal 50. [Figure 8] 11 is a sequence chart showing a specific example of the processing flow when an electronic prescription token is transferred from a user terminal 50 to a medicine management system 40. [Figure 9] 1 is a sequence chart showing a specific example of a processing flow when a medicine is dispensed to a user according to an electronic prescription. [Figure 10] FIG. 11 is a schematic block diagram showing a system configuration of a second embodiment of a management system 100 according to the present invention. [Figure 11] 11 is a sequence chart showing a specific example of the processing flow when an electronic prescription token is transferred from a user terminal 50 to an agent terminal 60. [Figure 12] 11 is a sequence chart showing a specific example of the processing flow when an electronic prescription token is transferred from an agent terminal 60 to a medicine management system 40. [Figure 13] 11 is a sequence chart showing a specific example of a process flow when medicines are dispensed to a representative according to an electronic prescription. [Figure 14] 13 is a sequence chart showing a specific example of a process flow when medicines received by a proxy are handed over to a user. [Figure 15] FIG. 13 is a diagram showing the configuration of a modified example of the management system 100. [Figure 16] FIG. 13 is a diagram showing a specific example of an authentication process in the modified example. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0014] Hereinafter, specific configuration examples of the present invention will be described with reference to the drawings. [First embodiment] 1 is a schematic block diagram showing the system configuration of a first embodiment of the management system 100 of the present invention. The management system 100 includes an electronic prescription management device 10, a history management system 20, a medical system 30, a medicine management system 40, and a user terminal 50. The electronic prescription management device 10, the history management system 20, the medical system 30, the medicine management system 40, and the user terminal 50 communicate with each other via a network 90. ​​The network 90 may be a network using wireless communication or a network using wired communication. The network 90 may be configured by combining a plurality of networks.

[0015] 2 is a schematic block diagram showing a specific example of the functional configuration of the electronic prescription management device 10. The electronic prescription management device 10 is configured using an information processing device such as a personal computer or a server device. The electronic prescription management device 10 includes a communication unit 11, a storage unit 12, and a control unit 13.

[0016] The communication unit 11 is a communication device. The communication unit 11 may be configured as, for example, a network interface. The communication unit 11 performs data communication with other devices via the network 90 in response to the control of the control unit 13. The communication unit 11 may be a device that performs wireless communication or a device that performs wired communication.

[0017] The storage unit 12 is configured using a storage device such as a magnetic hard disk device or a semiconductor storage device. The storage unit 12 stores data used by the control unit 13. The storage unit 12 may function as, for example, an electronic prescription storage unit 121. The electronic prescription storage unit 121 stores data of an electronic prescription issued in the management system 100. The electronic prescription data includes, for example, data included in a prescription. The electronic prescription data includes, for example, medicines prescribed for a user of the user terminal 50 and their usage (such as how to take them). The electronic prescription data may be stored in association with specific identification information (for example, a Uniform Resource Identifier (URI)). The electronic prescription data may be stored in a format such as Health Level Seven (HL7) or Fast Health Interoperable Resources (FHIR).

[0018] The control unit 13 is configured using a processor such as a CPU (Central Processing Unit) and a memory. The control unit 13 functions as an information management unit 131 and an information provision unit 132 by the processor executing a program. All or part of the functions of the control unit 13 may be realized using hardware such as an ASIC (Application Specific Integrated Circuit), a PLD (Programmable Logic Device), or an FPGA (Field Programmable Gate Array). The above program may be recorded on a computer-readable recording medium. The computer-readable recording medium is, for example, a portable medium such as a flexible disk, a magneto-optical disk, a ROM, a CD-ROM, or a semiconductor storage device (for example, an SSD: Solid State Drive), or a storage device such as a hard disk or a semiconductor storage device built into a computer system. The above program may be transmitted via an electric communication line.

[0019] The information management unit 131 performs management processes such as new registration, update, and deletion of electronic prescription data stored in the electronic prescription storage unit 121. For example, when a registration request for new electronic prescription data is received from the medical system 30, the information management unit 131 registers the received electronic prescription data in the electronic prescription storage unit 121. For example, when an update request for electronic prescription data is received from the medicine management system 40, the information management unit 131 updates the electronic prescription data to be updated in accordance with the received update request. For example, when a deletion request for electronic prescription data is received from the medicine management system 40, the information management unit 131 deletes the electronic prescription data to be deleted in accordance with the received deletion request. Note that the source of the update request or deletion request does not have to be limited to the above-mentioned medicine management system 40. For example, the medical system 30 may be the source.

[0020] The information providing unit 132 provides the electronic prescription data stored in the electronic prescription storage unit 121 to other information processing devices. For example, when a request for electronic prescription data is received by specifying predetermined specific identification information (e.g., a URI), the information providing unit 132 provides the electronic prescription data associated with the identification information to the requesting device in response to the request.

[0021] The history management system 20 is configured using one or more information processing devices. It is desirable that the history management system 20 is configured using a system in which the information stored therein is highly reliable. The history management system 20 may be configured, for example, as one information processing device or one information processing system, and configured to store all of the information of the history to be managed. The history management system 20 may be configured, for example, as a distributed system configured by connecting multiple information processing devices via a network, and configured to distribute and store the information of the history to be managed. The history management system 20 may be configured, for example, as a blockchain system. In this case, the blockchain applied to the history management system 20 may be configured as a public type or a private type.

[0022] The history management system 20 manages information regarding the history of transfer of information to be transferred (hereinafter referred to as "token"), for example, related to electronic prescriptions. The token may have the following values, for example. In addition, when the history management system 20 is configured using a blockchain, the identification information of the token may be realized as a block number or a contract address.

[0023] Token identification information (token ID) Prescription date ·date of expiry Issuer identification (e.g. doctor ID) · Identification of the current occupant Electronic prescription identifier (e.g. URI) -Hash value of electronic prescription data

[0024] A request for issuance of a token is sent to the history management system 20 in response to an operation of a medical professional (e.g., a doctor) in the medical system 30, and the history management system 20 issues the token in response to the request. The token may be issued, for example, per prescription, per type of medicine, or per group of multiple medicines. The token issued in response to the operation of the medical professional is delivered to the user terminal 50 of the user (e.g., a patient) to whom an electronic prescription corresponding to the token is to be issued. The delivery may be performed by, for example, delivering the token held in the medical system 30 to the user terminal 50 using a wallet address generated based on a private key held in the medical system 30 and a wallet address generated based on a public key held in the user terminal 50. When such a token is delivered, information indicating the history of the delivery is recorded in the history management system 20 in response to processing of the medical system 30 and the user terminal 50.

[0025] FIG. 3 is a schematic block diagram showing a specific example of the functional configuration of the medical system 30. The medical system 30 is a system used to manage patient information in a medical institution (e.g., a hospital or a clinic). The medical system 30 may be configured in compliance with a standard such as FHIR. The medical system 30 performs processing related to electronic prescriptions, for example. The medical system 30 is operated by a person who works in a medical institution (hereinafter referred to as a "medical worker"). Specific examples of medical workers include doctors, nurses, pharmacists, and front desk staff. The medical system 30 may be operated by a general person (a person who is not a medical worker) such as a patient for certain processing. A specific example of such processing is a process of transferring a token of an electronic prescription that has already been issued to the medical system itself.

[0026] The medical system 30 is configured using an information processing device such as a personal computer or a server device. It may be configured using one information processing device, or may be configured using multiple information processing devices. In the following explanation, a configuration in which the medical system is configured using one information processing device will be explained. The medical system 30 includes a communication unit 31, an operation unit 32, a display unit 33, an information acquisition unit 34, a storage unit 35, and a control unit 36.

[0027] The communication unit 31 is a communication device. The communication unit 31 may be configured as, for example, a network interface. The communication unit 31 performs data communication with other devices via the network 90 in response to the control of the control unit 36. The communication unit 31 may be a device that performs wireless communication or a device that performs wired communication.

[0028] The operation unit 32 is configured using existing input devices such as a keyboard, a pointing device (mouse, tablet, etc.), buttons, and a touch panel. The operation unit 32 is operated when inputting instructions from an operator of the medical system 30 (e.g., a medical professional or a patient) to the medical system 30. The operation unit 32 may be an interface for connecting an input device to the medical system 30. In this case, the operation unit 32 inputs an input signal generated in response to an input in the input device to the medical system 30. The operation unit 32 may be configured using a microphone and a voice recognition device. In this case, the operation unit 32 performs voice recognition on spoken words and inputs character string information of the recognition result to the medical system 30. The operation unit 32 may be configured in any way as long as it is configured to be able to input instructions from a medical professional or the like to the medical system 30.

[0029] The display unit 33 is an image display device such as a liquid crystal display or an organic EL (Electro Luminescence) display. The display unit 33 displays image data and text data. The display unit 33 may be an interface for connecting an image display device to the medical system 30. In this case, the display unit 33 generates a video signal for displaying the image data and text data, and outputs the video signal to the image display device connected to the display unit 33.

[0030] The information acquisition unit 34 acquires information required for transferring the token. The information acquisition unit 34 may be used, for example, to acquire information (e.g., a wallet address) indicating the destination of the token. In this case, for example, when the information indicating the destination of the token is represented as an image of coded information in a predetermined format (e.g., a barcode or a two-dimensional code), the information acquisition unit 34 may be configured using a camera (image sensor) for capturing the image. For example, when the information indicating the destination of the token is represented as a wireless signal in a predetermined format, the information acquisition unit 34 may be configured using a wireless communication device (e.g., an RFID reader, a Bluetooth (registered trademark) device) for receiving the wireless signal.

[0031] The information acquisition unit 34 may be used, for example, to transmit and receive the electronic prescription data itself. In this case, the information acquisition unit 34 transmits the electronic prescription data itself to a destination device (for example, a patient's user terminal 50) by wired communication or wireless communication.

[0032] The storage unit 35 is configured using a storage device such as a magnetic hard disk device, a semiconductor storage device, etc. The storage unit 35 functions as an electronic prescription storage unit 351, an authentication information storage unit 352, and a key information storage unit 353.

[0033] The electronic prescription storage unit 351 stores data of an electronic prescription issued by the medical system 30. The authentication information storage unit 352 stores authentication information used to authenticate an operator who operates the medical system 30. The authentication information storage unit 352 stores, for example, authentication information of each medical worker who has legitimate authority to operate the medical system 30. The authentication information storage unit 352 may store, for example, the user ID and password of each medical worker. The authentication information storage unit 352 may store authentication information for two-factor authentication. The key information storage unit 353 stores information on an encryption key used for issuing and transferring a token. The key information storage unit 353 may store, for example, encryption key information. The key information storage unit 353 may store, for example, encryption key information and public key information corresponding to the encryption key information.

[0034] The control unit 36 ​​is configured using a processor such as a CPU and a memory. The control unit 36 ​​functions as an authentication control unit 361, an electronic prescription issuing unit 362, and a token transfer control unit 363 by the processor executing a program. All or part of the functions of the control unit 36 ​​may be realized using hardware such as ASIC, PLD, and FPGA. The above program may be recorded on a computer-readable recording medium. The computer-readable recording medium is, for example, a portable medium such as a flexible disk, a magneto-optical disk, a ROM, a CD-ROM, or a semiconductor storage device (e.g., SSD), or a storage device such as a hard disk or a semiconductor storage device built into a computer system. The above program may be transmitted via an electric communication line.

[0035] The authentication control unit 361 authenticates a person who is going to operate the medical system 30. The authentication control unit 361 authenticates whether or not a person who is going to operate the medical system 30 has legitimate authority based on the authentication information stored in the authentication information storage unit 352. The system may be configured so that only a person authenticated by the authentication control unit 361 can operate the medical system 30, or so that only a person authenticated by the authentication control unit 361 can perform a specific operation (for example, an operation to issue an electronic prescription).

[0036] The electronic prescription issuing unit 362 performs a process of issuing an electronic prescription. The electronic prescription issuing unit 362 generates electronic prescription data according to, for example, a predetermined format. The electronic prescription issuing unit 362 registers the generated electronic prescription data in the electronic prescription management device 10. The electronic prescription issuing unit 362 requests the history management system 20 to generate a token related to the issued electronic prescription. The electronic prescription issuing unit 362 may issue electronic prescription data for each type of medicine prescribed for a patient and request the generation of a token. The electronic prescription issuing unit 362 may transmit the issued electronic prescription data to a user terminal 50 of a legitimate user (for example, a patient to whom a medicine is prescribed by an electronic prescription) by wireless communication or wired communication. In this case, the electronic prescription issuing unit 362 may transmit the electronic prescription data via, for example, the information acquiring unit 34. For example, the transmission of the electronic prescription data may be performed using short-range communication such as Bluetooth (registered trademark), or may be performed by communication via a network such as WiFi (registered trademark) or the Internet.

[0037] The token transfer control unit 363 performs a process of transferring the token issued by the history management system 20 to the user terminal 50 of a valid user (for example, a patient to whom a drug is prescribed by an electronic prescription). The token transfer control unit 363 may transfer the token by, for example, generating data (data indicating a history) indicating that the token is to be transferred to the user terminal 50 and registering the generated data in the history management system 20. The token transfer control unit 363 may transfer the token by generating data (data indicating a history) indicating that the token is to be transferred to the user terminal 50 in response to, for example, the issuance of an electronic prescription by the electronic prescription issuing unit 362 (or the transmission of electronic prescription data to the user terminal 50 by the electronic prescription issuing unit 362), and registering the generated data in the history management system 20. The process of the token transfer control unit 363 may be implemented in any manner as long as the history of the token transfer (information such as the source of the token transfer, the destination of the token transfer, and a timestamp) can be registered in the history management system 20.

[0038] FIG. 4 is a schematic block diagram showing a specific example of the functional configuration of the medicine management system 40. The medicine management system 40 is a system used to manage information on patients and medicines in an institution (e.g., a pharmacy) that dispenses medicines to patients based on an electronic prescription. The medicine management system 40 may be configured in compliance with a standard such as FHIR. The medicine management system 40 performs processing related to electronic prescriptions, for example. The medicine management system 40 is operated by a person who works in a pharmacy (hereinafter referred to as a "dispensing staff"). Specific examples of dispensing staff include pharmacists and counter staff. The medicine management system 40 may be operated by a general person (a person who is not a dispensing staff) such as a patient for specific processing. A specific example of such processing is a process of transferring a token of an electronic prescription related to medicines that have already been transferred to the person.

[0039] The drug management system 40 is configured using an information processing device such as a personal computer or a server device. It may be configured using one information processing device, or may be configured using multiple information processing devices. In the following explanation, a configuration in which it is configured using one information processing device will be explained. The drug management system 40 includes a communication unit 41, an operation unit 42, a display unit 43, an information acquisition unit 44, a storage unit 45, and a control unit 46.

[0040] The communication unit 41 is a communication device. The communication unit 41 may be configured as, for example, a network interface. The communication unit 41 performs data communication with other devices via the network 90 in response to the control of the control unit 46. The communication unit 41 may be a device that performs wireless communication or a device that performs wired communication.

[0041] The operation unit 42 is configured using existing input devices such as a keyboard, a pointing device (mouse, tablet, etc.), a button, a touch panel, etc. The operation unit 42 is operated when inputting instructions from an operator of the medicine management system 40 (e.g., a dispensing staff member or a patient) to the medicine management system 40. The operation unit 42 may be an interface for connecting an input device to the medicine management system 40. In this case, the operation unit 42 inputs an input signal generated in response to an input in the input device to the medicine management system 40. The operation unit 42 may be configured using a microphone and a voice recognition device. In this case, the operation unit 42 performs voice recognition on spoken words and inputs character string information of the recognition result to the medicine management system 40. The operation unit 42 may be configured in any manner as long as it is configured to input instructions from a medical staff member or the like to the medicine management system 40.

[0042] The display unit 43 is an image display device such as a liquid crystal display or an organic EL display. The display unit 43 displays image data and text data. The display unit 43 may be an interface for connecting the image display device to the medicine management system 40. In this case, the display unit 43 generates a video signal for displaying the image data and text data, and outputs the video signal to the image display device connected to the display unit 43.

[0043] The information acquisition unit 44 acquires information required for transferring the token. The information acquisition unit 44 may be used, for example, to acquire information (e.g., a wallet address) indicating the destination of the token. In this case, for example, when the information indicating the destination of the token is represented as an image of coded information in a predetermined format (e.g., a barcode or a two-dimensional code), the information acquisition unit 44 may be configured using a camera (image sensor) for capturing the image. For example, when the information indicating the destination of the token is represented as a wireless signal in a predetermined format, the information acquisition unit 44 may be configured using a wireless communication device (e.g., an RFID reader, a Bluetooth (registered trademark) device) for receiving the wireless signal.

[0044] The information acquisition unit 44 may be used, for example, to transmit and receive the electronic prescription data itself. In this case, the information acquisition unit 44 may receive the electronic prescription data itself from a source device (e.g., the patient's user terminal 50) by wired communication or wireless communication, or may transmit the electronic prescription data itself to a destination device (e.g., the patient's user terminal 50).

[0045] The storage unit 45 is configured using a storage device such as a magnetic hard disk device, a semiconductor storage device, etc. The storage unit 45 functions as an electronic prescription storage unit 451, an authentication information storage unit 452, and a key information storage unit 453.

[0046] The electronic prescription storage unit 451 stores data of an electronic prescription acquired in the medicine management system 40. The authentication information storage unit 452 stores authentication information used to authenticate an operator who operates the medicine management system 40. The authentication information storage unit 452 stores, for example, authentication information of each dispensing staff member who has legitimate authority to operate the medicine management system 40. The authentication information storage unit 452 may store, for example, the user ID and password of each dispensing staff member. The authentication information storage unit 452 may store authentication information for two-factor authentication. The key information storage unit 453 stores information on an encryption key used for transferring a token. The key information storage unit 453 may store, for example, encryption key information. The key information storage unit 453 may store, for example, encryption key information and public key information corresponding to the encryption key information.

[0047] The control unit 46 is configured using a processor such as a CPU and a memory. The control unit 46 functions as an authentication control unit 461, an electronic prescription management unit 462, and a token transfer control unit 463 by the processor executing a program. All or part of the functions of the control unit 46 may be realized using hardware such as ASIC, PLD, and FPGA. The above program may be recorded on a computer-readable recording medium. The computer-readable recording medium is, for example, a portable medium such as a flexible disk, a magneto-optical disk, a ROM, a CD-ROM, or a semiconductor storage device (e.g., SSD), or a storage device such as a hard disk or a semiconductor storage device built into a computer system. The above program may be transmitted via an electric communication line.

[0048] The authentication control unit 461 authenticates a person who is going to operate the medicine management system 40. The authentication control unit 461 authenticates whether or not a person who is going to operate the medicine management system 40 has legitimate authority based on the authentication information stored in the authentication information storage unit 452. The system may be configured so that only those authenticated by the authentication control unit 461 can operate the medicine management system 40, or so that only those authenticated by the authentication control unit 461 can perform specific operations (for example, an operation to obtain an electronic prescription).

[0049] The electronic prescription management unit 462 performs a process of managing an electronic prescription. The electronic prescription management unit 462 may acquire electronic prescription data from the electronic prescription management device 10 via the network 90 based on, for example, information recorded in a token acquired from the patient's user terminal 50. More specifically, the electronic prescription management unit 462 may acquire electronic prescription data by accessing specific identification information (such as a URI) recorded in the token. The electronic prescription management unit 462 may acquire electronic prescription data by other methods. For example, the electronic prescription management unit 462 may receive electronic prescription data from the user terminal 50 via wireless or wired communication. In this case, the electronic prescription management unit 462 may receive electronic prescription data via the information acquisition unit 44. For example, the exchange of electronic prescription data may be performed using short-range communication such as Bluetooth (registered trademark), or may be performed by communication via a network such as WiFi (registered trademark) or the Internet. The electronic prescription management unit 462 may display the contents of the acquired electronic prescription on the display unit 43. The electronic prescription management unit 462 may record the acquired electronic prescription data in the electronic prescription storage unit 451.

[0050] The token transfer control unit 463 performs a process of receiving the token of the electronic prescription acquired by the electronic prescription management unit 462 from the user terminal 50 of a valid user (for example, a patient who has been prescribed medicines by an electronic prescription) and a process of transferring the token to the user terminal 50 of a valid user (for example, a patient who has been dispensed medicines according to an electronic prescription). The token transfer control unit 463 may receive the token by, for example, generating data indicating that the token is received from the user terminal 50 and registering the generated data in the history management system 20 in response to receiving data of the electronic prescription from the user terminal 50, and may receive the token by registering the generated data in the history management system 20. The token transfer control unit 463 may perform a process of displaying information indicating information required for receiving the token (for example, a wallet address for receiving the token) on the display unit 43. The processing of the token passing control unit 463 may be implemented in any manner as long as the history of token passing (information such as the source of token passing, the destination of token passing, and timestamp) can be registered in the history management system 20. In addition, the processing of token passing is similar to that of the token passing control unit 363.

[0051] 5 is a schematic block diagram showing a specific example of the functional configuration of the user terminal 50. The user terminal 50 is configured using information equipment such as a smartphone, a tablet, a personal computer, a portable game machine, a wearable device such as a smart watch, or a dedicated device. The user terminal 50 includes a communication unit 51, an operation unit 52, a display unit 53, an information acquisition unit 54, a storage unit 55, and a control unit 56.

[0052] The communication unit 51 is a communication device. The communication unit 51 may be configured as, for example, a network interface. The communication unit 51 performs data communication with other devices via the network 90 in response to control by the control unit 56. The communication unit 51 may be a device that performs wireless communication or a device that performs wired communication.

[0053] The operation unit 52 is configured using existing input devices such as a keyboard, a pointing device (mouse, tablet, etc.), buttons, a touch panel, etc. The operation unit 52 is operated when an instruction from an operator of the user terminal 50 (e.g., a patient) is input to the user terminal 50. The operation unit 52 may be an interface for connecting an input device to the user terminal 50. In this case, the operation unit 52 inputs an input signal generated in response to an input in the input device to the user terminal 50. The operation unit 52 may be configured using a microphone and a voice recognition device. In this case, the operation unit 52 performs voice recognition on spoken words and inputs character string information of the recognition result to the user terminal 50. The operation unit 52 may be configured in any manner as long as it is configured to be able to input instructions from a patient, etc. to the user terminal 50.

[0054] The display unit 53 is an image display device such as a liquid crystal display or an organic EL display. The display unit 53 displays image data and character data. The display unit 53 may be an interface for connecting the image display device to the user terminal 50. In this case, the display unit 53 generates a video signal for displaying the image data and character data, and outputs the video signal to the image display device connected to the display unit 53.

[0055] The information acquisition unit 54 acquires information required for transferring the token. The information acquisition unit 54 may be used, for example, to acquire information (e.g., a wallet address) indicating the destination of the token. In this case, for example, when the information indicating the destination of the token is represented as an image of coded information in a predetermined format (e.g., a barcode or a two-dimensional code), the information acquisition unit 54 may be configured using a camera (image sensor) for capturing the image. For example, when the information indicating the destination of the token is represented as a wireless signal in a predetermined format, the information acquisition unit 54 may be configured using a wireless communication device (e.g., an RFID reader, a Bluetooth (registered trademark) device) for receiving the wireless signal.

[0056] The information acquisition unit 54 may be used, for example, to transmit and receive the electronic prescription data itself. In this case, the information acquisition unit 54 may receive the electronic prescription data itself from a source device (e.g., the medical system 30) by wired communication or wireless communication, or may transmit the electronic prescription data itself to a destination device (e.g., the medicine management system 40).

[0057] The storage unit 55 is configured using a storage device such as a magnetic hard disk device, a semiconductor storage device, etc. The storage unit 55 functions as an electronic prescription storage unit 551, an authentication information storage unit 552, and a key information storage unit 553.

[0058] The electronic prescription storage unit 551 stores data of an electronic prescription. The authentication information storage unit 552 stores authentication information used to authenticate an operator who operates the user terminal 50. The authentication information storage unit 552 stores, for example, authentication information of a user who has a legitimate authority to operate the user terminal 50. The authentication information storage unit 552 may store, for example, a user ID and a password issued in advance to the user. The authentication information storage unit 552 may store authentication information for two-factor authentication. The key information storage unit 553 stores information on an encryption key used for transferring a token. The key information storage unit 553 may store, for example, encryption key information. The key information storage unit 553 may store, for example, encryption key information and public key information corresponding to the encryption key information.

[0059] The control unit 56 is configured using a processor such as a CPU and a memory. The control unit 56 functions as an authentication control unit 561, an electronic prescription management unit 562, and a token transfer control unit 563 by the processor executing a program. All or part of the functions of the control unit 56 may be realized using hardware such as ASIC, PLD, and FPGA. The above program may be recorded on a computer-readable recording medium. The computer-readable recording medium is, for example, a portable medium such as a flexible disk, an optical magnetic disk, a ROM, a CD-ROM, or a semiconductor storage device (e.g., SSD), or a storage device such as a hard disk or a semiconductor storage device built into a computer system. The above program may be transmitted via an electric communication line.

[0060] The authentication control unit 561 authenticates a person who is attempting to operate the user terminal 50. The authentication control unit 561 authenticates whether or not a person who is attempting to operate the user terminal 50 has legitimate authority, based on the authentication information stored in the authentication information storage unit 552. The user terminal 50 may be configured so that only those authenticated by the authentication control unit 561 are allowed to operate the user terminal 50.

[0061] The electronic prescription management unit 562 performs a process of managing an electronic prescription. The electronic prescription management unit 562 may acquire electronic prescription data from the electronic prescription management device 10 via the network 90 based on, for example, information recorded in a token acquired from the medical system 30. More specifically, the electronic prescription management unit 562 may acquire electronic prescription data by accessing specific identification information (such as a URI) recorded in the token. The electronic prescription management unit 562 may acquire electronic prescription data by other methods. For example, the electronic prescription management unit 562 may receive electronic prescription data from another device (for example, the medical system 30 or the medicine management system 40) via wireless communication or wired communication. In this case, the electronic prescription management unit 562 may receive electronic prescription data via the information acquisition unit 54. For example, the exchange of electronic prescription data may be performed using short-range communication such as Bluetooth (registered trademark), or may be performed by communication via a network such as WiFi (registered trademark) or the Internet. The electronic prescription management unit 562 may display the contents of the acquired electronic prescription on the display unit 53. The electronic prescription management unit 562 may record the data of the acquired electronic prescription in the electronic prescription storage unit 551.

[0062] The token transfer control unit 563 performs a process of receiving the token of the electronic prescription acquired by the electronic prescription management unit 562 from a legitimate device (e.g., the medical system 30 or the medicine management system 40) and a process of transferring the token to a legitimate device (e.g., the medicine management system 40). The process of the token transfer control unit 563 may be configured similarly to, for example, the token transfer control unit 363 of the medical system 30 or the token transfer control unit 463 of the medicine management system 40.

[0063] FIG. 6 is a sequence chart showing a specific example of the process flow when an electronic prescription is issued. First, authentication processing is executed in the medical system 30 (step S101). The subsequent processing of the medical system 30 is processing according to the operation performed by a person authenticated as a person with legitimate authority by the authentication processing. When information regarding the prescription is input to the medical system 30, the medical system 30 generates an electronic prescription (step S102). The medical system 30 transmits request data (electronic prescription registration request) indicating that the electronic prescription is to be registered to the electronic prescription management device 10 (step S103).

[0064] When the electronic prescription management device 10 receives an electronic prescription registration request from a valid medical system 30, it registers the requested electronic prescription data. The electronic prescription management device 10 issues identification information (e.g., a URI) of the registered electronic prescription and transmits the identification information to the medical system 30 that requested the registration.

[0065] The medical system 30 requests the history management system 20 to generate a token including the identification information transmitted from the electronic prescription management device 10 (step S105). In this request, the medical system 30 may transmit a token generation request including, for example, a URI to the history management system 20. The history management system 20 issues the token requested by the medical system 30 (step S106). Then, the history management system 20 registers the token issued in response to the request (step S107).

[0066] FIG. 7 is a sequence chart showing a specific example of the process flow when the token of the electronic prescription is transferred from the medical system 30 to the user terminal 50. First, the authentication process is executed in the medical system 30 (step S201). The subsequent process of the medical system 30 is a process according to an operation performed by a person authenticated as a person having legitimate authority by the authentication process. In the medical system 30, an operation is performed to instruct the history management system 20 to transfer the token to the patient's user terminal 50 (step S202). In response to the operation, the medical system 30 requests the history management system 20 to transfer the token to the user terminal 50 (step S203). In response to this request, the history management system 20 generates information indicating that the token has been transferred from the medical system 30 to the user terminal 50 (data indicating history: token transfer history information) and records the generated token transfer history information (step S204). The medical system 30 transmits the data of the electronic prescription to the user terminal 50 (step S205). When the user terminal 50 receives the electronic prescription data, the user terminal 50 records the received electronic prescription data in the user terminal 50 (step S206).

[0067] FIG. 8 is a sequence chart showing a specific example of the process flow when the token of the electronic prescription is transferred from the user terminal 50 to the drug management system 40. First, the authentication process is executed in the user terminal 50 (step S301). The process of the user terminal 50 thereafter is a process according to an operation performed by a person authenticated as a person having legitimate authority by the authentication process. In the user terminal 50, an operation is performed to instruct the history management system 20 to transfer the token to the drug management system 40 (step S302). In response to the operation, the user terminal 50 requests the history management system 20 to transfer the token to the drug management system 40 (step S303). In response to this request, the history management system 20 generates information (data indicating history: token transfer history information) indicating that the token has been transferred from the user terminal 50 to the drug management system 40, and records the generated token transfer history information (step S304).

[0068] The medicine management system 40 requests the history management system 20 for information on the token (e.g., electronic prescription identification information) transferred from the user terminal 50 (step S305). The history management system 20 transmits the requested token information to the medicine management system 40 (step S306). The medicine management system 40, which has received the token information, acquires the electronic prescription data based on the received information. For example, the medicine management system 40 transmits information requesting the electronic prescription data to the electronic prescription management device 10 based on the electronic prescription identification information (e.g., URI) (step S307). When the electronic prescription management device 10 receives the information requesting the electronic prescription data, it transmits the requested electronic prescription data to the requesting device (the medicine management system 40) (step S308). The medicine management system 40, which has received the electronic prescription data, records and displays the contents of the received electronic prescription (step S309). The process of acquiring the electronic prescription data in steps S305 to S309 may be realized by transmitting the electronic prescription data from the user terminal 50 to the medicine management system 40 via wireless communication, wired communication, or the like.

[0069] FIG. 9 is a sequence chart showing a specific example of the process flow when a medicine is dispensed to a user according to an electronic prescription. First, a pharmacist dispenses medicine to a user according to the contents of the electronic prescription displayed in the medicine management system 40 in step S309 of FIG. 8. Then, the dispensed medicine is handed over to the user (step S400). After that, an authentication process is executed in the medicine management system 40 (step S401). The subsequent process of the medicine management system 40 is a process according to an operation performed by a person who has been authenticated as a person having legitimate authority by the authentication process. Note that such an authentication process may be performed before the process of S307 in FIG. 8. In that case, the process of step S401 in FIG. 9 may be omitted.

[0070] In the pharmaceutical management system 40, an operation is performed to instruct the history management system 20 to transfer the token to the user terminal 50 of the user who has received the dispensed pharmaceutical (step S402). In response to the operation, the pharmaceutical management system 40 requests the history management system 20 to transfer the token to the user terminal 50 (step S403). In response to this request, the history management system 20 generates information indicating that the token has been transferred from the pharmaceutical management system 40 to the user terminal 50 (data indicating history: token transfer history information), and records the generated token transfer history information (step S404).

[0071] In response to receiving delivery of the medicine, the user of the user terminal 50 operates the user terminal 50 to input that the medicine has been received. In response to this input, the token delivery control unit 563 of the user terminal 50 instructs the history management system 20 to amortize the token delivered to the user terminal 50 (step S405). When the history management system 20 receives an instruction to amortize the token, it performs amortization processing on the token instructed to be amortized (step S406). The history management system 20 may perform the amortization processing by, for example, recording information indicating that the token has been amortized.

[0072] According to the management system 100 configured in this manner, it is possible to improve the convenience of prescribing medicines. Specifically, it is as follows. In the management system 100, an electronic prescription is issued for a medicine prescription. The data of the electronic prescription itself is recorded in the electronic prescription management device 10. Data required to obtain the electronic prescription data from the electronic prescription management device 10 (e.g., identification information such as a URI) is handled as a token. The token data is managed in the history management system 20 independently of the electronic prescription data. History information regarding the transfer of the token is recorded in the history management system 20. This makes it possible to guarantee the legitimacy of the transfer of the electronic prescription data. For example, it is possible to confirm that the user for whom the medicine is prescribed is a legitimate user (i.e., a user who has been prescribed the medicine at a medical institution).

[0073] The token may also include a hash value of the electronic prescription data. In this case, when dispensing medicines in the medicine management system 40, it is possible to check whether the acquired electronic prescription data has been tampered with. Therefore, in a system using an electronic prescription, it is possible to more accurately dispense medicines. Specifically, the following process is performed. The electronic prescription management unit 462 acquires electronic prescription data and calculates a hash value based on a predetermined hash algorithm. The electronic prescription management unit 462 compares the hash value included in the token with the calculated hash value. If the hash values ​​match, the electronic prescription management unit 462 determines that the acquired electronic prescription data has not been tampered with. In this case, the electronic prescription management unit 462 may output a determination result that the data has not been tampered with to the display unit 43. On the other hand, if the hash values ​​do not match, the electronic prescription management unit 462 determines that the acquired electronic prescription data has been tampered with. In this case, the electronic prescription management unit 462 may output information indicating an error to the display unit 43. Such processing may be performed by the electronic prescription management section 562 of the user terminal 50, or by the agent terminal 60.

[0074] (Modification) The transmission of the token may be substantially performed by transmitting history information indicating the transfer of the token. For example, such processing may be performed by registering information indicating that the token is transferred from a wallet address corresponding to the private key of the transmission source device to a wallet address corresponding to the public key of the transmission destination device in the history management system 20 configured by the blockchain. In this case, the transmission destination device may obtain information indicating the contents of the transferred token by accessing the history management system 20 using the private key of the transmission destination device. In steps S205 and S206 of Figure 7, the process of the user terminal 50 acquiring electronic prescription data may be realized, for example, as in the processes of S305 to S309 shown in Figure 8, in which the user terminal 50 acquires token information and uses that information (e.g., identification information of the electronic prescription) to access the electronic prescription management device 10 to receive the electronic prescription data.

[0075] [Second embodiment] 10 is a schematic block diagram showing a system configuration of a second embodiment of the management system 100 of the present invention. The following mainly describes the management system 100 in the second embodiment, focusing on the differences from the management system 100 in the first embodiment.

[0076] The management system 100 in the second embodiment includes an electronic prescription management device 10, a history management system 20, a medical system 30, a medicine management system 40, a user terminal 50, and an agent terminal 60. The electronic prescription management device 10, the history management system 20, the medical system 30, the medicine management system 40, the user terminal 50, and the agent terminal 60 communicate with each other via a network 90.

[0077] The agent terminal 60 is an information device operated by an agent. The agent receives the medicine prescribed for the patient as the patient's agent, and then hands the medicine over to the patient. The agent terminal 60 is configured in the same manner as the user terminal 50, except that it is operated by an agent. In other words, the explanation of the agent terminal 60 is equivalent to the explanation of the user terminal 50 above, with "user" replaced by "agent."

[0078] FIG. 11 is a sequence chart showing a specific example of the process flow when the token of the electronic prescription is transferred from the user terminal 50 to the proxy terminal 60. First, the authentication process is executed in the user terminal 50 (step S501). The process of the user terminal 50 after this is a process according to the operation performed by the person authenticated as a person having legitimate authority by the authentication process. In the user terminal 50, an operation is performed to instruct the history management system 20 to transfer the token to the proxy terminal 60 (step S502). In response to the operation, the user terminal 50 requests the history management system 20 to transfer the token to the proxy terminal 60 (step S503). In response to this request, the history management system 20 generates information indicating that the token has been transferred from the user terminal 50 to the proxy terminal 60 (data indicating the history: token transfer history information) and records the generated token transfer history information (step S504). The user terminal 50 transmits the data of the electronic prescription to the proxy terminal 60 (step S505). When the proxy terminal 60 receives the electronic prescription data, the proxy terminal 60 records the received electronic prescription data in its own device (step S506).

[0079] FIG. 12 is a sequence chart showing a specific example of the process flow when the token of the electronic prescription is transferred from the proxy terminal 60 to the medicine management system 40. First, the proxy terminal 60 executes an authentication process (step S601). The process of the proxy terminal 60 thereafter is a process according to an operation performed by a person (a legitimate proxy) who has been authenticated as a person having legitimate authority by the authentication process. An operation is performed in the proxy terminal 60 to instruct the history management system 20 to transfer the token to the medicine management system 40 (step S602). In response to the operation, the proxy terminal 60 requests the history management system 20 to transfer the token to the medicine management system 40 (step S603). In response to this request, the history management system 20 generates information (data indicating history: token transfer history information) indicating that the token has been transferred from the proxy terminal 60 to the medicine management system 40, and records the generated token transfer history information (step S604). The subsequent processes are the same as steps S305 to S309 in FIG. 8, and therefore will not be described.

[0080] FIG. 13 is a sequence chart showing a specific example of the process flow when a medicine is dispensed to a representative according to an electronic prescription. First, a pharmacist dispenses medicine to a user according to the contents of the electronic prescription displayed on the medicine management system 40 in step S609 of FIG. 12. Then, the dispensed medicine is handed over to the representative of the user (step S700). After that, an authentication process is executed in the medicine management system 40 (step S701). The subsequent process of the medicine management system 40 is a process according to an operation performed by a person who has been authenticated as a person having legitimate authority by the authentication process. Note that such an authentication process may be performed before the process of S607 in FIG. 12. In that case, the process of step S701 in FIG. 13 may be omitted.

[0081] In the medicine management system 40, an operation is performed to instruct the history management system 20 to transfer the token to the proxy terminal 60 of the proxy who received the dispensed medicine (step S702). In response to the operation, the medicine management system 40 requests the history management system 20 to transfer the token to the proxy terminal 60 (step S703). In response to this request, the history management system 20 generates information indicating that the token has been transferred from the medicine management system 40 to the proxy terminal 60 (data indicating history: token transfer history information), and records the generated token transfer history information (step S704).

[0082] 14 is a sequence chart showing a specific example of the process flow when a medicine received by an agent is handed over to a user. First, the medicine is handed over from the agent to the user (step S800). Then, an authentication process is executed in the agent terminal 60 (step S801). The process of the agent terminal 60 thereafter corresponds to the operation performed by a person who has been authenticated as having legitimate authority by the authentication process.

[0083] An operation is performed on the proxy terminal 60 to instruct the history management system 20 to transfer the token to the user terminal 50 of the user who has received the medicine (step S802). In response to the operation, the proxy terminal 60 requests the history management system 20 to transfer the token to the user terminal 50 (step S803). In response to this request, the history management system 20 generates information indicating that the token has been transferred from the proxy terminal 60 to the user terminal 50 (data indicating history: token transfer history information), and records the generated token transfer history information (step S804).

[0084] In response to receiving delivery of the medicine from the proxy, the user of the user terminal 50 operates the user terminal 50 to input that the medicine has been received. In response to this input, the token delivery control unit 563 of the user terminal 50 instructs the history management system 20 to amortize the token delivered to the device (step S805). When the history management system 20 receives an instruction to amortize the token, it performs amortization processing for the token instructed to be amortized (step S806). The history management system 20 may perform the amortization processing by, for example, recording information indicating that the token has been amortized.

[0085] According to the management system 100 in the second embodiment configured as described above, it is possible to improve the convenience of prescribing medicines. Specifically, it is as follows. In the management system 100, regarding the prescription of medicines, a proxy can receive medicines on behalf of the patient himself / herself. At that time, it is possible to easily determine whether the proxy is a legitimate proxy according to the history information indicating that the token has been handed over to the proxy terminal 60. That is, it may be determined that the proxy is a legitimate proxy according to the fact that a token including identification information (identification information such as a URI) required to acquire the data of the electronic prescription has been handed over to the proxy terminal 60. In addition, by accessing the history management system 20 and checking the history of the handover of the token, it is possible to more accurately determine whether the proxy is a legitimate proxy.

[0086] (Modification) The token may be substantially transmitted by transmitting the history information indicating the transfer of the token. This configuration may be configured similarly to the first embodiment.

[0087] In steps S505 and S506 of Figure 11, the process of the proxy terminal 60 acquiring electronic prescription data may be realized, for example, as in the processes of S605 to S609 shown in Figure 12, in which the proxy terminal 60 acquires token information and uses that information (e.g., identification information of the electronic prescription) to access the electronic prescription management device 10 to receive the electronic prescription data.

[0088] FIG. 15 is a diagram showing a configuration of a modified example of the management system 100. The management system 100 of the modified example includes an authentication and authorization system 70. Such an authentication and authorization system 70 may be included in the management system 100 of the first embodiment, or in the management system 100 of the second embodiment. The authentication and authorization system 70 is configured using one or more information processing devices. The authentication and authorization system 70 stores in advance authentication information used by the user of the user terminal 50, the agent of the agent terminal 60, and the like. Any information may be used for the authentication information. For example, a combination of an email address (ID) and a password used by the user or agent may be used as the authentication information. The authentication and authorization system 70 may store a user identifier assigned to each user in association with the authentication information. The authentication and authorization system 70 also stores information about the attributes of the users. Specific examples of the information about the attributes include name, sex, and area of ​​residence (country, prefecture, city, town, village, zip code, etc.). An existing authentication protocol may be applied to the authentication and authorization system 70. For example, the authentication and authorization system 70 may apply OIDC (OpenID Connect), OAuth, or another authentication protocol.

[0089] FIG. 16 is a diagram showing a specific example of authentication processing in the modified example. In the first and second embodiments, for example, authentication processing as shown in FIG. 16 may be executed in the authentication processing of step S301 shown in FIG. 8 or the authentication processing of step S401 shown in FIG. 9. The processing shown in FIG. 16 will be described below. First, when an instruction to access the drug management system 40 is input to the user terminal 50 (step S901), the user terminal 50 accesses the drug management system 40 (step S902). When the drug management system 40 is accessed by the user terminal 50, it redirects the user terminal 50 that is the access source to the authentication authorization system 70. The authentication authorization system 70 transmits data of an authentication screen to the user terminal 50 (step S903).

[0090] The user terminal 50 displays the authentication screen received from the authentication authorization system 70 (step S904). The authentication screen includes characters and images that request the user to input authentication information. The user inputs the authentication information to the user terminal 50 (step S905). The user terminal 50 transmits the input authentication information to the authentication authorization system 70 (step S906). The authentication authorization system 70 uses pre-stored authentication information to determine whether the received authentication information is valid. If the received authentication information matches the pre-stored authentication information, the authentication authorization system 70 authenticates the user terminal 50 that transmitted the information (step S907). The authentication authorization system 70 returns authentication response data indicating the authentication result to the medicine management system 40 by redirection (step S908). At this time, the authentication authorization system 70 distributes a code for accessing the token end point.

[0091] Thereafter, a token request and a response are transmitted and received between the drug management system 40 and the token end point of the authentication and authorization system 70. At this time, information stored as user attributes in the authentication and authorization system 70 is distributed. Thereafter, the drug management system 40 transmits a result of the authentication process to the user terminal 50 (step S909).

[0092] When configured in this manner, the authentication control unit 461 authenticates the user of the user terminal 50 in cooperation with the authentication authorization system 70 as described above. Although the authentication process of the medicine management system 40 has been described as an example in FIG. 16, the authentication authorization system 70 may be used in authentication processes in other devices. For example, the authentication authorization system 70 may be applied in authentication processes in the medical system 30. More specifically, the authentication authorization system 70 may be used in the process of step S101 shown in FIG. 6. For example, the authentication authorization system 70 may be applied to authentication of a user in the user terminal 50.

[0093] Although an embodiment of the present invention has been described in detail above with reference to the drawings, the specific configuration is not limited to this embodiment, and designs that do not deviate from the gist of the present invention are also included. [Explanation of symbols]

[0094] 100...management system, 10...electronic prescription management device, 11...communication unit, 12...storage unit, 121...electronic prescription storage unit, 13...control unit, 131...information management unit, 132...information provision unit, 20...history management system, 30...medical system, 31...communication unit, 32...operation unit, 33...display unit, 34...information acquisition unit, 35...storage unit, 351...electronic prescription storage unit, 352...authentication information storage unit, 353...key information storage unit, 36...control unit, 361...authentication control unit, 362...electronic prescription issuance unit, 363...token transfer control unit, 40...medicine management system, 41...communication unit, 42...operation unit, 43...display unit, 44...information acquisition unit, 45...storage unit, 451...electronic prescription storage unit, 452...authentication information storage unit, 453...key information storage unit, 46...control unit, 461...authentication control unit, 462...electronic prescription management unit, 463...token transfer control unit, 50...user terminal, 51...communication unit, 52...operation unit, 53...display unit, 54...information acquisition unit, 55...storage unit, 551...electronic prescription storage unit, 552...authentication information storage unit, 553...key information storage unit, 56...control unit, 561...authentication control unit, 562...electronic prescription management unit, 463...token transfer control unit, 60...agent terminal

Claims

1. An issuing unit that accepts operations by a medical professional or a patient, issues electronic prescription data for medicines prescribed to the patient, and instructs a history management system, which is a device different from the medical system, to issue a token that is information on the subject of delivery related to the electronic prescription and records the history of delivery of the token. A delivery control unit that instructs the history management system to deliver the token to a terminal of a person who receives the medicine; A medical system that has:

2. The medical system according to claim 1 , wherein the history management system is configured using a blockchain.

3. The medical system according to claim 1 or 2, wherein the transfer control unit instructs the history management system to transfer the token to a terminal among the terminals that has been authenticated by an authentication authorization system that performs authentication using authentication information.

4. The medical system according to any one of claims 1 to 3, wherein the transfer control unit instructs the history management system to transfer the token to an agent terminal, which is one of the terminals and to which the token has been transferred from a user terminal used by the patient.

5. The medical system according to claim 4 , wherein the history management system records information indicating that the token has been handed over to the agent terminal.

6. The medical system of claim 1 , wherein the token comprises a hash value of data of the electronic prescription.

7. A computer program for causing a computer to function as the medical system according to any one of claims 1 to 6.

Images