CN110414253A

CN110414253A - A kind of electronic health record management method, device, system and equipment based on block chain

Info

Publication number: CN110414253A
Application number: CN201910718783.XA
Authority: CN
Inventors: 谢越津
Original assignee: Shenzhen Onething Technology Co Ltd
Current assignee: Shenzhen Onething Technology Co Ltd; Shenzhen Xunlei Network Technology Co Ltd
Priority date: 2019-08-05
Filing date: 2019-08-05
Publication date: 2019-11-05

Abstract

The invention discloses a kind of electronic health record management method, device, system and equipment, readable storage medium storing program for executing and computer program products.It in technical solution disclosed by the invention, after receiving medical record management request, is requested to send management authorization requests to patient customer end according to medical record management, to allow patient to determine whether to agree to management of the doctor to case history.It after the feedback result for receiving the transmission of patient customer end, when feedback result is to pass through authorization, is then managed using case history of the block chain to patient, to respond medical record management request.As it can be seen that patient exists in case history renewal process with the person of checking on of medical record data and leading controller.Due to being requested using block chain response medical record management, relative to the mode only stored in central server, this method enables to case history not to be tampered, and has further ensured leading position of patient during medical record management, it avoids case history from being distorted by premeditated, influences the equity of doctor or patient.

Description

A kind of electronic health record management method, device, system and equipment based on block chain

Technical field

The present invention relates to technical field of data storage, more particularly to a kind of electronic health record manager based on block chain Method, device, system, equipment, readable storage medium storing program for executing and computer program product.

Background technique

With the continuous development of network technology, the information content that electronic health record (this paper abbreviation case history) is recorded is more and more, The territorial scope for propagating application is more and more wider.This variation tendency, having in diagnosing and treating of the doctor to patient disease can not The benefit of ignorance.

But the management of case history is often controlled by medical staff at present, usual patient does not know medical doctor It is raw which kind of management has specifically been carried out in its case history.Similarly, patient can not also determine doctor manage whether based on the fact that It is carried out, records false medical history such as whether existing to evade a duty；It whether include that it is reluctant disclosed state of an illness medical history in case history. Medical record data is stored in the centralization database of hospital's foundation, typically stored in clear, grasps database-access rights Doctor can arbitrarily use medical record data, and patients' privacy cannot be protected, and there is also the risks of leaking data for database；Separately Outer database is grasped by hospital, and on the one hand when medical-accident disputes occur, it is unfavorable to patient that hospital is easy to distort case history, in addition On the one hand, the database between each hospital is independent, and patient is medical in Different hospital, diagnosis records, inspection result before Etc. data it is inconvenient to carry, often to do the inspection and treatment of repeatability, cause the waste of medical resource, the experience of patient is very not yet It is good.

Summary of the invention

The object of the present invention is to provide a kind of electronic health record management method, device, system, equipment, readable storage medium storing program for executing and Computer program product, it is intended to based on block chain can not tamper, and pipe is carried out to patient medical record in conjunction with patient's authorization Reason, to ensure the authenticity of case history, meets control of the patient to case history privacy.

It should be noted that the present invention provides a kind of electronic health record management method based on block chain, device, system, Equipment, readable storage medium storing program for executing and computer program product.Wherein, for ease of description, a kind of electronic health record pipe based on block chain Reason method is referred to as electronic health record management method or method, a kind of letter herein of the electronic health record managing device based on block chain herein Referred to as electronic health record managing device or device, a kind of electronic health record management equipment based on block chain are referred to as electronic health record herein Management equipment or equipment.

In order to solve the above technical problems, the invention provides the following technical scheme:

A kind of electronic health record management method based on block chain is applied to service server, which comprises

The medical record management request that doctor's client is sent is received, the medical record management request is for requesting the case history to patient It is managed；

It is requested to send management authorization requests to patient customer end according to the medical record management, the management authorization requests are used for Request patient customer end authorizes doctor's client to be managed the case history of the patient；

The patient customer end is received to the feedback result of the management authorization requests, if the feedback result is to pass through Authorization is then managed to respond the medical record management request using case history of the block chain to the patient.

Preferably, the medical record management request is that case history updates request, and it includes public by patient that the case history, which updates request, The case history ciphertext data to be updated of key encryption；

The management authorization requests are that case history updates authorization requests, and it includes described to be updated that the case history, which updates authorization requests, Case history ciphertext data；

The feedback result includes the signature by patient's private key to the case history ciphertext data to be updated；

Described be managed using case history of the block chain to the patient to respond the medical record management request includes: to area Block chain initiates to update case history write-in transaction, so that by the case history ciphertext data to be updated after signing described in block chain link point sign test Block chain is written.

Preferably, the medical record management request is case history request to create, and the case history request to create includes public by patient The case history ciphertext data to be created of key encryption；

The feedback result includes the signature by patient's private key to the case history ciphertext data to be created；

Described be managed using case history of the block chain to the patient to respond the medical record management request includes: to area Block chain initiates to update creation write-in transaction, so that by the case history ciphertext data to be created after signing described in block chain link point sign test Block chain is written.

Preferably, the method also includes: receive the case history that doctor's client is sent and check request, the case history is looked into See that request includes the parameter for the case history that doctor's client request is checked；

It checks that request is sent to patient customer end according to the case history and checks authorization requests, it is described to check that authorization requests are used for The case history corresponding with the parameter for requesting patient customer end that doctor's client is authorized to check the patient；

The patient customer end is received to the feedback result for checking authorization requests, if the feedback result is to pass through Authorization, then the feedback result includes the case history ciphertext data by doctor's public key encryption, described public by the doctor The case history ciphertext data of key encryption are that the patient customer end utilizes patient to the case history ciphertext data downloaded from the block chain Private key is decrypted, and obtains after recycling doctor's public key encryption.

Preferably, the case history checks that request includes doctor's public key or doctor id.

Preferably, the method also includes:

The case history acquisition request that the patient customer end is sent is received, the case history acquisition request includes that patient customer end asks Seek the parameter of the case history of acquisition；

According to the case history acquisition request, case history ciphertext number corresponding with the parameter is downloaded from the block chain According to；

The case history ciphertext data are sent to the patient customer end.

A kind of electronic health record managing device, comprising:

Request receiving module is managed, for receiving the medical record management request of doctor's client transmission, the medical record management is asked It asks for requesting to be managed the case history of patient；

Authorization inquiry module sends management authorization requests, institute to patient customer end for requesting according to the medical record management Management authorization requests are stated for requesting patient customer end that doctor's client is authorized to be managed the case history of the patient；

Manage ask respond module, for receive the patient customer end to it is described management authorization requests feedback result, If the feedback result is to be managed by authorization using case history of the block chain to the patient to respond the case history Management request.

Preferably, the management ask respond module, comprising:

Case history updating unit is used to then utilize block chain to institute when medical record management request is that case history updates request The case history for stating patient is updated to respond the medical record management request；

Case history creates unit, for when medical record management request is case history request to create, then utilizing block chain to institute The case history for stating patient is created to respond the medical record management request.

A kind of _ based Patient Records Management Systems, including service server, patient customer end, doctor's client and block chain；

Wherein, doctor's client, for sending medical record management request, the medical record management to the service server Request is for requesting to be managed the case history of patient；

The service server, for receiving the medical record management request；It is requested according to the medical record management to the trouble Person's client sends management authorization requests, and the management authorization requests are for requesting the patient customer end to authorize the doctor visitor Family end is managed the case history of the patient；Receive the patient customer end to it is described management authorization requests feedback result, It is managed if the feedback result is by authorization using case history of the block chain to the patient to respond the case history Management request；

The patient customer end is sent for receiving the management authorization requests, and to the service server to described Manage the feedback result of authorization requests；

The block chain, for storing the case history of the patient by encryption.

A kind of electronic health record management equipment, comprising:

Memory, for storing computer program；

Processor, the step of above-mentioned electronic health record management method is realized when for executing the computer program.

A kind of computer program product, including computer instruction, when run on a computer, so that computer can be with Execute above-mentioned electronic health record management method.

Using electronic health record management method provided by the embodiment of the present invention in service server, method includes: to receive The medical record management request that doctor's client is sent, medical record management request is for requesting to be managed the case history of patient；According to disease It goes through management request and sends management authorization requests to patient customer end, management authorization requests are for requesting patient customer end authorized doctor Client is managed the case history of patient；Patient customer end is received to the feedback result of management authorization requests, if feedback knot Fruit is then to be managed using case history of the block chain to patient by authorization to respond medical record management request.

This method requests to send management to patient customer end according to medical record management after receiving medical record management request Authorization requests, to allow patient to determine whether to agree to management of the doctor to case history.In the feedback for receiving the transmission of patient customer end As a result it after, when feedback result is to pass through authorization, is then managed using case history of the block chain to patient, to respond case history pipe Reason request.As it can be seen that patient exists in case history renewal process with the person of checking on of medical record data and leading controller.Due to utilizing area Block chain respond medical record management request, relative to the mode only stored in central server, this method enable to case history not by Distort, further ensured leading position of patient during medical record management, case history is avoided to be distorted by premeditated, influence doctor or The equity of patient.

Correspondingly, the embodiment of the invention also provides electronic health record management corresponding with above-mentioned electronic health record management method Device, equipment, system, readable storage medium storing program for executing and computer program product, have above-mentioned technique effect, and details are not described herein.

Detailed description of the invention

In order to more clearly explain the embodiment of the invention or the technical proposal in the existing technology, to embodiment or will show below There is attached drawing needed in technical description to be briefly described, it should be apparent that, the accompanying drawings in the following description is only this Some embodiments of invention for those of ordinary skill in the art without creative efforts, can be with It obtains other drawings based on these drawings.

Fig. 1 is one of embodiment of the present invention electronic health record management method flow chart；

Fig. 2 is that case history updates flow diagram in the embodiment of the present invention；

Fig. 3 is case history visioning procedure schematic diagram in the embodiment of the present invention；

Fig. 4 is that case history checks flow diagram in the embodiment of the present invention；

Fig. 5 is the application scenarios schematic diagram of one of embodiment of the present invention electronic health record management method；

Fig. 6 is the structural schematic diagram of one of embodiment of the present invention electronic health record managing device；

Fig. 7 is the structural schematic diagram of one of embodiment of the present invention electronic health record management equipment；

Fig. 8 is the structural schematic diagram of another electronic health record management equipment in the embodiment of the present invention.

Specific embodiment

In order to enable those skilled in the art to better understand the solution of the present invention, with reference to the accompanying drawings and detailed description The present invention is described in further detail.Obviously, described embodiments are only a part of the embodiments of the present invention, rather than Whole embodiments.Based on the embodiments of the present invention, those of ordinary skill in the art are not making creative work premise Under every other embodiment obtained, shall fall within the protection scope of the present invention.

Embodiment one:

It is one of embodiment of the present invention electronic health record management method flow chart referring to Fig. 1, Fig. 1.This method can be applied In business service end (such as server in kind or virtual server), in the present embodiment, this method comprises:

S101, the medical record management request that doctor's client is sent is received, medical record management request is for requesting the disease to patient It goes through and is managed.

Wherein, medical record management request may include checking case history, create the common medical record management such as case history and case history update Operate corresponding requests.

In embodiments of the present invention, determine that medical record management is requested there are many implementations of corresponding management category, below Two of them is enumerated to be illustrated:

Implementation 1 can pass through behaviour for different parameters is arranged in the request that doctor's client is different management category The reference that mutually should refer to management category made in the medical record management received request is matched, that is, can determine that corresponding pipe Manage classification.Preferably, a management category tag field is set in management request message, with the value of the field and different pipes Manage categorical match.For example, if the field is x, as x=0, it is determined that management category is creation；As x=1, it is determined that management Classification is to check；As x=2, it is determined that management category is to update.

Implementation 2 can also request the data information carried by medical record management, determine that corresponding management class is requested in management Not.For example, when the data that medical record management request carries be the specific identity information of patient necessary to creating new case history (such as name, The information such as patient ID, age, address) and state of an illness data etc., that is, it can be considered creation case history；When the number that medical record management request carries According to only including patient identification information (such as patient ID), then it can be considered and check case history；When the data that medical record management request carries include State of an illness data and patient identification information but do not carry creation case history necessary to the specific identity information of all patients, then can be considered Case history updates.

S102, it is requested to send management authorization requests to patient customer end according to medical record management, management authorization requests are for asking Patient customer end authorized doctor client is asked to be managed the case history of patient.

Wherein, it is requested to send management authorization requests to patient customer end according to medical record management, can be specially according to case history pipe Reason requests patient customer end corresponding to corresponding case history owner to send management authorization requests, so that patient customer end determines whether Xiang this medical record management permission of doctor's client authorization.

It may particularly include the corresponding personal information of initiation doctor, the positioning letter of medical record management request in empowerment management request The particular content of breath and medical record management, so that patient is after consulting empowerment management request, it is determined whether authorization.

It, can the content according to entrained by the management authorization requests that it is received after patient customer end receives management authorization requests Determine whether to authorize.For example, receiving increase pass newly in case history suddenly when patient is not engaged in the diagnosing and treating of certain disease It is updated in the case history of the diagnosing and treating of the disease, it is clear that this is not meet true medical record management, and user may be selected not at this time Doctor's client is licensed to, to refuse the request of this medical record management.

S103, receive patient customer end to management authorization requests feedback result, if feedback result be by authorization, It is managed using case history of the block chain to patient to respond medical record management request.

Patient customer end is being received for the feedback result of management authorization requests, whether can be according to authorizing in feedback result Information, it is determined whether enjoy medical record management request.When feedback result is by authorization, at this time using block chain to patient's Case history is managed, to respond medical record management request；When feedback result is that can directly ignore the case history pipe at this time not by authorization Reason request.

It certainly, can also be Xiang the unsanctioned prompt letter of doctor's client feedback authorization when feedback result is not pass through authorization Breath retransmits management authorization requests so that doctor is based on the prompt information.

This method requests to send management to patient customer end according to medical record management after receiving medical record management request Authorization requests, to allow patient to determine whether to agree to management of the doctor to case history.In the feedback for receiving the transmission of patient customer end As a result it after, when feedback result is to pass through authorization, is then managed using case history of the block chain to patient, to respond case history pipe Reason request.As it can be seen that patient exists in case history renewal process with the person of checking on of medical record data and leading controller.In the present embodiment, The medical record data of patient is stored on block chain, due to being requested using block chain response medical record management, relative to only in The mode stored in central server, this method enable to case history not to be tampered, and have further ensured patient in medical record management mistake Leading position in journey avoids case history from being distorted by premeditated, influences the equity of doctor or patient.

It should be noted that being based on above-mentioned each embodiment, the embodiment of the invention also provides be correspondingly improved scheme.In It is preferred that/improve and can mutually be referred between step or corresponding steps same with the above-mentioned embodiment involved in embodiment, have accordingly Beneficial effect can also be cross-referenced, no longer repeats one by one in preferred/improvement embodiment of this paper.

It should be noted that the patient customer end mentioned herein and doctor's client, can have for be respectively patient, The different clients that doctor individually develops；It can certainly be same client, have respectively because user's registration identity is different The client of standby different function.

To more fully understand the electronics disease provided by the embodiment of the present invention based on block chain convenient for those skilled in the art Management method is gone through, is provided for the embodiments of the invention the electronic health record based on block chain by taking specific medical record management as an example below Management method is described in detail.

Embodiment two:

In the present embodiment, when updating request to medical record management request for case history, corresponding treatment process is carried out specifically It is bright.

Referring to FIG. 2, Fig. 2 is that case history updates flow diagram in the embodiment of the present invention.Should the realization process includes:

S201, the case history update request that doctor's client is sent is received, case history updates request for requesting the disease to patient It goes through and is updated.

That is, medical record management request is that case history updates request, it includes by patient's public key encryption to more that case history, which updates request, New case history ciphertext data.

Usually doctor is updated to case history, medical diagnosis on disease treatment record is increased newly to case history.Thus, business service at this time The case history ciphertext data to be updated that device can upload doctor's client cache.

This waits for that case history ciphertext data can be specially the data content of this medical diagnosis on disease treatment record；Or and case history The data content of corresponding sufferer whole history medical diagnosis on disease record and the data content of this medical diagnosis on disease record are requested in management Summation.

In order to ensure sufferer case history privacy, avoid in transmission process or blocked during caching in the server It cuts, leakage sufferer privacy, or is tampered, cause case history false.Doctor's client upload update case history related data (such as this Data content and this medical diagnosis on disease of the data content or sufferer whole history medical diagnosis on disease record of medical diagnosis on disease treatment record The summation for treating the data content of record) when, medical record data can be encrypted.Preferably, doctor's client is using the disease Public key in the asymmetric cryptographic key of trouble encrypts data, so that case history ciphertext data to be updated are only capable of by patient visitor The decryption of family end is checked.

S202, request is updated according to case history to patient customer end transmission case history update authorization requests, case history, which updates authorization, asks It asks for requesting patient customer end authorized doctor client to be updated the case history of patient.

That is, management authorization requests are that case history updates authorization requests, it includes case history ciphertext to be updated that case history, which updates authorization requests, Data, case history ciphertext data to be updated can be using patient's public key encryption, and such patient customer end is receiving case history update After authorization requests, patient's private key can be used to decrypt case history ciphertext data to be updated, to obtain medical record data to be updated, Huan Zhetong Crossing patient customer end can check that doctor requests the medical record data updated whether true, wherein whether having careless omission or oneself being reluctant The data of case history are written.If patient approves that doctor requests the medical record data updated, it can be used and suffer from by patient customer end Person's private key signs to case history ciphertext data to be updated.

In embodiments of the present invention, corresponding relationship can be suggested in the patient customer end that patient uses with it.Based on the correspondence Relationship can position the corresponding patient customer end of some patient, such as patient logs in patient visitor using the username and password of its registration Family end.

In embodiments of the present invention, case history update request in can carry be managed case history owner (case history owner, i.e., Case history corresponds to sufferer) relevant information.For example, carrying the identity ID that case history corresponds to sufferer.Determining medical record management request When management category is that case history updates, corresponding sufferer client can be requested to send case history to medical record management and update authorization requests and more New case history ciphertext data.

S203, the feedback result that patient customer end updates authorization requests to case history is received, if feedback result is by awarding Power is then updated to respond case history and update request using case history of the block chain to patient.

Feedback result includes signature of the patient customer end using patient's private key to ciphertext data to be updated, in a kind of embodiment In, which indicates that feedback result is by authorization, and service server can obtain feedback result by the sign test signature.

I.e. when medical record management request is that case history updates request, it is managed using case history of the block chain to patient to respond Medical record management request includes: to initiate to update case history write-in transaction to block chain, so that will be to more after block chain link point sign test signature Block chain is written in new case history ciphertext data.

After patient customer's termination receives update case history ciphertext data, if updating case history ciphertext data is to utilize the non-of the patient What the public key in symmetric key was encrypted, then it is decrypted using the corresponding case history ciphertext data that update of the private key of the patient, And it is shown to patient and updates medical record data.

After patient customer's termination receives update authorization requests, authorization prompt information can be popped up in visualization interface, and to trouble In person's client can operation interface or button be monitored, to obtain the Authorization result of patient's input.

After the monitoring of patient customer end obtains update Authorization result, which can be fed back to business service Device.

When service server receives the feedback result for updating and authorizing.The feedback result for updating authorization can be identified, Determine whether patient authorizes update case history.When feedback result, which is, to be allowed to update (passing through authorization), then initiate to update to block chain The write-in of case history is traded.

Therefore electronic health record management method provided by the embodiment of the present invention, it is requested receiving medical record management Afterwards, the update case history ciphertext data for uploading doctor's client are especially needed at this time when determining management category is that case history updates It is sent to patient customer end corresponding with medical record management request, and initiates case history to patient customer end and updates authorization requests.This When patient can using patient customer end feed back according to actual needs update Authorization result.For example, when updating case history ciphertext data pair The case history answered more new content is not true or is related to being reluctant disclosed privacy, and the optional update Authorization result of patient is not authorize at this time. After the update Authorization result for obtaining patient customer end feedback, when updating Authorization result is to allow to update, initiated to block chain New case history write-in transaction.As it can be seen that patient is in case history renewal process with the person of checking on of medical record data and leading controller.To block New case history write-in transaction is initiated in chain write-in, relative to only storing in central server, case history is enabled to not to be tampered, into one Step has ensured leading position of patient during medical record management.

Preferably, it initiates to update case history write-in transaction to block chain, comprising: initiate signature to block chain and update case history ciphertext The write-in of data is traded；Wherein, it is that patient customer end is signed to case history ciphertext data are updated that signature, which updates case history ciphertext data, The ciphertext data fed back after name.In this way, signature can be determined more by way of sign test after block chain receives write-in transaction Whether new case history ciphertext data are true and reliable.

Preferably, the write-in transaction that signature updates case history ciphertext data is initiated to block chain, comprising:

Receive updating using patient's private key to the signature obtained after medical record data to be updated signature for patient customer end feedback Case history ciphertext data；Wherein, updating case history ciphertext data is that doctor's client utilizes patient's public key pair corresponding with patient's private key The ciphertext data that new case history encrypts；

The write-in transaction that signature updates case history ciphertext data is initiated to block chain.

Asymmetric cryptographic key can be used, encryption and decryption is carried out to medical record data, to ensure that medical record information is not leaked.

Preferably, in order to avoid server buffer is occupied, Authorization result be forbid update when, remove caching to more New case history ciphertext data.

Embodiment three:

In the present embodiment, when being case history request to create to medical record management request, corresponding treatment process is carried out specifically It is bright.

Referring to FIG. 3, Fig. 3 is case history visioning procedure schematic diagram in the embodiment of the present invention.Should the realization process includes:

S301, the case history request to create that doctor's client is sent is received, case history request to create is used to request the disease to patient It goes through and is created.

That is, medical record management request is case history request to create, case history request to create includes by patient's public key encryption wait create Build case history ciphertext data.

In embodiments of the present invention, case history ciphertext data to be created may include the specific identity information of patient that has encrypted (such as The information such as name, patient ID, age, address) and this go to a doctor and resulting encrypted state of an illness data.Used in data encryption Key can be the public key in the asymmetric cryptographic key of patient, and the registration that doctor can detect patient by operation doctor's client is public Key, the i.e. public key are the key of patient's generation when patient customer end carries out user's registration.Correspondingly, doctor can also infuse When volume, a pair of of unsymmetrical key is obtained.

S302, case history creation authorization requests are sent to patient customer end according to case history request to create, case history creation authorization is asked It asks for requesting patient customer end authorized doctor client to create the case history of patient.

S303, patient customer end is received to the feedback result of case history creation authorization requests, if feedback result is by awarding Power, then created using case history of the block chain to patient to respond case history request to create.

That is, being managed when medical record management request is case history request to create using case history of the block chain to patient with sound Answering medical record management request includes: to initiate to update creation write-in transaction to block chain, so that will be to after block chain link point sign test signature It creates case history ciphertext data and block chain is written.

Service server obtain creation case history ciphertext data after, can to patient customer end send case history creation authorization requests with And the creation case history ciphertext data.

After patient customer's termination receives creation case history ciphertext data, using the private key in rivest, shamir, adelman to creation disease It goes through ciphertext data to be decrypted, and the specific identity information obtained after decryption is showed into patient, so that patient checks identity letter Whether breath is true errorless.

After patient customer's termination receives creation authorization requests, patient's selection can be guided according to preset creation authorization flow The Authorization result for whether authorizing, and finally being determined to server-side feedback patient.It obtains case history request to create and corresponds to Authorization result mistake Journey can refer in embodiment two, and how patient customer end obtains the specific implementation process about modification case history Authorization result.

The Authorization result of patient customer end feedback is received, and determines whether to create.It is understood that the authorization knot Fruit includes allowing to create, that is, agrees to creation authorization, forbid creating, that is, disagrees creation authorization.It namely authorizes and whether passes through.Needle To different authorization conditions (whether allowing to create), different operating procedures is executed respectively.

When creating Authorization result is to allow to create, case history creation write-in transaction is initiated to block chain.When creation authorization knot Fruit is to show that patient has determined that identity information and doctor has been allowed to create case history when allowing to create, at this time can be directly by case history Creation write-in transaction.It completes case history to create, and newly-built case history is sent in block chain and is stored.Preferably, it is sent to The case history that block chain is stored can be specially having signature and being ciphertext shape after being encrypted and signed by patient customer end Medical record data under state.

When creating Authorization result is to forbid creation, the creation case history ciphertext data in caching are removed.When creation authorization knot Fruit is when forbidding creation, that is, to show that patient disagrees creation case history, and the case history creation that doctor initiates at this time is invalid, in order to avoid accounting for With server-side spatial cache, directly creation case history ciphertext data can be deleted.

Therefore electronic health record management method provided by the present embodiment, in the technology effect for having above-described embodiment one It, in embodiments of the present invention can be during case history be newly-built, it can be achieved that suffer from order to which Support case history is true and reliable except fruit Based on the quality control of person, it is newly-built to case history used in identity information identify, ensure that case history is true and reliable.

Example IV:

It in the present embodiment, further include when checking that request is handled to case history, corresponding treatment process carries out specifically It is bright.

Referring to FIG. 4, Fig. 4 is that case history checks flow diagram in the embodiment of the present invention.Should the realization process includes:

S401, the case history for receiving the transmission of doctor's client check request, and case history checks that request includes doctor's client request The parameter for the case history checked.

The case history ciphertext data are that patient customer end utilizes the ciphertext number after the public key encryption in the unsymmetrical key of patient According to.In this way, even if the case history ciphertext data being stored in block chain are illegally accessed, in the non-to in key of not patient Under the premise of private key is decrypted, can not also look up the illness record detailed data, can ensure that the medical record data of patient is not leaked.

Check that the parameter of case history can be for case history ID or patient identification information, to determine specific disease that doctor need to check It goes through.

S402, it checks that request checks authorization requests to the transmission of patient customer end according to case history, checks authorization requests for asking Patient customer end authorized doctor client is asked to check the case history corresponding with parameter of patient.

That is, case history checks that the parameter of request and case history have corresponding relationship, determining case history can be found by the parameter.Example It such as, can be using case history ID as the parameter for checking case history.

Preferably, case history checks that request includes doctor's public key or doctor id.

S403, receive patient customer end to the feedback result for checking authorization requests, if feedback result be by authorization, Feedback result includes the case history ciphertext data by doctor's public key encryption, and the case history ciphertext data by doctor's public key encryption are to suffer from The case history ciphertext data downloaded from block chain are decrypted using patient's private key for person's client, after recycling doctor's public key encryption It obtains.

Since case history ciphertext data are the data after the public key encryption of patient, and the data are only capable of by the private key solution of patient It is close, at this time to make doctor that can look up the illness record, case history ciphertext data can be sent to patient customer end.So as to patient customer end benefit Case history ciphertext data are decrypted with patient's private key.

Preferably, it is requested to ensure that medical record data and server-side are fed back to server-side in patient customer end to medical record management Corresponding promoter sends medical record data process, and case history is not tampered.At this point, patient customer end can utilize medical record management request pair Public key in the unsymmetrical key for the doctor's client answered encrypts medical record data, to ensure that only having case history checks request pair The doctor answered can consult the case history.

Then, service server receive patient customer end to fed back after case history ciphertext data re-encrypted to read case history close Literary data.It is that medical record management requests the data after the public key encryption of corresponding promoter that case history ciphertext data, which can be read,.

Service server can will can read case history ciphertext data and be sent to the doctor's client for sending case history and checking request.

After the acquisition of doctor's client can read case history ciphertext data, the private key logarithm in the unsymmetrical key of itself can be utilized According to being decrypted.

It is understood that then not including case history ciphertext number in feedback result when checking Authorization result is to forbid checking According to service server can check the prompt information that case history can not be read to destination client feedback current request at this time.

Therefore electronic health record management method provided by the present embodiment, in the technology effect for having above-described embodiment one Except fruit, in order to safeguard the privacy of patient, is checked in embodiments of the present invention for case history and authorize and use encryption and decryption process Safeguard protection is carried out to medical record data.It may make patient that can voluntarily choose whether that doctor is allowed to check related case history, and allowing to look into It when seeing, only allows the doctor to check by encryption and decryption, ensures that case history is not leaked.

In practical applications, not only doctor needs to check case history, the demand that patient itself also has case history to check acquisition.To trouble The case history acquisition request that person's client is sent is handled, and corresponding treatment process includes:

Step 1: receiving the case history acquisition request that patient customer end is sent, case history acquisition request includes that patient customer end asks Seek the parameter of the case history of acquisition；

Step 2: downloading case history ciphertext data corresponding with parameter from block chain according to case history acquisition request；

Step 3: sending case history ciphertext data to patient customer end.

Patient customer end needs to obtain case history, and the specific implementation of case history can be checked with doctor's client as described above Cheng Jinhang is cross-referenced, is not repeating herein.

Embodiment five:

To more fully understand electronic health record management method provided by the embodiment of the present invention convenient for those skilled in the art, under Face is provided for the embodiments of the invention electronic health record management for combining the specific application scenarios of above-mentioned each embodiment Method is described in detail.

Referring to FIG. 5, Fig. 5 is the application scenarios schematic diagram of one of embodiment of the present invention electronic health record management method.

As shown in figure 5, doctor and patient can access electronic medical system by mobile client or pc client Server-side.Electronic medical system includes service server and block chain.It is relevant that service server handles electron medical treatment business Operation, block chain is responsible for electronic health record persistence, and ensures safety and reliability.

The client of doctor and patient has an asymmetric key pair, can register user when generate.It is wherein public Key representative capacity, i.e. identity card, private key represent ownership, on block chain, as long as the data that can be decrypted by its private key, own Power all belong to itself so.Private key stores after being encrypted by symmetric cryptography, and password only has user (patient or doctor) to know, thus Guarantee safety.

Asymmetric key pair can back up in the database at service server end (ciphertext storage), and can be set and give for change Password prompt can be taken to lose afterwards in accidentally deletion client or client carrier (mobile phone or PC) by business Business device gives key for change.Certainly, for private key safety, it is proposed that password is voluntarily saved by user.

In the electronic health record management method provided by the embodiment of the present invention, realization only allows doctor to create and update case history, Patient can only authorize and not authorize.The operation for being related to case history during the consultation of doctors is as follows:

1. creating electronic health record:

A. doctor retrieves the registered public keys of patient in the client, and creates case history and be associated with the public key, then inputs Idagnostic logout is saved and is submitted.

B. when client is clicked and submitted, client encrypts data using the public key of patient (to be suffered from doctor in this way Person could be decrypted with the private key of oneself), it is then submitted to service server, service server is temporary in the database by data, And the authorization requests of one " data to be updated " are pushed to respective patient client.

C. after patient customer's termination receives PUSH message, from the corresponding total data of the business server pull message, It is decrypted with the private key voluntarily stored, it is seen that after authorization requests.Patient can choose agreement authorization or refusal authorization.If same Meaning, then carry out trading signature to the data crossed with the public key encryption of oneself with the private key voluntarily stored, then pass through business Server initiates write-in transaction to block chain.If disagreed, the temporary corresponding data in service server end just fails.

D. block chain node receives requests transaction, is signed with the public key verifications of patient, abandons if verifying does not pass through Otherwise transaction is agreed in write-in block chain.

2. checking electronic health record:

A. doctor retrieves the case history of patient in the client, and click is checked, can initiate authorization requests to service server (request may particularly include: the Data Position and parameter and the public key of oneself of Yao Shouquan, and the public affairs of patient can be used in these data Key encryption)；

B. after service server receives authorization requests, a request authorization message is pushed to patient customer end, including A. the request data in；

C. after patient customer's termination receives pushed information, from the corresponding total data of the business server pull message, It is decrypted with the private key voluntarily stored, it is seen that after request authorized content, can choose agreement request or refusal request.If same Meaning, then pull down data from block chain, with the public key encryption for pushing the doctor to come after decryption, then passes through business service Device is pushed to doctor.

D. after doctor's client receives the PUSH message, from the corresponding total data of the business server pull message, It is decrypted with the private key of oneself, so that it may see case history content.

3. updating electronic health record:

A. doctor updates case history in client according to diagnosis situation, saves and submits.

B. when client is clicked and submitted, client encrypts data with the public key of patient doctor, then submits To service server, service server is temporary in the database by data, and pushes the authorization requests of one " data to be updated " To patient customer end.

C. after patient customer's termination receives PUSH message, from the corresponding total data of the business server pull message, It is decrypted with the private key of oneself, it is seen that after request, can choose agreement request or refusal request.If agree to, with oneself Private key carries out trading signature to the data crossed with oneself public key encryption, is then write by service server to the initiation of block chain Enter transaction.If disagreed, the temporary corresponding data in service server end just fails.

D. block chain node receives requests transaction, is signed with the public key verifications of patient, abandons if verifying does not pass through Otherwise the transaction is agreed in write-in block chain.

From above-mentioned realization process as it can be seen that the data of patient can neither be stolen, it can not be tampered and forge.For convenient for reason Solve how the technical effect specifically generates, below to be illustrated so that patient removes hospital admission as an example.

Certain day, patient A come certain hospital admission, cure mainly as doctor B.Doctor B inquires patient A and comes hospital just for the first time It examines, there are no electronic health records, so patient A is allowed to download the client of an electronic medical record system, and are registered as user.So Afterwards, doctor B has been created that an electronic health record is associated with patient A, and wherein by diagnostic result and therapeutic scheme record.Doctor After creation case history terminates, patient A can audit the case history of oneself, and then authorized doctor B is that the case history that oneself is generated comes into force.It can To see, it is masters that this case history, which creates process patient A, and doctor B is passive side, recognize this case history, is determined by patient A, Thus doctor cannot practise fraud.

Several days have been spent, patient A is subscribed to doctor's B further consultation, and doctor B finds the case history of patient A from client, and click is checked, Doctor B can not be consulted at this time, and case history content can just be seen by needing patient A to be authorized in the client of oneself.Patient A from oneself Client be doctor B authorize, doctor B skims through case history, then carry out the diagnosis of today again, and provide therapeutic scheme, These are also recorded in case history.After end, patient A can audit the case history of oneself, and then authorized doctor B is the case history of oneself Update comes into force, or does not authorize.As it can be seen that it is masters that process patient A is checked and modified to this case history, doctor B is passive side, doctor Life cannot at will modify the case history of patient.

Embodiment six:

Corresponding to above method embodiment, the embodiment of the invention also provides a kind of electronic health record managing devices, hereafter The electronic health record managing device of description can correspond to each other reference with above-described electronic health record management method.

Shown in Figure 6, which comprises the following modules:

Request receiving module 101 is managed, for receiving the medical record management request of doctor's client transmission, medical record management request For requesting to be managed the case history of patient；

Authorization inquiry module 102 sends management authorization requests, management to patient customer end for requesting according to medical record management Authorization requests are for requesting patient customer end authorized doctor client to be managed the case history of patient；

Ask respond module 103 is managed, for receiving patient customer end to the feedback result of management authorization requests, if instead Presenting result is then to be managed using case history of the block chain to patient by authorization to respond medical record management request.

It is asked after receiving medical record management request according to medical record management using device provided by the embodiment of the present invention It asks to patient customer end and sends management authorization requests, to allow patient to determine whether to agree to management of the doctor to case history.It is receiving After the feedback result sent to patient customer end, when feedback result is to pass through authorization, then using block chain to the disease of patient It goes through and is managed, to respond medical record management request.As it can be seen that patient is in case history renewal process with the person of checking on of medical record data and master Lead controller's presence.Due to being requested using block chain response medical record management, relative to the mode only stored in central server, The present apparatus enables to case history not to be tampered, and has further ensured leading position of patient during medical record management, has avoided disease It goes through and is distorted by premeditated, influence the equity of doctor or patient.

In a kind of specific embodiment of the invention, ask respond module 103 is managed, comprising:

Case history updating unit is used to then utilize block chain to patient's when medical record management request is that case history updates request Case history is updated to respond medical record management request；

Case history creates unit, for when medical record management request is case history request to create, then utilizing block chain to patient's Case history is created to respond medical record management request.

In a kind of specific embodiment of the invention, case history updating unit, being specifically used for medical record management request is case history Request is updated, it includes the case history ciphertext data to be updated by patient's public key encryption that case history, which updates request,；Managing authorization requests is Case history updates authorization requests, and it includes case history ciphertext data to be updated that case history, which updates authorization requests,；Feedback result includes passing through patient Signature of the private key to case history ciphertext data to be updated；It is managed using case history of the block chain to patient to respond medical record management and ask Asking includes: to initiate to update case history write-in transaction to block chain, so that by case history ciphertext to be updated after block chain link point sign test signature Block chain is written in data.

In a kind of specific embodiment of the invention, case history creates unit, and being specifically used for medical record management request is case history Request to create, case history request to create include the case history ciphertext data to be created by patient's public key encryption；Feedback result includes warp Patient's private key is crossed to the signature of case history ciphertext data to be created；It is managed using case history of the block chain to patient to respond case history Management request includes: to initiate to update creation write-in transaction to block chain, so that by disease to be created after block chain link point sign test signature Go through ciphertext data write-in block chain.

In a kind of specific embodiment of the invention, further includes: request processing module is checked, for receiving doctor client The case history that end is sent checks request, and case history checks that request includes the parameter for the case history that doctor's client request is checked；According to case history It checks that request is sent to patient customer end and checks authorization requests, check authorization requests for requesting patient customer end authorized doctor objective The case history corresponding with parameter of patient is checked at family end；Patient customer end is received to the feedback result for checking authorization requests, if Feedback result is by authorization, then feedback result includes the case history ciphertext data by doctor's public key encryption, by doctor's public key The case history ciphertext data of encryption are that patient customer end solves the case history ciphertext data downloaded from block chain using patient's private key It is close, it is obtained after recycling doctor's public key encryption.

In a kind of specific embodiment of the invention, case history checks that request includes doctor's public key or doctor id.

Embodiment six:

Corresponding to above method embodiment, the embodiment of the invention also provides a kind of electronic health record management equipments, hereafter A kind of electronic health record management equipment of description can correspond to each other reference with a kind of above-described electronic health record management method.

Referring to FIG. 7, the electronic health record management equipment includes:

Memory D1, for saving computer program；

Processor D2, for executing computer program, to realize electronic health record manager disclosed in above-mentioned any embodiment Method.

In the present embodiment, electronic health record management equipment can be PC (Personal Computer, PC), It can be smart phone, tablet computer, palm PC or portable computer.

Electronic health record management equipment is that composition CDN network or the node of the block chain network electronic health record management equipment can To be the node for forming CDN (Content Delivery Network) network or block chain network.

Fig. 8 is referred to, Fig. 8 is the structural schematic diagram of another electronic health record management equipment in the embodiment of the present invention.It should Electronic health record management equipment may include memory 11, processor 12 and bus 13.

Wherein, memory 11 includes at least a type of readable storage medium storing program for executing, and readable storage medium storing program for executing includes flash memory, hard Disk, multimedia card, card-type memory (for example, SD or DX memory etc.), magnetic storage, disk, CD etc..Memory 11 exists It can be the internal storage unit of electronic health record management equipment in some embodiments, such as the electronic health record management equipment is hard Disk.Memory 11 is also possible to the External memory equipment of electronic health record management equipment, such as electronics disease in further embodiments Go through the plug-in type hard disk being equipped in management equipment, intelligent memory card (Smart Media Card, SMC), secure digital (Secure Digital, SD) card, flash card (Flash Card) etc..Further, memory 11 can also both include electronic health record management The internal storage unit of equipment also includes External memory equipment.Memory 11 can be not only used for storage and be installed on electronic health record pipe The application software and Various types of data, such as the code of electronic health record management program etc. for managing equipment, can be also used for temporarily storing The data that has exported or will export.

Processor 12 can be in some embodiments a central processing unit (Central Processing Unit, CPU), controller, microcontroller, microprocessor or other data processing chips, the program for being stored in run memory 11 Code or processing data, such as execute electronic health record management program etc..

The bus 13 can be Peripheral Component Interconnect standard (peripheral component interconnect, abbreviation PCI) bus or expanding the industrial standard structure (extended industry standard architecture, abbreviation EISA) Bus etc..The bus can be divided into address bus, data/address bus, control bus etc..For convenient for indicating, in Fig. 8 only with one slightly Line indicates, it is not intended that an only bus or a type of bus.

Further, electronic health record management equipment can also include network interface, and network interface optionally may include having Line interface and/or wireless interface (such as WI-FI interface, blue tooth interface), commonly used in the equipment and other electronic equipments it Between establish communication connection.

Optionally, which can also include user interface, and user interface may include display (Display), input Unit such as keyboard (Keyboard), optional user interface can also include standard wireline interface and wireless interface.It is optional Ground, in some embodiments, display can be light-emitting diode display, liquid crystal display, touch-control liquid crystal display and OLED (Organic Light-Emitting Diode, Organic Light Emitting Diode) touches device etc..Wherein, display can also be appropriate Referred to as display screen or display unit, for showing the information handled in the device and for showing visual user circle Face.

Fig. 8 illustrates only the electronic health record management equipment with component 11-13, it will be appreciated by those skilled in the art that It is that the structure shown in Fig. 8 does not constitute the restriction to equipment, may include than illustrating less perhaps more components or group Close certain components or different component layouts.

Step in electronic health record management method as described above can be realized by the structure of electronic health record management equipment.

Embodiment eight:

Corresponding to above method embodiment, the embodiment of the invention also provides a kind of _ based Patient Records Management Systems, hereafter A kind of _ based Patient Records Management Systems of description can correspond to each other reference with a kind of above-described electronic health record management method.

The system includes service server, patient customer end, doctor's client and block chain；

Wherein, doctor's client, for sending medical record management request to service server, medical record management is requested for requesting The case history of patient is managed；

Service server, for receiving medical record management request；It requests to send to patient customer end according to medical record management and manage Authorization requests, management authorization requests are for requesting patient customer end authorized doctor client to be managed the case history of patient；It connects Patient customer end is received to the feedback result of management authorization requests, using block chain to patient if feedback result is by authorization Case history be managed with respond medical record management request；

Patient customer end is sent for receiving management authorization requests, and to service server to the anti-of management authorization requests Present result；

Block chain, for storing the case history of the patient by encryption.

Wherein, the communication connection of the service server in the system, patient customer end, doctor's client and block chain is closed System can refer to Fig. 5.

_ based Patient Records Management Systems based on block chain provided by the embodiment of the present invention can be realized to above method reality The technical effect of the electronic health record management method based on block chain provided by example is applied, this is no longer going to repeat them.

Embodiment nine:

Corresponding to above method embodiment, the embodiment of the invention also provides a kind of readable storage medium storing program for executing, are described below A kind of readable storage medium storing program for executing can correspond to each other reference with a kind of above-described electronic health record management method.

A kind of readable storage medium storing program for executing is stored with computer program on readable storage medium storing program for executing, and computer program is held by processor The step of electronic health record management method of above method embodiment is realized when row.

The readable storage medium storing program for executing be specifically as follows USB flash disk, mobile hard disk, read-only memory (Read-Only Memory, ROM), the various program storage generations such as random access memory (Random Access Memory, RAM), magnetic or disk The readable storage medium storing program for executing of code.

Embodiment ten:

Corresponding to above method embodiment, the embodiment of the invention also provides a kind of computer program products, hereafter retouch A kind of computer program product stated can correspond to each other reference with a kind of above-described electronic health record management method.

A kind of computer program product, including computer instruction, when run on a computer, so that computer can be with Execute electronic health record management method disclosed in above method embodiment.

Computer program product includes one or more computer instructions.Load and execute on computers computer program When instruction, the process or function according to the embodiment of the present invention are entirely or partly generated.Computer can be general purpose computer, specially With computer, computer network or other programmable devices.Computer instruction can store in computer readable storage medium In, or transmit from a computer readable storage medium to another computer readable storage medium, for example, computer instruction can To pass through wired (such as coaxial cable, optical fiber, Digital Subscriber Line from a web-site, computer, server or data center (DSL)) or wireless (such as infrared, wireless, microwave etc.) mode is into another web-site, computer, server or data The heart is transmitted.Computer readable storage medium can be any usable medium or include one that computer can store Or the data storage devices such as integrated server, data center of multiple usable mediums.Usable medium can be magnetic medium, (example Such as, floppy disk, hard disk, tape), optical medium (for example, DVD) or semiconductor medium (such as solid state hard disk Solid State Disk (SSD)) etc..

In conclusion above embodiments of the present invention have the following beneficial effects: 1, doctor's client pair compared with prior art The creation of patient medical record data checks, updates etc. that operations are required to the authorization of patient customer end, so that patient has grasped the control of case history System power；2, encrypted patient medical record data are saved using block chain, due to the data characteristic that block chain can not be distorted, therefore can be with Case history is prevented to be tampered；3, encrypted patient medical record data are saved using block chain, the node that the block chain is added is ok Encrypted patient medical record data are got, as long as the hospital that patient successively sees a doctor in this way is added to the block chain, patient exists When Different hospital is gone to a doctor, the data such as medical situation before, inspection result can be recorded in block chain by checking Case history (needs patient customer end to authorize), avoids rechecking and treatment, saves medical resource.

It is apparent to those skilled in the art that for convenience and simplicity of description, the system of foregoing description, The specific work process of device and unit, can refer to corresponding processes in the foregoing method embodiment, and details are not described herein.

In several embodiments provided herein, it should be understood that disclosed equipment, device and method can be with It realizes by another way.For example, the apparatus embodiments described above are merely exemplary, for example, the division of unit, Only a kind of logical function partition, there may be another division manner in actual implementation, such as multiple units or components can be with In conjunction with or be desirably integrated into another system, or some features can be ignored or not executed.Another point, it is shown or discussed Mutual coupling, direct-coupling or communication connection can be through some interfaces, the INDIRECT COUPLING of device or unit or Communication connection can be electrical property, mechanical or other forms.

Unit may or may not be physically separated as illustrated by the separation member, shown as a unit Component may or may not be physical unit, it can and it is in one place, or may be distributed over multiple networks On unit.It can some or all of the units may be selected to achieve the purpose of the solution of this embodiment according to the actual needs.

It, can also be in addition, each functional unit in each embodiment of the application can integrate in one processing unit It is that each unit physically exists alone, can also be integrated in one unit with two or more units.Professional may be used also To be further appreciated that, unit and algorithm steps described in conjunction with the examples disclosed in the embodiments of the present disclosure can be with electricity The combination of sub- hardware, computer software or the two is realized, in order to clearly illustrate the interchangeability of hardware and software, upper It states in bright and generally describes each exemplary composition and step according to function.These functions are actually with hardware or soft Part mode executes, specific application and design constraint depending on technical solution.Professional technician can be to each spy Fixed application uses different methods to achieve the described function, but this realizes it is not considered that exceeding model of the invention It encloses.

It, can if integrated unit is realized in the form of SFU software functional unit and when sold or used as an independent product To be stored in a computer readable storage medium.Based on this understanding, the technical solution of the application substantially or Say that all or part of the part that contributes to existing technology or the technical solution can embody in the form of software products Out, which is stored in a storage medium, including some instructions are used so that a computer equipment The all or part of (can be personal computer, server or the network equipment etc.) execution each embodiment method of the application Step.And storage medium above-mentioned includes: USB flash disk, mobile hard disk, read-only memory (ROM, Read-OnlyMemory), deposits at random The various media that can store program code such as access to memory (RAM, RandomAccessMemory), magnetic or disk.

It should be noted that the serial number of the above embodiments of the invention is only for description, do not represent the advantages or disadvantages of the embodiments.And The terms "include", "comprise" herein or any other variant thereof is intended to cover non-exclusive inclusion, so that packet Process, device, article or the method for including a series of elements not only include those elements, but also including being not explicitly listed Other element, or further include for this process, device, article or the intrinsic element of method.Do not limiting more In the case where, the element that is limited by sentence "including a ...", it is not excluded that including process, device, the article of the element Or there is also other identical elements in method.

The above is only a preferred embodiment of the present invention, is not intended to limit the scope of the invention, all to utilize this hair Equivalent structure or equivalent flow shift made by bright specification and accompanying drawing content is applied directly or indirectly in other relevant skills Art field, is included within the scope of the present invention.

Claims

1. a kind of electronic health record management method based on block chain is applied to service server, which is characterized in that the method packet It includes:

The medical record management request that doctor's client is sent is received, the medical record management request is for requesting the case history to patient to carry out Management；

It is requested to send management authorization requests to patient customer end according to the medical record management, the management authorization requests are for requesting Patient customer end authorizes doctor's client to be managed the case history of the patient；

The patient customer end is received to the feedback result of the management authorization requests, if the feedback result is by awarding Power is then managed to respond the medical record management request using case history of the block chain to the patient.

2. it is requested the method according to claim 1, wherein the medical record management requests to update for case history, it is described It includes the case history ciphertext data to be updated by patient's public key encryption that case history, which updates request,；

The management authorization requests are that case history updates authorization requests, and it includes the case history to be updated that the case history, which updates authorization requests, Ciphertext data；

Described be managed using case history of the block chain to the patient to respond the medical record management request includes: to block chain It initiates to update case history write-in transaction, so as to which the case history ciphertext data to be updated are written after signing described in block chain link point sign test Block chain.

3. the method according to claim 1, wherein the medical record management request be case history request to create, it is described Case history request to create includes the case history ciphertext data to be created by patient's public key encryption；

Described be managed using case history of the block chain to the patient to respond the medical record management request includes: to block chain It initiates to update creation write-in transaction, so as to which the case history ciphertext data to be created are written after signing described in block chain link point sign test Block chain.

4. according to the method in claim 2 or 3, which is characterized in that the method also includes: receive doctor's client The case history of transmission checks request, and the case history checks that request includes the parameter for the case history that doctor's client request is checked；

It checks that request is sent to patient customer end according to the case history and checks authorization requests, it is described to check authorization requests for requesting Patient customer end authorizes doctor's client to check the case history corresponding with the parameter of the patient；

The patient customer end is received to the feedback result for checking authorization requests, if the feedback result is by awarding Power, then the feedback result includes the case history ciphertext data by doctor's public key encryption, described to pass through doctor's public key The case history ciphertext data of encryption are that the patient customer end is private using patient to the case history ciphertext data downloaded from the block chain Key is decrypted, and obtains after recycling doctor's public key encryption.

5. according to the method described in claim 4, it is characterized in that, the case history checks that request includes doctor's public key or doctor id。

6. according to the method in claim 2 or 3, which is characterized in that the method also includes:

The case history acquisition request that the patient customer end is sent is received, the case history acquisition request includes that the request of patient customer end obtains The parameter of the case history taken；

According to the case history acquisition request, case history ciphertext data corresponding with the parameter are downloaded from the block chain；

The case history ciphertext data are sent to the patient customer end.

7. a kind of electronic health record managing device characterized by comprising

Request receiving module is managed, for receiving the medical record management request of doctor's client transmission, the medical record management request is used The case history of patient is managed in request；

Authorization inquiry module sends management authorization requests, the pipe to patient customer end for requesting according to the medical record management Reason authorization requests are for requesting patient customer end that doctor's client is authorized to be managed the case history of the patient；

Ask respond module is managed, for receiving the patient customer end to the feedback result of the management authorization requests, if The feedback result is then to be managed by authorization using case history of the block chain to the patient to respond the medical record management Request.

8. device according to claim 7, which is characterized in that the management ask respond module, comprising:

Case history updating unit is used to then utilize block chain to the trouble when medical record management request is that case history updates request The case history of person is updated to respond the medical record management request；

Case history creates unit, for when medical record management request is case history request to create, then utilizing block chain to the trouble The case history of person is created to respond the medical record management request.

9. a kind of _ based Patient Records Management Systems, which is characterized in that including service server, patient customer end, doctor's client with And block chain；

Wherein, doctor's client, for sending medical record management request, the medical record management request to the service server For requesting to be managed the case history of patient；

The service server, for receiving the medical record management request；It is requested according to the medical record management to the patient visitor Family end sends management authorization requests, and the management authorization requests are for requesting the patient customer end to authorize doctor's client The case history of the patient is managed；The patient customer end is received to the feedback result of the management authorization requests, if The feedback result is then to be managed by authorization using case history of the block chain to the patient to respond the medical record management Request；

The patient customer end is sent for receiving the management authorization requests, and to the service server to the management The feedback result of authorization requests；

The block chain, for storing the case history of the patient by encryption.

10. a kind of electronic health record management equipment characterized by comprising

Memory, for storing computer program；

Processor realizes the electronic health record manager as described in any one of claim 1 to 6 when for executing the computer program The step of method.

11. a kind of readable storage medium storing program for executing, which is characterized in that be stored with computer program, the meter on the readable storage medium storing program for executing It is realized when calculation machine program is executed by processor as described in any one of claim 1 to 6 the step of electronic health record management method.