JP2014127167A - System monitoring program, method, and device - Google Patents

Abstract

PROBLEM TO BE SOLVED: To calculate the operation rate of a hospital integration information system as a whole based on the damage level of each stopped system in hospital jobs integrated by the hospital integration information system.SOLUTION: A system monitoring program causes a computer to execute the processing of calculating weight stop time weighting stop time from the stop of each system to resumption, totaling the weight stop time of every damage levels of the individual stopped systems to obtain the ratio of the total with respect to target operation time when the entire hospital integration information system operates without stopping the individual systems, and thereby calculating the operation rate of the hospital integration information system as a whole for each damage level, using the number of users using individual system for hospital jobs integrated by the hospital integration information system.

Description

  The present invention relates to evaluating a hospital integrated information system that integrates various systems.

  In recent years, hospital integrated information systems have been introduced in which individual systems related to specific tasks such as medical treatment of hospitals are coordinated and various individual systems are integrated into one. A system related to a hospital operation is a system related to the life of a patient, and it is required to provide a stable service for a 24-hour hospital operation.

  In the prior art, the degree of influence on the operation rate of the entire plant when a partial failure of the system occurs is determined according to the degree of influence of the individual functions on the entire system by weighting the failure contents in addition to the weighting of the failure time. It has been proposed to calculate the occupancy rate.

  In the prior art, it is known to calculate the data recovery cost and the compensation cost based on the amount of data lost due to the stop of at least a part of the function due to the failure or destruction of a part of the computer system.

Japanese Patent Laid-Open No. 2003-323212 JP 2001-243124 A

  However, the operating rate in the conventional technology, the cost in the event of shutdown, etc. are based on empirical judgments regarding the system operation by the individual system developer, and due to system malfunctions at the actual hospital operation site The degree of influence of the partial suspension of operations on the overall hospital operations was different.

  Since the impact that the developer thinks is different from the impact that the hospital considers when performing the work, there are unnecessary development man-hours and development costs when improving the system based on the record of the operation status of the system. There was a problem that said it would occur.

  Therefore, an object of the present invention is to calculate the operating rate of the entire hospital integrated information system according to the failure level of the stopped individual system in the hospital work integrated by the hospital integrated information system.

  According to one aspect of the present embodiment, by using the number of users who use each individual system related to hospital work integrated by the hospital integrated information system, the stop time from when the individual system stops until it restarts is calculated. The weighted weighted stop time is calculated, the weighted stop time is totaled for each failure level of the stopped individual system, and the target when the entire hospital integrated information system is operated without stopping the individual system By obtaining the total ratio with respect to the operation time, a system monitoring program for causing the computer to execute processing for calculating the operation rate of the entire hospital integrated information system for each failure level can be obtained.

  Further, as means for solving the above-described problem, a system monitoring method, a system monitoring apparatus, and a recording medium on which the program is recorded can be used.

  According to one aspect of the present embodiment, in the hospital work integrated by the hospital integrated information system, the stop of the individual system affects by calculating the operation rate of the entire hospital integrated information system according to the failure level of the stopped individual system. Appropriately assess the impact on overall hospital operations.

It is a figure which shows the network structure of the hospital integrated information system which concerns on a present Example. It is a figure which shows the hardware constitutions of a system monitoring server. It is a figure which shows the function structural example of a system monitoring server. It is a figure which shows the example of a data structure. It is a figure which shows the example of a data structure. It is a flowchart figure for demonstrating a coefficient weighting process. It is a flowchart for demonstrating an operation rate calculation process. It is a flowchart figure for demonstrating a review determination process. It is a figure which shows the example of a message display.

  Hereinafter, embodiments of the present invention will be described with reference to the drawings. FIG. 1 is a diagram illustrating a network configuration of the hospital integrated information system according to the present embodiment. In the hospital integrated information system 1000 shown in FIG. 1, a plurality of individual systems 6 and a monitoring server 100 are connected via a network 2. A plurality of individual systems 6-1, 6-2, 6-3, 6-4,... (Hereinafter collectively referred to as individual system 6) include electronic medical records, medical accounting, radiation, drugs, etc. Includes individual hospital operations. These electronic medical records, medical accounting, radiation, drugs and the like correspond to system names.

  In FIG. 1, the system monitoring server 100 periodically acquires system stop information 41 from each individual system 6 and accumulates and stores it in the stop log DB 31. The system stop information 41 includes information such as the stop system name and stop time.

  The system monitoring server 100 has a hardware configuration as shown in FIG. FIG. 2 is a diagram illustrating a hardware configuration of the system monitoring server. In FIG. 2, the system monitoring server is a terminal controlled by a computer, and includes a CPU (Central Processing Unit) 11, a main storage device 12, an auxiliary storage device 13, an input device 14, a display device 15, The output device 16, a communication I / F (interface) 17, and a drive 18 are connected to the bus B.

  The CPU 11 controls the system monitoring server 100 according to a program stored in the main storage device 12. The main storage device 12 uses a RAM (Random Access Memory) or the like, and stores a program executed by the CPU 11, data necessary for processing by the CPU 11, data obtained by processing by the CPU 11, and the like. A part of the main storage device 12 is allocated as a work area used for processing by the CPU 11.

  The auxiliary storage device 13 uses a hard disk drive and stores data such as programs for executing various processes. A part of the program stored in the auxiliary storage device 13 is loaded into the main storage device 12 and executed by the CPU 11, whereby various processes are realized. The storage unit 130 includes the main storage device 12 and / or the auxiliary storage device 13.

The input device 14 includes a mouse, a keyboard, and the like, and is used for a user to input various information necessary for processing by the system monitoring server 100. The display device 15 displays various information required under the control of the CPU 11. The output device 16 has a printer or the like and is used for outputting various types of information in accordance with instructions from the user. The communication I / F 17 is a device that is connected to, for example, the Internet, a LAN (Local Area Network), etc., and controls communication with an external device. Communication by the communication I / F 17 is not limited to wireless or wired.
A program for realizing the processing performed by the system monitoring server 100 is provided to the system monitoring server 100 by a storage medium 19 such as a CD-ROM (Compact Disc Read-Only Memory). That is, when the storage medium 19 storing the program is set in the drive 18, the drive 18 reads the program from the storage medium 19, and the read program is installed in the auxiliary storage device 13 via the bus B. . When the program is activated, the CPU 11 starts its processing according to the program installed in the auxiliary storage device 13. The medium for storing the program is not limited to a CD-ROM, and any medium that can be read by a computer may be used. As a computer-readable storage medium, in addition to a CD-ROM, a portable recording medium such as a DVD disk or a USB memory, or a semiconductor memory such as a flash memory may be used.

  FIG. 3 is a diagram illustrating a functional configuration example of the system monitoring server. In FIG. 3, the system monitoring server 100 includes a monitoring unit 51, a coefficient weighting unit 52, an operation rate calculation unit 53, and a review determination unit 54 as processing units. The storage unit 130 stores a stop log DB 31, a user coefficient master DB 32, a failure level master DB 33, and a review necessity table 34. Further, the stop time list 42, the stop time total table 43a, the operation rate correspondence table 43b, the abstract target level 44a, the abstract system list 44b, and the review necessity result 44c are stored in the storage unit 13. .

  The monitoring unit 51 acquires information indicating the operating state from each individual system 6 via the network 2. Based on the information indicating the operating state, the operating state, the state related to the stop, and the like are acquired. The monitoring unit 51 is a processing unit that acquires the system stop information 41 as information indicating a state related to the stop, and accumulates and records it in the stop log DB 31 stored in the storage unit 130. The stop time described below is based on the latest system stop information 41 before restart by receiving information indicating the restart state from each individual system 6, and the stop time and restart indicated by the system stop information 41 It can be obtained from the restart time of the hour.

  The coefficient weighting unit 52 uses the user coefficient master DB 32 and the failure level master DB 33 for the total stop time for each system name calculated with reference to the system stop information 41 of the stop log DB 31 stored in the storage unit 130. And a processing unit for weighting the stop time. The weighted stop time list 42 is stored in the storage unit 130.

  The operation rate calculation unit 53 is a processing unit that calculates the operation rate of the entire hospital integrated information system for each failure level. The operating rate is calculated by the difference between the total operating time required for the system and the weighted stop time for each failure level. A total stop time table 43a and an operation rate correspondence table 43b are output for each failure level.

  Based on the operating rate correspondence table 34b obtained by the operating rate calculating unit 53, the review determining unit 54 sets the review necessity table 34 for the system stopped at the failure level where the overall system operating rate is equal to or less than a predetermined ratio. It is a processing unit that determines whether or not it is necessary to review. The review determination unit 54 stores the extraction target level 44a in which the failure level at which the overall system operation rate is equal to or lower than the predetermined rate from the operation rate correspondence table 34b is stored in the storage unit 130. Based on the review necessity table 34 by the review determination unit 54, an extracted system list 44 b obtained by extracting a system stopped at the failure level indicated by the extraction target level 44 from the weighted stop time list 42 is stored in the storage unit 130. Stored in

  Examples of data configurations of various master DBs and tables will be described with reference to FIGS. 4 and 5 are diagrams showing data configuration examples. In FIG. 4, the stop log DB 31 has items such as a stop process, a stop system, a stop time, a stop date and time, and the system stop information 41 corresponds to each record. The stop process indicates a process name for identifying a process indicating the entire stopped individual system or a part of the processing part. The stop system indicates a system name for identifying the stopped system. The stop time indicates the time of continuous stop from each stop until restart. The stop date / time indicates the date / time of stop.

  In the data structure example of the stop log DB 31 shown in FIG. 4, the first system stop information 41 indicates that the process “EAOPU” of the “electronic medical record” of the individual system is “20120903125834” (12:58:34 on September 3, 2012) 2 seconds) from 2 seconds). The second system stop information 41 indicates that the “medical accounting” process “EXOITK” of the individual system has been stopped for one hour from “20120406010155” (01:01:55 on April 6, 2012). Yes. The third system stop information 41 indicates that the process “EXOSF” of “radiation” of the individual system has been stopped for two hours from “20010823060021” (August 23, 2001 6: 0: 21). . The same applies to the fourth and subsequent system stop information 41.

  In FIG. 4, the user coefficient master DB 32 has items such as a user ID, name, individual system name, and job type. The user ID indicates an ID for identifying a related person such as a doctor or a staff of the hospital. The name indicates the name of a hospital official. The system indicates a system name used by hospital staff. The job type indicates the job type of the hospital staff. The occupations are doctors, residents, nurses, radiographers, etc.

  In the data configuration example of the user coefficient master DB 32 shown in FIG. 4, in the first record, the name “Taro Yamada” identified by the user ID “YAMADA” uses the “electronic medical record” system, and the occupation is “doctor” ". In the second record, the name “Tsubasa Mitsukoshi” identified by the user ID “KOSHI” uses the “electronic medical record” system, and indicates that the occupation is “resident”. In the third record, the name “Hanako Ishitomi” identified by the user ID “ISHI” uses the “electronic medical record” system, and the occupation type is “nurse”. The same applies to the fourth and subsequent records.

  In FIG. 5, the failure level master DB 33 has items such as a stop process, a stop system, an effect on a patient, an effect on hospital income, an effect on other departments, and a failure level. The stop process indicates a process name for identifying a process indicating the entire stopped individual system or a part of the processing part. The stop system indicates a system name for identifying the stopped system. Patient impact indicates the presence or absence of patient impact from the stopped process. The impact on hospital revenue indicates whether the stopped process has an impact on hospital revenue. The impact on other departments indicates whether the stopped process has an impact on other departments.

  The fault level indicates the degree of the fault that affects the entire hospital integrated information system due to the stopped process. For example, it is shown in stages from level 1 to level 4. Level 1 has the smallest influence and level 4 has the largest influence.

  In the data structure example of the failure level master DB 33 shown in FIG. 5, in the first record, the process “EAOPU” of the “electronic medical record” of the individual system has an effect on the patient “Yes”, the effect on the hospital revenue “No” , And the influence on other departments is “None”, and the failure level of the process “EAOPU” is “Level 1”.

  In the second record, the “medical accounting” process “EXOITK” of the individual system has an impact on patients “Yes”, an impact on hospital income “Yes”, and an impact on other departments “No”. It is shown that the failure level of the process “EXOITK” is “level 2”.

  In the third record, the process “EXOSF” of the “radiation” of the individual system has an influence on the patient “Yes”, an influence on the hospital income “Yes”, and an influence on other departments “Yes”. It is indicated that the failure level of “EXOSF” is “level 3”.

  In the fourth record, the process “ESOIR” of the “surgery” of the individual system has an impact on the patient “Yes”, an impact on the hospital income “Yes”, and an impact on other departments “Yes”. It is shown that the failure level of “ESOIR” is “level 4”.

  The coefficient weighting process performed by the coefficient weighting unit 52 will be described with reference to FIG. FIG. 6 is a flowchart for explaining the coefficient weighting process.

  In FIG. 6, the coefficient weighting unit 52 uses the user number master DB 32 to acquire the total number of users and the number of affected users for each individual system (step S <b> 11). What is necessary is just to acquire the total number of records of user number master DB32 as a total number of users. The number of affected users for each individual system may be obtained by acquiring the number of records having the same individual system name in the user coefficient master DB 32. The affected users are the number of users who are directly affected when the individual system is stopped, and the number of affected users is the number of users who are performing business using the individual system.

  The coefficient weighting unit 52 calculates the following equation 1 (step S12).

重み付け係数は、全体利用者数［人］に対する影響利用者数合計［人］の割合で示される。

The weighting coefficient is indicated by the ratio of the total number of affected users [people] to the total number of users [people].

  Next, the coefficient weighting unit 52 uses the weighting coefficient calculated in step S12 and the stop log DB 31 to create a stop time list 42 that lists the times when the weighted individual systems have stopped ( Step S13). The weighted stop time is a time recorded in a predetermined period (for example, the past one year). By multiplying the stop time by a weighting coefficient, the stop time is converted into a stop time corresponding to the degree of influence that the stop has had on the entire hospital integrated information system 1000. Expressed as stop time after weighting. The stop time list 42 is stored in the storage unit 130.

  Then, the coefficient weighting unit 52 refers to the failure level master DB and adds the failure level to the stop time list 42 created in step S13 in association with the stop process (step S14).

  FIG. 7 shows an operation rate calculation process for calculating the operation rate for each failure level by the operation rate calculation unit 53 using the stop time list 42 stored in the storage unit 130 by the coefficient weighting process by the coefficient weighting unit 52 described above. I will explain it. FIG. 7 is a flowchart for explaining the operation rate calculation processing.

  In FIG. 7, the operation rate calculation unit 53 refers to the stop time list 42 from the storage unit 130 and sums the stop times after weighting for each failure level (step S21). The operating rate calculation unit 53 creates a total stop time table 43 a in which the total stop time is associated with each failure level, and is stored in the storage unit 130.

  The total stop time table 43a includes items such as a failure level and a total stop time. In the example illustrated in FIG. 7, the total of the stop time “3 hours”, “1 hour”, “30 minutes”, and “10 minutes” are associated with the failure levels 1 to 4.

  And the operation rate calculation part 53 calculates the whole system operation rate for every failure level using the total stop time obtained at step S21 (step S22). The operating rate calculation unit 53 calculates the following equation 2.

  The overall system operation rate [%] is indicated by the ratio of the difference between the target operation time [h] and the total stop time [h] to the target operation time [h]. The target operating time [h] indicates the total number of hours when the entire medical system 1000 is operated without stopping all or a part of each individual system 6, and the annual operating time [h] It is indicated by a value obtained by multiplying the number of days [day]. In this example, the target operation time [h] is shown when 24 hours a day, 365 days are operated annually.

  As a result of the processing in step S <b> 22, the operation rate correspondence table 43 b is created by the operation rate calculation unit 53 and stored in the storage unit 130. In the example of FIG. 7, the system overall operation rate “80.0%” at the failure level 1, the system overall operation rate “95.0%” at the failure level 2, and the system overall operation rate “97.0%” at the failure level 3. In the failure level 4, the overall system operation rate is “99.5%”.

  Next, the review determination process for determining whether the individual system 6 or the hospital integrated information system 100 needs to be reviewed by the review determination unit 54 will be described with reference to FIG. FIG. 8 is a flowchart for explaining the review determination process.

  In FIG. 8, the review determination unit 54 refers to the operation rate correspondence table 43 b created by the operation rate calculation unit 53 from the storage unit 130, so that the overall system operation rate is set to a preset target operation rate (for example, A failure level smaller than 90% is extracted (step S31). In the example of FIG. 8, the extraction target level 44 a indicating the failure level 1 of the overall system operation rate “80.0%” extracted from the operation rate correspondence table 43 b is stored in the storage unit 130.

  The review determining unit 54 extracts the record of the individual system corresponding to the failure level indicated by the extraction target level 44a from the stop time list 42, creates the extracted system list 44b, and stores it in the storage unit 130 (step S32). ).

  Then, the review determination unit 54 calculates the ratio of the stop time for each process based on the stop time of the entire target level and the stop time of each individual system (step S33).

プロセス停止時間の割合［％］は、障害レベル全体の重み付け後の停止時間［ｈ］に対するプロセスの重み付け後の停止時間［ｈ］の割合を示す。抽象システム一覧４４ｂに含まれる停止プロセス毎にプロセス停止時間の割合［％］を算出する。

The process stop time ratio [%] indicates the ratio of the process weighted stop time [h] to the weighted stop time [h] of the entire failure level. A ratio [%] of the process stop time is calculated for each stop process included in the abstract system list 44b.

  The review determination unit 54 displays a message indicating that a review (replacement) is necessary for a process having a process stop time ratio [%] of 40% or more (step S34). The review necessity table 34 is created and stored in the storage unit 130 by the processing in steps S33 and S34.

  In the flowchart of FIG. 8, the failure level to be reviewed by comparison with a preset target operation rate is specified. For level 4 with a high failure degree, the record indicating level 4 in the operation rate correspondence table 43b is specified. Only the presence or absence may be checked. If there is a record in the operation rate correspondence table 43b, it may be determined that the review is necessary.

  The ratio calculated in step S33 is associated with the stop process, the stop system, the stop time, and the weighted items in the abstract system list 44b, and if the ratio is 40% or more, “required” is necessary. If the ratio is less than 40%, “No” is set as the necessity of review. A message indicating that a review (replacement) is necessary is displayed on the display device 15 for the stop process in which the review necessity item is set to “necessary”.

  In the example shown in FIG. 8, by referring to the review necessity table 34, it is understood that the review (replacement) is necessary for the electronic medical record system specified by the stop process “EAOPU”. For example, a message as shown in FIG. 9 is displayed on the display device 15. FIG. 9 is a diagram illustrating a message display example.

  FIG. 9 shows an example in which a message for failure level 1 is displayed. For example, “EAOPU (electronic medical record) is at fault level 1. It accounts for 85.7% of the total fault level. Please review the process!”.

  As described above, the hospital integrated information system 100 according to the present embodiment collectively monitors the processes of the plurality of individual systems 6. By multiplying the stop time required from an unexpected process stop due to an abnormal end or the like to a restart by a weighting coefficient based on the number of users of each individual system 6, the degree of influence on the entire hospital integrated information system 100 is obtained. It is possible to quantitatively indicate the stop time after weighting (FIG. 6).

  Determine the necessity of review (replacement) of the entire medical system, not the necessity of review within the individual system, by showing the impact of the stop process on the entire medical system based on the weighted stop time Can do.

  Therefore, for example, even if the radiation system goes down, only a limited number of staff such as radiology doctors and radiologists are considered to be affected, such as outpatient examinations and prescriptions, ward procedures, etc. There will be no impact on staff engaged in business. In this embodiment, since the weighting coefficient is determined based on the number of users who use the radiation system in business, it is possible to appropriately determine whether or not the review is necessary based on the influence of obstacles in practice. Can be identified.

  The present invention is not limited to the specifically disclosed embodiments, and various modifications and changes can be made without departing from the scope of the claims.

The following additional notes are further disclosed with respect to the embodiment including the above examples.
(Appendix 1)
Using the number of users who use each individual system related to hospital work integrated in the hospital integrated information system, calculate the weighted stop time that weights the stop time until the individual system stops and restarts,
Summing up the weighted stop time for each failure level of the stopped individual system, and determining the ratio of the total to the target operating time when the entire hospital integrated information system is operated without stopping the individual system The system monitoring program which makes a computer perform the process which calculates the operation rate of this hospital integrated information system for every said failure level by this.
(Appendix 2)
In calculating the heavy stop time,
Calculating a weighting factor by determining a ratio of the number of users of the individual system to the number of users of the entire hospital integrated information system;
By multiplying the stop time by the weighting coefficient to obtain a stop time after weighting, it is converted into a stop time according to the degree of influence given to the entire hospital integrated information system, and for each stopped individual system, Create a stop time list in which the stop times after the weighting are associated and store them in the storage unit,
Referring to the failure level master database that stores the failure level in association with the individual system name stored in advance in the storage unit, the failure level is added in association with the individual system name in the outage time list and stored. The system monitoring program according to supplementary note 1, which causes the computer to execute processing stored in a section.
(Appendix 3)
In calculating the operating rate,
Referring to the stop time list from the storage unit, for each failure level, sum the weighted stop time,
By calculating the ratio of the difference between the target operating time and the total for each failure level to the target operating time, the operating rate of the hospital integrated information system is calculated, and the failure level and the operating rate are associated with each other. The system monitoring program according to supplementary note 2, which causes the computer to execute a process of storing the availability ratio correspondence table in the storage unit.
(Appendix 4)
By referring to the stop time list stored in the storage unit, an individual system indicating a failure level that satisfies a predetermined condition from the operating rate correspondence table stored in the storage unit is identified,
By referring to the stop time list, whether or not the entire hospital integrated information system needs to be reviewed based on the ratio of the weighted stop time of the identified individual system to the entire failure level satisfying the predetermined condition. The system monitoring program according to supplementary note 3, which causes the computer to execute a determination process.
(Appendix 5)
Obtaining stop information indicating the stop of the individual system from the individual system, and recording it in a stop log database stored in the storage unit,
The system monitoring program according to any one of appendices 1 to 4, wherein in the weighting of the stop time, the computer executes a process of calculating the stop time based on the stop information recorded in the stop log database.
(Appendix 6)
A system monitoring method executed by a computer,
Using the number of users who use each individual system related to hospital work integrated in the hospital integrated information system, calculate the weighted stop time that weights the stop time until the individual system stops and restarts,
Summing up the weighted stop time for each failure level of the stopped individual system, and determining the ratio of the total to the target operating time when the entire hospital integrated information system is operated without stopping the individual system To calculate the operating rate of the entire hospital integrated information system for each failure level.
(Appendix 7)
Weighting to calculate the weighted stop time by using the number of users who use each individual system related to hospital work integrated by the hospital integrated information system, and weighting the stop time from when the individual system stops until it restarts And
Summing up the weighted stop time for each failure level of the stopped individual system, and determining the ratio of the total to the target operating time when the entire hospital integrated information system is operated without stopping the individual system The system monitoring apparatus, further comprising: an operating rate calculating unit that calculates an operating rate of the entire hospital integrated information system for each failure level.

2 Network 6 Individual system 11 CPU
12 Main storage device 13 Auxiliary storage device 14 Input device 15 Display device 16 Output device 17 Communication I / F
18 Drive 19 Storage medium 31 Stop log DB
32 User coefficient master DB
33 Failure level master DB
34 Review necessity table 41 System stop information 42 Stop time list 43a Total stop time table 43b Operation rate correspondence table 44a Extraction target level 44b Extraction system list 51 Monitoring unit 52 Coefficient weighting unit 53 Operation rate calculation unit 54 Review determination unit 100 System Monitoring server 130 storage unit

Claims (5)

Using the number of users who use each individual system related to hospital work integrated in the hospital integrated information system, calculate the weighted stop time that weights the stop time until the individual system stops and restarts,
Summing up the weighted stop time for each failure level of the stopped individual system, and determining the ratio of the total to the target operating time when the entire hospital integrated information system is operated without stopping the individual system The system monitoring program which makes a computer perform the process which calculates the operation rate of this hospital integrated information system for every said failure level by this. In calculating the heavy stop time,
Calculating a weighting factor by determining a ratio of the number of users of the individual system to the number of users of the entire hospital integrated information system;
By multiplying the stop time by the weighting coefficient to obtain a stop time after weighting, it is converted into a stop time according to the degree of influence given to the entire hospital integrated information system, and for each stopped individual system, Create a stop time list in which the stop times after the weighting are associated and store them in the storage unit,
Referring to the failure level master database that stores the failure level in association with the individual system name stored in advance in the storage unit, the failure level is added in association with the individual system name in the outage time list and stored. The system monitoring program according to claim 1, which causes the computer to execute processing stored in a unit. In calculating the operating rate,
Referring to the stop time list from the storage unit, for each failure level, sum the weighted stop time,
By calculating the ratio of the difference between the target operating time and the total for each failure level to the target operating time, the operating rate of the hospital integrated information system is calculated, and the failure level and the operating rate are associated with each other. The system monitoring program according to claim 2, which causes the computer to execute a process of storing the availability ratio correspondence table in the storage unit. A system monitoring method executed by a computer,
Using the number of users who use each individual system related to hospital work integrated in the hospital integrated information system, calculate the weighted stop time that weights the stop time until the individual system stops and restarts,
Summing up the weighted stop time for each failure level of the stopped individual system, and determining the ratio of the total to the target operating time when the entire hospital integrated information system is operated without stopping the individual system To calculate the operating rate of the entire hospital integrated information system for each failure level. Weighting to calculate the weighted stop time by using the number of users who use each individual system related to hospital work integrated by the hospital integrated information system, and weighting the stop time from when the individual system stops until it restarts And
Summing up the weighted stop time for each failure level of the stopped individual system, and determining the ratio of the total to the target operating time when the entire hospital integrated information system is operated without stopping the individual system The system monitoring apparatus, further comprising: an operating rate calculating unit that calculates an operating rate of the entire hospital integrated information system for each failure level.

Images