JP2011192086A - Medical trouble event countermeasure support system and program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To quickly provide required information while preventing the leakage of information for participants of a countermeasure meeting of a medical trouble event. <P>SOLUTION: A medical trouble event countermeasure support system 1 registers an electronic document describing a content of each medical trouble event, identifies a medical trouble event satisfying predetermined conditions as a result of totaling of the registered electronic documents, acquires authority information for permitting the acquisition of information from one or a plurality of predetermined medical systems for the identified medical trouble event, temporarily gives the acquired authority information to participants selected for a countermeasure meeting of the identified medical trouble event, and then notifies the respective participants of participation in the countermeasure meeting. <P>COPYRIGHT: (C)2011,JPO&INPIT

Description

  The present invention relates to a medical failure event countermeasure support system and program.

  In order to prevent the occurrence of medical malfunction events, incident reports may be analyzed to help improve medical care. For example, Japanese Patent Application Laid-Open No. H10-228707 discloses that factor information analyzed based on electronic medical record information is presented to assist the analyst.

JP 2007-108815 A

  In order to prevent the occurrence of medical failure events, it is desirable to consider improvement activities not only by incident reports but also by using information on each system managed by the medical system such as medical affairs, nursing and medicine. However, since high security is imposed on medical systems, in order to acquire information from each system, it is necessary to ask each administrator to acquire information. The necessary information could not be provided promptly to the participants.

  One of the objects of the present invention is to provide a medical failure event countermeasure support system and program capable of promptly providing necessary information to participants of a medical failure event countermeasure meeting while preventing leakage of information.

  In order to achieve the above object, the invention described in claim 1 is characterized in that registration means for registering electronic documents each describing the contents of a medical malfunction event, and a result of totalizing electronic documents registered in the registration means, A specifying unit that specifies a medical failure event that satisfies a predetermined condition, and authority information that permits acquisition of information from one or more medical systems that are determined in advance for the medical failure event specified by the specifying unit An acquisition unit; a grant unit that temporarily grants authority information acquired by the acquisition unit to a participant selected in a countermeasure meeting for a medical malfunction event identified by the identification unit; and the countermeasure to the participant A medical failure event countermeasure support system comprising: notification means for notifying participation in a conference.

  Further, in the invention according to claim 2, a medical system corresponding to each of the selected participants is determined, and the granting unit corresponds to the participant the authority information acquired by the acquiring unit. The medical malfunction event countermeasure support system according to claim 1, wherein the system is selectively given to the participant according to a medical system.

  The invention described in claim 3 further includes means for canceling the authority information given by the granting means when the report document of the countermeasure meeting is registered. It is a medical malfunction event countermeasure support system described in 1.

  According to a fourth aspect of the present invention, the content of the medical malfunction event includes the impact level of the medical malfunction event, and the medical malfunction event is determined based on the electronic document registered in the registration unit. The medical malfunction event countermeasure support system according to any one of claims 1 to 3, further comprising means for causing the display means to display a result obtained by summing up the data.

  Further, the invention according to claim 5 satisfies a predetermined condition as a result of totalizing the registration means for registering electronic documents each describing the contents of the medical malfunction event and the electronic documents registered in the registration means. Specifying means for specifying a medical malfunction event to be performed; acquisition means for acquiring authority information permitting information acquisition from one or a plurality of predetermined medical systems for the medical malfunction event specified by the specifying means; and the acquisition Information collecting means for collecting information from the one or more medical systems based on the authority information obtained by the means, and the information selected by the participant selected in the medical malpractice event countermeasure meeting specified by the specifying means; And a notification means for providing information collected by the collection means and notifying the participant of participation in the countermeasure meeting. It is a failure events measure support system.

  Further, the invention according to claim 6 satisfies a predetermined condition as a result of totalizing the registration means for registering electronic documents each describing the contents of the medical malfunction event and the electronic documents registered in the registration means. Specifying means for specifying a medical malfunction event to be performed; acquisition means for acquiring authority information permitting information acquisition from one or a plurality of medical systems determined in advance for the medical malfunction event specified by the specifying means; A granting means for temporarily granting authority information acquired by the acquisition means to a participant selected for the countermeasure meeting for a medical malfunction event identified by the means, and notifying the participant of participation in the countermeasure meeting This is a program for causing a computer to function as notification means.

  Further, the invention according to claim 7 satisfies a predetermined condition as a result of counting the registration means for registering electronic documents each describing the contents of the medical malfunction event and the electronic documents registered in the registration means. Specifying means for specifying a medical malfunction event to be performed; acquisition means for acquiring authority information permitting information acquisition from one or a plurality of predetermined medical systems for the medical malfunction event specified by the specifying means; and the acquisition Information collecting means for collecting information from the one or more medical systems based on the authority information obtained by the means, and the information selected by the participant selected in the medical malpractice event countermeasure meeting specified by the specifying means; Providing the information collected by the collecting means, and causing the computer to function as notifying means for notifying the participants of participation in the countermeasure meeting It is a program for.

  According to the first and sixth aspects of the present invention, necessary information can be promptly provided to a participant in a medical trouble event countermeasure meeting while preventing leakage of information.

  According to the second aspect of the present invention, since a medical system capable of acquiring information is limited even if a participant in a medical trouble event countermeasure meeting, information leakage can be prevented.

  According to the third aspect of the present invention, information leakage can be prevented because a period during which a participant in a medical malfunction event countermeasure meeting can acquire information from the medical system is limited.

  According to the invention described in claim 4, since the state according to the influence degree and frequency of the medical trouble event can be confirmed, it is possible to prevent oversight and improve the accuracy of the judgment.

  According to the inventions described in claims 5 and 7, it is not necessary for a participant to a medical malfunction event countermeasure meeting to acquire information from the medical system himself / herself, and necessary information while preventing leakage of information to each participant. Can be provided quickly.

It is a system configuration figure of the medical management system concerning this embodiment. It is a figure which shows an example of an incident report. It is a figure which shows an example of an influence degree. It is a figure which shows the example of analysis of an incident report. It is a figure which shows an example of a threshold value table. It is a figure which shows an example of a countermeasure meeting information registration screen. It is a figure which shows an example of an authority information table. It is a flowchart of the process in a medical malfunction event countermeasure support system. It is a system block diagram of the medical management system containing the medical malfunction event countermeasure assistance system which concerns on 2nd Embodiment. It is a flowchart of the process in the medical failure event countermeasure assistance system which concerns on 2nd Embodiment.

  Hereinafter, embodiments for carrying out the present invention (hereinafter referred to as embodiments) will be described with reference to the drawings.

  FIG. 1 shows a system configuration diagram of a medical management system 1 according to the present embodiment. As shown in FIG. 1, the medical management system 1 includes a medical failure event countermeasure support system 10 and a plurality of medical systems 5.

  In the present embodiment, the medical system 5 includes, for example, a medical system 5A for managing medical office work, an electronic medical record system 5B for managing patient electronic medical records, a nursing system 5C for managing patient nursing information, and managing patient operation information. A surgical operation system 5D, an article management system 5E that manages medical devices and equipment, a pharmaceutical system 5F that manages medicines, and a document management system 5G that manages documents. From the viewpoint of protecting personal information and preventing information leakage, the authentication processing of each medical system 5 described above is independent. For example, even if you have access to the medical system 5A, other medical systems such as the surgical system 5D Access to the system 5 is not permitted.

  The medical failure event countermeasure support system 10 receives registration of an incident report describing a medical failure event (including a near miss) that has occurred, and a medical failure that is determined to require countermeasures based on the analysis result of the received incident report This system supports the holding of event countermeasure meetings. Details of the medical failure event countermeasure support system 10 will be described below.

  As shown in FIG. 1, the medical failure event countermeasure support system 10 includes an input unit 12, a display unit 14, an incident report registration unit 16, an information analysis unit 18, a countermeasure meeting necessity determination unit 20, and a countermeasure meeting holding request registration unit. 22, a participant selecting unit 24, an authority information holding unit 26, an authority information acquiring unit 28, an authority information adding unit 30, a notification unit 32, and an authority information releasing unit 34. The medical failure event countermeasure support system 10 may be configured using one computer, or may be configured by a plurality of computers sharing functions. The functions of the above-described units are programs stored in a computer-readable information storage medium by a computer including a control unit such as a CPU, a storage unit such as a memory, and an input / output unit that transmits and receives data to and from an external device. May be realized by reading and executing. Note that the program may be supplied to the computer by an information storage medium, or may be supplied via data communication means such as the Internet.

  The input unit 12 receives a user operation input from an input device such as a keyboard or a mouse.

  The display unit 14 includes a display device such as a liquid crystal display or a CRT, and displays a user interface screen.

  The incident report registration unit 16 registers an incident report describing the contents of a medical malfunction event. The incident report registration unit 16 may receive and register an input of an incident report created in advance, or may register an incident report edited according to a user operation received by the input unit 12.

  FIG. 2 shows an example of an incident report. As shown in FIG. 2, the incident report includes the date and time of occurrence of an incident (medical malfunction event), the location of the incident, patient information about the patient in whom the incident occurred, the responder of the incident, the occurrence scene, the impact level, the content of the occurrence, and the occurrence Information on factors, improvement measures, etc. is included. Here, an incident means an occurrence of an act or situation that is out of the ideal state of medical care or care of a patient. It also includes situations where it is thought that there was. The impact level is a numerical value of the impact of an incident.

  FIG. 3 shows an example of the influence degree. As shown in FIG. 3, the degree of influence is provided in, for example, multiple levels from level 0 to level 5, and the sustainability of injury, the degree of injury, and the description of the content are associated with each level. In the present embodiment, the degree of influence increases as the numerical value of the level increases. And the influence level described in an incident report is good also as, for example, referring to the influence degree table | surface shown in FIG.

  The information analysis unit 18 analyzes information on incidents generated by counting the incident reports registered in the incident report registration unit 16. For example, the information analysis unit 18 performs aggregation using the “occurrence content”, “occurrence location”, and “impact level” of the incident report as keys, so that how much accidents occur where and how much. Analyzes whether or not Note that the information analysis unit 18 may set a period for the occurrence date and time of the incident to be analyzed when the incident reports are tabulated.

  FIG. 4 shows an analysis example of an incident report by the information analysis unit 18. The analysis result display table shown in FIG. 4 includes items of “influence”, “total”, and “today” in each cell of the table having the horizontal axis as “occurrence content” and the vertical axis as “occurrence location”. The value of is stored. The “Total” column stores how many times the incident identified by “occurrence content”, “occurrence location”, and “impact” has occurred, and the “Today” column specifies the above-mentioned identification. How many times an incident occurred today. The analysis result display table generated by the information analysis unit 18 may be displayed on the display unit 14. In the example shown in FIG. 4, in “6F” of “East Ward”, “5” incidents with an influence degree “1” relating to “drug” have occurred, and “1” has occurred today. Show. In the analysis result display table, a cell whose frequency (integrated number) exceeds a threshold, a cell indicating that an incident whose influence exceeds the threshold, or the like may be highlighted. In the example illustrated in FIG. 4, for example, when an incident with an integrated number of 7 or more and an incident with an influence degree of 4 or more are occurring today, they are highlighted.

  The countermeasure meeting necessity determination unit 20 determines whether or not it is necessary to hold a countermeasure meeting among the generated incidents based on the analysis result by the information analysis unit 18. For example, in the analysis result display table generated by the information analysis unit 18, the countermeasure meeting necessity determination unit 20 may generate an incident in which the “influence” exceeds the threshold or the “influence” does not exceed the threshold. When there is an incident whose frequency exceeds the threshold, the incident may be determined as a target of the countermeasure meeting.

  In FIG. 5, an example of the threshold value table used in the countermeasure meeting necessity determination part 20 was shown. As shown in FIG. 5, threshold values are stored in the threshold value table with respect to the frequency calculated for each “occurrence content”, “occurrence location”, and “impact level” of the incident. For example, if an incident related to “drug” occurs in “East Ward” and “6F” and there are 5 or more cases with an influence level of “1” in January, it is determined that a countermeasure meeting is required. I will do it. Note that incidents with an influence degree equal to or greater than a threshold (for example, 4 or more) are determined to be countermeasure meetings regardless of frequency. Of course, the contents of the threshold value table shown in FIG. 5 are examples, and the threshold values set for each incident are not limited to the above contents.

  The countermeasure meeting holding request registration unit 22 registers information related to the countermeasure meeting determined to be necessary when the countermeasure meeting necessity determination section 20 determines that the countermeasure meeting is necessary. The countermeasure meeting holding request registration unit 22 displays a countermeasure meeting information registration screen in which information related to the countermeasure meeting is input, and registers information on the countermeasure meeting to be held based on the information input on the countermeasure meeting information registration screen. That's good. Specifically, the countermeasure meeting holding request registration unit 22 registers and registers the incident report selected by the user among the incident reports describing the incident determined to be the countermeasure meeting necessity by the countermeasure meeting necessity determination unit 20. As good as

  FIG. 6 shows an example of the countermeasure meeting information registration screen. As shown in FIG. 6, the countermeasure meeting information registration screen displays a list of incident reports determined to require countermeasure meeting and the contents of the incident report selected from the list. Then, on the countermeasure meeting information registration screen, the user selects the incident report judged to be necessary by pressing the “report registration” button, and when all selections are completed, the user presses the “measure meeting request” button. And By doing so, countermeasure meeting information in which the target incident report is associated with the countermeasure meeting is generated.

  The participant selection unit 24 selects participants to the countermeasure meeting registered by the countermeasure meeting holding request registration unit 22. The participant selection unit 24 may select a member of a predetermined countermeasure meeting, or may select a person in charge of the medical system 5 (medical system 5A, electronic medical record system 5B, etc.) predetermined for the incident that has occurred. It is good also as selecting. The selected medical system 5 may be associated with each selected participant in advance.

  The authority information holding unit 26 holds an authority information table that defines the access rights of the medical system 5 required in association with the incident.

  FIG. 7 shows an example of the authority information table. In the authority information table shown in FIG. 7, necessary access rights for the medical system 5 are stored according to the location and content of the incident. For example, in the example shown in FIG. 7, when the occurrence location is “6F surgery” in “East Ward” and the occurrence content is “medicine”, the necessary access rights are “electronic medical record”, “nursing system” ”,“ Pharmaceutical system ”, and“ surgical system ”.

  The authority information acquisition unit 28 uses the access right held in the authority information holding unit 26 based on the incident indicated by the incident report associated with the countermeasure meeting registered by the countermeasure meeting holding request registration unit 22, and the necessary medical system. 5 access right is acquired. Specifically, the authority information acquisition unit 28 acquires by referring to the access right information stored in the authority information table regarding the occurrence location and content of the common incident in the incident report associated with the countermeasure meeting. As good as

  The authority information assigning unit 30 temporarily grants the access right information acquired by the authority information acquiring unit 28 to the participant selected by the participant selecting unit 24. Specifically, the authority information grant unit 30 may grant the access right of one or more medical systems 5 acquired by the authority information acquisition unit 28 to the participants associated with each medical system 5. By doing so, even if the participant is selected for the countermeasure meeting, access to the medical system 5 not in charge is not permitted.

  The notification unit 32 notifies each participant in the countermeasure meeting to which the access right has been granted by the authority information giving part 30 of participation in the countermeasure meeting. In the present embodiment, the notification unit 32 notifies each participant of the countermeasure meeting information generated regarding the countermeasure meeting. And the participant in a countermeasure meeting shall hold a countermeasure meeting, after acquiring required information from the medical system 5 which he takes charge of based on the access right given to each. Thereafter, the participant in the countermeasure meeting may collect the results of the countermeasure meeting as a report document and register it in the document management system 5G, for example.

  The authority information canceling unit 34 cancels the access right granted to the participant in the countermeasure meeting by the authority information giving unit 30. The authority information canceling unit 34 may cancel the access right when a predetermined period has elapsed, or may cancel the access right when the countermeasure meeting ends. In the latter case, the authority information release unit 34 may release the access right given to each participant when the report document is registered in the document management system 5G, for example.

  FIG. 8 shows a flowchart of processing in the medical failure event countermeasure support system 10. As shown in FIG. 8, the medical failure event countermeasure support system 10 accepts the registration of incident reports (S101), and totals and analyzes the registered incident reports (S102). The medical failure event countermeasure support system 10 displays the result of analyzing the incident report (S103), and when an incident with a high impact has occurred (S104: Y), or the occurrence frequency in a given period has a threshold value. If there are more incidents (S105: Y), the incident is selected as a target for the countermeasure meeting (S106).

  Next, the medical failure event countermeasure support system 10 displays a countermeasure meeting information registration screen for registering information on the selected incident (S107), and accepts information registration on the displayed countermeasure meeting information registration screen (S108). . The medical failure event countermeasure support system 10 selects a participant to the countermeasure meeting (S109), acquires necessary access rights based on the incident targeted for the countermeasure meeting (S110), and sends the above-mentioned information to the selected participant. The acquired access right is given (S111), and each participant is notified of participation in the countermeasure meeting (S112).

  The medical failure event countermeasure support system 10 accepts registration of a report issued through the countermeasure meeting (S113), cancels the access right given to the participant of the countermeasure meeting (S114), and ends the process.

  In the medical malfunction event countermeasure support system 10 according to the above embodiment, each participant receives a notification by temporarily granting the necessary access right to the incident of the countermeasure meeting regarding the incident for which the countermeasure is determined to be necessary. Although access to necessary information is permitted at that time, information leakage is unlikely to occur because the period during which access to information is permitted is limited.

  Next, a second embodiment of the present invention will be described. FIG. 9 shows a system configuration diagram of the medical management system 1 including the medical malfunction event countermeasure support system 10 according to the second embodiment.

  As illustrated in FIG. 9, the medical failure event countermeasure support system 10 according to the second embodiment includes an input unit 12, a display unit 14, an incident report registration unit 16, an information analysis unit 18, and a countermeasure meeting necessity determination unit 20. , A countermeasure meeting holding request registration unit 22, a participant selection unit 24, an authority information holding unit 26, an authority information acquisition unit 28, a notification unit 32, an information collection unit 36, and a provision information creation unit 38. Regarding the medical failure event countermeasure support system 10 according to the second embodiment, the function blocks having the same reference numerals as those of the first embodiment have the same functions, and thus description thereof is omitted. In the following, the medical malfunction event countermeasure support system 10 according to the second embodiment will be described with a focus on differences from the first embodiment.

  The information collection unit 36 uses the access right acquired by the authority information acquisition unit 28 to collect information related to the incident targeted for the countermeasure meeting from the corresponding medical system 5. The information collecting unit 36 may collect information related to the incident targeted for the countermeasure meeting based on keys such as the patient ID related to the incident and the occurrence time of the incident.

  The provided information creating unit 38 creates an information group (information set) to be provided to the participants of the countermeasure meeting by collecting the information collected by the information collecting unit 36.

  The notification unit 32 notifies each participant selected by the participant selection unit 24 of participation in the countermeasure meeting and provides each participant with the information group created by the provision information creation unit 38.

  In FIG. 10, the flowchart of the process in the medical failure event countermeasure assistance system 10 which concerns on 2nd Embodiment was shown. As shown in FIG. 10, the medical failure event countermeasure support system 10 accepts the registration of incident reports (S201), and totals and analyzes the registered incident reports (S202). The medical failure event countermeasure support system 10 displays the result of analyzing the incident report (S203), and when an incident with a high impact has occurred (S204: Y), or the occurrence frequency in a given period has a threshold value. If there are more incidents (S205: Y), the incident is selected as a target for the countermeasure meeting (S206).

  Next, the medical failure event countermeasure support system 10 displays a countermeasure meeting information registration screen for registering information on the selected incident (S207), and accepts information registration on the displayed countermeasure meeting information registration screen (S208). . The medical failure event countermeasure support system 10 selects a participant in the countermeasure meeting (S209), and acquires necessary access rights based on the incident targeted for the countermeasure meeting (S210).

  The medical failure event countermeasure support system 10 collects information from each target medical system 5 using the acquired access right (S211), and creates an information group to be provided to each participant based on the collected information (S212). The medical failure event countermeasure support system 10 notifies each participant of participation in the countermeasure meeting together with the created information group (S213). Then, the medical failure event countermeasure support system 10 accepts registration of a report issued through the countermeasure meeting (S214), and ends the process.

  In the medical failure event countermeasure support system 10 according to the second embodiment, since it is not necessary for participants in the countermeasure meeting to access the medical system 5 to acquire information, information leakage is unlikely to occur.

  The present invention is not limited to the above-described embodiment. For example, an incident targeted for a countermeasure meeting may be selected by a user based on the displayed analysis result display table.

  1 Medical Management System, 5 Medical System, 5A Medical System, 5B Electronic Medical Record System, 5C Nursing System, 5D Surgery System, 5E Product Management System, 5F Drug System, 5G Document Management System, 10 Medical Malfunction Event Countermeasure Support System, 12 Input , 14 Display section, 16 Incident report registration section, 18 Information analysis section, 20 Countermeasure meeting necessity determination section, 22 Countermeasure meeting holding request registration section, 24 Participant selection section, 26 Authority information holding section, 28 Authority information acquisition section , 30 authority information giving unit, 32 notifying unit, 34 authority information releasing unit, 36 information collecting unit, 38 providing information creating unit.

Claims (7)

A registration means for registering electronic documents each describing the contents of a medical malfunction event;
As a result of counting the electronic documents registered in the registration means, a specifying means for specifying a medical malfunction event that satisfies a predetermined condition;
Acquisition means for acquiring authority information permitting information acquisition from one or a plurality of predetermined medical systems for the medical malfunction event specified by the specifying means;
A granting means for temporarily granting authority information acquired by the acquiring means to a participant selected in the medical malpractice event countermeasure meeting specified by the specifying means;
A medical failure event countermeasure support system comprising: notification means for notifying the participant of participation in the countermeasure meeting. Each of the selected participants has a corresponding medical system,
The medical failure event according to claim 1, wherein the granting unit selectively grants the authority information acquired by the acquiring unit to the participant according to a medical system corresponding to the participant. Countermeasure support system. The medical failure event countermeasure support system according to claim 1 or 2, further comprising means for canceling authority information given by the grant means when a report document of the countermeasure meeting is registered. The content of the medical malfunction event includes the degree of influence of the medical malfunction event,
4. The apparatus according to claim 1, further comprising: a display unit configured to display a result of aggregating medical trouble events with respect to the degree of influence and the frequency based on the electronic document registered in the registration unit. 5. Medical failure event countermeasure support system. A registration means for registering electronic documents each describing the contents of a medical malfunction event;
As a result of counting the electronic documents registered in the registration means, a specifying means for specifying a medical malfunction event that satisfies a predetermined condition;
Acquisition means for acquiring authority information permitting information acquisition from one or a plurality of predetermined medical systems for the medical malfunction event specified by the specifying means;
Information collecting means for collecting information from the one or more medical systems based on the authority information obtained by the obtaining means;
Notifying means for providing information collected by the information collecting means to a participant selected in the medical trouble event countermeasure meeting specified by the specifying means and notifying the participant of participation in the countermeasure meeting And a medical failure event countermeasure support system characterized by comprising: A registration means for registering electronic documents each describing the contents of a medical malfunction event;
As a result of counting the electronic documents registered in the registration means, a specifying means for specifying a medical malfunction event that satisfies a predetermined condition;
Acquisition means for acquiring authority information permitting information acquisition from one or a plurality of predetermined medical systems for the medical malfunction event specified by the specifying means;
A granting means for temporarily granting authority information acquired by the acquiring means to a participant selected in the medical malpractice event countermeasure meeting specified by the specifying means;
A program for causing a computer to function as notifying means for notifying the participant of participation in the countermeasure meeting. A registration means for registering electronic documents each describing the contents of a medical malfunction event;
As a result of counting the electronic documents registered in the registration means, a specifying means for specifying a medical malfunction event that satisfies a predetermined condition;
Acquisition means for acquiring authority information permitting information acquisition from one or a plurality of predetermined medical systems for the medical malfunction event specified by the specifying means;
Information collecting means for collecting information from the one or more medical systems based on the authority information obtained by the obtaining means;
Notifying means for providing information collected by the information collecting means to a participant selected in the medical trouble event countermeasure meeting specified by the specifying means and notifying the participant of participation in the countermeasure meeting As a program to make the computer function as.

Images