JP4328305B2 - Fault notification system - Google Patents

Description

  The present invention relates to a system for notifying a failure when a failure occurs in a device installed in a business facility.

2. Description of the Related Art Conventionally, there has been proposed a failure notification system that detects a failure of a device installed in a business facility such as a medical institution and transmits the content of the failure using distribution means such as an electronic mail. For example, Patent Document 1 discloses a technology for notifying an operation manager who performs maintenance work of failure information by e-mail when a failure occurs in business processing.
JP 2001-160029 A

  However, in the failure notification system according to Patent Document 1 described above, when a failure occurs in the business process, the person in charge at the business facility such as a medical institution is in charge of what kind of failure the operation manager performing the maintenance work There is no way to know if the plan will be implemented.

  The present invention has been made in view of these problems, and an object of the present invention is to provide a failure notification system that can present a failure handling plan related to a failure that has occurred to a person in charge on the business facility side when a failure occurs. .

  One embodiment of the present invention relates to a failure notification system. This failure notification system is a system for notifying a maintenance system of a failure that has occurred in a device or component provided in a business system, and the business system has occurred in a device or component provided in the business system. A failure detection unit that detects a failure, an identification information acquisition unit that acquires identification information associated with the detected failure, and an identification information transmission unit that transmits the acquired identification information. The maintenance system includes a plan creation unit that creates a failure handling plan for a failure associated with the transmitted identification information, and a presentation unit that presents the created failure handling plan to the business system.

  Examples of the business system include a system that executes a predetermined process for performing business such as a medical institution system and a laboratory system. A failure occurring in a device or part provided in the business system refers to a failure occurring in a hardware component or software component constituting the device and the device constituting the system. In particular, when the business system is a medical institution system, the devices constituting the system are connected to a terminal such as a PC (Personal Computer) or PDA (Personal Digital Assistant), and a terminal such as a LAN (Local Area Network). Examples include a management server. On the other hand, hardware components that constitute the device include a CPU (Central Processing Unit), a cable, and the like that are internal to the device and a device attached to the device, and an OS (Operating System) and the like as the software component. Can be mentioned.

  According to this configuration, the person in charge of the business system can refer to the contents of the failure response plan created by the person in charge of the maintenance system and can know the contents of the failure recovery work performed by the person in charge of the maintenance system. .

  The plan creation unit creates a plurality of failure response plans for the failure that has occurred, and the maintenance system is created by a maintenance person input unit that receives an instruction from a person in charge on the maintenance system side, and an instruction received. And a selecting unit that selects any one of the plurality of failure handling plans as an execution target.

  The failure response plan includes items related to ordering of devices or parts useful for recovery from failures, and the maintenance system includes a determination unit that determines whether or not there is a fee for ordering devices or parts, An ordering unit that notifies the ordering party of ordering parts may be further provided. The business system further includes a business person input unit that receives a confirmation instruction for approving an order for the device or part by a person in charge on the business system side, and a confirmation instruction transmission unit that transmits the received confirmation instruction to the ordering unit. The ordering unit notifies the ordering party of the order of the device or parts after receiving the confirmation instruction from the confirmation instruction transmitting unit when the determining unit determines that the cost for ordering the device is charged. Also good.

  The failure notification system may further include a holding unit that holds maintenance contract information related to the device or the component, and the determination unit may determine whether or not there is a fee for ordering the device or the component based on the maintenance contract information. .

  ADVANTAGE OF THE INVENTION According to this invention, the failure response plan regarding the failure which occurred can be shown to the person in charge at the business facility side.

  FIG. 1 shows the overall configuration of a failure notification system according to the present embodiment. The failure notification system 10 includes a medical operation support system 20 provided in a medical institution, a maintenance management system 70 that performs maintenance management of the medical operation support system 20, and the medical operation support system 20 and the maintenance management system 70. And a WAN (Wide Area Network) 12 that is communicably connected.

  The medical operation support system 20 includes a medical device 24 such as an endoscope device, a PC 26 or a PDA 28 used by a doctor or nurse, medical data obtained by the medical device 24, patient chart information, nursing information, or the like. The medical service support server 30 to be stored, the business management terminal 23 operated by a business person in charge, the medical business mail server 38 for transferring the received e-mail, and these devices, terminals and servers are connected so as to communicate with each other. LAN22. The business person in charge refers to a person in charge of managing the operation of the business system.

  The medical device 24 transmits the data obtained by the intended processing to the medical service support server 30 via the LAN 22 and records the data in a data storage unit described later inside the server. The data obtained by the medical device 24 includes, for example, an image of the stomach taken by an endoscope apparatus.

  The PC 26 or PDA 28 can access the medical service support server 30 via the LAN 22. In connection with the examination of the patient, the doctor uses the PC 26 to read out medical record data and medical data stored in the data storage unit inside the medical service support server 30 and stores these data in the data storage unit as necessary. It is possible to record. In addition, the nurse can record it as nursing information in the data storage unit inside the medical service support server 30 using the PDA 28 in relation to patient nursing.

  The medical service support server 30 stores medical information such as medical data, patient chart information, and nursing information, and transmits and receives data according to requests from the medical device 24, the PC 26, and the PDA 28. At the time of data transmission / reception, the medical service support server 30 records a communication history with the medical device 24, the PC 26, and the PDA 28 as a communication log. The communication log includes an OS (Operating System) event log mounted on the PC 26 and the PDA 28, an application log on the medical device 24, and the like. Specifically, a device name and an IP (Internet Protocol) address. Information for identifying a communication partner such as communication time, communication content, and error message. Note that the error message includes patient information such as a patient ID for specifying which patient information was accessed when the failure occurred, and information for specifying an individual such as a doctor or a nurse.

  The medical service support server 30 includes a failure detection unit 32, an identification information acquisition unit 34, an identification information transmission unit 36, a log information determination unit 33, a log transmission unit 35, a failure list holding unit 37, and a data storage unit. 39. The failure detection unit 32 monitors a communication log recorded in the medical service support server 30 and detects a failure that has occurred in an apparatus provided in the medical service support system 20.

  Specifically, the failure detection unit 32 determines whether a failure occurs in the communication log according to whether or not an error message registered in the failure list held in the failure list holding unit 37 inside the medical service support server 30 is included in the communication log. Detect the presence or absence of occurrence. This failure list is a file in which error messages relating to failures that may occur in the medical service support system 20 are recorded, and may be created in advance by a maintenance person based on the results of an operation test performed in advance. Note that an error message related to a failure recorded in the failure list is associated with a failure number associated with the failure. This failure number is identification information for identifying a failure.

  When the occurrence of a failure is detected by the failure detection unit 32, the identification information acquisition unit 34 refers to the failure list and acquires a failure number associated with an error message related to the detected failure. The identification information transmission unit 36 transmits an email including the failure number acquired by the identification information acquisition unit 34 to the maintenance management mail server 40 via the medical service mail server 38.

  When notifying the occurrence of a failure, the log information determination unit 33 determines whether or not personal information such as a patient ID, a doctor, and a nurse is included in the communication log. When the log information determination unit 33 determines that personal information is included, the log transmission unit 35 performs encryption processing on the communication log, and transmits an e-mail including the communication log to the maintenance management mail server 40. To do. On the other hand, when it is determined by the log information determination unit 33 that personal information is not included, the log transmission unit 35 may transmit the communication log as it is or after performing compression processing on the communication log. You may send it. Note that the log transmission unit 35 may change the transmission destination of the electronic mail depending on whether or not the communication log is encrypted. By changing the transmission destination of the e-mail, it is possible to designate a maintenance person who can access highly confidential information such as patient information.

  FIG. 2 shows an example of a communication log when personal information is included. The communication log 100 shown in FIG. 2 is a log generated when, for example, a doctor accesses the data storage unit 39 from the PC 26 when a failure occurs, and the log information 102 in the communication log 100 includes personal information. Contains information. That is, the log information 102 indicates that a doctor named “Olym Suichiro” accessed the data storage unit 39 at “18:48:57” on “January 12, 2005”. This doctor name corresponds to personal information. As described above, when a failure occurs, the log transmission unit 35 encrypts the communication log, and an e-mail including the encrypted communication log is transmitted to the maintenance management mail server 40.

  Returning to FIG. 1, the person in charge of business uses the business management terminal 23 to refer to the failure response plan created by the person in charge of maintenance, the devices, hardware parts, and software parts (hereinafter referred to as the medical work support system 20). , Collectively referred to simply as “parts”). Note that a GUI (Graphical User Interface) program that accepts the reference operation and input operation and a program that performs internal processing of data received via the GUI program (hereinafter, these programs are collectively referred to simply as “program”) Provided via a WAN 12 and a LAN 22 from a failure management device described later.

  The business management terminal 23 is equipped with the above-described program, and the program includes a business staff input unit 25 and a confirmation instruction transmission unit 27. Although details will be described later, the business staff input unit 25 receives a confirmation instruction for approving an order for an apparatus or a part by the business staff. The confirmation instruction transmitting unit 27 transmits the confirmation instruction received by the business staff input unit 25 to the ordering unit described later.

  Further, when the trouble recovery work by the maintenance person is completed and the trouble report is provided to the work person by e-mail or paper medium, the work person input unit 25 receives the trouble report from the work person. Accept the confirmation instruction to approve the contents of the document. The confirmation instruction transmission unit 27 transmits the confirmation instruction received by the business staff input unit 25 to the maintenance management system 70.

  The maintenance management system 70 includes a maintenance management mail server 40 that forwards the received e-mail, a maintenance management terminal 50 that is used by a maintenance person, and a failure management plan created by the maintenance management terminal 50 and the business management terminal 23 and maintenance. A failure management device 80 presented to the management terminal 50 and a LAN 14 that connects these devices and terminals so as to communicate with each other are included. The maintenance management mail server 40 transfers the email transmitted by the identification information transmission unit 36 to the maintenance management terminal 50.

  Note that the failure management apparatus 80 according to the present embodiment provides a program related to the creation of a failure response plan to the business management terminal 23 and the maintenance management terminal 50 via the network. That is, the business management terminal 23 and the maintenance management terminal 50 operate as clients with respect to the failure management apparatus 80. As a result, the version of the program relating to the creation of the failure response plan and the data input via the program can be managed in a unified manner on the failure management device 80 on the server side. As a result, the person in charge of the business and the person in charge of maintenance can share information about the failure such as a failure response plan.

  The failure management device 80 includes a presentation unit 82, a failure handling information holding unit 84, and a maintenance contract information holding unit 86. The presentation unit 82 presents the failure handling plan created by the plan creation unit described later to the maintenance management terminal 50 via the LAN 14. Further, the presentation unit 82 presents the plan to the work management terminal 23 in the medical work support system 20 via the WAN 12 and the LAN 22.

  The failure handling information holding unit 84 mainly holds a correspondence relationship between a failure number and a policy for handling a failure associated with the number (hereinafter simply referred to as “failure handling policy”). The maintenance contract information holding unit 86 mainly holds maintenance contract information related to devices or parts. The maintenance contract is concluded by the maintenance management system 70 side and an apparatus or parts supplier. As a result, order processing using maintenance contract information becomes possible.

  The maintenance management terminal 50 is loaded with the above-described program, which includes the receiving unit 52, the plan creation unit 54, the maintenance person input unit 56, the selection unit 58, the determination unit 60, the ordering unit 62, And a totaling unit 64. The receiving unit 52 receives an e-mail including a failure number transferred by the maintenance management mail server 40. The plan creation unit 54 refers to the failure handling information holding unit 84 and creates a failure handling policy associated with the failure number included in the email received by the receiving unit 52 as a failure handling plan. The totaling unit 64 totals the number of emails received by the receiving unit 52 for each failure number. The results of the aggregation are included in the monthly or annual data report.

  The failure response plan created by the plan creation unit 54 is presented to the maintenance staff and the business staff by the presentation unit 82. When the plan creation unit 54 creates a plurality of failure handling plans for the failure that has occurred, the plurality of failure handling plans are presented to the maintenance staff and the business staff. According to the present embodiment, the business person in charge can know the content of the failure recovery work performed by the maintenance person by referring to the content of the failure handling plan created by the maintenance person. Although the details will be described later, this failure response plan includes the number of workers required for failure recovery work, the work schedule, and items related to ordering of devices or parts useful for failure recovery. As an example of the item relating to ordering, there is a cost related to ordering.

  The maintenance person input unit 56 receives an instruction from the maintenance person through an external device such as a mouse or a keyboard. The maintenance person input unit 56 receives, for example, an instruction to select a failure response plan, an instruction to update or add an item in the failure response plan from the maintenance person. The selection unit 58 selects one of the plurality of failure handling plans created by the plan creation unit 54 as an execution target according to the instruction received by the maintenance person input unit 56. Which trouble handling plan is selected as an implementation target may be determined by a maintenance person logging in remotely to the medical service support server 30 and referring to a communication log.

  The determination unit 60 refers to the maintenance contract information holding unit 86 to determine whether or not there is a charge for the cost for ordering the device or parts. For example, if the maintenance contract information defines that the ordering cost is free if the usage period is within 3 years, the determination unit 60 determines that the usage period of the device or part is within 3 years. By determining whether or not there is a charge for the order, it is determined.

  The ordering unit 62 notifies the ordering party of an order for an apparatus or a part. When it is determined by the determination unit 60 that there is a charge for ordering the device or part, the ordering unit 62 receives the confirmation instruction from the confirmation instruction transmission unit 27 and then places an order for the device or part. Notify first. In other words, after obtaining confirmation of approval by the person in charge of business, the ordering unit 62 notifies the ordering party of the order of the device or part. As a result, it is possible to reduce the occurrence of troubles related to the ordering cost of devices or parts between the business staff and the maintenance staff. When placing an order, the ordering unit 62 may send an ordering e-mail including the serial number of the device or part to the ordering party.

  FIG. 3 shows the data structure of the failure handling information table stored in the failure handling information holding unit according to the present embodiment. In the failure handling information table 110, failures that have occurred in the past and details of work actually performed on the failures are recorded as a history. Note that each row of the failure handling information table 110 illustrated in FIG. 3 corresponds to each of the failure handling information. The failure handling information table 110 includes an identification number column 112, a failure number column 114, a failure occurrence cause column 116, a failure handling policy column 118, and a failure occurrence date column 120.

  The identification number column 112 stores an identification number for identifying each failure handling information. A failure number is stored in the failure number column 114. The failure cause column 116 stores the cause of the failure. The failure response policy column 118 stores a specific countermeasure for the cause of the failure. Further, the failure date column 120 stores the date on which the failure occurred.

  Speaking of the failure response information 122, if a failure with the failure number “1001” or “1002” occurs, the cause of the failure is “hard disk failure”, and the countermeasure for the failure is “hard disk repair”. Further, it indicates that the day when the failure occurred is “January 3, 2004”.

  FIG. 4 shows the data structure of the maintenance contract information table stored in the maintenance contract information holding unit according to the present embodiment. The maintenance contract information table 140 includes a device name or part name column 142, a serial number column 144, a security content column 146, and an order amount column 148. The device name or part name column 142 stores the name of the device or part. The serial number column 144 stores a serial number that is a unique number of the device or component.

  The security content column 146 stores the security content related to the order of the device or part. As described above, the security content of an apparatus or a part is determined based on the content of contract information previously concluded between the ordering party and the maintenance management system 70 side. For example, if the contract information indicates that the ordering fee is free for a specific device that has been in use for 3 years or less, the warranty details column for the device will contain “free for 3 years in use” data. Is stored. The order amount column 148 stores specific expenses related to ordering of devices or parts. As for the data 150, the ordering cost of the device name “Hard Disk A” whose serial number is “S100” is charged, and the ordering cost is “100,000 yen”.

  Hereinafter, the process from the start of the preparation of the failure response plan to the completion of the failure response work by the maintenance staff will be described with reference to FIGS. 5, 6, and 8 show the failure response plan screen presented to the maintenance staff, while FIGS. 7 and 9 show the failure response plan screens presented to the business staff. It is.

  FIG. 5 shows a failure response plan screen presented to the maintenance staff by the presentation unit. FIG. 5 shows an example of the failure response plan screen 130 created when a failure with the failure number “1001” occurs. The failure response plan screen 130 includes at least one failure response plan 131 and a selection button 133 associated with each of the policies. The failure handling plan 131 shown in FIG. 5 is information obtained by extracting and combining a failure occurrence cause held in the failure handling information holding unit 84 shown in FIG. 1 and a failure handling policy for the cause. That is, the plan creation unit 54 searches the failure handling information holding unit 84 using the failure number “1001” as a key, and the first failure handling plan 132 related to the identification number “1” and the second failure related to the identification number “2”. A response plan 136 is created. As a result, a failure handling plan can be automatically created based on the failure handling information stored in the failure handling information holding unit 84 shown in FIG.

  When one of the selection buttons is pressed by the maintenance person, one of the first failure handling plan 132 and the second failure handling plan 136 is selected as an execution target. That is, when the first selection button 134 is pressed, the selection unit 58 selects the first failure handling plan 132, and when the second selection button 138 is pressed, the selection unit 58 selects the second failure handling plan 136.

  FIG. 6 shows a failure handling plan screen presented to the maintenance staff by the presentation unit after selecting a plan as an implementation target. The failure handling plan screen shown in FIG. 6 is displayed for more detailed items than the failure handling plan screen shown in FIG. That is, the failure response plan screen shown in FIG. 6 displays the detailed failure response plans for repairing a plurality of hard disks after “hard disk repair” is selected in the failure response plan screen shown in FIG. Is.

  The failure response plan screen 160 includes attribute information corresponding to the first failure response plan 132 selected in FIG. 5, the case selection column 162, the progress status column 164, and various images displayed in the progress status column 164. It includes an attribute information column 169 to be displayed, a work force number column 166, and an order amount column 148. In addition, about the structure which attached | subjected the code | symbol same as FIG.4 and FIG.5, description is abbreviate | omitted suitably. The failure response plan in FIG. 6 indicates information included not only in the first failure response plan 132 but also in the progress status column 164, the number of workers column 166, and the order amount column 148.

  The progress status column 164 shows a schedule of the entire failure handling work related to the repair work of each hard disk using a horizontal bar graph image. That is, the case 1 is a schedule of the entire failure handling work involving the repair work of the hard disk A shown in FIG. 4, the case 2 is the schedule of the whole failure handling work involving the repair work of the hard disk B shown in FIG. FIG. 5 shows a schedule of the entire failure handling work involving repair work of the hard disk C shown in FIG. As shown in FIG. 6, the respective work periods are, in order, 3 days, 7 days, and 10 days. The horizontal bar graph image includes a first horizontal bar graph image 174, a second horizontal bar graph image 176, and a third horizontal bar graph image 178. Information indicated by these images is displayed in an attribute information column 169 described later.

  The attribute information column 169 holds the correspondence between the display mode of each horizontal bar graph image and the attribute information. As shown in the figure, the first horizontal bar graph image 174 indicates an “order period”, the second horizontal bar graph image 176 indicates a “test period”, and the third horizontal bar graph image 178 indicates a “failure recovery work period”. The case selection field 162 includes a plurality of radio buttons associated with each case. When one of the radio buttons is turned on by a maintenance person's mouse operation or the like, a case associated with the turned on radio button is selected.

  The number of workers required column 166 displays the number of personnel required for repairing each hard disk. The number of personnel may be input by the maintenance staff via the maintenance staff input unit 56. The order amount column 168 displays the cost for ordering each hard disk. After any case is selected, when the determination button 171 is pressed by a maintenance person's mouse operation or the like, the process proceeds to an approval phase by the next person in charge of business.

  FIG. 7 shows a failure response plan screen presented to the person in charge of business by the presentation unit. Instead of the enter button 171 in the failure response plan table displayed on the maintenance person side shown in FIG. 6, a business person operation column 170 that can be operated by the business person is displayed. This business person operation column 170 includes an approval button 172. When the approval button 172 is pressed by the business person in charge, the confirmation instruction transmitting unit 27 transmits the confirmation instruction received by pressing the approval button 172 to the maintenance management system 70. When the determination unit 60 determines that the cost for ordering devices or parts is free, the presentation unit 82 does not have to present the business person operation column screen for approval to the business person.

  FIG. 8 shows a failure response plan screen that has been approved by the business person to be presented to the maintenance person by the presentation unit. In addition, description is abbreviate | omitted suitably about the structure which attached | subjected the code | symbol same as FIG. As shown in the figure, the execution of the failure response plan in case 1 has been approved by the person in charge of the business, and therefore has an approved status. In this case, when the ordering mail button 180 is pressed by the maintenance staff, an e-mail indicating the ordering of the hard disk A is transmitted to the ordering party in accordance with the failure handling plan of case 1.

  FIG. 9 shows a failure response plan screen after ordering presented to the person in charge of business by the presentation unit. In addition, description is abbreviate | omitted suitably about the structure which attached | subjected the code | symbol same as FIG. The current progress is indicated by an arrow mark 182. As a result, the person in charge of business can check the current progress on the screen. In addition, when the repair work is completed by the maintenance staff and a report is provided to the business staff by e-mail or paper, the contents are confirmed and approved by the business staff. By pressing the end button 184, a series of failure handling operations are completed.

  FIG. 10 shows a flow of failure handling processing according to the present embodiment. The failure detection unit 32 detects whether or not a failure has occurred according to whether or not an error message registered in the failure list is included in the communication log (S10). When the failure detection unit 32 detects the occurrence of a failure, the identification information acquisition unit 34 refers to the failure list and acquires a failure number associated with an error message related to the detected failure (S12). The identification information transmitting unit 36 transmits an e-mail including the failure number acquired by the identification information acquiring unit 34 to the maintenance management mail server 40 (S14).

  The log information determination unit 33 determines whether or not personal information such as a patient ID, a doctor, and a nurse is included in the communication log generated in the medical service support server 30 (S16). When the log information determination unit 33 determines that personal information is included (Y in S16), the log transmission unit 35 performs an encryption process on the communication log (S18), and sends an e-mail including the communication log. It transmits to the maintenance management mail server 40 (S20). In this case, the log transmission unit 35 may change the transmission destination of the electronic mail depending on whether or not the communication log is encrypted. On the other hand, when the log information determination unit 33 determines that personal information is not included (N in S16), the log transmission unit 35 transmits the communication log as it is (S20). The maintenance management mail server 40 transfers the received email including the failure number and communication log to the maintenance management terminal 50 (S22).

  The receiving unit 52 receives the e-mail including the failure number transferred from the maintenance management mail server 40 (S24). The plan creation unit 54 refers to the failure handling information holding unit 84 and creates a failure handling policy associated with the failure number included in the email received by the receiving unit 52 as a failure handling plan (S26). In this case, when a plurality of failure handling plans are created by the plan creation unit 54, the plurality of failure handling plans are displayed to the maintenance staff.

  The maintenance person input unit 56 receives an instruction from the maintenance person (S28). The selection unit 58 selects one of the plurality of failure handling plans created by the plan creation unit 54 as an execution target according to the instruction received by the maintenance person input unit 56 (S30). The business person input unit 25 receives a confirmation instruction for approving the order of the device or part by the business person (S32). The determination unit 60 refers to the maintenance contract information holding unit 86 to determine whether or not there is a charge for the cost for ordering the device or parts (S34).

  When the determination unit 60 determines that there is a charge for ordering an apparatus or a part (Y in S34), the presentation unit 82 presents a business person operation column screen for approval to the business person and confirms it. The transmission unit 27 transmits the confirmation instruction received by the business staff input unit 25 to the ordering unit 62 (S36). When the determination unit 60 determines that the cost for ordering an apparatus or a part is free (N in S34), the presentation unit 82 does not have to present the business person operation column screen for approval to the business person. Good.

  After receiving the confirmation instruction transmitted from the confirmation instruction transmission unit 27, the ordering unit 62 notifies the ordering party of the order of the device or the part (S38). After the order is processed, the maintenance staff updates the plan as needed (S40). When the failure recovery work by the maintenance staff is completed, a failure report regarding the failure is provided by e-mail or the like (S42). After the confirmation by the business person in charge, when the end button in the screen is pressed, the failure handling work is finished (S44).

  The present invention has been described based on the embodiments. The embodiments are exemplifications, and it will be understood by those skilled in the art that various modifications can be made to combinations of the respective constituent elements and processing processes, and such modifications are within the scope of the present invention. .

It is a figure which shows the whole structure of the failure notification system which concerns on this Embodiment. It is a figure which shows an example of the communication log in case personal information is included. It is a figure which shows the data structure of the failure response information table stored in the failure response information holding | maintenance part which concerns on this Embodiment. It is a figure which shows the data structure of the maintenance contract information table stored in the maintenance contract information holding part which concerns on this Embodiment. It is a figure which shows the failure response plan screen shown to a maintenance person by a presentation part. It is a figure which shows the failure response plan screen shown to a maintenance person by the presentation part after selecting the plan as implementation object. It is a figure which shows the failure response plan screen shown to a business person in charge by a presentation part. It is a figure which shows the failure response plan screen approved by the business staff side presented to the maintenance staff by the presenter. It is a figure which shows the failure response plan screen after ordering shown to a business person in charge by a presentation part. It is a figure which shows the flow of the failure response process which concerns on this Embodiment.

Explanation of symbols

  DESCRIPTION OF SYMBOLS 10 Failure notification system, 20 Medical operation support system, 25 Operation person input part, 27 Confirmation instruction transmission part, 32 Failure detection part, 34 Identification information acquisition part, 36 Identification information transmission part, 54 Plan preparation part, 56 Maintenance person Input unit 58 selection unit 60 determination unit 62 ordering unit 70 maintenance management system 82 presentation unit 86 maintenance contract information holding unit

Claims (2)

A failure notification system for notifying a maintenance system of a failure that has occurred in a device or component provided in a business system,
The business system is
A fault list holding unit that holds a fault list in which error messages relating to faults that may occur in the business support system are recorded in association with identification information for identifying faults;
By detecting whether or not an error message recorded in the failure list is included in a communication log generated during data transmission / reception between devices provided in the business support system, A fault detection unit that detects a fault that has occurred in a device or component provided in
When an occurrence of a failure is detected by the failure detection unit, an identification information acquisition unit that refers to the failure list and acquires identification information associated with an error message related to the detected failure ;
An identification information transmitter for transmitting the acquired identification information;
A business person input unit that receives a confirmation instruction for approving the order of the device or part by a person in charge on the business system side,
A confirmation instruction transmission unit for transmitting the accepted confirmation instruction to the maintenance system;
With
The maintenance system includes:
A failure handling information holding unit that holds a correspondence relationship between the identification information and a handling policy for a failure associated with the identification information;
A maintenance contract information holding unit for holding maintenance contract information regarding the device or parts;
A plan for identifying a response policy associated with the identification information transmitted from the identification information transmission unit with reference to the failure response information holding unit and creating a failure response plan for the failure including the response policy The creation department;
A presentation unit for presenting the created failure response plan to a business system;
A determination unit that determines whether or not there is a fee for ordering the device or parts based on the maintenance contract information;
An ordering unit for notifying the ordering party of the device or parts ;
Equipped with a,
The ordering unit places an order for the device or part after receiving the confirmation instruction transmitted from the confirmation instruction transmitting unit when the determination unit determines that the cost for ordering the device or part is charged. Notify the supplier, and when it is determined that the cost is free, notify the supplier of the order of the device or component without being subject to the confirmation instruction transmitted from the confirmation instruction transmitter. A failure notification system characterized by: The plan creation unit creates a plurality of failure response plans for the failure that has occurred,
The maintenance system includes:
A maintenance person input unit for receiving instructions from the maintenance person on the maintenance system side;
In accordance with the received instruction, a selection unit that selects any one of the plurality of prepared failure response plans as an implementation target;
The failure notification system according to claim 1, further comprising:

Images