JP2004094313A - Medical information management method - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a medical information management method smoothly continuing medical services even if some failure occurs in a server managing the medical information in a hospital. <P>SOLUTION: This medical information management method is so formed that a medical information input terminal 40 transmits the medical information input by a user to the medical information management server 10 managing the medical information and a services server 50 using the medical information. This method is provided with a transmission affirmative/negative determination step of determining whether or not transmitting the medical information to the services server 50 and a print instruction step of printing documents based on the medical information when the transmission of the medical information is impossible. <P>COPYRIGHT: (C)2004,JPO

Description

[0001]
TECHNICAL FIELD OF THE INVENTION
The present invention relates to a medical information management method, and more particularly, to a medical information management method using a computer.
[0002]
[Prior art]
In hospitals where computerization is progressing, medical charts for recording medical information, paper sheets for recording medication information, and the like have been digitized, and the transmission of information by paper is unnecessary. When a doctor who performs medical treatment inputs information such as medical treatment information, medication information, and test instructions from a terminal, the information is electronically transmitted to a hospital window, a pharmacy, and other related units. Based on the information, the counter asks the patient for a consultation fee, and the pharmacy dispenses the medicine and pays out the medicine to the patient.
[0003]
In a medical setting that deals with human life, it is not permissible for the above information transmission to be delayed. Therefore, the server of the information processing system that realizes such an environment is required to have high reliability. In general, the reliability of the system is enhanced by duplicating the server into a main server and a standby server, thereby ensuring the reliability of information transmission.
[0004]
[Problems to be solved by the invention]
However, even if the servers are duplicated, the server operation rate cannot be made 100%. In some cases, it is necessary to stop the entire system including the standby server as well as the main server for a short time due to the maintenance work. In such a case, there has been a problem that smooth information transmission is impaired.
[0005]
The present invention has been made in view of the above points, and provides a medical information management method capable of smoothly continuing medical work even if a failure occurs in a server for managing medical information in a hospital. With the goal.
[0006]
[Means for Solving the Problems]
In order to solve the above problem, the present invention provides a medical information input terminal that transmits medical information input by a user to a medical information management server that manages the medical information and a business server that uses the medical information. A medical information management method, wherein the medical information input terminal determines whether transmission of the medical information to the business server is possible or not, and the medical information input terminal performs transmission of the medical information. And printing a document based on the medical information when printing is not possible.
[0007]
In such a medical information management method, the medical information input terminal can automatically print a document based on the medical information when the input medical information cannot be transmitted. Therefore, by sending the printed document to the relevant section, medical services can be smoothly continued without interruption of information transmission in the hospital.
[0008]
Further, in order to solve the above problem, the present invention is a medical information management method in which an alternative server having at least a part of the function of a medical information management server manages medical information received from a medical information input terminal, An abnormality detecting step in which an alternative server detects an abnormality in the medical information management server; and the alternative server substitutes the medical information transmitted from the medical information input terminal based on the abnormality detection in the medical information management server. An alternative information storing step of storing information as information, a recovery detecting step in which the alternative server detects recovery of the medical information management server, and the alternative server performing the replacement based on detection of recovery of the medical information management server. Transmitting alternative information to the medical information management server.
[0009]
In such a medical information management method, at least a part of the function of the medical information management server can be performed by the substitute server when an abnormality occurs in the medical information management server. Therefore, medical work can be smoothly continued without interruption of information transmission in the hospital.
[0010]
Further, in order to solve the above problem, the present invention is a medical information management method in which a server monitoring terminal monitors the status of a business server using medical information, wherein the server monitoring terminal checks the status of the business server. A server monitoring step of monitoring, the server monitoring terminal detects an abnormality of the business server, a business server abnormality detection step, and the server monitoring terminal detects the abnormality of the business server, And a print instruction step of instructing printing of medical information to be input thereafter.
[0011]
In such a medical information management method, when the server monitoring terminal detects an abnormality in the business server, the medical information input to the medical information input terminal is automatically printed as a document. Therefore, by sending the printed document to the relevant section, medical services can be smoothly continued without interruption of information transmission in the hospital.
[0012]
In order to solve the above problems, the present invention may be an apparatus for realizing the processing in the medical information management method, a program for causing a computer to execute the method, and a storage medium storing the program.
[0013]
BEST MODE FOR CARRYING OUT THE INVENTION
Hereinafter, embodiments of the present invention will be described with reference to the drawings.
[0014]
FIG. 1 shows a configuration diagram of an example of a medical information management system according to the present invention. The medical information management system 1 of FIG. 1 includes a medical information management server 10, an alternative server 20, an administrator terminal 30, a user terminal 40 as a medical information input terminal, an examination server 50a, and a pharmacy server 50b. Are connected via a network 60 such as a LAN (Local Area Network).
[0015]
The medical information management server 10 is a server computer that manages various data related to medical work, such as patient medical information (medical record), medicine prescription instruction information, examination instruction information, and examination result information input from the user terminal 40. Then, various information is transmitted to the business server such as the test server 50a or the pharmacy server 50b as necessary. For example, the medical information management server 10 transmits the test instruction information to the test server 50a, and transmits the prescription instruction information of the medicine to the pharmacy server 50b.
[0016]
The substitution server 20 is a computer that substitutes for the processing of the medical information management server 10 when the medical information management server 10 cannot continue processing due to some cause, for example, a maintenance operation or a failure. However, the substitute server 20 does not have to have the same function as the medical information management server 10, and performs processing of information necessary for the immediate business until the recovery work of the medical information management server 10 is completed. Therefore, the substitute server 20 does not need to be constituted by expensive hardware called a so-called server machine, but may be constituted by hardware such as a personal computer.
[0017]
The administrator terminal 30 is a computer used by an administrator of the medical information management system 1. The administrator terminal 30 monitors the medical information management server 10, the test server 50a, the pharmacy server 50b, and the like, and when detecting an abnormality occurring in any of these servers, performs a process described later.
[0018]
The user terminal 40 is a computer used by hospital staff, such as doctors and nurses performing medical treatment, for registering medical information and referring to medical information. Further, the user terminal 40 is used for exchanging various types of information relating to operations in the hospital. Although the user terminal 40 is represented as one block in the medical information management system 1 of FIG. 1, a plurality of user terminals 40 are arranged in a hospital. Further, a printer 70 is connected to the user terminal 40. The printer 70 prints data input from the user terminal 40, but does not necessarily need to be directly connected to the user terminal 40, and may be connected to a printer server (not shown) connected via the network 60. .
[0019]
The test server 50a and the pharmacy server 50b are examples of a server specialized for work in each section in the hospital. For example, the inspection server 50a manages information related to the inspection. The pharmacy server 50b manages information in the pharmacy. Such servers exist in addition to accounting servers and the like, but are hereinafter collectively referred to as "department servers 50".
[0020]
Next, a functional configuration example of the medical information management system 1 will be described. FIG. 2 shows a functional configuration diagram of an embodiment of the medical information management system according to the present invention. In FIG. 2, the medical information management server 10 is configured to include a medical information DB (Data Base) 11, an extraction table 12, a data extraction unit 13, a recovery unit 14, and an entry unit 15.
[0021]
The medical information DB 11 stores various types of data related to medical work, such as patient medical information (medical record), drug prescription instruction information, examination instruction information, and examination result information, which are input from the user terminal 40. In the extraction table 12, of the data stored in the medical information DB 11, the type of data to be transferred to the alternative server 20 as a backup is registered. The data extraction unit 13 performs a backup process of extracting data registered in the extraction table 12 from the medical information management unit 10 and transferring the extracted data to the alternative server 20. The recovery unit 14 receives data registered in the alternative server 20 and executes a process of updating the medical information DB 11 to the latest state based on the received data. The entry unit 15 performs registration, update, search processing, and the like of data stored in the medical information DB 11 according to a request from the user terminal 40.
[0022]
Further, the substitution server 20 is configured to include a substitution DB 21, a backup unit 22, a substitution data transfer unit 23, and a substitution entry unit 24.
[0023]
The substitute DB 21 is a substitute database that manages at least a part of the data of the medical information DB 11. The backup unit 22 receives the backup data transmitted from the medical information management server 10 and registers the backup data in the alternative DB 21. When the medical information management server 10 recovers from a failure or the like, the alternative data transfer unit 23 extracts data from the alternative DB 21 and transmits the data to the medical information management server 10. When the medical information management server 10 cannot be used due to a failure or the like, the alternative entry means 24 provides the user terminal 40 with at least a part of the functions replacing the entry means 15 of the medical information management server 10.
[0024]
Further, the administrator terminal 30 is configured to include a system monitoring unit 31 and a switching notification unit 32.
[0025]
The system monitoring unit 31 monitors the medical information management server 10, the department server 50, and the like, and when detecting an abnormality occurring in any of those servers, performs a process described later. The switching notification unit 32 instructs the user terminal 40 to switch the connection destination server when a failure occurs in the medical information management server 10 or when the medical information management server 10 recovers from the failure.
[0026]
Further, the user terminal 40 is configured to include a connection destination management table 41, a terminal entry unit 42, a connection destination switching unit 43, and a printing unit 44.
[0027]
The connection destination management table 41 manages which of the medical information management server 10 and the alternative server 20 the user terminal 40 should connect to. The terminal entry means 42 requests data registration to the server (the medical information management server 10 or the alternative server 20) specified in the connection destination management table 41 in accordance with the input of the user of the user terminal 40, Make a search request. The connection destination switching unit 43 switches the connection destination server of the user terminal 40 by updating the connection destination management table 41 in accordance with an instruction from the administrator terminal 30. The printing unit 44 causes the printer 70 to print the data input to the user terminal 40 as a predetermined document.
[0028]
It should be noted that the section server 50 indicates various servers placed in each section in the hospital.
[0029]
Hereinafter, the processing procedure of the medical information management system 1 of FIG. 2 will be described.
[0030]
First, a process for backing up data managed in the medical information DB 11 of the medical information management server 10 to the alternative DB 21 of the alternative management server 20 will be described. FIG. 3 shows a flowchart of one embodiment of the data backup process.
[0031]
In step S10, the data extraction unit 13 of the medical information management server 10 obtains, from the extraction table 12, the type of data to be transmitted to the alternative server 20 among the data managed in the medical information DB 11.
[0032]
FIG. 4 shows a configuration diagram of an example of the extraction table. In the extraction table 12 of FIG. 4, it can be seen that information on the inpatient on the day, information on the patient scheduled for medical treatment on the day, and information on patients for the past three months are to be extracted. In the extraction table 12, it is sufficient to register only the minimum types of data necessary for daily work so that the work is not hindered while the medical information management server 10 cannot be used due to a failure or the like. If other information is also to be backed up, the data type may be registered in the extraction table 12. If there is any unnecessary data, the type of the data may be deleted from the extraction table 12.
[0033]
When only specific information among the patient information is to be backed up, the table shown in FIG. 5 may be used. FIG. 5 shows a configuration diagram of an example of the patient information extraction table. In the patient information extraction table 121 in FIG. 5, information such as prescription information, X-ray instruction information, injection instruction, treatment instruction, specimen test instruction, physiological test instruction, test result, and the like are extracted as information on each patient. Therefore, by combining the extraction table 12 and the patient information extraction table 121, the information registered in the patient information extraction table 121 for the in-patient on the day, the patient whose medical treatment is required on the day, and the patient for the past three months is set as a backup target. can do.
[0034]
Proceeding to step S11 following step S10 in FIG. 3, the data extracting means 13 extracts data targeted for extraction in the extraction table 12 from the medical information DB 11.
[0035]
Proceeding to step S12 following step S11, the data extracting unit 13 transmits the data extracted from the medical information DB 11 to the alternative server 20.
[0036]
Proceeding to step S13 following step S12, the backup unit 22 of the alternative server 20 receives data from the medical information management server 10.
[0037]
Proceeding to step S14 following step S13, the backup unit 22 registers the received data in the alternative DB 21, and the process ends.
[0038]
The above-described processing is executed periodically (for example, every day), and only data necessary for daily work is registered in the alternative DB 21.
[0039]
Further, a description will be given of a process performed when the medical information management process is switched from the medical information management server 10 to the alternative server 20 when a failure occurs in the medical information management server 10 or the like. FIG. 6 is a flowchart illustrating an example of a process of switching to an alternative server.
[0040]
In step S20, the system monitoring means 31 of the administrator terminal 30 detects an abnormality of the medical information management server 10. Proceeding to step S21 following step S20, the system monitoring unit 31 checks whether the related department server 50 is connectable, that is, whether a failure or the like has occurred in the department server 50. Proceeding to step S22 following step S21, the system monitoring unit 31 instructs the medical information management server 10 in which the failure has occurred to end the processing. Thereby, the medical information management server 10 ends the processing.
[0041]
Proceeding to step S23 following step S22, the system monitoring unit 31 transmits an instruction to the alternative server 20 to activate the alternative entry unit 24 to substitute the processing of the medical information management server 10.
[0042]
In step S24 in response to step S23, the substitute server 20 activates the substitute entry means 24 in preparation for the processing substitute based on the instruction of the administrator terminal 30.
[0043]
The process of the administrator terminal 30 proceeds to step S25 following step S23, and the switching notification unit 32 transmits an instruction to all the user terminals 40 to switch the connection destination to the alternative server 20. This notification includes information for uniquely specifying the connection destination, such as the IP address or host name of the connection destination. However, when the user terminal 40 knows the IP address of the alternative server 20 or the like in advance, the user terminal 40 may simply notify the switching.
[0044]
Proceeding to step S27 in response to step S25, the connection destination switching means 43 of the user terminal 40 changes the connection destination management table 41 based on the switching instruction received from the administrator terminal 30.
[0045]
FIG. 7 shows a configuration diagram of an example of the connection destination management table.
In the connection destination management table 41 of FIG. 7, XXX. XXX. XXX. XXX is registered. The user terminal 40 connects to a server registered in the connection destination management table 41 when referring to or registering medical information. Normally, the IP address of the medical information management server 10 is registered in the connection destination management table 41, but since the IP address of the alternative server 20 has been changed in step S27, the connection to the alternative server 20 will be made thereafter.
[0046]
The process of the administrator terminal 30 proceeds to step S28 following step S25, and the switching notification unit 32 transmits to all the user terminals 40 whether or not the connection to the related unit server 50 is possible. Proceeding to step S29 in response to step S28, the connection destination switching means 43 of the user terminal 40 receives the information indicating whether or not connection to the related section server 50 is possible.
[0047]
The process of the administrator terminal 30 proceeds to step S30 following step S28, and the switching notification unit 32 of the administrator terminal 30 instructs all the user terminals 40 to start the process of the printing unit 44. Send. Proceeding to step S31 in response to step S30, the user terminal 40 starts the process of the printing unit 44, and the process ends.
[0048]
By the processing described above, the function of the medical information management server 10 will be replaced by the substitute server 20 thereafter.
[0049]
Further, the entry process after switching the process to the alternative server 20 will be described. Note that the entry process refers to a process when the user terminal 40 connects to the medical information management server 10 or the alternative server 20 to refer to or register medical information. FIG. 8 shows a flowchart of an embodiment of an entry process after switching to an alternative server.
[0050]
In step S40, the terminal entry means 42 of the user terminal 40 receives input of medical information from a doctor, a nurse, or the like.
[0051]
Proceeding to step S41 following step S40, the terminal entry means 42 acquires the IP address of the connection destination server from the connection destination management table 41. Here, since the IP address of the alternative server 20 is registered in the connection destination management table 41, the IP address of the alternative server 20 is obtained.
[0052]
Proceeding to step S42 following step S41, the terminal entry means 42 transmits the input data that has been input to the alternative server 20. Proceeding to step S43 following step S42, the substitute entry means 24 of the substitute server 20 receives the input data transmitted from the user terminal 40.
[0053]
Thereafter, the processing is executed in parallel by the user terminal 40 and the alternative server 20 respectively.
[0054]
First, the alternative server 20 will be described. Proceeding to step S46 following step S43, the alternative entry means 24 registers the received input data in the alternative DB 21. Proceeding to step S47 following step S46, the alternative entry means 24 determines whether or not it is possible to connect to the related section server 50 by inquiring of the administrator terminal 30. For example, when information related to a test instruction is input at the user terminal 40, the test server 50a corresponds to the related department server 50, and when information related to prescription of a drug is input, the pharmacy server 50b is This corresponds to the related department server 50. If the connection to the department server 50 cannot be established, the alternative entry means 24 terminates the processing, and if the connection can be established, the process proceeds to step S48.
[0055]
In step S48, the alternative entry means 24 transmits necessary data for transmitting the information to the relevant section server 50, and ends the processing.
[0056]
Next, the user terminal 40 will be described. Proceeding to step S44 following step S42, the terminal entry means 42 determines whether or not connection to the related section server 50 is possible by inquiring of the administrator terminal 30. If it is possible to connect to the department server 50, the data has been transmitted from the alternative server 20 in step S48, and the terminal entry unit 42 ends the processing. If the connection to the department server 50 cannot be established, the process proceeds to step S45.
[0057]
In step S45, the printing unit 44 of the user terminal 40 causes the printer 70 to print the input data as a document in a predetermined format. What is printed here is, for example, a patient's chart, prescription, examination instruction, and the like. If the data cannot be transmitted to the department server 50, the required document is printed here. By sending the printed document to the related department, information can be transmitted to other departments, and business operations can be performed. Delay can be prevented.
[0058]
Note that, in a normal case, the processing of the alternative server 20 is executed by the medical information management server 10. Although the registration process has been described above, when the medical information is referred to from the user terminal 40, only a part of the data, that is, the backed-up data is different from the case where the medical information is connected to the normal medical information management server 10. Can be referred to. However, since the minimum data required for daily work is backed up, there is no hindrance to work.
[0059]
Further, a recovery process when the medical information management server 10 recovers will be described. FIG. 9 shows a flowchart of an embodiment of the recovery processing at the time of recovery of the medical information management server.
[0060]
In step S50, the system monitoring means 31 of the administrator terminal 30 detects the restoration of the medical information management server 10. Proceeding to step S51 following step S50, the system monitoring unit 31 transmits an instruction to the alternative server 20 to transfer the data stored in the alternative DB 21 to the medical information management server 10.
[0061]
Proceeding to step S52 following step S51, the substitute data transfer unit 23 of the substitute server 20 transmits data stored in the substitute DB 21 to the medical information management server 10 based on an instruction from the administrator terminal 30.
[0062]
Proceeding to step S53 following step S52, the recovery unit 14 of the medical information management server 10 receives the data transmitted from the alternative server 20. Proceeding to step S54 following step S53, the recovery unit 14 registers the received data in the medical information DB 11, and updates the medical information DB 11 to the latest state.
[0063]
In the alternative server 20, the process proceeds to step S55 following step S52, and transmits to the administrator terminal 30 that the data transfer to the medical information management server 10 is completed.
[0064]
Proceeding to step S56 following step S55, the system monitoring means 31 of the administrator terminal 30 receives the notification from the substitute server 20. Proceeding to step S57 following step S56, the switching notification means 32 of the administrator terminal 30 transmits an instruction to all the user terminals 40 to switch the connection destination server to the medical information management server 10.
[0065]
In step S59, the connection destination switching unit 43 of the user terminal 40 changes the connection destination management table 41 based on the switching instruction received from the administrator terminal 30. Here, the IP address of the medical information management server 10 is registered in the connection destination management table 41.
[0066]
Proceeding to step S60 following step S59, the switching notification means 32 of the administrator terminal 30 sends an instruction to all the user terminals 40 to end the process of the printing means 44.
[0067]
Proceeding to step S61 following step S60, the user terminal 40 ends the process of the printing unit 44, and ends the processing. As described above, the state of the information management server 10 becomes the latest state. From now on, the user terminal 40 will connect to the information management server 10 and execute the entry process.
[0068]
As described above, in the present embodiment, the substitute server 20 manages only the information necessary for the business at hand, and provides only the functions necessary for the business at hand to the user terminal 40. Hardware. Therefore, the cost can be kept low and the reliability of the medical information management system 1 can be increased. Further, when a failure occurs in the department server 50 that needs to transmit information, a necessary document is automatically printed on the user terminal 40. Therefore, by using the document as an information transmission medium, medical work can be performed. It can be performed smoothly.
[0069]
As described above, the preferred embodiments of the present invention have been described in detail. However, the present invention is not limited to the above embodiments, and various modifications and changes may be made within the scope of the present invention described in the appended claims. Changes are possible.
[0070]
In addition, the following supplementary notes are disclosed with respect to the above description.
(Supplementary Note 1) A medical information management method in which a medical information input terminal transmits medical information input by a user to a medical information management server that manages the medical information and a business server that uses the medical information. ,
The medical information input terminal, transmission permission determination step of determining whether transmission of the medical information to the business server,
A print instruction step for causing the medical information input terminal to print a document based on the medical information when the transmission of the medical information is impossible; and
A medical information management method comprising:
(Supplementary Note 2) When the medical information input terminal cannot transmit the medical information to the medical information management server, the medical information input terminal may include an alternative server having at least a part of functions of the medical information management server and the business server. 3. The medical information management method according to claim 1, wherein at least a part of the medical information is transmitted.
(Supplementary Note 3) A medical information management method in which an alternative server having at least a part of the function of the medical information management server manages medical information received from a medical information input terminal,
An abnormality detection step in which the substitute server detects an abnormality in the medical information management server,
The alternative server, medical information transmitted from the medical information input terminal based on the detection of an abnormality of the medical information management server, alternative information storage step of storing as alternative information,
The alternative server, a recovery detection step of detecting the recovery of the medical information management server,
An alternative information transmitting step in which the alternative server transmits the alternative information to the medical information management server based on detection of recovery of the medical information management server;
A medical information management method comprising:
(Supplementary Note 4) The alternative server, a transfer information receiving step of receiving at least a part of the medical information stored in the medical information management server as transfer information from the medical information management server,
A transfer information storing step of storing the transfer information;
3. The medical information management method according to claim 3, wherein the method includes at least before the abnormality detection step.
(Supplementary Note 5) A medical information management method in which a server monitoring terminal monitors a state of a business server using medical information,
A server monitoring step in which the server monitoring terminal monitors the state of the business server; and a business server abnormality detecting step in which the server monitoring terminal detects an abnormality in the business server.
A print instruction step in which the server monitoring terminal instructs the medical information input terminal to print medical information subsequently input to the medical information input terminal based on the detection of the abnormality of the business server;
A medical information management method comprising:
(Supplementary Note 6) The server monitoring step further monitors a state of a medical information management server that manages medical information input to the medical information input terminal,
A destination server of the medical information input to the medical information input terminal based on the detection of the abnormality of the medical information management server, an alternative server having at least a part of the function of the medical information management server from the medical information management server 5. The medical information management method according to claim 5, wherein the method is switched to:
(Appendix 7)
Medical information entered by the user, a transmission availability determination procedure to determine whether it is possible to transmit to the business server using the medical information,
When determining that the medical information cannot be transmitted to the business server, a print instruction procedure for printing a document based on the medical information by a predetermined printing unit;
A medical information management program for running.
(Appendix 8)
An abnormality detection procedure for detecting an abnormality of the medical information management server that manages the medical information received from the medical information input terminal;
An alternative information storage procedure for storing medical information transmitted from the medical information input terminal based on detection of an abnormality of the medical information management server as alternative information,
A recovery detection procedure for detecting recovery of the medical information management server,
An alternative information transmission procedure for transmitting the alternative information to the medical information management server based on detection of recovery of the medical information management server;
A medical information management program for running.
(Appendix 9)
A server monitoring procedure for monitoring the status of the business server using medical information,
A business server abnormality detection procedure for detecting an abnormality of the business server,
A print instruction procedure for instructing the medical information input terminal to print medical information that is subsequently input to the medical information input terminal based on the detection of the abnormality of the business server;
A medical information management program for running.
(Appendix 10)
Medical information entered by the user, a transmission availability determination procedure to determine whether it is possible to transmit to the business server using the medical information,
When determining that the medical information cannot be transmitted to the business server, a print instruction procedure for printing a document based on the medical information by a predetermined printing unit;
A computer-readable recording medium on which a medical information management program for executing the program is recorded.
(Supplementary Note 11)
An abnormality detection procedure for detecting an abnormality of the medical information management server that manages the medical information received from the medical information input terminal;
An alternative information storage procedure for storing medical information transmitted from the medical information input terminal based on detection of an abnormality of the medical information management server as alternative information,
A recovery detection procedure for detecting recovery of the medical information management server,
An alternative information transmission procedure for transmitting the alternative information to the medical information management server based on detection of recovery of the medical information management server;
A computer-readable recording medium on which a medical information management program for executing the program is recorded.
(Supplementary Note 12)
A server monitoring procedure for monitoring the status of the business server using medical information,
A business server abnormality detection procedure for detecting an abnormality of the business server,
A print instruction procedure for instructing the medical information input terminal to print medical information that is subsequently input to the medical information input terminal based on the detection of the abnormality of the business server;
A computer-readable recording medium on which a medical information management program for executing the program is recorded.
[0071]
【The invention's effect】
As described above, according to the present invention, even if a failure occurs in a server that manages medical information in a hospital, medical services can be continued smoothly.
[Brief description of the drawings]
FIG. 1 is a configuration diagram of an example of a medical information management system according to the present invention.
FIG. 2 is a functional configuration diagram of an embodiment of a medical information management system according to the present invention.
FIG. 3 is a flowchart of an embodiment of a data backup process.
FIG. 4 is a configuration diagram of an example of an extraction table.
FIG. 5 is a configuration diagram of an example of a patient information extraction table.
FIG. 6 is a flowchart illustrating an example of a process of switching to an alternative server.
FIG. 7 is a configuration diagram of an example of a connection destination management table.
FIG. 8 is a flowchart of an embodiment of an entry process after switching to an alternative server.
FIG. 9 is a flowchart of an embodiment of a recovery process when recovering the medical information management server.
[Explanation of symbols]
1 medical information management system
10 Medical information management server
11 medical information DB
12 Extraction table
13 Data extraction means
14 Recovery means
15 Entry means
20 Alternative server
21 Alternative DB
22 Backup means
23 Alternative data transfer means
24 Alternative entry means
30 Administrator terminal
31 System monitoring means
32 Switching notification means
40 user terminals
41 Connection destination management table
42 Terminal entry means
43 Connection destination switching means
44 Printing means
50 copies server
50a Inspection server
50b Pharmacy server
60 Network
70 Printer

Claims (3)

A medical information input terminal, a medical information management method for transmitting medical information input to a user, to a medical information management server that manages the medical information and a business server that uses the medical information,
The medical information input terminal, transmission permission determination step of determining whether transmission of the medical information to the business server,
A step of instructing the medical information input terminal to print a document based on the medical information when the transmission of the medical information is impossible. An alternative server having at least a part of the function of the medical information management server is a medical information management method for managing medical information received from a medical information input terminal,
An abnormality detection step in which the substitute server detects an abnormality in the medical information management server,
The alternative server, medical information transmitted from the medical information input terminal based on the detection of an abnormality of the medical information management server, alternative information storage step of storing as alternative information,
The alternative server, a recovery detection step of detecting the recovery of the medical information management server,
Transmitting an alternative information to the medical information management server based on detection of recovery of the medical information management server, wherein the alternative server transmits the alternative information to the medical information management server. A server monitoring terminal is a medical information management method for monitoring a state of a business server using medical information,
A server monitoring step in which the server monitoring terminal monitors a status of the business server;
A business server abnormality detection step in which the server monitoring terminal detects an abnormality in the business server;
A print instruction step of instructing the medical information input terminal to print medical information subsequently input to the medical information input terminal based on the detection of an abnormality of the business server.

Images