JP2018148490A - Information management system, program and recording medium - Google Patents

Abstract

PROBLEM TO BE SOLVED: To share medical information while maintaining security via no dedicated network among a plurality of medical institutions.SOLUTION: An information management system comprises: a first acquiring section that acquires a first encryption key; a first encrypting section that encrypts user information by use of the first encryption key; a second acquiring section that encrypts a second encryption key; a second encrypting section that encrypts information by use of the second encryption key, the information specifying a storage place for the user information encrypted by the first encrypting section; a management section that stores information identifying the user and information specifying the encrypted storage place, in association with each other; a first decrypting section that acquires information specifying the encrypted storage place on the basis of the information identifying the user and decrypts information specifying the storage place thus encrypted; and a second decrypting section that acquires the encrypted user information on the basis of information specifying the decrypted storage place and decrypts the user information thus encrypted.SELECTED DRAWING: Figure 3

Description

  The present invention relates to an information management system, a program, and a recording medium.

  2. Description of the Related Art Conventionally, a technique in which a plurality of medical institutions share medical records, image data (X-ray photographs, MRI (Magnetic Resonance Imaging) images, etc.), prescription data, etc. as data related to patients using a server via a network. Is already known. In particular, when introducing a patient to another medical facility, the medical record and medical image are output to paper or film, etc., and the patient's diagnosis contents and medical image are used at the other medical facility without bringing the patient to the patient. For this purpose, a system capable of transmitting and receiving medical information such as an electronic medical record and a medical image from a client terminal provided in a medical facility to a server connected via a network having a security function is disclosed (for example, a patent). Reference 1).

  However, in the conventional technology, since medical information needs to be stored in a server, there is a problem that the system can be used only in a medical facility that can be connected to the same dedicated network as the server for security.

  The present invention has been made in view of the above points, and an object of the present invention is to share medical information with a plurality of medical institutions while maintaining security without using a dedicated network.

  In order to solve the above problem, an information management system for managing user information includes a first acquisition unit that acquires a first encryption key and a first encryption unit that encrypts user information using the first encryption key. The second encryption unit, a second acquisition unit that acquires a second encryption key, and information that specifies a storage location of the user information encrypted by the first encryption unit. Based on the second encryption unit that encrypts with a key, the information that identifies the user, the management unit that stores the encrypted information that specifies the storage location, and the information that identifies the user Information for specifying the encrypted storage location, and decrypting the encrypted information for specifying the storage location, and information for specifying the decrypted storage location Based on the encrypted user information. To have a second decoding unit for decoding the information of the encrypted the user.

  Medical institutions can share medical information while maintaining security without using a dedicated network.

It is a figure which shows the structural example of the information management system 4000 in embodiment of this invention. It is a figure which shows the hardware structural example of the server 1001 in embodiment of this invention. It is a figure which shows the function structural example of the information management system 4000 in embodiment of this invention. It is a sequence diagram for demonstrating an example of the process sequence which shares medical information in embodiment of this invention.

  Hereinafter, embodiments of the present invention will be described with reference to the drawings.

  FIG. 1 is a diagram showing a configuration example of an information management system 4000 in the embodiment of the present invention. In FIG. 1, the information management system 4000 includes a hospital A 1000a, a hospital B 1000b, a cloud 2000, and a wide area network 3000. The hospital A 1000a includes a server 1001a. The hospital B 1000b includes a server 1001b. The cloud 2000 includes a plurality of server computers.

  The hospital A 1000a has a network composed of a LAN (Local Area Network) or the like. The server 1001 a is installed in the network of the hospital A 1000 a and is connected to the cloud 2000 via the wide area network 3000. The server 1001a may be further connected to the wide area network 3000 and the cloud 2000 via a firewall. The hospital B 1000b has a network composed of a LAN or the like, like the hospital A 1000a. The server 1001b is installed in the network of the hospital B 1000b and is connected to the cloud 2000 via the wide area network 3000. The server 1001b may be further connected to the cloud 2000 via a firewall. The firewall is a device installed to protect the network installed in the hospital A 1000a or the hospital B 1000b from the security threat of the wide area network 3000.

  The cloud 2000 is a group of server computers connected to the wide area network 3000. The cloud 2000 includes a plurality of server computers, communicates with the server 1001a or the server 1001b, and performs processing related to medical information and storage or management of medical information.

  The wide area network 3000 is, for example, the Internet and is a public network. Since the wide area network 3000 is not a dedicated line but a public line, if security measures are not taken, there is a possibility of threats such as tampering, spoofing, and wiretapping.

  A server 1001a and a server 1001b (hereinafter referred to as “server 1001” when they are not distinguished from each other) are server computers. The server 1001 communicates with the cloud 2000 to perform processing related to input / output with the user, processing related to medical information, storage or management of medical information, and the like.

  As shown in FIG. 1, there are the patient's public and private keys and the hospital's public and private keys. “Public” shown in FIG. 1 indicates a public key, and “secret” indicates a secret key. The public key encrypts the information, and the encrypted information is decrypted with the corresponding private key. The processing flow of the information management system 4000 is as follows (details will be described later). 1. The hospital A server encrypts the medical information with the public key of the patient 1 and stores it in the hospital A server. 2. The server of hospital A encrypts the storage location of medical information with the public key of hospital B and stores it in the cloud. 3. Patient 1 is transferred to hospital B with a secret key. 4). Upon receiving the patient 1's transfer, the hospital B server obtains the encrypted storage location from the cloud and decrypts it with the private key it owns. 5. The server of hospital B obtains the encrypted medical information from the server of hospital A based on the decrypted storage location, decrypts it with the private key possessed by patient 1, and obtains decrypted medical information. As shown in FIG. 1, a “patient ID” for identifying a patient is stored in association with a medical information storage location stored in the cloud 2000.

  FIG. 2 is a diagram illustrating a hardware configuration example of the server 1001 according to the embodiment of the present invention. 2 includes a CPU (Central Processing Unit) 1101, a network interface 1102, an input / output interface 1103, an auxiliary storage device 1104, a memory device 1105, and the like that are connected to each other.

  A program for realizing processing in the server 1001 is stored in the auxiliary storage device 1104. The auxiliary storage device 1104 stores the installed program and also stores necessary files and data. The auxiliary storage device 1104 may be a computer-readable recording medium.

  The memory device 1105 reads the program from the auxiliary storage device 1104 and stores it when there is an instruction to start the program. The CPU 1101 executes functions related to the server 1001 in accordance with a program stored in the memory device 1105.

  The network interface 1102 is a wired or wireless interface for communicating with the server 2001 or the like.

  The input / output interface 1103 is an interface for connecting to various input / output devices such as USB (Universal Serial Bus) devices, hardware keys, status notification LEDs, and liquid crystal displays.

  Note that the server computer included in the cloud 2000 and the patient information reading device 105 shown in FIG. 3 may also have the same hardware configuration as in FIG.

FIG. 3 is a diagram illustrating a functional configuration example of the information management system 4000 according to the embodiment of the present invention. A server 1001 illustrated in FIG. 3 includes a communication unit 101, a data management unit 102, a medical information management database 103, and a data encryption / decryption unit 104. Each of these units is realized by processing that one or more programs installed in the server 1001 cause the CPU 1101 to execute. In addition, the medical information management database 103 can be realized using the auxiliary storage device 1104 or the memory device 1105 or the like. Further, a patient information reading device 105 is connected to the server 1001. The patient information reading device 105 is a device having a function of reading patient information connected to the server 1001 via the input / output interface 1103. The patient information reading device 105 may be configured as a function built in the server 1001.

  The communication unit 101 communicates with the cloud 2000 or another hospital server 1001.

  The data management unit 102 inputs / outputs medical information to / from the medical information management database 103 via the communication unit 101.

  The medical information management database 103 receives input / output of medical information from the data management unit 102 and stores the information. The information may be encrypted.

  The data encryption / decryption unit 104 encrypts and decrypts medical information. The patient's public key or secret key is used for the encryption and decryption. In addition, the data encryption / decryption unit 104 encrypts and decrypts information specifying a location where medical information is stored (hereinafter referred to as a medical information storage location). The public key or private key of the hospital is used for the encryption and decryption.

  The patient information reader 105 reads a public key or a private key owned by a patient.

  A cloud 2000 shown in FIG. 3 includes one or a plurality of servers 2001, and includes a communication unit 201, a data management unit 202, and a transfer information management database 203.

  The communication unit 201 communicates with the server 1001 installed in the hospital.

  The data management unit 202 performs processing related to a medical information storage location that is transmitted from the server 1001 installed in the hospital or transmitted to the server 1001 via the communication unit 201.

  The transfer information management database 203 receives the input of the medical information storage location from the data management unit 202 and stores the medical information storage location. The medical information storage location may be encrypted.

  FIG. 4 is a sequence diagram for explaining an example of a processing procedure for sharing medical information according to the embodiment of the present invention. With the sequence shown in FIG. 4, the hospital A and the destination hospital B can share the medical information of the patients who are transferred while maintaining security without using a dedicated network. In addition, the medical information of the patient to be transferred is stored in the server 1001a. The patient also has a public key and a secret key. In addition, the server 1001b of the hospital B as the transfer destination has a public key and a secret key.

  Here, in order to distinguish the functional configuration included in the server 1001a or the server 1001b, the server 1001a includes a communication unit 101a, a data management unit 102a, a medical information management database 103a, a data encryption / decryption unit 104a, and a patient information reading device 105a. The server 1001b includes a communication unit 101b, a data management unit 102b, a medical information management database 103b, a data encryption / decryption unit 104b, and a patient information reading device 105b.

  The following steps S1 to S5 shown in FIG. 4 correspond to the process at the hospital A as the transfer source.

  In step S1, the patient information reader 105a acquires the patient's public key and outputs it to the data encryption / decryption unit 104a. The acquisition of the public key may be performed, for example, by the patient information reading device 105a reading the recording medium or the storage area of the smartphone possessed by the patient, or by communication via the wide area network 3000 because it is a public key. It may be done. Further, the patient information reading device 105a may register the use history of the patient's public key in the medical information management database 103 by storing the date and time when the public key is acquired in association with the public key. The server 1001b may acquire the use history of the registered patient's public key from the server 1001a in the hospital B as the transfer destination and confirm the authenticity of the medical information encrypted by the public key.

  Subsequently, the data management unit 102a encrypts the medical information of the patient using the public key by the data encryption / decryption unit 104a. The data management unit 102a stores the encrypted medical information in the medical information management database 103a (S2). Further, the data management unit 102a may assign an expiration date to the encrypted medical information. When the expiration date has passed, the encrypted medical information is not used, so the security in managing the medical information is improved.

  In step S3, the data encryption / decryption unit 104a acquires the public key of the hospital B as the transfer destination from the server 1001b via the communication unit 101a. At this time, the public key is received via the wide area network 3000, but since it is a public key, there is no security problem. The public key may be acquired by a method other than communication such as causing the server 1001a to read the recording medium. The data encryption / decryption unit 104 a may store the public key in the medical information management database 103. As a result, even if it becomes necessary to use the public key again later, the data encryption / decryption unit 104a does not need to obtain the server 1001b again. An expiration date may be given to the public key of hospital B. When the expiration date has passed, the encryption using the public key is not performed, so that the security for managing the public key of the hospital B is improved.

  Subsequently, the data encryption / decryption unit 104a encrypts the medical information storage location indicating the location where the encrypted medical information is stored using the public key of the hospital B (S4). In step S4, the data management unit 102a issues a patient ID for identifying a patient corresponding to the encrypted medical information, and manages the patient ID in association with the encrypted medical information storage location. In addition, issue of patient ID is not restricted to step S4, You may perform in any of step S1 to step S3. The patient ID may be notified to the patient.

  Subsequently, the data management unit 102a transmits the patient ID and the encrypted medical information storage location issued in step S4 to the cloud 2000 via the communication unit 101a. The data management unit 202 of the cloud 2000 stores the information received from the communication unit 201 in the transfer information management database 203 (S5).

  In step S6, the patient is transferred to the hospital B, and transfer of medical information related to the transfer is started.

  The following steps S7 to S11 shown in FIG. 4 correspond to the processing in the hospital B as the transfer destination.

  In step S7, the data management unit 102b makes an inquiry to the cloud 2000 based on the patient ID via the communication unit 101b, and acquires the encrypted medical information storage location stored in step S5. The patient ID may be received from the patient who has been transferred to the hospital, or may be received by other methods such as receiving from the server 1001a. At this time, in the cloud 2000, the data management unit 202 reads the encrypted medical information storage location from the transfer information management database 203 and transmits the encrypted medical information storage location to the server 1001b via the communication unit 201. .

  Subsequently, the data encryption / decryption unit 104b decrypts the medical information storage location using the private key of the hospital B possessed in advance (S8).

  Subsequently, based on the decrypted medical information storage location, the data management unit 102b acquires the encrypted medical information from the server 1001a via the communication unit 101b and stores it in the medical information management database 103b (S9). . Since the medical information is encrypted, security is maintained even if it is received via the wide area network 3000. At this time, in the server 1001a, the data management unit 102a reads the encrypted medical information from the medical information management database 103a, and transmits the encrypted medical information to the server 1001b via the communication unit 101a.

  In step S10, the patient information reader 105b acquires the patient's secret key. The receipt of the secret key may be performed, for example, when the patient information reading device 105b reads a recording medium possessed by the patient or a storage area of a smartphone. The secret key is output to the data encryption / decryption unit 104b.

  Subsequently, the data encryption / decryption unit 104b decrypts the encrypted medical information using the patient's secret key (S11). The data management unit 102b stores the decrypted medical information in the medical information management database 103b.

  With the above procedure, the processing procedure for sharing medical information between the hospital A as the transfer source and the hospital B as the transfer destination is completed.

  As described above, according to the embodiment of the present invention, the information management system 4000 allows the patient to be transferred to the hospital A and the hospital B to be transferred while maintaining security without using a dedicated network. Medical information can be shared. That is, a plurality of medical institutions can share medical information while maintaining security without using a dedicated network.

  In the embodiment of the present invention, the data encryption / decryption unit 104a is an example of a first encryption unit, a second encryption unit, and a second acquisition unit. The data management unit 102 is an example of a management unit. The data encryption / decryption unit 104b is an example of a first decryption unit and a second decryption unit. The patient information reading device 105a is an example of a first acquisition unit. The medical information management database is an example of a first storage unit. The hospital transfer information management database 203 is an example of a second storage unit. The server 1001a and the cloud 2000 are examples of a plurality of servers. The server 1001b is an example of a computer. The patient's public key is an example of a first encryption key. The public key of the hospital is an example of a second encryption key.

  As mentioned above, although the Example of this invention was explained in full detail, this invention is not limited to such specific embodiment, In the range of the summary of this invention described in the claim, various deformation | transformation・ Change is possible.

1000a Hospital A
1000b Hospital B
1001a, b Server 2000 Cloud 3000 Wide area network 4000 Information management system 1101 CPU
1102 Network interface 1103 Input / output interface 1104 Auxiliary storage device 1105 Memory device 101 Communication unit 102 Data management unit 103 Medical information management database 104 Data encryption / decryption unit 105 Patient information reader 201 Communication unit 202 Data management unit 203 Transfer information management database

JP 2002-269243 A

Claims (8)

An information management system for managing user information,
A first acquisition unit for acquiring a first encryption key;
A first encryption unit that encrypts the user information with the first encryption key;
A second acquisition unit for acquiring a second encryption key;
A second encryption unit that encrypts information specifying a storage location of the user information encrypted by the first encryption unit with the second encryption key;
A management unit that associates and stores information for identifying the user and information for specifying the encrypted storage location;
A first decryption unit that obtains information for identifying the encrypted storage location based on the information for identifying the user, and decrypts the information for identifying the encrypted storage location;
A second decryption unit for obtaining the encrypted user information based on the decrypted information for specifying the storage location, and decrypting the encrypted user information;
An information management system.   The information management system according to claim 1, wherein the first acquisition unit registers a usage history of the first encryption key.   The information management system according to claim 1, wherein the second acquisition unit stores the second encryption key.   The information management system according to claim 1, wherein the second encryption key is given an expiration date.   The information management system according to claim 1, wherein the information encrypted by the first encryption unit is given an expiration date. An information management system for managing user information, including a plurality of servers and a computer executable program,
The plurality of servers are:
A first acquisition unit for acquiring a first encryption key;
A first encryption unit that encrypts the user information with the first encryption key;
A second acquisition unit for acquiring a second encryption key;
A second encryption unit that encrypts information specifying a storage location of the user information encrypted by the first encryption unit with the second encryption key;
A management unit that associates and stores information for identifying the user and information for specifying the encrypted storage location;
The program is
A first decryption procedure for obtaining information identifying the encrypted storage location based on the information for identifying the user, and decrypting the encrypted information identifying the storage location;
A second decryption procedure for obtaining the encrypted user information and decrypting the encrypted user information based on the decrypted information specifying the storage location;
Information management system for causing the computer to execute. In the information management system that manages user information,
A first acquisition procedure for acquiring a first encryption key;
A first encryption procedure for encrypting the user information with the first encryption key;
A second acquisition procedure for acquiring a second encryption key;
A second encryption procedure for encrypting information specifying a storage location of the user information encrypted by the first encryption procedure with the second encryption key;
A management procedure for storing the information for identifying the user and the information for specifying the encrypted storage location in association with each other;
A first decryption procedure for obtaining information identifying the encrypted storage location based on the information for identifying the user, and decrypting the encrypted information identifying the storage location;
A second decryption procedure for obtaining the encrypted user information and decrypting the encrypted user information based on the decrypted information specifying the storage location;
A program for running In the information management system that manages user information,
A first acquisition procedure for acquiring a first encryption key;
A first encryption procedure for encrypting the user information with the first encryption key;
A second acquisition procedure for acquiring a second encryption key;
A second encryption procedure for encrypting information specifying a storage location of the user information encrypted by the first encryption procedure with the second encryption key;
A management procedure for storing the information for identifying the user and the information for specifying the encrypted storage location in association with each other;
A first decryption procedure for obtaining information identifying the encrypted storage location based on the information for identifying the user, and decrypting the encrypted information identifying the storage location;
A second decryption procedure for obtaining the encrypted user information and decrypting the encrypted user information based on the decrypted information specifying the storage location;
The computer-readable recording medium with which the program for performing this was recorded.

Images