TWI737857B - Service supporting system, service supporting method, and computer program - Google Patents

Abstract

The present invention presents the conceivable causes, factors, risk factors and matters for attention of the cases that have occurred from various viewpoints. The service support system 210 has: a reason database 460, which stores a data group that associates each cause of each state of affairs related to the occurrence of the case according to the type of each case; the acceptance section 314, which accepts the types and types of cases that occurred The input of the occurrence status of the case; the matching unit 316, which matches the accepted occurrence status with the data group corresponding to the type of the accepted case stored in the cause database; and the output unit 317, which outputs the matching from the matching unit The reason for the result.

Description

Service support system, service support method and program

The present invention relates to a service support system, service support method and program.

In nursing facilities or medical facilities, various accidents may occur to the elderly who live here. The causes, factors, risk factors and matters that should be paid attention to to prevent accidents vary according to the type of accident or the situation of occurrence. In addition, in order to identify the causes of various accidents, etc., corresponding knowledge or experience is required. In addition, the analysis of the accident or the filing of future response or preventive measures will also consume a lot of time and labor. In Patent Document 1, there is disclosed a technique for extracting assistance target items that match the combination pattern of the evaluation items selected by the user when generating a care plan. [Prior Art Document] [Patent Document] [Patent Document 1] Japanese Patent No. 3889189

[Problem to be solved by the invention] No technology is proposed to remind employees of the reasons, factors, risk factors and matters that should be paid attention to in cases that have occurred. The reasons for the occurrence of cases vary according to the type of case or the situation of occurrence, and cannot be uniformly specified. On the contrary, there are also dangers that employees may ignore the real reason that they have not noticed due to certain beliefs. Therefore, the purpose of the present invention is to provide a service support system, service support method, and program that can prompt the possible reasons, factors, risk factors, precautions, etc., of a case that has occurred from various perspectives. [Technical Means to Solve the Problem] The service support system of one aspect of the present invention is provided with: a reason database, which stores a data group related to each cause of each situation related to the occurrence of the case according to the type of each case; Part, which accepts the input including the type of the case that occurred and the occurrence status of the case; The matching part, which matches the accepted occurrence status with the data group corresponding to the type of the accepted case stored in the cause database; And the output part, which outputs the reason obtained from the matching result of the matching part. The service support method of one aspect of the present invention includes the following steps: accepting the input including the type of case that occurred and the occurrence status of the case; making the accepted occurrence status and reason database stored in the database correspond to the accepted information in the data group The data group of the case type is matched. The above-mentioned reason database stores the data group that associates the causes of each situation related to the occurrence of the case according to the type of each case; and outputs the reason obtained from the matching result. The program of one aspect of the present invention is to make the computer execute the following steps: accept the input including the type of case and the occurrence status of the case; make the accepted occurrence status and reason database stored in the corresponding data group accepted Match the data groups of the case types. The above-mentioned reason database stores the data groups that will be associated with the causes of the events related to the occurrence of the case according to the type of each case; and output the reasons obtained from the matching results. [Effects of the Invention] According to the present invention, the reasons, factors, risk factors, precautions, etc. of an existing case can be presented from various viewpoints.

[Explanation of terms] The terms explained in this embodiment will be explained. [Employee]: Department of facility manager/manager, care manager (person in charge of plan production), service provider, care worker/home care attendant, caregiver, functional training instructor, life counselor, life care worker and reception clerk Workers who perform facilities related. [User]: Those who use the system described in this embodiment. As a specific example, list the employees of the facility. [Service Provided]: A person who receives services provided by facilities or operators. It is not necessary to move into the facility, and it also includes those who receive some services from outside. In the following embodiment, the service provider is an occupant who has moved into a nursing facility as an example. In addition, the service recipient may be a person who has not moved into the facility, such as a person receiving day care or home visit care, and the two may be mixed in the embodiment described below. The preferred embodiments of the present invention will be described with reference to the accompanying drawings. In addition, in each figure, those with the same symbol have the same or the same structure. [Explanation of accident factors] Figure 1 is a diagram schematically showing an example of accident factors in nursing facilities. Figure 1 shows an example of the various factors involved in the occurrence of a fall accident. For example, if the factors that cause a fall accident are roughly divided into two, they can be divided into internal factors and external factors. The so-called internal factors are those caused by the occupant. In a fall accident, it is the occupant's body, physiological factors, disease, illness, symptoms, medications, and other factors related to the occupant. For example, as shown in Figure 1, it can be classified into physical, physiological factors, diseases, disorders, symptomatic factors, and drug factors. For example, examples of physical and physiological factors include advanced age, a history of falls, decreased sensation or lack of exercise, insomnia, constipation, poor health, decreased judgment, and conditions that are different from usual. As the disease, illness, symptom factor, include diseases, disorders, symptoms of the circulatory system such as high blood pressure, diseases, disorders, symptoms of the cranial nervous system, diseases of the heart system, disorders, symptoms, fractures, decreased muscle strength and other motor functions Drop and so on. As the drug factor, list the type of medicine taken, or the quantity of medicine taken, etc. For example, dizziness and falls may occur due to the side effects of the medicine. As an external factor, it is caused by factors other than the occupant, including the structure of the building of the facility or the environment of the room, the clothes or shoes worn by the occupant, the use of tools such as crutches or wheelchairs, and the skills and knowledge of the staff of the facility Factors related to facility management, such as experience, assistance methods or participation, information sharing, or various training courses. For example, as shown in Figure 1, it can be classified into environmental factors and family and employee factors. As environmental factors, there are surrounding environment or surrounding environment. For example, the surrounding environment such as the corridor with steps, or the situation where the ground becomes slippery, the use of tools such as walking sticks, and the wearing of shoes such as slippers are examples. Family and employee factors include, for example, employee assistance methods, information sharing within the family, well-known methods, evaluations, plans, or employee management. In addition, the above factors are only an example, and are not limited to this. In this way, although only the summary of the fall accident is cited as an example, various factors are included as the factors of the accident. In addition, there are cases where a fall accident occurs due to a plurality of these factors being related. Furthermore, as a type of accident, not only fall accidents, but also accidents such as swallowing, suffocation, or drug accidents may occur. The factors of these accidents include various factors that are different from the factors of fall accidents. In this way, among the various accidents that may occur to the occupants of nursing facilities, various factors often occur in combination. In addition, there are also situations where employees have insufficient knowledge or experience and insufficient follow-up of the system, leading to inadequate analysis, which may result in inappropriate response or preventive measures. Therefore, in this embodiment, according to the type of each accident, the various causes, factors, and risk factors that may occur in the accident are systemized and databased. For example, it becomes a database in a way that becomes the data of the same hierarchical structure. In addition, when an accident occurs, the user inputs information about the situation of the accident (including the accident discovery situation. The following is the same.) so that the input information is the same as the information stored in the systemized (such as structured, hierarchical) database Match according to specific rules. Also, the cause candidates are scored based on the matching result. As a result, for example, candidates for reasons with high scores are displayed on the user terminal. In this way, support the analysis of the cause of the accident. [Overall Configuration] Fig. 2 is a diagram showing an example of the usage mode of this embodiment. The service support system 210 can be configured as a server device and connected to a plurality of user terminals 220a and 220b. Figure 2 shows two user terminals, but the number of user terminals is arbitrary. The plural user terminals are collectively referred to as user terminals 220. The user terminal 220 and the service support system 210 are connected to each other through a network such as the Internet and a LAN (Local Area Network). The user terminal 220 is an information processing terminal used by the employees of the nursing facility. The users of this embodiment include employees of nursing facilities. The user can refer to the information displayed on the user terminal 220 and confirm the information required for the provision of the service. The service support system 210 is an information processing device such as a server that records information about the provided service. The user terminal 220 may display information on the user terminal 220 based on the data sent from the server support system 210. In addition, the server support system 210 can also manage users by logging in, and send the user data corresponding to the user terminal 220 to the user terminal 220. FIG. 3 is a block diagram showing an example of the configuration of the service support system 210 and the configuration of the user terminal 220 of this embodiment. [Configuration of User Terminal] The user terminal 220 includes an input unit 320, a communication unit 321, a display unit 323, a display control unit 324, a storage unit 325, and a storage control unit 326. The user terminal 220 can be used as various information processing terminals such as a tablet terminal, a smart phone, and a personal computer, for example. An operation instruction from the user is input to the input unit 320. Various data are sent and received between the communication unit 321 and the communication unit 311 of the service support system 210. That is, the communication unit 321 functions as a receiving unit and a transmitting unit. The display unit 323 displays various screens including the creation screen of the accident report to be described later. For example, the display unit 323 can be used as a liquid crystal display, an organic EL (electroluminescence) display, etc. The display control unit 324 controls the information displayed on the display unit 323. The memory unit 325 stores various data. For example, the memory unit 325 Memorizes the data used for the preparation of the accident report. The storage unit 325 can also be various storage media such as HDD (Hard Disk Drive) or flash memory. The memory control unit 326 writes various data to the storage unit 325, And read out various data from the memory part 325. The user terminal 220 may have a CPU (Central Processing Unit), RAM (Random Access Memory), flash memory or HDD (not shown). The flash memory or HDD may be the same as the above-mentioned memory section 325 or different. The programs stored in the flash memory or HDD are temporarily read out to RAM, and the programs read out to RAM are executed by the CPU. Therefore, the CPU can function as the various parts of the user terminal 220 shown in Figure 3. Here, the configuration implemented by software is taken as an example for description, but it can also be constituted by any of hardware, firmware, and software. Figure 3 It is only an example of the display configuration, and the user terminal 220 may also include other configurations. In addition, all the configurations described in Fig. 3 are not essential. [Server Configuration] Next, the configuration of the server support system 210 will be described. The server support system 210 includes a communication unit 311, a memory control unit 312, a memory unit 313, a receiving unit 314, a database 315, a matching unit 316, and an output unit 317. The communication unit 311 uses the interface of the Internet and LAN, etc. Data is sent and received with the user terminal 220. That is, the communication unit 311 functions as a transmitting unit and a receiving unit. The memory control unit 312 writes various data to the memory unit 313, or reads various data from the memory unit 313. Memory unit 313 stores various data. For example, the memory unit 313 stores the reservation and actual performance data of the services provided by the occupant. The memory unit 313 can also be various storage media such as HDD (Hard Disk Drive) or flash memory. The section 314 accepts input of various information including the type of the case (such as an accident) that occurred and the occurrence status of the case (such as an accident). For example, the receiving section 314 may receive the information received from the communication section 311 and sent from the user terminal 220 The following is an example of an accident. The database 315 stores the occurrence (including discoveries) of the case (accident), for example, according to the type of each case (accident). The following is the same. The related events are systematized ( Such as structured, hierarchical) data group. As the types of accidents, for example, fall accidents, swallowing accidents, suffocation accidents and drug accidents. That is, in this case, the storage will be The data group obtained by linking the causes of each state of the fall accident, the data group obtained by linking the causes of each state of the accident such as swallowing and suffocation, and the data group obtained by linking the causes of each state of the drug accident Data group. In addition, three types of accidents are listed here for description, but they are not limited to this. In addition, for the convenience of description, the description is divided into the memory unit 313 and the database 315, but it may also be a configuration in which the two are shared. The matching unit 316 matches the occurrence status accepted by the accepting unit 314 with the data group stored in the database 315 and corresponding to the type of the accepted case (accident). The details are described below. The output unit 317 outputs the cause information obtained from the matching result in the matching unit 316. For example, the output unit 317 may send the cause information to the user terminal 220 via the communication unit 311. The service support system 210 may have a CPU, RAM, and flash memory or HDD (not shown). The flash memory or HDD may be the same as the above-mentioned memory portion 313 or may be another. The program stored in the flash memory or HDD is temporarily read to the RAN, and the CPU executes the program read to the RAM, whereby the CPU can function as various parts of the service support system 210 shown in FIG. 3. Here, the configuration implemented by software is taken as an example for description, but it can also be configured by any of hardware, firmware, and software. At least a part of the parts of the service support system 210 can also be realized by distributed processing using a plurality of information processing devices. In addition, the service support device 210 can also execute processing according to a program downloaded from a cloud server, etc. not shown. FIG. 3 is only an example of the configuration, and the service support system 210 may also include other configurations. In addition, all the constitutions described in Fig. 3 are not essential requirements. FIG. 4 is a diagram showing an example of the detailed structure of the database 315 and the matching unit 316. In this embodiment, the database 315 has an occurrence database 450 and a cause database 460. The occurrence status database 450 has a database for each type of accident. In the example of FIG. 4, the occurrence situation database 450 includes a fall accident occurrence situation database 451, a swallowing and suffocation accident occurrence situation database 452, and a drug accident occurrence situation database 453. The cause database 460 also has a database for each accident type similarly to the occurrence situation database 450. In the example of FIG. 4, the cause database 460 includes a fall accident cause database 461, a swallowing and suffocation accident cause database 462, and a drug accident cause database 463. In addition, the common cause can also be shared as the common cause database 465 of the accident. The occurrence situation database 450 and the cause database 460 both store data groups that systematize (structuralize, hierarchical) events related to the occurrence of the accident for each accident type. The occurrence database 450 and the cause database 460 each store a data group including a plurality of systemized (structured, hierarchical) data records. In this embodiment, the data record stored in the occurrence situation database 450 is referred to as the "occurrence situation data record". The data record stored in the reason database 460 is called the "cause data record". In this embodiment, the cause data record contains a data structure common to the occurrence data record. It is structured to store, for example, the data of the Nth item (N is a natural number) of a certain occurrence data record and the Nth item of the cause data record as the same kind of data. That is, the same kind of events related to the occurrence of the accident are mutually stored in the Nth item of the occurrence data record and the cause data record. In this embodiment, an item with an N value of "1" is regarded as an item with the highest level, and an item whose level becomes lower as the N value increases. In addition, in addition to the data structure common to the occurrence data record, the cause data record will be related to data representing various factors of the accident such as the "viewpoint to be controlled or candidate for the cause". In other words, the cause database 460 stores data groups that will be associated with each cause of each event related to the occurrence of the accident. The following describes the details of the occurrence data record and the cause data record. The matching unit 316 includes a keyword extraction unit 401, an input data record acquisition unit 402, a matching rule holding unit 403, a matching method determination unit 404, a matching processing execution unit 405, and a matching result output unit 406. The keyword extracting unit 401 extracts keywords used for retrieval of the database based on the information related to the occurrence status of the received input. For example, the accident report creation screen 500 displayed on the display unit 323 of the user terminal 220 as shown in FIG. 5 (described later) includes an input area for inputting the situation of the accident. The keyword extracting unit 401 can extract keywords based on the information input into the input area. For example, if it is a fall accident, enter "room" as the keyword of "discovery, place of occurrence", and "bed" as more detailed information. In this case, the keyword extraction unit 401 will capture "house" and "bed" as keywords. In addition, methods such as natural language analysis or software can also be used to decompose the input sentence into words or sentences to generate one or more keywords. The input data record acquisition unit 402 selects from the occurrence status database 450 a database corresponding to the type of accident that has been accepted by the accepting unit 314 for input. For example, if the type of accident accepted for input is "fall accident", the input data record acquisition unit 402 selects the fall accident occurrence status database 451. In addition, the input data record acquisition unit 402 uses the keywords extracted by the keyword extraction unit 401 to search the selected fall accident occurrence status database 451, and acquires the occurrence status data record containing all the keywords as the input data record. The obtained input data record is used for matching processing with the reason data record stored in the reason database 460. The input data record is sent to the matching method determination unit 404. The matching rule holding unit 403 holds matching rules. In this embodiment, the matching process is performed by comparing the items corresponding to the input data record and the cause data record (the Nth items). In this way, in this embodiment, the matching process of comparing the Nth items with each other is referred to as "horizontal matching". In this embodiment, an example of basically using the horizontal matching for matching processing is described, but for input data records containing specific items (or specific keywords), other matching methods may be performed. The details are described later. The matching method determination unit 404 refers to the matching rule held in the matching rule holding unit 403 to determine the matching method of the input data record. The matching processing execution unit 405 performs matching processing using the input data record on the cause database 460 corresponding to the accident type in accordance with the matching method determined by the matching method determination unit 404. As described above, if the type of accident is a fall accident, the matching processing execution unit 405 performs matching processing on the fall accident cause database 461. For example, the matching processing execution unit 405 determines whether the keywords included in the Nth item of the input data record of the processing object are consistent with the keywords included in the Nth item of the processing object's cause data record. And, if they are consistent, the score corresponding to the weight of the corresponding relationship with the Nth item is added to the score accumulated in the cause data record of the processing object. This matching process (horizontal matching process) is performed on all the cause data records of the candidates for the processing object of the fall accident cause database 461. In addition, the above-mentioned matching process is performed while changing the input data record of the processing object. Since the scores for matching are cumulatively added, the result is higher consistency with the input data record because the score of the data record becomes higher. The matching result output unit 406 outputs the matching processing result of the matching processing execution unit 405. The matching processing result of the matching processing execution unit 405 is calculated from the score of each cause data record. The matching result output unit 406 may output a data record of the reason for calculating the score exceeding a certain threshold as the result of the matching process. Or the matching result output unit 406 may also output data representing the non-cause data record itself, but related to the cause data record, such as "controllable viewpoint or cause candidate" accident occurrence data, etc., as the matching result. Next, the details of the matching process will be described while citing specific examples. FIG. 5 is a diagram showing an example of an accident report creation screen 500 of a fall accident displayed on the display unit 323 of the user terminal 220. The so-called accident report is a report that records the content of the accident or the corresponding situation, cause analysis, future response or preventive measures, etc. when the accident occurred (or the accident was discovered). The user of the user terminal 220 (employee of the nursing facility) inputs necessary items according to the creation screen 500. In addition, the completed input items on other screens not shown in the figure can also be reflected in the production screen 500. The input area 501 is an area where the user of the user terminal 220 inputs the date and time when the fall accident is discovered, and the date and time when the fall accident occurs. The input area 502 is an area where the user of the user terminal 220 inputs the status of a fall accident and the occurrence of a fall accident. The input area 503 is an area where the user of the user terminal 220 inputs a place where a fall accident is found and a place where a fall accident occurs. The input area 504 is an area where the user of the user terminal 220 inputs the discoverer of the fall accident. The production screen 500 in FIG. 5 illustrates a part of the input area. For example, a screen for inputting other input areas by scrolling an animation screen is displayed on the display unit 323. Fig. 6 shows the input areas 601, 602, and 603 of the production screen 500 of Fig. 5 being scrolled or displayed on another screen, and the occurrence data record group 610 of the occurrence status database 450 containing events corresponding to these input areas , 620, 630. Occurrence data records group 610, 620, 630 are data records group about external factors. As illustrated in Fig. 1, the external factors are classified into categories, and the example in Fig. 6 shows examples of "discovery, occurrence" category, "obstacle" category, and "side" category. Taking the occurrence situation data record group 610 as an example, the data structure of the occurrence situation data record stored in the occurrence situation database 450 is explained. The occurrence data record has a hierarchical structure as described above. In the example in Figure 6, the uppermost level is displayed as "Lv1", and the number of levels increases to "Lv2" and "Lv3" as the level decreases. Figure 6 is the data record about "external factors" as illustrated in Figure 1, so the items of the top level include "external" data. In addition, the data record group 610 is a data record group of the "discovery, occurrence location" category, so the item of the "Lv2" level includes the data of the "location". Subsequent hierarchical items include data records containing items that can be input in the input area 601. As shown in Fig. 6, the occurrence situation data record is set with more detailed (specific) content from the top level to the lower level. In the input area 601, list multiple items that can be checked with the check box as candidates for discovery and occurrence locations. In this example, check "Room". In addition, the "Room" further includes a radio button to specify the detailed location in the room. In this example, select "toilet". The information input by the input unit 320 as displayed in the input area 601 of the display unit 323 of the user terminal 220 is sent from the user terminal 220 to the service support system 210. In the service support system 210, the keyword retrieval unit 401 retrieves keywords based on the information sent from the user terminal 220. In this example, as the keyword of the category of "discovery, place of occurrence", based on the sent data, extract "room, toilet" as the keyword. In addition, the input data record acquisition unit 402 acquires the occurrence situation data record corresponding to the keyword from the fall accident occurrence situation database 451 as the input data record. That is, in the example of FIG. 6, the data record 611 in the data record group 610 is obtained as the input data record of the "discovery/occurrence location" category. Similarly, according to the items entered in the input area 602, the corresponding input data records are obtained from the data record group 620 of the "obstacle" category, and the data records group 630 of the "side" category are obtained according to the items input in the input area 603 Obtain the corresponding input data record in. That is, in the example of FIG. 6, the input data record acquisition unit 402 acquires the occurrence situation data records 611, 621, 622, 631, 632, and 633 as input data records in accordance with the items input in the input areas 601, 602, and 603. The input data is recorded as described later and will be used for matching processing. FIG. 7 shows the input areas 701 and 703 of the production screen 500 of FIG. 5 being scrolled or displayed on another screen, the input area 501 included in the production screen of FIG. 5, and the occurrence status database 450 corresponding to these input areas The data record group 710. The data record group 710 is a data record group about internal factors. The internal factors are classified into "actions during accidents", "conditions different from usual", "disease, illness, symptoms", and "drugs". The example in Figure 7 shows an example of the occurrence status data record of the "action at the time of an accident" category. The data record group 710 contains the data records corresponding to the items input in the input area 701 in the same way as the content explained by the external factors in FIG. Key words. In addition, the input data record acquisition unit 402 acquires the occurrence situation data record corresponding to the keyword from the fall accident occurrence situation database 451 as an input data record. That is, in the example of FIG. 7, the data records 711, 712, and 713 are acquired in the data record group 710 of the "action in accident" category. In addition, in the case of internal factors as shown in Fig. 7, in addition to the information entered in the input area of the corresponding category, the information entered in other areas can be used as keywords for specific items in the data record. For example, in the input area 501, the date and time when the accident was discovered and the date and time when the accident occurred are input, so the keyword extraction unit 401 captures keywords in the time zone based on the input date and time. For example, as shown in the form 721, a form is prepared in advance to correspond the value entered as the date and time of the accident report and the occurrence date and time to the time zone. The keyword extraction unit 401 refers to the table 721, and determines, for example, whether the time zone is "morning" or "daytime" or "night" or "late night". Moreover, the input data record acquisition unit 402, as shown in the data record group 730, acquires the data record group 730 that contains the keyword ("night" in this example) in the "Lv6" hierarchy of the data record group 710 as input data record. That is, by reusing the values entered in other input areas, the procedure for re-entering can be saved, and the input data record obtaining section 402 can obtain the appropriate data record as the input data record even if there is an input omission. Similarly, the input area 703 corresponds to the input area other than the input area of the "action in accident" category, and represents the area where the accident occurrence situation is selected. The table 722 is a table in which the values input into the input area 703 and the corresponding keywords are established correspondingly. The keyword extraction unit 401 determines "NULL" which is "under assistance" or "non-assistance" or neither of them based on the value input in the input area 703 and the table 722. Moreover, the input data record acquisition unit 402, as shown in the data record group 730, acquires the data record group 730 that contains the keyword (in this example, "aiding") in the "Lv7" layer of the data record group 710 as input Information record. In addition, in this way, table information referring to values entered in other areas, or various information representing the input terminal for inputting keywords obtained by reference can also be stored in the matching rule holding section 403, the keyword extracting section 401 and the input data The record acquisition unit 402 can refer to the matching rule held in the matching rule holding unit 403 to perform processing. Similarly, the input data record obtaining unit 402 also obtains other types of input data records of "conditions different from usual", "disease, illness, symptom" and "drugs". FIG. 8 is a diagram showing an example of an input data record about external factors acquired by the input data record acquisition unit 402. Obtain the input data records of each category according to the processing described in Figure 6. The matching processing execution unit 405 performs a process of matching each input data record of each category obtained in this way with each cause data record stored in the cause database 460. In addition, as illustrated in FIG. 7, such as item 801 or item 802, the item processed as an external factor is set as a keyword of a specific item of the internal factor, etc. The items processed in a certain category will also be used in other categories. FIG. 9 is a diagram showing an example of the input data record regarding internal factors acquired by the input data record acquisition unit 402. Obtain the input data records of each category according to the processing described in Figure 7. The item 951 includes the keywords of the item 801 and the item 802 in FIG. 8. In addition, in the examples so far, it is explained that the radio button and the check box are equal to the predetermined value in the input area, and the predetermined value (keyword) is used as it is, but it is not limited to this. For example, as shown in item 960, suppose that there is an item of "be tired after bathing" in the selection items of the input area. In this case, the keyword extraction unit 401 sets "bath" as a keyword as shown in item 955, and may also set "bath fatigue" as shown in item 956. The keyword extraction unit 401 may also perform such keyword extraction according to the rules held in the matching rule holding unit 403, for example. In addition, the form in which the selection items are pre-included in the input area has been described as an example so far, but the input area may also be a free entry field. In this case, the keyword extracting unit 401 can also extract keywords based on the input information. Next, the structure of the cause database 460 will be described. Figure 10 is a diagram schematically showing an example of the cause data record contained in the cause database. The cause data record contained in the cause database 460 contains the same hierarchical structure as the occurrence data record contained in the occurrence database 450. For example, Fig. 10(a) shows an example of the structure of the cause data record for external factors. The first part 1001 of the cause data record is the same structure as the input data record (occurrence data record) of Fig. 8. However, for the keywords set in each item of the occurrence data record, the cause data record system can set the corresponding words, corresponding words, synonyms, other languages, alternatives, expressions, etc. forms of the keywords. This reason is that when situations such as orthographic variants of keywords included in each item of the occurrence data record are generated, matching processing can also make them consistent. For example, if the item of "bed" is taken as an example, the item of "bed (ベッド)" in the cause data record can also be used to prevent spelling variants, such as "べっと", "べっど", Set multiple keywords in "ベット", "bed", etc. In addition, the reason data record further includes the second part 1002. The second part 1002 contains data corresponding to the contents of each first part 1001, such as "a viewpoint to be controlled or a candidate for a cause" indicating various factors of the accident. In other words, the cause data record can be said to be data that associates the cause (the second part 1002) of the situation (the first part 1001) related to the occurrence of the accident. Figure 10(b) shows an example of the structure of the cause data record for internal factors. Like the external factors, the first part of the cause data record 1051 is the structure of the input data record (occurrence data record) in Figure 9 With the same structure, the second part 1052 of the cause data record contains data corresponding to the content of the first part 1051, such as the "viewpoint to be controlled or candidate for the cause" indicating various factors of the accident. 11 is a schematic diagram for explaining the matching process executed by the matching process execution unit 405 according to the matching method determined by the matching method determination unit 404. Before describing the matching process, first, the type of matching method determined by the matching method determining unit 404 will be described. The matching method determination unit 404 refers to the matching rule held in the matching rule holding unit 403 to determine the matching method corresponding to the input data record. As the types of matching methods in this embodiment, there are "horizontal matching", "vertical matching", and "cross matching". Of course, this is only an example, and various other matching methods such as "random matching" or "full matching" are also considered, and it is not limited to this. Hereinafter, each matching method will be described. [Horizontal matching] "Horizontal matching" is the process of matching each item of the input data record with each item of the reason data record contained in the reason database, so that the same items of the same hierarchical level are matched with each other. For example, if the example in Figure 11 is used, the item of the uppermost level (Lv1) of the input data record 1110 of the category of "discovery, occurrence location" and the cause data record 1152 contained in the cause data record 1151 group are the highest The items of the upper level (Lv1) match each other. Specifically, the keywords contained in the uppermost layer (Lv1) of the input data record 1110 are compared with the keywords contained in the uppermost layer (Lv1) of the cause data record 1152 to determine whether they are consistent. In the case of agreement, the score corresponding to the weight of the weight coefficient 1102 of the input data record is added to the score accumulated in the reason data record 1152 (the initial value is set to 0). Next, match the items of the second level (Lv2) of the input data record 1110 of the category of "discovery, occurrence place" with the items of the second level (Lv2) of the cause data record 1152 included in the cause data record 1151 group. . Also, in the example of Fig. 11, if the items of the lowest level (Lv7) and (Lv7) are matched with each other, proceed to continue occurrence data record 1110 and cause data record group 1151 to include the next cause data record 1153 The matching processing. In this way, the input data record 1110 of the "discovery, occurrence location" category is matched with all the cause data records included in the cause data record group of the "discovery, occurrence location" category. If the processing of the input data record 1110 ends, the input data record 1111 under the category of "discovery, occurrence location" in the occurrence situation data record group 1101 is used as the input data record to be processed, and the matching process is performed in the same way. If the matching process using the input data record of the "discovery, occurrence location" category is completed, the input data record of the next category "obstacle" and the cause data of the "obstacle" category in the reason data record group 1151 will be performed. Record matching processing. In this embodiment, the weight coefficient 1102 is set according to the hierarchy. Specifically, the weight coefficient 1102 is a coefficient whose weight is higher as the hierarchy goes down. As explained in the above examples, the occurrence status data record and the cause data record of this embodiment are set with more detailed items as the hierarchy descends. For example, if the category "Discovery, Occurrence" is taken as an example, if there is a situation in which "room" is set in the upper layer, set the "bed" in the lower layer, and then set the "bunk bed" in the lower layer, etc. . The more detailed the item, the more specific the alternative content of the viewpoint or reason that should be controlled. Therefore, by using the weight coefficient 1102 that increases the weight more and more downward, the score of the data record of the reason for the situation where the detailed items are consistent can be improved. Therefore, it will be easy to choose a specific "viewpoint or reason candidate that should be controlled". In addition, in the example shown in Figure 11, an example of processing according to each category is explained. However, as mentioned above, the uppermost level of the occurrence data record and the cause data record can contain items of "internal factors" or "external factors". The top level and the next level can contain items of categories such as "discovery, place of occurrence" and so on. Therefore, the input data record of the processing object can also be processed with all the cause data records as the processing object for the input data record of the processing object. [Vertical Matching] Figure 12 is a diagram for explaining "Vertical Matching" and "Cross Matching". The "vertical matching" is explained. "Vertical matching" is a process that uses keywords of a specific level of the input data record of a specific type, and only matches the items of the predetermined level in each cause data record. In this way, it means that matching is performed only on a specific level in each cause data record, that is, matching is performed in the row direction (vertical direction). In this way, matching across categories is performed. The specific hierarchy of the specific category is defined in advance by the matching rule held in the matching rule holding unit 403. That is, when the matching method determination unit 404 receives the input data record from the input data record acquisition unit 402, the matching method determination unit 404 refers to the matching rule held in the matching rule holding unit 403 to determine whether it corresponds to "vertical matching". Moreover, in the case of an equivalent situation, the matching method determination unit 404 uses the keywords contained in the item to decide to further execute the processing of "vertical matching". In addition, if the item does not contain keywords, no processing will be performed. Specific examples are given for explanation. As a match, the following is defined in advance. That is, define and execute the matching rules that match the keywords of the specific items set in the specific categories and the items of the specific levels in each cause data record. And, for example, when the "different condition" category item (Lv5) of the input data record of the processing object contains the keyword "dizziness", if the "action in accident", "disease, illness, symptom" If the level (Lv5) of the "drug" category performs "vertical matching", the matching method determination unit 404 will make a decision. In addition, "vertical matching" is an additional matching process to "horizontal matching". When processing input data records containing specific keywords (such as "dizziness"), the input data record of the processing object is also subjected to "horizontal matching" "The treatment itself. For the specific item corresponding to the specific keyword (dizziness) defined by the matching rule, the matching processing execution unit 405 searches for only items of a specific level across categories according to the defined matching rule. And, if there is a consistent item, the weight corresponding to the item is added to the score accumulated in the reason record containing the item. For example, as the cause of dizziness, consider various situations such as physical causes, illness symptoms, and drug effects. Therefore, for example, in the category of "conditions different from usual", if the condition includes "dizziness" as a condition different from usual, search for the "movement" item of the category "action in accident" and search for "disease/diseases/symptoms" For the "symptom" item of the category, search for the "side effect" item of the "drug" category. As a result, for example, the "ADL (Activities of Daily Living, activities of daily living), decline in muscle strength" in the cause data record of "Actions in Accidents" will increase the scores of the cause data records, "Illness, illness, The cause data record of "Symptoms" contains "peripheral symptoms of Alzheimer's disease" and "cerebrovascular disease" as the cause, and the cause data record of "Drugs" contains "hypnotics" and "anxiety drugs". ""Anti-epileptic drugs" as the cause, the score of the cause data record has become higher. According to this kind of processing, it is possible to extensively collect those who may be the cause. In addition, the user is prompted with a higher score, and the user is urged for confirmation. Therefore, when considering various reasons such as "dizziness", add the score of the cause data record that includes those who may be the cause. Therefore, based on the user's experience, etc., the missing items from self-consideration can be reduced. That is, when the user (employee) inputs the occurrence situation, the score of the cause data record about the cause that cannot be immediately detected by the information inputted by the user (employee) becomes higher, so the possibility of detecting the cause that the user cannot detect is increased. In addition, vertical matching can be performed on multiple levels that also include relatively lower levels (levels that specify detailed items). Therefore, as described above, the weight of the case of coincidence becomes higher. Therefore, the scores of the cause data records that are consistent with the vertical match are relatively higher than the scores of the cause data records that are not consistent with the vertical match. Therefore, the scores of the cause data records related to the cause of "dizziness" in the above example are higher, as a match As a result, the possibility of selection is further increased. [Cross Match] Describes [Cross Match]. Cross-matching is to enable the input data record acquisition unit 402 to re-acquire the input data record of the occurrence situation when the processing target item of the input data record is an item of a specific class of a specific level. In addition, the re-acquired input data record is used to perform the above-mentioned matching processing. In other words, when the item of the processing object of the input data record is an item of a specific type of a specific level, the keywords contained in the item are used to match the items of different types of different levels. For items and keywords of a specific class and a specific level that are the target of cross-matching, matching rules are also defined in advance for the matching rule holding unit 403. In addition, if the item does not contain keywords, no processing will be performed. For example, for items not input by the user (therefore, items that do not contain keywords in a specific item of the input data record) are processed as if the user seems to be typing, and matching is performed indirectly. A specific example will be explained. For example, imagine a situation where Parkinson's disease has been entered as "disease, illness, symptom". At this time, although the user sometimes knows that the occupant has Parkinson's disease, he does not know the medicine used by the person. In this case, in the "drug" category, no drug has been selected, that is, an empty column. By using cross-matching, even if this is empty, the input data record related to "drugs" can be processed as an input data record containing drug names related to Parkinson's disease. Specifically, the input data record acquisition unit 402 re-acquires the input data record contained in the corresponding item of the input data record of "drugs", and will follow the matching rules defined in the matching rule holding unit 403 to the Parkinson’s disease. The name of the medicine is processed as the input data record of the processing object. With this, in the state where the name of the drug has been entered, horizontal matching of the "drug" category is performed. According to this kind of processing, it is possible to extensively collect those who may be the cause. In addition, the user is prompted with a higher score, and the user is urged to confirm. Therefore, based on the user's experience, etc., the missed items can be reduced. That is, when the user (employee) inputs the occurrence situation, the score of the related cause data record becomes higher due to the reason that cannot be immediately noticed from the information input, so the possibility that the user perceives the previously undetected reason increases . In addition, the cross matching is also performed at the lower level (the level specifying the detailed items) in the same way as the vertical matching. Therefore, as described above, the weight is higher in the case of coincidence. Therefore, the score of the data record of the reason for the consistent cross-matching is relatively higher than the score of the data record of the reason for the inconsistent cross-matching, so the probability of being selected as the matching result becomes higher. In addition, when performing cross-matching, the weight of the item of the specific level can also be set to be lower than the weight of the input data record obtained by the user based on the actual input information. This is because the case of entering the name of the "drug" actually used is more reliable than the actual drug taken by the occupant. In this way, the matching processing execution unit 405 performs matching processing for each entry in the record according to the matching method determined by the matching method determination unit 404. As a result, the score of each of the cause data records in the cause database 460 is obtained. The matching result output unit 406 outputs a data record of the reason why the score meets the specific condition. For example, it can output the reason data record of the score exceeding a specific threshold, output the reason data record of the specific number in the order of the score, output the reason data record of the specific number of each category in the order of the score, output the set number of pieces, or It will not be output when the set score is not reached. The output unit 317 sends to the user terminal 220, for example, the contents of the second part 1002, 1052 included in the cause data record output by the matching result output unit 406, that is, it indicates an accident as "a viewpoint that should be controlled or a candidate for a cause" Information on various factors that occurred. In addition, the rules held in the matching rule holding unit 403 may also include the following rules: after the search is performed, if there is no next item, it is stipulated to end the search, or continue the search, or limit the search to a specific range, or skip and continue the search, etc. . In addition, when performing a search, it may also include rules that are consistent or partially consistent with the full text according to the item settings. In addition, it may also include a rule for changing the weight coefficient according to the category. In addition, the matching rule can also be a rule that refers to other information disclosed on the Internet, for example. For example, when entering the keyword Parkinson's disease, you can also search the web page to obtain the information of the corresponding therapeutic drug or new drug, and use the information to perform cross-matching. FIG. 13 is a diagram showing an example of a matching result screen 1300 displayed on the display unit 323 of the user terminal 120. Here, the information about the viewpoints and reasons that should be controlled is displayed in the order of the highest score. The user confirms the matching result screen 1300, and checks the most important items in the check box 1310. In addition, if the selection instruction of the OK button 1320 is input into the input unit 320, the checked content is sent to the service support system 210 through the communication unit 321. In the service support system 210, the checked content is determined as the data of the viewpoint or reason that should be controlled. In addition, the memory control unit 312 stores in the memory unit 313 the determined viewpoint or reason data that should be controlled. The data of the viewpoint or reason memorized in this way that should be controlled is read out by the memory control unit 312 and automatically set when the accident report is made. FIG. 14 shows an example of a search screen 1400 showing the viewpoint or reason that should be controlled finally. The search result screen 1400 of the viewpoint or reason is displayed on the display unit 323 of the user terminal 220. [Flowchart of User Terminal] FIG. 15 is a flowchart showing an example of a control method of the user terminal 220. In step S1505, the display control unit 324 displays the creation screen 500 of the accident report on the display unit 323 in accordance with the instruction input to the input unit 320. The user of the user terminal 220 inputs various values and information according to the creation screen 500. In step S1510, the communication unit 321 sends the information input to the input unit 320 to the service support system 210. Thereafter, the matching process is executed in the service support system 210. In step S1515, the display control unit 324 displays the matching result screen 1300 on the display unit 323 based on the information sent from the service support system 210. The user of the user terminal 220 confirms the content displayed on the matching result screen 1300, and selects what is deemed appropriate. In step S1520, the communication unit 321 transmits the selected item to the service support system 210 based on the selection instruction input to the input unit 320. In step S1525, the display control unit 324 displays a search result screen 1400 of opinions or reasons based on the information sent from the service support system 210. [Flowchart of Service Support System 210] FIG. 16 is a flowchart showing an example of the service support method of the service support system 210. In step S1650, the receiving unit 314 receives the information sent from the user terminal 220 through the communication unit 311. In step S1610, the matching unit 316 performs matching processing. The flow of matching processing is described below. In step S1615, the output unit 317 transmits the matching result to the user terminal 220 via the communication unit 311. In step S1620, the accepting unit 314 accepts the item selected in the user terminal 220 through the communication unit 311. In step S1625, the storage control unit 312 writes the data of the items accepted in step S1620 into the storage unit 313. In step S1630, the output unit 317 transmits information of the search result of the opinion or reason to the user terminal 220 through the communication unit 311 based on the matter accepted in step S1620. FIG. 17 is a flowchart showing an example of the detailed processing of the matching processing in step S1610. In step S1705, the keyword extracting unit 401 extracts keywords for the selected item based on the information input by the user in the creation screen 500 of the accident report, for example. In step S1710, the input data record obtaining unit 402 obtains the occurrence status data record corresponding to the keywords retrieved in step S1705 from the transmission status database 450 as an input data record. At this time, use the database corresponding to each accident type to obtain the input data record. Obtain input data records for each category. In addition, multiple input data records can also be obtained in each category. In step S1715, the matching method determination unit 404 refers to the matching rule held in the matching rule holding unit 403 to determine the matching rule to be applied to each input data record obtained in step S1710. For example, in addition to "horizontal matching", various matching rules such as "vertical matching" and "cross matching" can be determined. In step S1720, the matching processing execution unit 405 uses the input data records obtained in step S1610 to perform matching processing on the cause data records stored in the cause database 460 according to the matching rule determined in step S1615. At this time, the cause data record stored in the database corresponding to the accident type is matched. The matching processing execution unit 405 adds up the score accumulated in each cause data record based on the matching result. In step S1725, the matching result output unit 406 specifies a matching result based on the score obtained in step S1720. For example, it is determined that the record of the reason for exceeding a certain threshold is used as a candidate for the matching result. In step S1730, the matching result output unit 406 outputs the matching result specified in step S1725 to the output unit 317. Fig. 18 is a flowchart showing an example of the detailed processing of step S1720. In step S1805, the matching processing execution unit 405 selects unprocessed items in the input data record of the processing target. From the top-level items of the input data record of the processing object to the lower-level items, each item is processed. In step S1810, the matching processing execution unit 405 determines whether or not items of the next level can be selected in step S1805. If the next item can be selected, proceed to step S1815, if the next item cannot be selected, proceed to step S1835. In step S1815, the matching processing execution unit 405 determines whether the item to be processed is an item consistent with a specific rule. For example, it is determined whether it is a target item for vertical matching or cross matching. In the case of items that are consistent with the specific rule, the process proceeds to step S1820. In step S1820, the matching processing execution unit 405 executes processing in accordance with the specific rule. If it does not conform to the specific rule, proceed to step S1825. In step S1825, the matching processing execution unit 405 determines whether the keywords of the processing target item and the corresponding item of the cause data record are consistent. That is, the horizontal matching as described above is performed. In the case of coincidence, proceed to step S1830. In case of inconsistency, proceed to step S1832. In step S1830, the matching processing execution unit 405 adds the score corresponding to the weight of the item of the processing target and the score of the cause record of the processing target. Then, proceed to step S1832. In step S1832, the matching processing execution unit 405 determines whether to proceed to the next item. For example, when the matching results are inconsistent, there are situations where you do not want to advance to the next item, or there are only items from the structure of the processing target's cause record to the mid-level. In this case, if the item currently being processed is an Lv3 item, the process does not advance to the next item in step S1832, and the process advances to step S1835. In the case other than the above, the process returns to step S1805. In this way, matching processing is performed between each item in the input data record of the processing object and each item in the cause data record of the processing object. In step S1810, when it is determined that the next item cannot be selected, the process proceeds to step S1835. In step S1835, the matching processing execution unit 405 determines whether there is a cause data record for the next processing target. When there is a situation where the next reason data is recorded, proceed to step S1840. If there is no next cause data record, the processing of all the cause data records ends, so this process ends. In step S1840, the matching processing execution unit 405 updates the cause data record of the processing target. In step S1845, the matching processing execution unit 405 clears the processed item information in the input data record. That is, each item of the input data record is changed to the status of an unprocessed item. And return to step S1805. Thereby, for the reason data record of the processing target updated in step S1840, the horizontal matching of the top-level items is performed again from step S1805. Fig. 19 is a flowchart showing an example of the detailed processing of step S1820. In step S1905, the matching processing execution unit 405 determines whether the processing target item is the target of vertical matching. If it is the object of vertical matching, proceed to step S1910. In the case of non-vertical matching objects, proceed to step S1935. In step S1910, the matching processing execution unit 405 performs a search for items of a specific level specified by the matching rule. In step S1915, the matching processing execution unit 405 determines whether it is consistent with the keyword of the item of the specific level of the cause data record. In the case of coincidence, proceed to step S1920, and add the score corresponding to the weight of the item of the processing target of the input data record and the score accumulated in the coincidence cause data record. Then, proceed to step S1925. In step S1925, the matching processing execution unit 405 determines whether the cause data record of the processing object is the last cause data record of the processing object. That is, it is determined whether it is the final column in the row direction. In the case of the final list, proceed to step S1935. In the case of non-final list, proceed to step S1930, update the cause data record of the processing target, and return the processing to step S1910. In step S1935, the matching processing execution unit 405 determines whether the processing target item of the input data record is the target of cross matching. In the case of a cross-matching object, proceed to step S1940, and in the case of a non-cross-matching object, the process ends. In step S1940, the matching processing execution unit 405 adds the input data record in the state where the specific keyword specified by the matching rule is input to the target item specified by the matching rule, as an unprocessed input data record. In this way, horizontal matching is performed using the input data in the state where the specific keyword is input. The above is the description of the flow chart. So far, the case of a fall accident has been explained as an example. Below, in addition to fall accidents, specific examples of accidents and their factors that may occur in nursing facilities are explained. In addition to fall accidents, accidents that occur in nursing facilities include accidents of swallowing and suffocation (hereinafter referred to as "swallowing accidents"). In the case of a swallowing accident, in addition to the external factors such as the content of the diet at the time of the accident, the eating place, the assistance methods of the employees, and the participation of the employees, as the factors of the accident, the occupants’ dietary methods, physical and physiological factors, diseases, etc. Illnesses, symptoms, medications and other internal factors related to the occupant. In the case of a swallowing accident, the external factors such as the food form of the food, the presence or absence of the use of viscose, the time of eating, the place of eating, the use of tools, and the dentures are classified in detail. In addition, the method of assistance or participation for employees also includes collaboration with the kitchen, and detailed classification of how to respond before, during, and after eating. Regarding the occupants themselves, the food intake ability, eating posture, eating movements, nutritional status, appetite, will, oral care conditions, environmental changes, conditions different from usual, diseases, illnesses, symptoms, and medications taken Detailed classification of internal factors. In this way, by making the occurrence of the accident more detailed, it is possible to exactly match the reason associated with it or the viewpoint that should be controlled. As a specific example, the situation of residents suffering from Alzheimer’s disease is determined by "whether the food is recognizable, whether it is eaten at a clear taste or temperature", "whether it interferes with the diet of other residents, whether there are abnormal eating behaviors, and whether nothing is mixed." In addition, in the case of residents suffering from Parkinson's disease, the viewpoint of "whether the hand shakes and spills" is listed in the matching result screen 1300. Also, as other accidents in nursing facilities, there are drug accidents. In drug accidents, such as the doctor’s prescription, the dispensing and handover of the pharmacy, the drug management of the caregiver in the nursing facility, the medication assistance of the caregiver or nursing staff, etc., a series of operations until the occupant takes the drug becomes the cause of the drug accident . Therefore, it can be classified into external factors such as pharmacy factors, nursing staff factors, and nursing staff factors. In addition, each category can be further detailed. As the cause of the drug accident or the point of view that should be controlled, for example, the error of the pharmacy can be detailed into "dispensing error", "packing error", "typographical error", "prescription problem whereabouts error", etc. The caregiver's mistakes can be detailed into "receiving errors", "prescribing over-the-counter medicines", "mistaking people to put them", "mistaking counts, measuring and placing", "mistaking times when taking prescriptions", and "mistaking prescription days to put them" , "Wrong way of taking it", "Forget to give", etc. The mistakes of the nursing staff can be detailed into, for example, “take the wrong medicine”, “take the wrong person”, “take the wrong time to take”, “take the wrong count, take the meter,” “take the wrong way to take”, and “take the wrong medicine”. Unable to take" and so on. The reason why each occurrence becomes the object or the viewpoint to be controlled is listed in the matching result screen 1300. In the embodiments described so far, accidents that may occur in facilities have been described as examples, but they are not limited to this, and can be applied to various cases. As an example of a case, it can also be applied to accidents including accidents and potential accidents. In other words, it can be applied not only to the scene of making an accident report, but also to making the report when a potential accident occurs in daily business. Also, it can also be applied to other business cases besides accidents. Enumerate, for example, a care plan. In order to derive the form of the best care plan candidates based on the evaluation results of each occupant. As an implementation method of this application example, each evaluation item is classified, systemized (structured, hierarchical), and databased. Cases of categorized care plans are merged, systemized (structured, hierarchical) and databaseized. In addition to the case of the care plan of each evaluation item, it also envisages cases that cross the classification, such as the above-mentioned fall accident, and can also maintain any matching rules for vertical matching or cross matching. As an example of the classification of both assessment and care plans, include "diet, water", "oral care", "bathing", "facelift", "excretion", "movement, migration, body function", "sleep", " Interests, activities", "memory, cognition", "spirit, action", "health management, medical care", "other life" and other life scenes or the ability, will, and characteristics of the residents. Based on the assessment of the residents based on this classification, the best care plan can be made, so that specific and appropriate life support can be comprehensively considered and judged for each resident’s ability, will, and characteristics. In addition, as a case, it is not only a case that has a problem or a possible problem, but also a case that has an improvement or a possible improvement. For example, in nursing facilities, when there are certain circumstances (such as decorating flowers, changing the walking path, greeting differently from usual, etc.), there are certain improvements (for example, the occupant's mood becomes better, such as humming casually, More than usual). In this way, not only cases where problems or problems may occur, but also cases where improvements or improvements may occur, the constitution and processing described in the above embodiments can also be applied. In addition, so far, the description has mainly taken the form used in nursing facilities as an example, but it is not limited to this. For example, in medical providing facilities, there are cases where the same kind of accident may occur, and the above-mentioned service support system 210 can also be used in the medical providing facilities. In addition, the service provider does not necessarily need to be an elderly person or a patient. For example, it can also be applied to kindergartens or children's clubs that use children as the service provider. In addition, for cases that may occur in various scenarios such as schools and workplaces, the service support system 210 described in the above embodiment can also be applied. For the systematization, structuring, and hierarchization of the above-mentioned various materials, tags can also be attached to the materials to give meaning. Incorporating into various rules to install a system equipped with artificial intelligence functions, not only the limited database is used as the matching object, but also the more web pages on the Internet are used as the information source, so as to realize the diversity and matching of matching processing. Speed up. For example, based on the information displayed on the matching result screen 1300 and the information of the item selected by the user through the matching result screen 1300, the matching rule held in the matching rule holding unit 403 is appropriately changed. For example, a plurality of pieces of information displayed on the matching result screen 1300 and information about the items selected by the user through the matching result screen 1300 can also be collected in advance, and the weighting coefficient can be optimized using the information. In addition, the database can also be reconstructed based on the information of the items selected by the user through the matching result screen 1300. For example, the content displayed on the user terminal 220 in the matching result screen 1300 and the items selected by the user through the matching result screen 1300 can also be used as teacher data to construct a learning mode. In addition, it is also possible to adopt a configuration that uses the constructed learning pattern as a matching unit and outputs the matching result. The learning model can be constructed according to each service provider, or it can be grouped according to specific conditions, and the learning model can be constructed according to each group. [Variation example] In addition, in the example described so far, a mode in which the user performs the matching process by inputting the accident report as shown in FIG. 5 has been described as an example, but it is not limited to this. For example, the service support system 210 can also automatically retrieve data at a specific point in time, and perform matching processing based on the retrieved data. According to this processing, for example, when an accident occurs due to body changes, etc., a warning can also be output. Take the occupants of nursing facilities as an example. At the scene of the nursing facility, employees are always alert to the changes or dangers of the occupants and seek appropriate responses. However, when employees provide daily care services under the shift system, there are often changes in the status of the occupants or the dangers are not noticed. The reason is that only a certain abnormal state cannot be immediately specified. For example, when the intake of food or water is lower than a certain amount for a certain number of times, when there is no excretion for a certain period of time, when necessary vital signs such as body temperature, pulse, blood pressure, and weight deviate from the specified range for a certain period of time Etc., when the condition that is different from the usual condition continues, the condition of the occupant may change or be dangerous. The above-mentioned embodiment can also be applied to this attention-raising form. Take the situation of weight change as an example to illustrate the types of cases. Data such as the weight of the occupant is stored in the memory unit 313 and so on. Therefore, the receiving unit 314 can access the data accumulated in the memory unit 313 and the like at a specific point in time, and input the accumulated data as the occurrence status. And, the input data is sent to the matching unit 316. In this way, the matching process can also be performed automatically at a specific point in time. The reason database 460 may also include a record of items related to the passage of the time series. For example, when the specific reference day is set as the value of the Lv1 level (weight), the value of the Lv2 level can also be stored as the reason data record of the allowable value (weight) on the day following the reference day. In addition, the matching unit 316 performs matching processing using the input data record configured with the accumulated weight data as time-series items. In this example of processing, in the level after Lv2, when the item (allowable value (weight)) in the cause data record is inconsistent, the method of increasing the score can be used. That is, when the items in the input data record of the level after Lv2 are consistent with the items in the cause data record of the level after Lv2 (ie, the value within the allowable range), the matching process is ended, and the situation of inconsistency (ie, non-allowable range) In the case of the value of ), the method of adding a score can also be used. If this kind of processing is performed, it should be noted that the value of the body change included in the item's cause data record (for example, the cause data record corresponding to the daily weight loss) has a higher score, and the output from the matching unit 316 is created and the cause data record is created The reason for the association (for example, attention due to possible illness, etc.). The output unit 317 may also send the matching result output from the matching unit 316 to the user terminal 220 to urge the user to warn. As explained above, according to this embodiment, it is possible to derive the cause of the accident or candidates for the viewpoint that should be controlled based on the occurrence of various accidents in the facility, and to support the analysis, response, and preventive measures of the accident. In addition, the data records of the occurrence database 450 and the cause database 460 can be easily added and changed. Therefore, it is easier to maintain the situation where a new item needs to be set. In addition, according to this embodiment, even if employees with high professional knowledge or less experience value, as long as they faithfully and correctly select the accident status from the options, the list can be displayed to ensure accuracy and comprehensiveness above a certain level. The cause of the accident or the alternate point of view that should be controlled. Therefore, the investigation time of various professional books and other materials can be reduced, and the cooperation of relevant departments can be effectively implemented based on the contents listed. In addition, according to this embodiment, it is possible to prevent the real cause such as the fact that the employee who neglects the facility does not notice. In addition, it is possible to remind employees and other users of the causes, factors, risk factors, and precautions corresponding to the occurrence of the accident from various perspectives. The embodiments described above are for easy understanding of the present invention, and are not for limiting interpretation of the present invention. The various elements provided in the embodiment and their arrangement, materials, conditions, shapes, dimensions, etc. are not limited to the examples, and can be changed as appropriate. In addition, it is possible to partially replace or combine the configurations shown in the different embodiments. The programs used to implement the embodiments of the present invention described above can also be stored in the recording medium. If the recording medium is used, the above program can be installed on any computer that has been used for other purposes in the facility or a re-purchased computer. Here, the recording medium storing the above-mentioned program may also be a non-temporary storage medium. The non-transitory storage medium is not particularly limited, and may be, for example, a storage medium such as CD-ROM.

210‧‧‧Service support system 220‧‧‧user terminal 220a‧‧‧user terminal 220b‧‧‧user terminal 311‧‧‧communication unit 312‧‧‧memory control unit 313‧‧‧memory unit 314‧‧‧receiving unit 315‧‧‧Database 316‧‧‧Matching unit 317‧‧‧Output unit 320‧‧‧Input unit 321‧‧‧Communication unit 323‧‧‧Display unit 324‧‧‧Display control unit 325‧‧‧Memory unit 326 ‧‧‧Memory Control Unit 401‧‧‧Keyword Extraction Unit 402‧‧‧Input Data Record Acquisition Unit 403‧‧‧Matching Rule Holding Unit 404‧‧‧Matching Method Decision Unit 405‧‧‧Matching Process Execution Unit 406‧ ‧‧Matching result output unit 450‧‧‧Occurrence status database 451‧‧‧Fall accident occurrence status database 452‧‧‧Swallowing and suffocation accident occurrence status database 453‧‧‧Pharmaceutical accident occurrence status database 460‧‧ ‧Cause database 461‧‧‧Fall accident cause database 462‧‧‧Swallowing, suffocation accident cause database 463‧‧‧Pharmaceutical accident cause database 465‧‧‧Fall accident database 500‧‧‧Fall accident report Book 501～504‧‧‧Input area 601～603‧‧‧Input area 610‧‧‧Occurrence data record group 620‧‧‧Occurrence data record group 630‧‧‧Occurrence data record group 611‧‧‧Data record 621‧‧‧Data record 622‧‧‧Data record 631‧‧‧Data record 632‧‧‧Data record 633‧‧‧Data record 701‧‧‧Input area 703‧‧‧Input area 710‧‧‧Data record group 711 ‧‧‧Data record 712‧‧‧Data record 713‧‧‧Data record 721‧‧‧Form 722‧‧‧Form 730‧‧‧Data record group 801‧‧‧Item 802‧‧‧Item 951‧‧‧Item 955 Project 956. Input data record 1151‧‧‧Cause data record 1152‧‧‧Cause data record 1153‧‧The next cause data record 1300‧‧‧Match result screen 1310‧‧‧Check box 1320‧‧‧OK button 1400‧‧‧ Search screen S1505, S1510, S1515, S1520, S1525, S1605, S1610, S1620, S1625, S1630, S1710, S1715, S1720, S1725, S1730, S1805, S1810, S1815, S1820, S1825, S1830, S1832, S1835, S1840 S1845, S1905, S1910, S1915, S1920, S1925, S1930, S19 35、S1940‧‧‧Step

Figure 1 is a diagram schematically showing an example of the factors of a fall accident in a nursing facility. Fig. 2 is a diagram showing an example of the usage form. FIG. 3 is a block diagram showing an example of the structure of the service support system and the structure of the user terminal. Fig. 4 is a diagram showing an example of the detailed structure of the database unit and the matching unit. Figure 5 is a diagram showing an example of a screen for making an accident report of a fall accident. Fig. 6 is a diagram showing an input area and a group of occurrence data records corresponding to the input area. Fig. 7 is a diagram showing the input area and the occurrence status data record group corresponding to the input area. Figure 8 is a diagram showing an example of an input data record regarding external factors. Fig. 9 is a diagram showing an example of an input data record regarding internal factors. Figure 10 (a) and (b) are diagrams schematically showing examples of cause data records. Fig. 11 is a schematic diagram for explaining the matching process. Figure 12 is a diagram for explaining vertical matching and cross matching. Fig. 13 is a diagram showing an example of a matching result screen. Fig. 14 is a diagram showing an example of the analysis result screen. Fig. 15 is a flowchart showing an example of a control method of a user terminal. FIG. 16 is a flowchart showing an example of the service support method of the service support system. Fig. 17 is a flowchart showing an example of matching processing. Fig. 18 is a flowchart showing an example of detailed processing of matching processing. Fig. 19 is a flowchart showing an example of processing according to specific rules.

315‧‧‧Database

316‧‧‧Matching Department

401‧‧‧Keyword Extraction Department

402‧‧‧Input data record acquisition department

403‧‧‧Matching rule holding part

404‧‧‧Matching Method Decision Division

405‧‧‧Matching processing execution unit

406‧‧‧Matching result output unit

450‧‧‧Occurrence database

451‧‧‧Fall accident situation database

452‧‧‧Database of accidents of swallowing and suffocation

453‧‧‧Pharmaceutical Incident Status Database

460‧‧‧Cause Database

461‧‧‧Fall accident cause database

462‧‧‧Database of causes of accidental swallowing and suffocation

463‧‧‧ Drug Accident Cause Database

465‧‧‧Database of Common Causes of Accidents

Claims (12)

A service support system with: a reason database, which is stored according to the type of each case: for each state of affairs related to the occurrence of the case, a data group that associates the cause of each state with each factor being considered; the acceptance department, It accepts input including the type of case that occurred and the occurrence status of the above-mentioned case; the matching department, based on the type of case accepted by the above-mentioned acceptance department, specifies the type of the corresponding case stored in the above-mentioned reason database, and the above-mentioned The input information of the occurrence status accepted by the acceptance unit is matched with the data group stored in the type of the specified case, and scores for various factors in the data group extracted by the above matching are calculated; and the output unit, Based on the scores of various factors calculated in the above-mentioned matching unit, it outputs more than one of the various factors as the cause of the occurrence of the case. For example, the service support system of claim 1, wherein the above matching unit is based on the comparison of various factors in the data group stored in the data group of the above-mentioned specific case with each occurrence of the above-mentioned acceptance As a result, the scores of various factors are cumulatively added, and the output unit outputs the above-mentioned reasons associated with the above-mentioned data whose accumulated scores exceed a specific threshold. For example, the service support system of claim 1 or 2, which further has: an occurrence database, which stores, according to the type of each of the above-mentioned cases, a plurality of occurrence data records after the occurrence of each situation related to the occurrence of the case is hierarchized; and The acquisition department, which obtains the occurrence status data record corresponding to the above-mentioned accepted case type and occurrence status from the above occurrence status database as the input data record. The above reason database storage includes the same hierarchical data as the above input data record. The reason data record of the data structure, as the data contained in the above data group, the above matching part makes the keywords contained in the specified level of the input data record obtained above, and the above specific keywords contained in each cause data record stored in the above reason database Match the keywords contained in the hierarchy. For example, in the service support system of claim 3, the matching unit includes: a holding unit that maintains matching rules; and a determination unit that refers to the matching rules to determine a matching method. For example, in the service support system of request 4, the above-mentioned matching rule includes the following rule: use the keywords of the above-mentioned specific level in the above-mentioned input data record to match the predetermined level in each cause data record. For example, in the service support system of request 4, the above-mentioned matching rules include the following rules: when the item of the processing object of the above-mentioned input data record is an item of a specific level, the input data record of the occurrence status of the selected item is retrieved. For example, in the service support system of request 5, the above-mentioned matching rules include the following rules: when the item of the processing object of the above-mentioned input data record is an item of a specific level, the input data record of the occurrence status of the selected item is retrieved. For example, in the service support system of claim 6, wherein the accepting unit can further accept the reasons selected by the user among the reasons output by the output unit, and the matching rules are changed based on the reasons output by the output unit and the reasons selected by the user. For example, in the service support system of claim 7, wherein the accepting unit can further accept the reasons selected by the user among the reasons output by the output unit, and the matching rules are changed based on the reasons output by the output unit and the reasons selected by the user. For example, in the service support system of claim 1 or 2, where the above-mentioned state of affairs includes items related to the transition of data in time series, the above-mentioned acceptance unit is: input the accumulated data related to the service provider as the above-mentioned occurrence situation, and the above-mentioned matching unit makes the above-mentioned accumulation The data is matched with the items related to the data transition of the above time series. A method of service support, which includes the following steps: by a processor, in the cause database, storing according to the type of each case: for each state of affairs related to the occurrence of the case, the cause of each state of affairs is associated with each factor being considered Data group; through the above-mentioned processor, accept the types of cases that occurred and the occurrence status of the above-mentioned cases Input of the situation; by the above processor, according to the type of the accepted case, the type of the corresponding case stored in the database for the above reason is specified, and the input information of the occurrence situation of the above acceptance is combined with the specified case in the above The data group stored in the type of data group is matched, and the scores of the various factors in the data group extracted by the above-mentioned matching are calculated; and the various factors are calculated by the above-mentioned processor according to the scores of the various factors calculated above More than one of them is output as the cause of the occurrence of the case. A program for service support that causes the computer to perform the following steps: Store in the cause database according to the type of each case: For each state of affairs related to the occurrence of the case, associate the cause of each state with the factors being considered Data group; accept input including the type of case that occurred and the occurrence status of the above-mentioned case; according to the type of the above-mentioned accepted case, specify the type of the corresponding case stored in the database for the above-mentioned reason, and the occurrence status of the above-mentioned acceptance The input information is matched with the data group stored in the type of the above specified case, and the scores for the various factors in the data group extracted by the above matching are calculated; and the scores for the various factors calculated according to the above calculation, Output more than one of various factors as the cause of the occurrence of the case.

Images