KR101894661B1 - Medical treatment information transfer system and medical treatment information transfer method - Google Patents

Abstract

The present application relates to an information exchange system and a method thereof and, more specifically, to an information exchange system for providing patient treatment information to a user terminal and a method thereof. According to an embodiment of the present application, a hospital treatment system of a medical treatment information system comprises a hospital EMR server which stores medical treatment information of a patient; and a medical treatment information server which is physically distinguished from the hospital EMR server, and stores medical treatment information received from the hospital EMR server. The medical treatment information server comprises an encryption engine for encrypting medical treatment information received from the hospital EMR server; and a medical treatment information database (hereinafter, MT DB) for storing the medical treatment information encrypted by the encryption engine. The medical treatment information exchange system according to an embodiment of the present application enables an individual patient to conveniently check medical treatment information through a user terminal, and can also secure high confidentiality of the medical treatment information.

Description

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a medical information exchange system and a medical information exchange method,

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to an information exchange system and a method thereof, and more particularly, to an information exchange system and a method thereof for providing patient information to a user terminal.

The exchange of medical information is traditionally used when a patient is referred from a subordinate medical institution (for example, a first or second medical institution such as a private hospital or a small hospital) to a higher medical institution (for example, a university hospital or a general hospital) . For example, it was necessary to exchange medical information when requesting medical information of a patient visiting a private hospital to a general hospital.

On the other hand, as the development of information communication and the interest in health have increased in recent years, demands for confirming personal health records are also increasing. Especially, as the establishment of the electronic medical treatment system in the hospital spreads, there is an increasing need for individual patients to directly read their medical information and check personal medical records.

However, it is difficult to access the personal medical information provided to the patient at the hospital only due to the prevention of leakage of the patient's medical information, and it is difficult for the individual patient to use a user terminal such as a smart phone from the outside.

An object of the present invention is to provide a medical care information exchange system and a medical care information communication method that can easily check medical care information using a user terminal while at the same time ensuring the confidentiality of medical care information.

The hospital medical treatment system of the medical care information exchange system according to the embodiment of the present application includes a hospital EMR server that stores medical information of a patient; A medical care information server physically distinguished from the hospital EMR server and storing medical care information received from the hospital EMR server, the medical care information server comprising: an encryption engine for encrypting medical care information received from the hospital EMR server; And a medical care information database (hereinafter referred to as an MT DB) storing medical care information encrypted by the encryption engine.

In the embodiment, the medical care information server further includes a medical care information requesting unit for receiving an identification code from the outside, and requesting the hospital EMR server for medical treatment information corresponding to the identification code.

In an embodiment, the medical care information server includes an identification code combiner for combining the identification code and the encrypted medical care information corresponding to the identification code; And a transmitter for transmitting the identification code and encrypted medical care information corresponding to the identification code to an information relay server physically separated from the medical care information server.

The information relay server of the medical care information exchange system according to the embodiment of the present application includes a receiver for receiving encrypted medical care information from an external medical care information server; An encrypted medical care information database (EMT DB) for storing the encrypted medical care information received through the receiver; A decryption engine for decrypting the encrypted medical care information stored in the EMT DB in response to a request from the user terminal; And a transmitter for transmitting the decoded medical care information to the user terminal.

In an embodiment, the receiver receives an identification code corresponding to the encrypted medical care information from the medical care information server, and the EMT DB includes a mapping table for managing the identification code and the encrypted medical care information corresponding to the identification code .

An identification code verifier for verifying whether a target identification code corresponding to a request of the user terminal exists among a plurality of identification codes managed in the mapping table in response to a request of the user terminal; And an identification code generator for generating the target identification code based on a request of the user terminal in the absence of the target identification code among a plurality of identification codes managed in the mapping table.

In the embodiment, when there is the target identification code among the plurality of identification codes managed in the mapping table, the decryption engine decrypts the encrypted medical care information corresponding to the target identification code, and the transmitter decrypts the decrypted And transmits the medical care information to the superior terminal.

In an embodiment, the information management apparatus further includes an information manager for, in response to the information destruction request, deleting the selected encrypted medical care information from a plurality of encrypted medical care information stored in the EMT DB.

The apparatus of claim 1, further comprising: a volatile memory for temporarily storing the decoded medical information by the decryption engine; And an information manager for deleting the selected data from the plurality of data included in the decoded medical care information.

In an embodiment, the apparatus further includes an encryption engine for re-encrypting the unselected data among the plurality of data included in the decrypted medical information.

In an embodiment, the information manager selects data to be deleted based on a generation time of a plurality of data included in the decoded medical care information.

The medical information exchange method according to an embodiment of the present application includes encrypting medical information received from a hospital EMR server in a hospital medical service system; Storing the encrypted medical care information in a medical care information database (hereinafter referred to as MT DB) in the hospital medical care system; Transmitting the encrypted medical care information stored in the MT DB to an information relay server located outside the hospital care system; Storing the encrypted medical care information in an encrypted medical care information database (hereinafter EMT DB) in the information relay server; Decrypting the encrypted medical care information stored in the EMT DB in response to a request from the user terminal; And transmitting the decoded medical care information to the user terminal.

The medical consultation information exchange system according to the embodiment of the present application not only allows the individual patient to easily check the medical care information through the user terminal but also ensures the confidentiality of the medical care information to a high level.

1 is a view showing a medical care information exchange system according to an embodiment of the present application.
2 is a flowchart showing the operation of the medical care information exchange system of FIG.
FIG. 3 is a view showing an embodiment of the care information server of FIG. 1;
4 is a flowchart for explaining the operation of the care information server of FIG.
FIG. 5 is a view showing an embodiment of the information relay server of FIG. 1. FIG.
FIG. 6 is a flowchart showing the operation of storing operation information of the information relay server of FIG. 5;
FIG. 7 is a flowchart showing a response operation to the medical information request of the information relay server of FIG. 5;
8 is a view showing a medical care relay server according to another embodiment of the present application.
FIG. 9 is an exemplary view showing a mandatory retention period for each of a plurality of data included in one medical care information.
10 is a view showing an information relay server according to another embodiment of the present application.
11 is a flowchart illustrating some data destruction operations performed by the information relay server of FIG.

The medical care information exchange system according to the embodiment of the present application provides a medical care information exchange service for allowing a user to conveniently check hospital medical care information through an application installed in a mobile terminal and / or a program installed in a personal computer. In addition, the medical care information exchange system according to the embodiment of the present application can secure the confidentiality of the medical care information by encrypting and transmitting the medical care information of the user.

Hereinafter, embodiments of the present invention will be described with reference to the accompanying drawings in order to facilitate a person skilled in the art to easily implement the technical idea of the present application.

1 is a view showing a medical care information exchange system 10 according to an embodiment of the present application. 1, the medical care information exchange system 10 includes a hospital medical treatment system 100, an information relay server 200, and a user terminal 300. As shown in FIG.

The hospital medical treatment system 100 refers to an electronic medical care system installed in a hospital to electronically record, store and manage patient's medical care information. For example, the hospital care system 100 may be an electronic medical care system installed at a higher medical institution such as a university hospital or a general hospital. In another example, the hospital care system 100 may be an electronic care system installed at a sub-medical facility, such as an individual or a small-sized clinic. The hospital care system 100 includes a hospital EMR server 110 and a care information server 120.

The hospital EMR server 110 refers to a server that manages and stores an electronic medical record, that is, a medical record of a patient in a hospital. The hospital EMR server 10 can manage and store information on the patient's medical record, for example, a medical record, a prescription, an operation record, an inspection record, a radiograph, and the like. The hospital EMR server 110 may be, for example, a general-purpose server installed in a hospital having an ordinary EMR system.

The medical care information server 120 is a server installed in the hospital, and indicates a server independent of the hospital EMR server 110. [ For example, the medical care information server 120 and the hospital EMR server 110 may be installed in the same hospital but may be independent servers physically separated from each other.

The medical care information server 120 receives the patient's medical care information from the hospital EMR server 110, and encrypts and stores the received medical care information. To this end, the care information server 120 includes an encryption engine 122 for encrypting the care information and a medical treatment data base (MT DB) 124 for storing the encrypted care information.

The information relay server 200 receives the encrypted medical care information from the medical care information server 120 and stores the received encrypted medical care information. In response to the request from the user terminal, the information relay server 200 decrypts the encrypted medical care information and transmits the decrypted medical care information to the user terminal 300. [ To this end, the information relay server 200 includes an Encrypted Medical Treatment Data Base (EMT DB) 220 for storing the encrypted medical care information and a decryption engine 240 for decrypting the encrypted medical care information .

User terminal 300 refers to a mobile terminal such as a smart phone, tablet PC, and / or personal computer. The user terminal 300 may be provided with an application 310 supporting the medical care information exchange technology of the present invention downloaded from an application store and / or a play store.

The user terminal 300 may receive the decoded care information from the information relay server 200 and the application 310 may provide the received care information to the user in a visual and / or auditory manner.

FIG. 2 is a flowchart showing the operation of the medical care information exchange system 10 of FIG.

In step S10, the user terminal 300 requests the information relay server 200 for treatment information.

For example, the user terminal 300 may request treatment information for the owner of the user terminal 300. In another example, the user terminal 300 may request treatment information for the family of the user terminal 300.

In step S20, the information relay server 200 accesses the hospital treatment system 100 corresponding to the request of the user terminal 300 among a plurality of hospitals and requests the corresponding treatment information.

For example, the information relay server 200 can access the hospital medical service system installed in only one of a plurality of hospitals adopting the medical information exchange system of the present application to request medical information. As another example, the information relay server 200 may access at least two out of a plurality of hospitals adopting the medical information system of the present application to request medical information.

In step S30, the care information server 120 of the hospital care system 100 transmits the care information requested by the user terminal to the information relay server 200. [

For example, the medical care information server 120 encrypts and stores the medical care information in the MT DB 124 before requesting the medical care information from the information relay server 200, and stores the encrypted medical care information previously stored in response to the medical care information request To the information relay server 200. As another example, the care information server 120 may receive the care information from the EMR server 110 in response to the request of the information relay server 200, encrypt the received care information, and transmit the encrypted information to the information relay server 200 .

In step S40, the information relay server 200 receives the encrypted medical care information and decrypts the encrypted medical care information.

For example, the EMT DB of the information relay server 200 stores the encrypted medical care information transmitted from the medical care information server 120, and the decryption engine 240 of the information relay server 200 stores the encrypted medical care information It can be decoded.

In step S50, the information relay server 200 provides the decrypted care information to the user terminal 300. [

In step S60, the user terminal 300 provides the user with the received medical care information through the installed application 310. [

As described above, the medical care information exchange system 10 according to the embodiment of the present application allows the user to easily check the hospital medical care information through the application 310 installed in the user terminal 300 or the like. In addition, the medical care information exchange system 10 according to the embodiment of the present application can secure the confidentiality of the medical care information by encrypting and transmitting the medical care information of the user. In addition, the medical care information exchange system 10 according to the embodiment of the present application can more easily confirm and manage the health of the family by allowing the medical care information of the family other than the principal to be confirmed through the authentication procedure.

On the other hand, the medical care information server and the information relay server constituting the medical care information exchange system 10 of the present application can be implemented in various ways. Hereinafter, specific embodiments of the medical information server and the information relay server according to the embodiment of the present application will be described in more detail.

3 is a view showing an embodiment of the care information server 120 of FIG. The care information server 120 of FIG. 3 and the care information server 120 of FIG. 1 are similar. Accordingly, the same or similar configurations will be described below using the same or similar reference numerals.

3, the medical care information server 120 includes a medical care information requesting unit 121, an encryption engine 122, an identification code combiner 123, an MT DB 124, and a transmitter 125.

The medical care information requesting unit 121 receives the identification code from the information relay server 200 (see FIG. 1). The medical information requesting unit 121 requests the hospital EMR server 110 for medical information on the patient corresponding to the identification code and the hospital EMR server 110 transmits the medical information about the requested patient to the medical information requesting unit 121 ).

Here, the identification code means a unique code for specifying a patient to which the user terminal requests the treatment information. For example, the identification code may include a hospital code for specifying a prescribed hospital among a plurality of hospitals, and a personal code for specifying a predetermined patient among a plurality of patients of the hospital.

The encryption engine 122 receives the care information about the patient from the care information requester 121 and encrypts the received care information. For example, the encryption engine 122 may encrypt the care information using a block cipher algorithm with a security strength of a certain bit. Here, the block cipher algorithm is an algorithm that divides the plain text into a certain block size and encrypts each block using a secret key shared between the sender and the receiver.

The identification code combiner 123 receives the identification code from the information relay server 200 and receives the encrypted medical care information from the encryption engine 122. The identification code combiner 123 combines the identification code with the encrypted medical care information. Therefore, not only the medical information of the patient is encrypted, but also the personal information of the patient corresponding to the medical information is also replaced with the identification code. Therefore, when the medical information on the predetermined patient is transmitted to the outside, Can be further guaranteed.

The MT DB 124 receives the identification code and the encrypted medical care information corresponding to the predetermined patient from the identification code combiner 123, and stores the same. Then, the identification code and the encrypted medical care information for a predetermined patient stored in the MT DB 124 are transmitted to the information relay server 200 through the transmitter 125. [

FIG. 4 is a flowchart for explaining the operation of the care information server 120 of FIG.

In step S110, the medical care information requesting unit 121 requests the hospital EMR server 110 for the patient's medical care information corresponding to the identification code, and receives the medical care information from the hospital EMR server 110. [

In step S120, the encryption engine 122 receives the care information from the care information requester 122 and encrypts the received care information.

In step S130, the identification code combiner receives the encrypted medical care information from the encryption engine 122 and combines the identification code with the encrypted medical care information.

In step S140, the MT DB 140 receives the encrypted medical care information combined with the identification code, and stores the encrypted medical care information.

In step S150, the transmitter 125 receives the encrypted medical care information combined with the identification code from the MT DB 124, and transmits the encrypted medical care information to the information relay server 200. [

Meanwhile, in the embodiment according to the technical idea of the present application, the above-described steps S110 to S15 may be performed at various time intervals according to the designer's setting. For example, steps S110 through S150 may be performed as soon as the patient visits the hospital and the medical care information is stored in the hospital EMR server 110. As another example, steps S110 to S150 may be performed in accordance with a preset time period. As another example, steps S110 to S150 may be performed each time the user terminal 300 is in a request.

FIG. 5 is a diagram showing an embodiment of the information relay server 200 of FIG. The information relay server 200 of FIG. 5 and the information relay server 200 of FIG. 1 are similar. Accordingly, the same or similar configurations will be described below using the same or similar reference numerals.

5, the information relay server 200 includes a receiver 210, an EMT DB 220, a decryption engine 230, a transmitter 240, an identification code verifier 250, and an identification code generator 260 .

The receiver 210 receives the encrypted medical care information with the identification code combined from the care information server 120. [ The receiver 210 transmits the encrypted medical care information combined with the corresponding identification code to the EMT DB 220.

Receiver 210 also receives a request for a patient's care information from user terminal 300. The receiver 210 transmits a request for the medical care information of the predetermined patient to the identification code verifier 250.

The EMT DB 220 receives the encrypted medical care unit combined with the identification code from the receiver and stores it. The EMT DB 220 can store and manage the identification code and corresponding encrypted medical information using, for example, a mapping table.

The decryption engine 230 receives the encrypted medical care information combined with the identification code from the EMT DB 220. The decryption engine 230 decrypts the encrypted medical care corresponding to the identification code when the identification code for the patient requested from the user terminal 300 and the identification code stored in the EMT DB 220 coincide with each other, Information from the EMT DB 220 can be received.

Also, the decryption engine 230 performs a decryption operation on the encrypted medical care information. The decryption engine 230 can perform a decryption operation on the encrypted medical care information using, for example, a predetermined decryption key. The decryption engine 230 transmits decrypted medical information to the transmitter 240 and transmits the decrypted medical information to the user terminal 300 through the transmitter 240.

The identification code verifier 250 receives a request for a patient's medical care information from a receiver. The identification code verifier 250 refers to the EMT DB 220 and confirms whether an identification code corresponding to the patient exists. For example, the identification code verifier 250 can check the presence of the identification code by checking the mapping cable stored in the EMT DB 220.

The identification code generator 260 receives a signal (hereinafter referred to as an identification code non-existence signal) indicating that the identification code corresponding to the patient requested by the identification code verifier 250 does not exist. The identification code generator 260 generates an identification code in response to the identification code non-existence signal, and transmits the identification code to the transmitter 240.

The identification code includes a hospital code indicating a hospital where the patient is treated and a personal code indicating personal information of the patient. Information on the hospital code and the personal code is transmitted to the user terminal 300 and / or the care information server 120 ). ≪ / RTI >

On the other hand, the transmitter 240 refers to the hospital code of the received identification code, and transmits the identification code to the hospital care system 100 of the hospital where the treatment information is stored.

FIG. 6 is a flowchart showing the operation of storing operation information of the information relay server 200 of FIG.

In step S210, the receiver 210 of the information relay server 200 receives the encrypted medical care information and the identification code from the care information server 120. [

In step S220, the receiver 210 transmits the encrypted medical care information and the identification code to the EMT DB 220, and the EMT DB 220 stores the same.

Meanwhile, the operation of storing the encrypted medical care information and the identification code described in FIGS. 5 and 6 in the EMT DB 220 can be performed at various time intervals. For example, the operation of storing the encrypted medical care information and the identification code in the EMT DB 220 can be performed each time the patient visits the hospital. As another example, the medical care information server 120 and the information relay server 200 are designed to transmit and receive data every predetermined time period, and the EMT DB 220 receives the encrypted medical care information and the identification code in a predetermined time period You can save it every time.

FIG. 7 is a flowchart showing a response operation to the medical care information request of the information relay server 200 of FIG.

In step S310, the receiver 210 of the information relay server 200 receives a request for treatment information from the user terminal 300. [

In step S320, the identification code verifier 250 confirms whether an identification code corresponding to the medical care information request of the user terminal 300 among the identification codes managed in the mapping table of the EMT DB 220 exists.

If there is an identification code in the mapping table of the EMT DB 220, the identification code verifier 250 selects the information about the identification code and transmits the selected information to the EMT DB 220 so that the selected information is transmitted to the decryption engine 230. [ (Step S370). Thereafter, the decryption engine 230 decrypts the encrypted medical care information (step S380), and the transmitter 240 transmits the decrypted medical care information to the user terminal 300. [

If the identification code does not exist in the mapping table of the EMT DB 220, the identification code generator 260 refers to the information of the user terminal 300 requesting the care information (such as the inpatient hospital and the patient personal information) (Step S330). The identification code generator 260 transmits the identification code to the transmitter 240, and the transmitter 240 transmits the identification code to the corresponding care information server 120 in step S340. The receiver 210 of the information relay server 200 receives the encrypted medical care information from the medical care information server 120 in step S350 and stores the received information in the EMT DB 220 in step S360. Thereafter, steps S370 to S390 are sequentially performed.

It should be understood, however, that the above description is exemplary and that the technical idea of the present application is not limited thereto. The technical idea of the present application can be variously applied and applied by a person having ordinary skill in the technical field of the present application. Hereinafter, as an application example of the present application, an embodiment including a function of discarding personal information will be described in more detail.

FIG. 8 is a view showing a medical care relay server 200 'according to another embodiment of the present application. The information relay server 200 'of FIG. 8 is similar to the information relay server 200 of FIG. Accordingly, the same or similar configurations will be described using the same or similar reference numerals, and the overlapping descriptions will be omitted below for the sake of brevity and clarity.

8, the information relay server 200 'includes a receiver 210, an EMT DB 220, a decryption engine 230, a transmitter 240, an identification code verifier 250, an identification code generator 260, And an information manager 270.

Compared to the information relay server 200 of FIG. 5, the information relay server 200 'of FIG. 8 further includes an information manager 270. The information manager 270 receives the information destruction request through the receiver 210 and discards the specific data among the data stored in the EMT DB 220 in response to the information destruction request.

For example, the hospital EMR server 110 of the hospital care system 100 (see FIG. 1) transmits an identification code for the care information desired to be destroyed to the information relay server 200 ' It is possible to select data to be discarded among the data stored in the EMT DB 220 by referring to the requested identification code. Thereafter, the information manager 270 may control the EMT DB 220 to delete the corresponding data.

As a result, the information relay server 200 'according to the embodiment of the present application can further improve the confidentiality of the medical care information by selectively discarding the medical care information.

On the other hand, the data included in one medical care information may have different retention periods. For example, as shown in Fig. 9, among the data included in one medical information, the prescription should be destroyed after two years, and the medical record should be destroyed only after ten years. In FIGS. 10 and 11 below, embodiments of the present application for supporting selective destruction of data exceeding the mandatory retention period of data included in one medical care information will be described in more detail.

10 is a diagram showing an information relay server 200 '' according to another embodiment of the present application. The information relay server 200 '' of FIG. 10 is similar to the information relay server 200 of FIG. Accordingly, the same or similar configurations will be described using the same or similar reference numerals, and the overlapping descriptions will be omitted below for the sake of brevity and clarity.

Referring to FIG. 10, the information relay server 200 '' includes a receiver 210, an EMT DB 220, a decryption engine 230, a transmitter 240, an identification code verifier 250, an identification code generator 260 An information manager 270, a timer 281, a volatile memory 282, and an encryption engine 283.

10 includes an information manager 270, a timer 281, a volatile memory 282, and an encryption engine 283 in addition to the information relay server 200 of FIG. 5 . The information manager 270, the timer 281, the volatile memory 282, and the encryption engine 283 perform an operation of selectively destroying some data among the data included in one medical care information (hereinafter, some data erasing operations) Support.

Specifically, the timer 281 confirms whether or not a predetermined period of time has elapsed. For example, if some data destruction operations are set to be performed on a 2-year, 3-year, 5-year and 10-year basis from the date of creation of the medical care information, the timer 281 is set to 2, 3, And an overtime signal to the information manager 270 every ten years.

The volatile memory 282 temporarily stores the decoded medical care information during the execution of some data destruction operations. Of the decoded medical care information temporarily stored in the volatile memory 282, data to be destroyed is selected and deleted by the information manager 270.

The encryption engine 283 re-encrypts the data temporarily stored in the volatile memory 282. For example, the encryption engine 283 re-encrypts data other than data deleted by the information manager 270 among data included in one medical care information.

The information manager 270 communicates with the EMT DB 220, the decryption engine 230, the timer 281, the volatile memory 282, and the encryption engine 283, and controls some data destruction operations in general.

11 is a flowchart for explaining some data destruction operations performed by the information relay server 200 " in Fig.

In step S410, the information manager 270 is notified that the timer 281 has exceeded the preset period.

For example, the timer 281 informs the information manager 270 of information on encrypted medical care information stored in the EMT DB 220 exceeding 2 years from the creation date. As another example, the timer 281 notifies the information manager 270 every predetermined period (e.g., two years), without an individual confirmation of the encrypted medical care information stored in the EMT DB 220. [

In operation S420, the information manager 270 controls the EMT DB 220 and the decryption engine 230 to decrypt encrypted medical care information stored in the EMT DB 220.

For example, the information manager 270 selects information that is more than two years old from the generation date of the encrypted medical care information stored in the EMT DB 220 based on the information received from the timer 281, And controls the EMT DB 220 and the decryption engine 230 to perform the authentication.

As another example, the information manager 270 may be configured to perform a decryption operation on some or all of the encrypted medical care information stored in the EMT DB 220, based on the time period received from the timer 281, And controls the decryption engine 230.

In step S430, the decoded medical care information is temporarily stored in the volatile memory 282. [

In step S440, the information manager 270 selectively deletes data whose setting period is exceeded, out of a plurality of data included in the decoded medical care information temporarily stored in the volatile memory 282. [

For example, when the decrypted medical information includes prescription data exceeding two years from the creation date, the information manager 270 selectively deletes the corresponding prescription data.

In step S450, the encryption engine 283 performs an encryption operation on data remaining in the volatile memory 282 under the control of the information manager 270. [

For example, if the prescription data of the data of the predetermined medical care information is deleted in the volatile memory 282 and other data remains, the encryption engine 283 performs a re-encryption operation on the remaining data.

In step S460, the information manager 283 stores the re-encrypted medical care information in the EMT DB 220 again.

As described above, the information relay server 200 '' according to the embodiment of the present application performs a decryption operation and a re-encryption operation on the medical care information stored in the EMB DB 220, It can support the destruction operation.

On the other hand, it is to be understood that the above description is exemplary and the technical idea of the present application is not limited to the above-described embodiments. It should be appreciated that all configurations and methods that are readily applicable and applicable within the scope of the technical idea of the present application are all within the scope of the present application.

10: Medical information exchange system
100: Hospital Medical System
110: Hospital EMR Server
120: Care information server
122: Encryption engine
124: Medical information database (MT DB)
200, 200 ', 200'': Information relay server
220: Encrypted medical information database (EMT DB)
240: encryption engine
300: user terminal
310: Application

Claims (12)

A hospital EMR server storing patient's medical information;
A medical care information server physically distinguished from the hospital EMR server and encrypting the medical care information received from the hospital EMR server with medical care information encrypted by an encryption engine and storing the medical care information; And
And an information relay server that stores the encrypted care information received from the care information server and decrypts the encrypted care information through a decryption engine in response to a request from the user terminal and transmits the decrypted care information to the user terminal ,
Wherein the information relay server notifies an overtime signal every fixed period of the data included in the encrypted medical care information or notifies the terminal that the period overtime signal for the data has exceeded a predetermined period of time A timer for notifying the timer; And
And an information manager for deleting the data based on the overtime signal,
The information manager selects the encrypted medical care information including the data to be decrypted through the decryption engine from the encrypted medical care information database and temporarily stores the encrypted medical care information in the volatile memory before deleting the data,
Re-encrypting the decrypted medical care information in which the data is deleted from the decrypted medical care information temporarily stored in the volatile memory through the encryption engine, and storing the decrypted medical care information in the encrypted medical care information database after deleting the data,
Wherein the data includes the obligatory storage period for each type so that the timer can automatically check the discarding period.

delete delete delete delete delete delete delete delete delete delete delete

Images