TWM569002U - Medical record sharing system - Google Patents

Abstract

A medical record sharing system, the system is connected with a blockchain network, and the medical record sharing system mainly comprises a plurality of reading end information devices and a medical record center server, wherein the plurality of reading end information devices can be respectively established An electronic medical record information is written to the blockchain network and sent to the medical record center server for storage. After the medical record center server completes the storage, a corresponding key information is transmitted to the reading end information device. When the information device of the reading end reads the electronic medical record information to the medical record center server, the medical record center server performs an identity verification program on the reading end information device, and the reading end information device can be a key. After the information completes the authentication program, the electronic medical record information is further obtained.

Description

Medical record sharing system

A medical record sharing system, especially a medical record sharing system that can protect patient privacy and share electronic medical record information.

Electronic medical records are medical records of digitalized patients that are stored, managed, transmitted, and reproduced using electronic devices (computers, health cards, etc.), replacing handwritten paper medical records, which include all information on paper medical records, National Institute of Medical Research. It will be defined as: EMR is an electronic patient record based on a specific system that provides users with access to complete and accurate data, alerts, prompts, and clinical decision support systems. Electronic medical records are generated by the network management of hospital computers, information storage media, optical discs and IC cards, and the globalization of the Internet. Electronic medical records are the inevitable outcome of information technology and network technology in the medical field. It is an inevitable trend in the modern management of hospital medical records. Its preliminary application in the clinic has greatly improved the hospital's work efficiency and medical quality, but this is only electronic. The beginning of the medical record application. Electronic Medical Record (EMR) is defined in the "Electronic Medical Record Basic Structure and Data Standard Electronic Medical Record" issued by the Ministry of Health. The electronic medical record is the clinical diagnosis of outpatients, inpatients (or health care items) by medical institutions. The digital medical service work record of treatment and guidance intervention is a complete and detailed clinical information resource generated and recorded by residents in the medical institution. However, the current electronic medical records are mainly stored in the hospital's medical record system. Except for a few full-time doctors who have permission to enter, the general patients cannot enter the electronic medical record system, which limits the sharing of electronic medical records, and some materials that can be shared. For example, diagnostic methods, treatment methods, prescriptions, etc. are not known, resulting in an increase in medical costs for the entire society. However, the emergence of mobile Internet technology can provide borderless and ubiquitous medical and health services, and form an efficient and resource-sharing medical and health service. The system, while alleviating the problem of medical resources, can form a worldwide electronic medical record sharing system through voluntary sharing of users, providing reference materials for thousands of users, thereby reducing the medical cost of the whole society.

In view of the above problems, the creator is based on years of experience in related industries, researching and analyzing the process of establishing and reading electronic medical records, and is able to develop methods to solve the above problems; The purpose is to provide a medical record sharing system that can protect patient privacy and protect the integrity of medical records to achieve medical record sharing.

In order to achieve the above objectives, the present invention mainly comprises a plurality of reading end information devices and a medical record center server, which are respectively connected with a blockchain network, and each reading end information device can establish an electronic medical record. After the information is further transmitted to the medical record center server for storage, and the electronic medical record center After receiving the electronic medical record information, the server generates a corresponding set of key information and transmits it to the reading end information device. When the reading end information device requests a medical record reading from the medical record center server, The medical record reading request is encrypted by the key information for the medical record center server to perform an identity verification process, and after the information device of the reading end completes the identity verification process, the electronic medical record information can be transmitted to the reading end information device, For reading or modifying the information device at the reading end.

In order for your review board to have a clear understanding of the purpose, technical features and effectiveness of this work, please refer to the following instructions for illustration.

10‧‧‧ medical record sharing system

101‧‧‧Reader information device

102‧‧‧ medical record center server

101’‧‧‧Reader information device

1021‧‧‧Processing module

101”‧‧‧Reader information device

1022‧‧‧Key Generation Module

20‧‧‧blockchain network

1023‧‧‧ medical record database

A‧‧‧ verification information

10231‧‧‧Key Information Unit

A’‧‧‧Verification information

1024‧‧‧Authentication Module

E‧‧‧Electronic medical record information

10241‧‧‧Key Comparison Unit

M‧‧‧ Key Information

10242‧‧‧Information Encryption Unit

M1‧‧‧ public key

M2‧‧‧ Private Key

M3‧‧‧symmetric encryption key

R‧‧‧ medical record reading requirements

S‧‧‧Authentication Procedure

ST1‧‧‧ Establish electronic medical record information steps

ST11‧‧‧ Receiving electronic medical record information steps

ST2‧‧‧Key Key Information Steps

ST21‧‧‧Receive key information steps

ST3‧‧‧Transfer medical record reading request message steps

ST31‧‧‧Steps in the authentication process

ST32‧‧‧Send encrypted electronic medical record information steps

ST4‧‧‧Modify electronic medical record information steps

ST41‧‧‧Additional electronic medical record information steps

ST51‧‧‧ Establish electronic medical record information steps

ST52‧‧‧Generation Key Steps

ST53‧‧‧Transfer medical record reading request message steps

ST54‧‧‧Steps in the authentication process

ST55‧‧‧Send encrypted electronic medical record information steps

Figure 1 is a system architecture diagram of the creation.

Figure 2 is a schematic diagram of the architecture of the medical record center server of the creation.

Figure 3 is a flow chart for the creation of electronic medical record information for the creation.

Figure 4 is a flow chart of the key information transmission of the creation.

Figure 5 is a flow chart for reading the medical records of the creation.

Figure 6 is a flow chart of additional medical records for this creation.

Figure 7 is a schematic diagram of the steps of the implementation process of the creation.

Please refer to "Figure 1", which shows the system architecture of the creation. The medical record sharing system 10 shown in the figure mainly comprises: a plurality of reading end information devices (101, 101', 101"..) and a medical record center server 102, and a plurality of reading end information devices. (101, 101', 101"..) and the medical record center server 102 form a blockchain network 20 in a peer-to-peer manner for a plurality of read-end information devices (101, 101' , 101"..) or the medical record center server 102 can respectively write information into the blockchain network 20, and the plurality of read-end information devices (101, 101', 101"..) are respectively associated with the medical record center. The server 102 forms an information link, and the reading end information device 101 is mainly a medical device or an information device used by the patient itself, and can be a personal computer (PC), a notebook computer (NB), a smart phone. One of the tablet computers or a combination thereof, but preferably the information device used by the medical institution, and the blockchain network 20 can be an internet network, a private network, and a virtual private network. One of the roads, in turn, the reading end information device 101 can generate an electronic medical record information E (the said electric The medical record information may include the patient's personal data, condition assessment, treatment plan, medical record, disease record, care plan, record, vital signs record, drug use record, and related medical laboratory test data and reports. Check data and reports (including diagnostic imaging reports, X-rays, etc.), past medical history, family history, vaccination, etc.), and send them to the medical record center server 102 for storage, and simultaneously receive the medical record center server 102 A key information M is sent, and the key information M includes a public key M1, a private key M2, and a symmetric encryption key M3, which are mainly kept by the patient or the medical institution. The holder of the key information M can also issue a disease to the medical record center server 102 through the reading end information device 101. The reading request message R (the holder of the key information M, mainly the patient itself and the relevant personnel of the medical institution, may also be the family member of the patient or other related persons, whereby the patient itself may The key information M is authorized to be used by the family or the related person, so that the electronic medical record can be read by the patient's own authorization, and the medical record center server 102 receives the medical record reading request message R, relative to the reading end information. The device 101 performs an identity verification procedure S. After the reader-side information device 101 passes the identity verification program S, the medical record center server 102 can output the electronic medical record information E corresponding to the reading-end information device 101 (ie, the original reading) The same electronic medical record information E) transmitted from the medical information device 101 to the medical record center server 102 is further sent to the reading end information device 101 for reading and modification, thereby allowing the patient to go to another medical institution for treatment. It is also possible to obtain the electronic medical record information E established by the previous medical institution through the key information M held to achieve the purpose of sharing medical records.

Please refer to "Figure 2". The figure shows the architecture of the medical record center server of the creation. Please refer to "Figure 1". The medical record center server 102 shown in the figure has a The processing module 1021, a key generation module 1022, a medical record database 1023, and an identity verification module 1024 respectively form an information link with the processing module 1021. The processing module 1021 can be a central processing unit (CPU). And having the functions of logic operation, temporary storage operation result, saving execution instruction position, etc., for running the medical record center server 102; the key generation module 1022 can generate the key information M, and the key information includes public Key M1, private key M2 and symmetric encryption key M3; medical record database 1023, for storing information devices of each reading end (101, 101', 101"..) generated electronic medical record information E, and the medical record database 1023 is further provided with a key information unit 10231, and the key information unit 10231 is formed with the key generation module 1022. The information link, when the medical record database 1023 stores an electronic medical record information E, the key information unit 10231 can be used to store the key information M generated by the key generation module 1022, and the key information M is relative to The electronic medical record information E means that each electronic medical record information E corresponds to a different set of key information M; the identity verification module 1024 can identify the reading information device 101 that issues the medical record reading request message R. Verification program S, and the authentication module 1024 has a key matching unit 10241 and an information encryption unit 1042, and the key comparison unit 10241 and the information encryption unit 1042 respectively form information with the key information unit 10231. After the connection, the key matching unit 10241 can be driven by the processing module 1021 to read the request message R according to the received medical record to compare the key information M stored in the key information unit 10231, and the information is encrypted. After yuan 10242 can be driven processing module 1021, in 1023 for medical records database stored in electronic medical record information E were encrypted information needs encryption, authentication procedures and assist in S.

Please refer to "Figure 3", which shows the flow chart for the creation of electronic medical record information. Please refer to "Figure 1" and "Figure 2" together. The process for establishing electronic medical record information includes: (1) The electronic medical record information step ST1: the reading end information device 101 can generate the electronic medical record information E and write it into the blockchain network 20; (2) receive the electronic medical record information step ST11: the medical record center server 102 The electronic medical record information E can be received through the blockchain network 20 and further stored in the medical record database 1023.

Please refer to "Figure 4". The figure shows the flow chart of the key information transmission for this creation. Please refer to "Figure 1" and "Figure 2" together with the following: (1) Step of generating key information ST2: The medical record center server 102 generates a set of key information M that does not include the symmetric encryption key M3 through the key generation module 1022, and writes it to the blockchain network 20, and then sends it to the reading end information device 101. (2) Receive Key Information Step ST21: The read-side information device 101 receives the key information M through the blockchain network 20.

Please refer to "Figure 5". The figure shows the flow chart of reading the medical records of the creation. Please refer to "Figure 1" and "Figure 2" together with the following: (1) A medical record reading requirement Message step ST3: The reading end information device 101 encrypts the medical record reading request message R with the public key M1 in the key information M, and further transmits it to the medical record center server 102; (2) performs an authentication process step ST31. The public key M1 can be used as the UID (unique identifier) of the reading end information device 101 to avoid the privacy exposure of the patient, and the public key M1 that the medical record center server 102 can receive is used as the number index. The key matching unit 10241 retrieves and decrypts the private key M2 of the public key M1 in the key information unit 10231, and if the medical record center server 102 can decrypt the secret key M2 to encrypt the public key M1. When the request message R is read, it indicates that the medical record reading request message R is indeed the electronic medical record information E from the patient's own request to read the patient's own request, and the medical record center server 102 is the authentication module. 1024, the reading end information device 101 that issues the medical record reading request message R performs an authentication procedure S, and encrypts the symmetric encryption key M3 with the public key M1 through the information encryption unit 1042 by using the received public key M1. To form a verification information A, and further transmit the verification information A to the reading end information device 101 for identity confirmation; (3) to send the encrypted electronic medical record information step ST32: the reading end information device 101 receives the verification information A, the authentication key A can be decrypted by the private key M2 to obtain the symmetric encryption key M3, and the reading end information device 101 encrypts the verification information A with the obtained symmetric encryption key M3 to form a verification information A'. And further, the verification information A' is returned to the medical record center server 102, and if the medical record center server 102 can decrypt the verification information A' by the symmetric encryption key M3, the medical record is determined to be read. The request message R is sent by the patient himself, and the medical record center server 102 transmits the electronic medical record information E of the corresponding patient to the reading end information device 101 in any encrypted (symmetric or asymmetric encryption) manner. The read end information device 101 decrypts and reads the electronic medical record information E.

Please refer to "Figure 6". The figure shows the additional medical record data flow chart for this creation. Please refer to "Figure 1" and "Figure 2" together with: (1) A modified electronic medical record information step ST4: after receiving the electronic medical record information E, the reading end information device 101 can further modify the electronic medical record information E by adding content, and the electronic medical record information E after the modification can be completed. Further encrypted by the public key M1, written into the blockchain network 20, and further transmitted to the medical record center server 102; (2) an additional electronic medical record information step ST41: after the medical record center server 102 receives the modification The electronic medical record information E is stored in an additional manner in the medical record database 1023 of the medical record center server 102.

Please refer to "Figure 7". The figure shows the steps of the implementation process of the creation. Please refer to "Figure 1" to "Figure 6". It includes: (1) Establish electronic medical record information step ST51: The reading end information device 101 can generate the electronic medical record information E and write it into the blockchain network 20. The medical record center server 102 can receive the electronic medical record information E through the blockchain network 20 and further store the medical record information database. 1023; (2) generating key information step ST52: the medical record center server 102 generates a set of key information M not including the symmetric encryption key M3 through the key generation module 1022, and writes it to the blockchain network 20 Then, it is further sent to the reading end information device 101, and the reading end information device 101 receives the key information M through the blockchain network 20; (3) transmits the medical record reading request message step ST53: the reading end information The device 101 encrypts the medical record reading request message R by the public key M1 in the key information M, and then sends it to the medical record center server 102; (4) Performing the authentication procedure Step ST54: The public key M1 can be used as the UID (unique identifier) of the reading end information device 101 to avoid the patient's privacy exposure, and the medical record center 102 can receive the public gold. The key M1 is used as the number index, and the private key M2 of the public key M1 can be decrypted and decrypted in the key information unit 10231. If the medical record center server 102 can decrypt the private key M2, the public key M1 is encrypted. When the medical record reading request message R indicates that the medical record reading request message R is indeed a request for reading the electronic medical record information E of the patient itself from the patient's will, the medical record center server 102 receives the public information again. The key M1 encrypts the symmetric encryption key M3 with the public key M1 to form a verification information A, and further transmits the verification information A to the reading end information device 101 for identity confirmation; and (5) transmits the encrypted electronic The medical record information step ST55: when the reading end information device 101 receives the verification information A, the authentication information A can be decrypted by the private key M2 to obtain the symmetric encryption key M3, and the reading end information device 101 obtains The symmetric encryption key M3 encrypts the verification information A to form a verification information A', and further transmits the verification information A' back to the medical record center server 102. If the medical record center server 102 can symmetrically encrypt the key M3, the verification information is verified. If the A' is decrypted, it is determined that the medical record reading request message R is sent by the patient himself, and the medical record center server 102 performs the electronic medical record information E of the corresponding patient in a symmetric key algorithm (Symmetric-key algorithm). After being encrypted, it is sent to the reading end information device 101 for reading the information device 101. After decryption, the electronic medical record information E is read.

It can be seen from the above that the creation of the medical record sharing system mainly prevents the electronic medical record information from being stolen or modified by the illegal person other than the patient himself by using the key encryption method, and the public key can be used as the UID to protect the disease. Suffering from privacy; according to this, after the implementation of this creation, it can indeed achieve the purpose of providing a medical record sharing system that can protect the privacy of patients and protect the integrity of medical records to achieve medical records sharing.

The above description is only for the preferred embodiment of the present invention, and is not intended to limit the scope of the present invention; any person skilled in the art can make equal changes and modifications without departing from the spirit and scope of the present invention. , should be covered by the scope of this creation patent.

To sum up, the effectiveness of this creation is in the possession of patents such as “industry availability”, “novelty” and “progressiveness” of the invention; the applicant filed a new patent with the bureau in accordance with the provisions of the Patent Law. Application.

Claims (8)

A medical record sharing system includes: a plurality of reading end information devices respectively connected to a blockchain network, and the plurality of reading end information devices respectively write the generated electronic medical record information into the blockchain a medical record center server, connected to the blockchain network, having a processing module respectively forming a information link with a key generation module, an identity verification module, and a medical record database, the medical record database can receive Each of the electronic medical record information sent by each of the reading end information devices is stored in the medical record database, and a corresponding key information is generated by the key generation module, and stored in the medical record database. And sending to each of the reading end information devices; the reading end information device can send a medical record reading request message to the medical record center server to request to read the electronic medical record information through the blockchain network, and the medical record center The server performs an identity verification procedure on the read end device that sends the medical record read request message through the identity verification module; and the read end information device passes the identity verification After the sequence, i.e., the server center records the electronic medical record information will be sent to the information reading means through the end of the block chain network. The medical record sharing system of claim 1, wherein the medical record database has a key information unit, and the key generation module forms an information link with the key information unit, and the key information unit is available. The key information generated by the key generation module is stored. The medical record sharing system of claim 2, wherein the identity verification module has a key comparison unit, and forms an information link with the key information unit, which can be driven by the processing module. The medical record reads the request message to compare the key information stored in the key information unit. The medical record sharing system of claim 1, wherein the identity verification module has an information encryption unit. The medical record sharing system of claim 4, wherein the medical record center server can encrypt the electronic medical record information through the information encryption unit, and then send the information to the read end information device through the blockchain network. The medical record sharing system according to claim 1, wherein the reading end information device can encrypt the medical record reading request message by the key information and transmit the information. The medical record sharing system of claim 1, wherein the key information comprises a public key, a private key, and a symmetric encryption key. The medical record sharing system of claim 7, wherein each of the key information transmitted to each of the reading end information devices does not include the symmetric encryption key.