Interview record input support device, interview record input support method and program

Abstract

The present invention provides an interview record input support device that streamlines the input of records related to interviews by including a selection unit configured to accept a selection of one or more of elements carried out in relation to a certain interview from among a plurality of elements constituting a process of dialogue between an interviewer and an interviewee, and a registration unit configured to: accept a record related to the certain interview for an item associated with any of the selected elements from among a plurality of items serving as candidates to be recorded in relation to an interview in order to review the interview; and register the record in a storage unit.

Description

[Technical Field]

[0001] The present invention relates to an interview record input support device, an interview record input support method, and a program. [Background technology]

[0002] It is important to support behavioral change so that people who need to improve their behavior, such as those who need to prevent lifestyle-related diseases, can take the initiative to do so.

[0003] Therefore, in specific health guidance, interviews are conducted by professionals (public health nurses, registered dietitians, etc.) to promote behavioral change.

[0004] When recording health guidance interviews, there is a system in place that allows the interviewer to reflect on the interview by registering the health challenges and action plans of the interviewee (the person receiving support for behavioral change). [Prior art documents] [Non-patent literature]

[0005] [Non-Patent Document 1] Kana Kazawa, Naoko Takeyama, Madoka Kawai, Keiko Umeki, Tokika Masaki, Ayako Tsunoi, Kanko Hosokawa, Michiko Moriyama, Shunichi Kurino, Noriaki Yoshikai, "Development of a Health Guidance Questionnaire and Intervention Support System to Support Behavioral Change and Self-Management Improvement in Patients with Chronic Diseases: Interim Report," Proceedings of the 20th Annual Meeting of the Japan Society for Medical Informatics and Nursing Science (2187-1469), Pages 103-106 (September 2019) Summary of the Invention [Problem to be solved by the invention]

[0006] Conventional systems require users to enter all items that are candidates for recording for an interview one by one, making it time-consuming to create interview records.

[0007] The present invention has been made in consideration of the above points, and aims to improve the efficiency of inputting interview records. [Means for solving the problem]

[0008] In order to solve the above problem, the interview record input support device has a selection unit configured to accept the selection of one or more elements that were performed in a certain interview from among a plurality of elements that make up the process of dialogue between the interviewer and the interviewee, and a registration unit configured to accept a record of the certain interview for an item associated with any of the selected elements from among a plurality of items that are candidates for recording in relation to the interview in order to look back on the interview, and to register the record in a memory unit. [Effects of the Invention]

[0009] It is possible to efficiently input interview records. [Brief explanation of the drawings]

[0010] [Figure 1] 1 is a diagram illustrating an example of the hardware configuration of an interview record input support device 10 according to an embodiment of the present invention. [Figure 2] 1 is a diagram illustrating an example of a functional configuration of an interview record input support device 10 according to an embodiment of the present invention. [Figure 3] 10 is a flowchart illustrating an example of a processing procedure executed by an executed dialogue process management unit 11. [Figure 4] FIG. 10 is a diagram showing an example of the configuration of a common dialogue process model DB 121. [Figure 5] FIG. 10 is a diagram showing a display example in which Level 1 interactive process elements are displayed. [Figure 6] FIG. 10 is a diagram showing a display example in which Level 2 interactive process elements are displayed. [Figure 7] FIG. 10 is a diagram showing an example of the configuration of an interactive process execution record DB 122. [Figure 8]10 is a flowchart illustrating an example of a processing procedure executed by an interview content registration unit 12. [Figure 9] 10 is a diagram showing an example of the configuration of an acquired data item ID attribute table 123-1 that constitutes the interview manual record item DB 123. FIG. [Figure 10] 10 is a diagram showing an example of a tree structure 123-2 constituting an interview manual record item DB 123. FIG. [Figure 11] FIG. 10 is a diagram showing a first display example of an individual interview record input screen. [Figure 12] A figure showing a second display example of the individual interview record input screen. [Figure 13] FIG. 10 is a diagram showing an example of the configuration of an individual interview manual record DB 124. [Figure 14] 10 is a flowchart illustrating an example of a processing procedure executed by a reason input candidate management unit 13. [Figure 15] FIG. 10 is a diagram showing an example of the configuration of a reason recording information recording table 125-1. [Figure 16] FIG. 10 is a diagram illustrating an example of calculation of parental reason candidate scores. [Figure 17] 10 is a diagram showing an example of the configuration of a reason reference destination candidate ID management table 125-2. FIG. [Figure 18] FIG. 10 is a diagram showing a display example of a visualization screen 550. [Figure 19] 10 is a flowchart illustrating an example of a processing procedure executed by an interview case visualization unit 14. [Figure 20] FIG. 10 is a diagram illustrating an example of the configuration of a visualization definition DB 126. DETAILED DESCRIPTION OF THE INVENTION

[0011] An embodiment of the present invention will be described below with reference to the drawings. Figure 1 is a diagram showing an example of the hardware configuration of an interview record input support device 10 in an embodiment of the present invention. The interview record input support device 10 in Figure 1 has a drive device 100, an auxiliary storage device 102, a memory device 103, a CPU 104, an interface device 105, a display device 106, and an input device 107, which are all interconnected by a bus B.

[0012] The program that realizes the processing in the interview record input support device 10 is provided by a recording medium 101 such as a CD-ROM. When the recording medium 101 storing the program is set in the drive device 100, the program is installed from the recording medium 101 to the auxiliary storage device 102 via the drive device 100. However, the program does not necessarily have to be installed from the recording medium 101, but may be downloaded from another computer via a network. The auxiliary storage device 102 stores the installed program as well as necessary files, data, etc.

[0013] The memory device 103 reads and stores the program from the auxiliary storage device 102 when an instruction to start the program is received. The CPU 104 realizes the functions related to the interview record input support device 10 in accordance with the program stored in the memory device 103. The interface device 105 is used as an interface for connecting to a network. The display device 106 displays a GUI (Graphical User Interface) or the like according to the program. The input device 107 is composed of a keyboard, mouse, etc., and is used to input various operational instructions.

[0014] It should be noted that the interview record input support device 10 does not have to have the display device 106 and the input device 107. In this case, for example, a terminal connected to the interview record input support device 10 via a network may function as the display device 106 and the input device 107. Examples of such terminals include a PC (Personal Computer), a smartphone, or a tablet terminal.

[0015] FIG. 2 is a diagram illustrating an example of the functional configuration of an interview record input support device 10 according to an embodiment of the present invention. In FIG. 2, the interview record input support device 10 includes an executed dialogue process management unit 11, an interview content registration unit 12, a reason input candidate management unit 13, and an interview case visualization unit 14. These units are implemented by the CPU 104 executing one or more programs installed in the interview record input support device 10. The interview record input support device 10 also utilizes databases (storage units), such as a common dialogue process model DB 121, a dialogue process execution record DB 122, an interview manual record item DB 123, an individual interview manual record DB 124, a reason input candidate management DB 125, and a visualization definition DB 126. Each of these databases can be implemented using, for example, an auxiliary storage device 102 or a storage device connectable to the interview record input support device 10 via a network.

[0016] The processing procedure executed by the interview record input support device 10 will be described below.

[0017] [Implemented Dialogue Process Management Section 11] Fig. 3 is a flowchart for explaining an example of the processing procedure executed by the completed dialogue process management unit 11. The processing procedure in Fig. 3 is executed to register information about a certain interview (hereinafter referred to as a "target interview") after an interviewer (such as a public health nurse) has conducted an interview with an interviewee (hereinafter referred to as a "target person") or the like. An example of a target person is a person receiving support for behavioral change.

[0018] In step S101, the executed dialogue process management unit 11 displays a screen showing dialogue process information registered in the common dialogue process model DB 121 on the display device 106 in response to a dialogue process display request from a user (interviewee).

[0019] Information (dialogue process information) relating to the elements that make up the dialogue exchange or process (hereinafter referred to as the "dialogue process") between an interviewer (such as a public health nurse) and an interviewee (hereinafter simply referred to as the "subject") in a single interview is registered in advance in the common dialogue process model DB 121. In other words, the dialogue process information stored in the common dialogue process model DB 121 is not a DB that stores information about specific interviews that have been conducted individually, but rather refers to information about a typical or general configuration of the dialogue process in an interview.

[0020] Fig. 4 is a diagram showing an example of the configuration of the common dialogue process model DB 121. As shown in Fig. 4, the common dialogue process model DB 121 stores in advance, for each element (a step or unit into which the dialogue process in one interview is divided according to its role; hereinafter referred to as a "dialogue process element") that can constitute a dialogue process, an element ID, an element name, a display statement, hierarchical information, parent information, other element link information, an acquired data item ID associated with the element, etc.

[0021] The element ID is identification information of the dialogue process element. The element name is a name given to the dialogue process element. The element display sentence is a character string for display that represents the dialogue process element. The hierarchical information is information that expresses the level in the hierarchical relationship (parent-child relationship) between dialogue process elements in the format of "Lv.N." Here, N is a number indicating the level from the highest in the hierarchical relationship (parent-child relationship). The parent information is the element ID of the dialogue process element that is the parent in the hierarchical relationship between dialogue process elements. The other element link information is information that indicates the element ID of the dialogue process element that is next in the temporal order relationship (front-to-back relationship) between dialogue process elements. If the order relationship of the dialogue process element based on the other element link information at Level N spans multiple dialogue process elements at Level N-1 (i.e., the parent level), there will be a temporal order relationship between the multiple dialogue process elements at Level N-1. The order of dialogue process elements with no such order relationship and whose hierarchical information is "Level 1" follows the order of records in the common dialogue process model DB 121. The acquired data item ID associated with an element is the acquired data item ID associated with (related to) the dialogue process element. The meaning of the acquired data item ID will be described later.

[0022] The executed dialogue process management unit 11 may initially limit the dialogue process information to be displayed based on the hierarchical information, thereby preventing the contents of the displayed screen from becoming too complicated.

[0023] Fig. 5 is a diagram showing a display example when Level 1 dialogue process elements are the display targets. In Fig. 5, each rectangle corresponds to a Level 1 dialogue process element, and includes a "dialogue process display statement" for the corresponding dialogue process element stored in the common dialogue process model DB 121 (Fig. 4). Arrows connecting the rectangles indicate the chronological order relationship between the dialogue process elements.

[0024] Each rectangle includes a button for expanding the corresponding dialogue process element. For example, when the button b1 corresponding to the dialogue process element with the element ID "10" is pressed, the executed dialogue process management unit 11 displays the child elements (dialogue process elements of Level 2) of the dialogue process element.

[0025] 6 is a diagram showing a display example when the display target is an interaction process element of Level 2. In FIG. 6, the anteroposterior relationship between child elements in an interaction process element with an element ID of "10" is shown.

[0026] The user selects the dialogue process elements that were implemented in the target interview from the dialogue process elements displayed on the screen. At this time, the dialogue process elements are selected in the order in which they were implemented. Alternatively, the implemented dialogue process elements do not have to be selected in the order in which they were implemented. In this case, the implemented dialogue process management unit 11 may display a list of the selected dialogue process elements (i.e., a list of the dialogue process elements implemented by the user), and the selected dialogue process elements may be arranged in the order in which they were implemented in the list by operations such as drag and drop.

[0027] That is, since the dialogue process elements that can constitute a dialogue process are identified and registered in the common dialogue process model DB 121, not all dialogue process elements are necessarily implemented in every interview. Therefore, in this case, a selection of dialogue process elements is accepted from the user in order to narrow down the dialogue process elements that are implemented.

[0028] When the selection of the dialogue process element is accepted from the user, the executed dialogue process management unit 11 registers information about the dialogue process element executed by the user for the target interview in the dialogue process execution record DB 122 based on the selection result by the user (S102).

[0029] Fig. 7 is a diagram showing an example of the configuration of the dialogue process execution record DB 122. As shown in Fig. 7, the dialogue process execution record DB 122 stores records including an interview ID, an interviewer ID, a target person ID, an executed dialogue process ID, an execution order, etc. for each dialogue process element executed in each interview that was held in the past.

[0030] The interview ID is identification information for the interview. The interviewer ID is identification information for the person who conducted the interview (interviewer). The target ID is identification information for the target of the interview. The implemented dialogue process element ID is the dialogue process element ID of the dialogue process element implemented in the interview. The implementation order is the order in which the dialogue process elements were implemented in the interview.

[0031] The interview ID, interviewer ID, and target person ID are input by the user, for example, at the start of the processing procedure in Fig. 3. The completed dialogue process ID and the execution order are identified by the completed dialogue process management unit 11 based on operations on the screens in Fig. 5 and Fig. 6.

[0032] [Interview Content Registration Section 12] When the processing procedure of Fig. 3 is completed for the target interview, the processing procedure of Fig. 8 is executed subsequently. However, the processing procedure of Fig. 8 may be executed for the target interview without executing the processing procedure of Fig. 3.

[0033] 8 is a flowchart for explaining an example of the processing procedure executed by the interview content registration unit 12. The processing procedure in FIG. 8 is executed so that the user (interviewer) can register interview information for reviewing the interview ((1) information on understanding the subject, (2) information on the intervention, and (3) information on the reason for the intervention) in the interview record input support device 10.

[0034] In step S201, the interview content registration unit 12 receives a request from the user to display a registration screen. At this time, the user inputs the interview ID of the target interview (hereinafter referred to as the "target interview ID") and a value indicating the acquisition timing (hereinafter referred to as the "target acquisition timing") (for example, "after the interview"). The acquisition timing will be described later.

[0035] Next, the interview content registration unit 12 checks whether or not a record of the target interview (that is, a record including the target interview ID as the "interview ID") is registered in the dialogue process implementation record DB 122 (S202).

[0036] If the record of the target interview is registered in the dialogue process implementation record DB 122 (FIG. 7) (Yes in S203), the interview content registration unit 12 acquires, for each record, an "acquired data item ID associated with an element" that is associated in the common dialogue process model DB 121 (FIG. 4) with the "executed dialogue process element ID" (S204). As a result, the acquired data item IDs that may have been implemented in the target interview are narrowed down based on the dialogue process elements. For example, if the target interview ID is "dialogue1," the "executed dialogue process element IDs" of each record of the target interview ID in the dialogue process implementation record DB 122 (FIG. 7) are 10, U100, BA100, U103, and 20. The interview content registration unit 12 acquires, for these dialogue process element IDs, the "acquired data item ID associated with an element" that is stored in the common dialogue process model DB 121 (FIG. 4). In this case, the acquired data item IDs such as 2-2-1, . . ., 3-1-2-1, 3-1-2-2, . . ., 2-2-2, etc. are acquired.

[0037] On the other hand, if the record of the target interview is not registered in the dialogue process implementation record DB 122 (Figure 7) (No in S203), the interview content registration unit 12 acquires all acquired data item IDs at the top level of the interview manual record item DB 123 (S205).

[0038] The interview manual record item DB123 is a database in which information specifying candidate items to be recorded for the interviewer to review each interview (e.g., "What was this subject's blood sugar level?", "What were their personality traits?", etc.) is pre-registered. In this embodiment, the candidate items to be recorded (hereinafter referred to as "candidate record items") are broadly divided into items related to understanding the subject and items related to intervention. Understanding the subject refers to the interviewer grasping (understanding) the subject's situation, etc. during the interview. Intervention refers to any general approach (questions, explanations, etc.) that the interviewer makes to the subject during the interview. For example, after listening to (understanding) the subject's lifestyle habits, saying, "Your rice is high in carbohydrates, why don't you try reducing the amount of rice you eat" corresponds to intervention. In addition, greetings made by the interviewer during the interview to build a good relationship with the subject also fall under intervention. In this embodiment, it is assumed that the reason for the interviewer's intervention will also be recorded. For example, for an intervention such as "Explanation about lifestyle-related diseases" the reason recorded might be, "Because subject A had absolutely no knowledge of health." This is based on the premise that there is value in learning how to intervene in a way that is suited to the subject's characteristics when reviewing the interview.

[0039] The interview manual record item DB123 also stores not only the candidate record items themselves, but also information regarding the categories that classify the candidate record items to make it easier to input values ​​for the candidate record items (for example, information indicating that blood glucose levels are one of the biological aspects).

[0040] In this embodiment, these "record candidate items" and "categories" are collectively referred to as "acquired data items," and the identification information of an acquired data item is referred to as an "acquired data item ID." A "record candidate item" belongs (is classified) to one of the "categories," and a "category" can belong to a higher-level (parent) "category." In other words, categories have a hierarchical relationship (parent-child relationship). Therefore, a group of acquired data item IDs form a hierarchical relationship (parent-child relationship). The interview manual record item DB 123 stores tree structure information (hereinafter referred to as "tree structure 123-2") that represents this hierarchical relationship, and a table (hereinafter referred to as "acquired data item ID attribute table 123-1") in which attribute information for each acquired data item ID ("record candidate item" or "category") is registered.

[0041] Figure 9 is a diagram showing an example of the configuration of the acquired data item ID attribute table 123-1 that constitutes the interview manual record item DB 123. As shown in Figure 9, the acquired data item ID attribute table 123-1 pre-registers, for each acquired data item ID, the acquired data item name, answer acquisition node flag, reason input flag, reason reference ID, answer method, acquisition necessity, acquisition timing, and options 1 to 3.

[0042] The acquired data item name is the name of the acquired data item ID and is mainly used for display. The answer acquisition node flag is an item that indicates whether or not the item is one for which a value is entered by the user (i.e., whether or not it is a record candidate item). "1" indicates that it is a record candidate item, and "0" indicates that it is a category.

[0043] The reason input flag indicates whether or not a reason (why the record indicates that something was done) needs to be input for the record for the acquired data item ID. "1" indicates that a reason needs to be input, and "0" indicates that a reason does not need to be input. In this embodiment, acquired data item IDs are broadly divided into those related to subject understanding and those related to intervention, and it is the acquired data item ID related to intervention that requires the input of a reason. In the case of intervention, it is important to record why such intervention was performed for reviewing the interview. Therefore, the reason input flag of an acquired data item ID related to intervention that is also a record candidate item is "1", and the reason input flag of an acquired data item ID that is not related to intervention is "0". The reason reference ID is an item in which acquired data item IDs that are candidate reasons for an acquired data item ID with a reason input flag of "1" are registered. In other words, in this embodiment, the reason for an acquired data item ID related to intervention (record candidate item) is selected from records for other acquired data item IDs. The acquired data item ID that can be a reason is an acquired data item ID related to subject understanding. Because understanding the subject gives rise to intervention, understanding the subject provides a reason for intervention, i.e., there is a causal relationship between subject understanding and intervention.

[0044] The acquisition requirement is an item that indicates whether or not recording by the user is required. "1" indicates that the user must enter a value, and "0" indicates that it is not required. Therefore, an acquisition data item ID with an acquisition requirement of "1" indicates that it is a candidate item to be recorded, and an acquisition data item ID with an acquisition requirement of "0" indicates that it is a category. This is because categories simply categorize candidate items to be recorded, and are not the subject of recording.

[0045] The acquisition timing is an item that indicates the timing at which recording is performed (when the interview content registration unit 12 accepts the recording). Since the recording target is a candidate recording item, the acquisition timing is also an item that is valid for the candidate recording item. An acquisition data item ID with an acquisition timing of "after the interview" indicates that the candidate recording item is to be recorded after the interview ends.

[0046] Options 1 to 3 are valid items for the record candidate item, and indicate the options (candidates) of the value to be recorded for the record candidate item. An acquisition data item ID corresponding to a record candidate item and for which no options are registered indicates that the content of the record is free format. Note that the upper limit of options does not have to be three.

[0047] Figure 10 is a diagram showing an example of a tree structure 123-2 constituting the interview manual record item DB 123. In Figure 10, each node represented by a circle corresponds to one acquired data item ID, and the parent-child relationship of the nodes indicates the parent-child relationship between the acquired data item IDs. The terminal nodes of the circle nodes correspond to candidate record items, and the node nodes correspond to categories. Hereinafter, the terminal nodes of the circle nodes are also referred to as "leaf nodes."

[0048] The rounded rectangular nodes that are child nodes of leaf nodes are not nodes that correspond to the acquired data item IDs, but for convenience, represent that the "answer acquisition node flag" of the acquired data item ID that corresponds to the leaf node is "1." Furthermore, the rounded rectangular nodes that are grandchild nodes of leaf nodes and contain the string "reason" are not nodes that correspond to the acquired data item IDs, but for convenience, represent that the "reason input flag" of the acquired data item ID that corresponds to the leaf node is "1." Therefore, strictly speaking, the rounded rectangular nodes are not nodes in a tree structure that indicates a parent-child relationship between acquired data item IDs. In the following, the rounded rectangular nodes will not be treated as nodes in the tree structure. Therefore, in the following, "leaf nodes" and "terminal nodes" refer to the leaf nodes of the circular nodes in Figure 10.

[0049] In the above-mentioned step S205, all acquired data item IDs corresponding to the top-level categories in the tree structure 123-2 (FIG. 10) are acquired. In the example of FIG. 10, four acquired data item IDs are acquired. That is, if the record of the target interview is not registered in the dialogue process implementation record DB 122 (FIG. 7), it is not possible to narrow down the acquired data item IDs that may have been implemented in the target interview based on the dialogue process elements, so all acquired data item IDs in the top level are acquired. Note that in this embodiment, the acquired data item IDs are broadly categorized into subject understanding and intervention, but strictly speaking, there are also acquired data item IDs that belong to other concepts (such as "Plan / Result" and "Other" in FIG. 10), so in FIG. 10, categories other than subject understanding and intervention are also shown as top-level categories.

[0050] Following step S204 or S205, the interview content registration unit 12 refers to the tree structure 123-2 (FIG. 10) and searches for acquired data item IDs corresponding to all leaf nodes that are descendants of the acquired data item ID for each acquired data item ID acquired in step S204 or S205 (S206). Note that only acquired data item IDs whose acquisition requirement flag is "required" may be searched for. Alternatively, each acquired data item ID in the manual interview record item DB 123 may have a column of respondent flags (flags indicating who should enter the answer (such as the public health nurse who conducted the interview, the senior public health nurse who observed, etc.)), and only acquired data item IDs that match the respondent flag specified at the start of FIG. 8 may be searched for.

[0051] Following step S206, the interview content registration unit 12 determines whether or not there is one or more acquired data item IDs whose "acquisition timing" (FIG. 9) is the target acquisition timing (for example, "after the interview") among the acquired data item IDs related to the searched leaf nodes (S207). The "acquisition timing" is an item that is valid for the acquired data item ID that is a record candidate item, and indicates the timing at which the interview record input support device 10 acquires the record for that record candidate item (in other words, the timing at which the user inputs the record for that record candidate item into the interview record input support device 10).

[0052] If the determination result is negative (No in S207), the process of Fig. 8 ends because in this case the user cannot input the desired acquisition data item ID.

[0053] If the determination result is positive (Yes in S207), the interview content registration unit 12 acquires from the tree structure 123-2 (FIG. 10) a tree structure (path) relating to each path from the acquired data item ID that was the search source for the leaf node whose "acquisition timing" is the target acquisition timing among the acquired data item IDs acquired in step S204 or S205 (i.e., the acquired data item ID that was the starting point of the search in step S206) to the acquired data item ID relating to the leaf node (S208). Note that there is a possibility that multiple tree structures (paths) may be acquired.

[0054] Next, a loop process including steps S209 to S214 is executed for each acquired tree structure (path). The tree structure that is the processing target in this loop process is referred to as the "target tree structure."

[0055] In step S209, the interview content registration unit 12 acquires the value of the "reason input flag" of the acquired data item ID (i.e., the acquired data item ID of the leaf node; hereinafter referred to as the "referenced acquired data item ID") whose "answer acquisition node flag" is 1 in the target tree structure from the acquired data item ID attribute table 123-1 (Figure 9) (S209). Next, the interview content registration unit 12 determines whether the value of the "reason input flag" is 1 (i.e., whether the referenced acquired data item ID is a candidate item for recording regarding intervention) (S210).

[0056] If the value of the "reason input flag" is 0 (if the reference source acquired data item ID is a record candidate item related to subject understanding) (No in S210), steps S211 to S214 are not executed for the subject tree structure.

[0057] If the value of the "reason input flag" is 1 (if the reference source acquired data item ID is a record candidate item related to intervention) (Yes in S210), the interview content registration unit 12 determines whether the "reason reference destination Id" of the reference source acquired data item ID is null (S211). As described above, the "reason reference destination Id" is an acquired data item ID that is a candidate for the reason (for the intervention). Also, the value of the "reason input flag" of the reference source acquired data item ID is 1. Therefore, here, if the "reason reference destination Id" is null, it means that the user is expected to input a reason, but no acquired data item ID that can be a candidate for the reason has been set.

[0058] If the "Reason Reference Id" is null (Yes in S211), the interview content registration unit 12 acquires the acquired data item ID related to the "Subject Understanding" at the top of the tree structure 123-2 (Figure 10) (i.e., the entire tree structure) as the "Referenced Acquired Data Item ID" (S212). Here, the referenced acquired data item ID refers to the acquired data item ID that will be the input destination of the reason for the record entered by the user in subsequent processing for the referencing acquired data item ID. If the "Reason Reference Id" is null, it is not possible to narrow down the acquired data item ID that will be the input destination of the reason, so the acquired data item ID corresponding to the top-level "Subject Understanding" is set as the referenced acquired data item ID that serves as the starting point for the input destination of the reason.

[0059] On the other hand, if the "Reason Reference Id" is not null (No in S211), the interview content registration unit 12 acquires the acquired data item ID registered in the "Reason Reference Id" as the "Reference Acquired Data Item ID" (S213).

[0060] Following step S212 or S213, the interview content registration unit 12 acquires from the tree structure 123-2 (FIG. 10) a tree structure starting from the referenced acquired data item ID to all acquired data item IDs (leaf nodes) whose "answer acquisition node flag" is 1 and whose "acquisition timing" is the target acquisition timing, and connects the acquired tree structure to the referenced acquired data item ID of the target tree structure (S214). The acquired tree structure is connected under the target tree structure using the referenced acquired data item ID as the connection point.

[0061] When the loop processing for all tree structures acquired in step S208 is completed, the interview content registration unit 12 generates an individual interview record input screen by referring to the tree structures acquired in step S208 whose ``reason input flag'' of the reference source acquisition data item ID is 0 (i.e., tree structures for which step S124 has not been executed) and the tree structure acquired in step S214, and displays the screen (S215).

[0062] Figure 11 is a diagram showing a first display example of the individual interview record input screen. The left side of Figure 11 shows the tree structure acquired in step S208 or S214 (hereinafter referred to as the "target tree structure"). The target tree structure is the tree structure acquired when the "acquired data item ID linked to the element" acquired in step S204 (i.e., the acquired data item ID that serves as the starting point for searching the tree structure) is "1-1" and "1-2".

[0063] In step S215, first, a main screen 510 constituting the individual interview record input screen is displayed. The main screen 510 has a column for each acquired data item ID (category) corresponding to the top node of the subject tree structure. At the top of the column, the acquired data item name of the corresponding acquired data item ID (in the example of FIG. 11, "subject understanding" and "intervention") is displayed as a label. Below the label of each column, a button is displayed for each acquired data item ID (category) corresponding to the child node of the acquired data item ID corresponding to the column. The label of the button is the acquired data item name of the corresponding acquired data item ID.

[0064] The user presses a category button from the buttons arranged on the main screen 510 that corresponds to the matters (subject understanding or intervention) that the user performed during the subject interview, and enters records related to that category for each category. Note that on the main screen 510, buttons corresponding to acquired data item IDs including descendant nodes whose "acquisition requirement" is "required" may be highlighted by blinking, etc. This is to prevent the user from forgetting to enter information for acquired data item IDs whose "acquisition requirement" is "required," as these are required for input by the user. Note that, because recording related to subject understanding can be a candidate reason for recording related to intervention, it is preferable to record related to subject understanding first. Therefore, when recording related to subject understanding is completed, the button corresponding to intervention may be grayed out, etc., making it inoperable.

[0065] For example, when a user selects the "Psychological Aspects" button on the main screen 510 to enter records related to "Psychological Aspects," the interview content registration unit 12 displays the input screen 520 shown in the lower right of Figure 11.

[0066] The input screen 520 includes one or more questions to guide the user in entering records, and answer options for each question. Each question is generated for each acquired data item ID (hereinafter referred to as a "target end-acquired data item ID") that is a leaf node (i.e., a record candidate item) among the descendant nodes of the acquired data item ID (here, "psychological aspect"; hereinafter referred to as a "target acquired data item ID") selected on the main screen 510. According to the target tree structure, there are three leaf nodes that are descendant nodes of "psychological aspect." Therefore, the input screen 520 includes three questions. For example, questions corresponding to each target end-acquired data item ID are generated based on the following question generation rules: Please tell me about [name of acquired data item for target acquired data item ID] and [name of acquired data item for target end acquired data item ID]. Here, [] means that it will be replaced by the name of the acquired data item shown within []. For example, for "Anxiety about the future," one of the descendant nodes of "Psychological Aspects," the first [] is replaced by "Anxiety," and the second [] is replaced by "Anxiety about the future." As a result, the question "Regarding anxiety, please tell me about anxiety about the future." is generated.

[0067] The answer options are options stored in the acquired data item ID attribute table 123-1 (FIG. 9) for the target end-acquired data item ID (for example, "anxiety about the future").

[0068] For each question, the user selects an option that corresponds to what they understood about the subject or what they intervened with the subject during the interview.

[0069] When the user has finished inputting data into one input screen 520, he or she returns to the main screen 510, and if there is a button on the main screen 510 that corresponds to an uninputted acquired data item ID, the user selects that button and continues inputting data for that acquired data item ID (target acquired data item ID).

[0070] For example, after inputting records for each category related to understanding the target person, when "10. Relationship building / understanding" is selected as the target acquisition data item ID, the interview content registration unit 12 displays an input screen 530 as shown in the upper right corner of Figure 12.

[0071] There are four leaf nodes (hereinafter referred to as "target leaf nodes") among the descendant nodes of the target acquired data item ID "10. Relationship Building / Understanding." However, for convenience, the input screen 530 in FIG. 12 displays only one question ("10. Regarding Innovations / Interventions, what innovations / interventions did you make regarding the opening greeting?") related to one target leaf node ("Opening Greeting"), and the questions related to the other target leaf nodes are omitted. Note that the format of the question related to the target leaf node in FIG. 12 is slightly different from the format of the question generation rule described above, but the question generation rule may be changed depending on the acquired data item ID. In addition, the answer to the question is in a free-entry format. This is because no values ​​(options) are registered in options 1 to 3 of the acquired data item ID attribute table 123-1 (FIG. 9) for the target end acquired data item ID related to the first target leaf node.

[0072] The input screen 530 further includes the question "Why is that?" along with buttons for "Psychological Aspects" and "Social Aspects." This is because the "reason input flag" for the target end-acquired data item ID is 1. Note that the question "Why is that?" and the like are also displayed for questions regarding other target end-acquired data item IDs (such as "Explanation," "Hearing," and "Acceptance / Praise"), but are omitted from FIG. 12 for convenience.

[0073] Here, the reason why the interview content registration unit 12 places the buttons "Psychological Aspects" and "Social Aspects" on the input screen 530 is because the tree structure (hereinafter referred to as the "referenced tree structure") below the referenced acquired data item ID ("Subject Understanding" in FIG. 12) is connected to the target leaf node by the action of step S214 in FIG. 8. In other words, in step S214, the referenced tree structure is connected to the leaf node in order to enable the presentation of reason options (candidates) for the leaf node that requires the input of a reason (the "reason input flag" is 1). When the "reason input flag" of the target end-acquired data item ID is 1, the interview content registration unit 12 places buttons on the input screen 530 corresponding to each node ("Psychological Aspects" and "Social Aspects" in the example of FIG. 12) of the referenced tree structure connected to the leaf node related to the target end-acquired data item ID that branches into multiple hierarchical levels. In the tree structure on the left side of Figure 12, the leaf nodes (such as "Explanation," "Hearing," and "Acceptance / Praise") that are sibling nodes of the target leaf node ("Opening Greeting") also have a "Reason Input Flag" of 1, so they should normally be connected to the reference tree structure, but this has been omitted in Figure 12 for convenience.

[0074] First, the user enters the answer (e.g., "I spoke in a brighter voice") to the first question ("10. Regarding ideas and interventions, what ideas and interventions did you make regarding the opening greeting?") as a record for the target end-acquisition data item ID.

[0075] Next, the user selects a button corresponding to the reason for the answer (e.g., "He spoke in a brighter voice") from among "Psychological Aspects" and "Social Aspects." For example, if the reason is related to "Psychological Aspects" and the user selects the "Psychological Aspects" button, the interview content registration unit 12 updates the display content of the input screen 530 as shown in the lower right of FIG. 12.

[0076] The input screen 530 at the bottom right of FIG. 12 includes a reason input area 531 for "psychological aspects." The reason input area 531 includes, in a tabular format, records (answers) entered on the input screen 520 (FIG. 11) for each leaf node belonging to "psychological aspects." That is, one row corresponds to one leaf node, the first column includes the name of the acquired data item corresponding to the leaf node, and the second column includes the record (answer) entered for the acquired data item ID corresponding to the leaf node. The reason input area 531 presents possible reasons for the answer entered by the user to the first question. That is, each row in the tabular format corresponds to a possible reason.

[0077] The user inputs a reason in the reason input area 531 by selecting a row corresponding to the reason for intervention indicated by the answer (e.g., "Spoke in a brighter voice") entered in response to the first question ("10. Regarding innovations and interventions, what innovations and interventions did you make in the opening greeting?"). Multiple rows may be selected. The interview content registration unit 12 associates the acquired data item name and answer related to the reason entered for the first target end-acquired data item ID with the target end-acquired data item ID and stores them. For example, if the row "Anxiety about the future" and "High" is selected, the interview content registration unit 12 associates "Anxiety about the future: High" with the first target end-acquired data item ID and stores it. In this case, the user's "Spoke in a brighter voice (intervened)" is considered to be an input of the causal relationship "because (the subject's) anxiety about the future is high."

[0078] By inputting the reasons, the interviewer can later reflect on why they performed that intervention and whether it was appropriate. As a result, when interviewing a similar subject (for example, a subject with little knowledge about health) in the future, by using the same intervention as the one they had previously devised, the possibility of conducting an effective interview can be increased.

[0079] When the user has finished inputting the record, the interview content registration unit 12 registers the record content in the individual interview manual record DB 124 (S216).

[0080] 13 is a diagram showing an example of the configuration of the individual interview manual record DB 124. The individual interview manual record DB 124 is a database that records information indicating how the interviewer understood the subject in each interview and what kind of intervention they performed. Therefore, it is possible to look back on each interview using the data in the individual interview manual record DB 124. This allows each interviewer to look back on what characteristics were present in interviews that they conducted well, or what characteristics were present in interviews that their seniors or juniors conducted well.

[0081] In FIG. 13, each record in the individual interview manual record DB 124 includes items such as an interview ID, an acquired data item ID, recorded content, and reason.

[0082] The interview ID is the interview ID of the target interview. The acquired data item ID is the target end-acquired data item ID for which a record (answer) was entered on the input screen 520 (FIG. 11) or the input screen 530 (FIG. 12). The recorded content is the content of the record (answer) entered by the user for the acquired data item ID. For example, if a choice is made from among the options included in the input screen 520 (FIG. 11), the selected option is registered as the recorded content. In the case of a free-input format such as the first question on the input screen 530 (FIG. 12), the entered character string is registered as the recorded content. The reason is the reason entered (selected) by the user for the recorded content for the acquired data item ID when the "reason input flag" for the acquired data item ID is 1. The reason is expressed in the format "[acquired data item name]:[input content]". The [acquired data item name] is the acquired data item name of the acquired data item ID selected as the reason. The [input content] is the input content for the acquired data item ID selected as the reason. In the individual interview manual record DB124, the combination of the acquired data item ID of a record in which a value is registered in "reason" and the acquired data item ID (hereinafter referred to as "reason input destination acquired data item ID") corresponding to the reason ([acquired data item name]:[input content]) (corresponding to the [acquired data item name]) is hereinafter referred to as "reason recording information." In the example of Figure 12, the combination of "opening greeting" and "anxiety about the future" corresponds to reason recording information, and the acquired data item ID corresponding to "anxiety about the future" corresponds to the reason input destination acquired data item ID. For the target interview, reason recording information exists for each corresponding combination. Therefore, multiple reason recording information may exist.

[0083] Next, the interview content registration unit 12 transmits the group of reason record information relating to the target interview to the reason input candidate management unit 13 (S217).

[0084] [Reason input candidate management section 13] FIG. 14 is a flowchart illustrating an example of a processing procedure executed by the reason input candidate management unit 13. The processing procedure of FIG. 14 is executed, for example, upon completion of the processing procedure of FIG. 8 in order to limit candidates likely to be selected as reasons for intervention, thereby reducing the time and effort required for an interviewee to search for a relevant reason from a large number of reason candidates when entering a reason for intervention. Reason record information from multiple past interviews is also utilized to identify reason candidates likely to be generally selected for a certain end-level acquired data item ID related to intervention. The reason input destination acquired data item ID or the ancestor acquired data item ID of the reason input destination acquired data item ID corresponding to the reason candidate determined to be likely to be generally selected for the end-level acquired data item ID is registered in the "reason reference destination ID" of the end-level acquired data item ID. As a result, the determination of step S211 of FIG. 8 for the end-level acquired data item ID is affirmative (Yes), and step S212 is executed. That is, the tree structure below the reason input destination acquired data item ID or the ancestor acquired data item ID is connected to the end-level acquired data item ID as a reference destination tree structure. As a result, for example, the candidate reasons displayed on the input screen 530 of Figure 12 can be limited to candidates that are likely to be entered. Note that the "Reason Reference ID" in the manual interview record item DB123 may be manually registered, for example, by an administrator or the like.

[0085] In step S301, the reason input candidate management unit 13 receives the reason record information group transmitted from the interview content registration unit 12. The reason input candidate management unit 13 executes the loop processing from step S302 onwards for each reason record information included in the reason record information group. Hereinafter, the reason record information being processed in the loop processing will be referred to as "target reason record information", and the acquisition data item ID and reason input destination acquisition data item ID of the target reason record information will be referred to as "target acquisition data item ID" and "target reason input destination acquisition data item ID", respectively.

[0086] In step S302, the reason input candidate management unit 13 refers to the reason recording information recording table 125-1 stored in the reason input candidate management DB 125, and adds 1 to the occurrence count of the reason recording information that matches the target reason recording information (S302).

[0087] Figure 15 is a diagram showing an example of the configuration of the reason recording information recording table 125-1. As shown in Figure 15, the reason recording information recording table 125-1 stores the number of occurrences for each reason recording information (acquired data item ID, reason input destination acquired data item ID). The number of occurrences is the number of times the same reason recording information has been registered in the individual interview manual record DB 124 across all past interviews. In other words, the number of occurrences is the number of times a record for an acquired data item ID related to a "reason input destination acquired data item ID" has been selected as the reason for the intervention entered for the "acquired data item ID."

[0088] Next, the reason input candidate management unit 13 acquires the number of occurrences of each acquired data item ID that is a sibling of the target reason input destination acquisition data item ID (hereinafter referred to as "sibling reason input destination acquisition data item ID") for the target acquisition data item ID from the reason recording information recording table 125-1 (Fig. 15) (S303). That is, the number of occurrences of all records in the reason recording information recording table 125-1 (Fig. 15) whose value of "acquired data item ID" matches the target acquisition data item ID and whose value of "reason input destination acquisition data item ID" matches each acquired data item ID that is a sibling of the target reason input destination acquisition data item ID is acquired from the reason recording information recording table 125-1 (Fig. 15). Note that each acquired data item ID that is a sibling of the target reason input destination acquisition data item ID refers to an acquired data item ID that corresponds to a sibling node (a node belonging to a common parent node) of the target reason input destination acquisition data item ID in the tree structure 123-2 (Fig. 10).

[0089] Next, the reason input candidate management unit 13 determines whether the total number of occurrences (number of occurrences of siblings) acquired in step S303 is equal to or greater than a preset threshold A (S304). The total number of occurrences of siblings is the total of the number of occurrences of all sibling reason input destination acquisition data item IDs. In other words, the target reason input destination acquisition data item ID is not included in "siblings."

[0090] If the total number of occurrences of the siblings is equal to or greater than threshold A (Yes in S304), the reason input candidate management unit 13 calculates the reason candidate score of the acquired data item ID related to the parent node of the siblings (S305). The reason candidate score of a certain acquired data item ID is an index indicating the degree to which the reason data item ID is appropriate as a "reason reference ID" for the target acquired data item ID. In this case, the reason candidate score can be calculated, for example, based on the following formula: Reason candidate score = Σ(C i / n) n: Number of siblings with occurrence count of 1 or more + 1 (+1 is the number of data item IDs to input the target reason) C i : The number of occurrences of siblings with an occurrence count of 1 or more and the number of occurrences of the target reason record information That is, the reason candidate score in the above example is the average value of the number of occurrences of the target reason record information and the number of occurrences of sibling nodes whose number of occurrences is 1 or more.

[0091] Fig. 16 is a diagram showing an example of calculating a parent's candidate reason score. Fig. 16 shows an example where the target acquired data item ID is 3-2-1-1 ("opening greeting") and the target reason input destination acquired data item ID is 3-1-2-1 ("personality tendencies"). In this case, the average of the number of occurrences of the target reason input destination acquired data item ID=3-1-2-1 and the number of occurrences of its sibling reason input destination acquired data item ID=3-1-2-2 is calculated as the reason candidate score for the parent's ("psychological aspect") acquired data item ID=2-1-2.

[0092] Next, the reason input candidate management unit 13 updates the reason candidate score for the target acquisition data item ID for the parent acquisition data item ID of the target reason input destination acquisition data item ID in the reason reference destination candidate ID management table 125-2 of the reason input candidate management DB 125 (S306).

[0093] FIG. 17 is a diagram illustrating an example of the configuration of the reason reference destination candidate ID management table 125-2. As illustrated in FIG. 17, each record in the reason reference destination candidate ID management table 125-2 includes fields such as an "acquired data item ID," a "reason reference destination candidate ID," and a "reason candidate score." Each record indicates the degree to which the acquired data item ID associated with the "reason reference destination candidate ID" is appropriate for the "acquired data item ID." Therefore, in step S306, the value of the "reason candidate score" of a record whose "acquired data item ID" value matches the target acquired data item ID and whose "reason reference destination candidate ID" value matches the parent acquired data item ID of the target acquired data item ID is updated with the reason candidate score calculated in step S305. If no corresponding record exists, a new record may be registered. The first record in FIG. 17 corresponds to the example in FIG. 16.

[0094] In this way, the reason reference candidate ID management table 125-2 (FIG. 17) registers a reason candidate score for the parent of the target reason input destination acquisition data item ID. The parent reason candidate score is calculated based on the number of occurrences of the target reason input destination acquisition data item ID and the number of occurrences of the reason input destination acquisition data item IDs of its siblings. This is based on the idea that in the tree structure 123-2 (FIG. 10), children inherit the characteristics of their parents. By using the parent acquisition data item ID as the reason reference candidate ID for the target acquisition data item, even if only some of the children of the parent have been selected as reasons in the past, it is possible to avoid limiting the reason candidates for the target acquisition data item to only those children, and it is possible to present to the user other children (i.e., siblings) that are thought to have inherited common characteristics with the child as reason candidates. In addition, instead of the parent, the candidate reason score may be calculated for one of the parent's ancestors' acquired data item IDs in the same manner as for the parent, and the candidate reason score for the ancestor's acquired data item ID for the target acquired data item ID may be updated in the reason reference candidate ID management table 125-2 (Figure 17).

[0095] On the other hand, if the total number of appearances of the siblings is less than the preset threshold A (No in S304), the reason input candidate management unit 13 calculates the reason candidate score for the target reason input destination acquisition data item ID (S307). In this case, the reason candidate score can be calculated, for example, based on the following formula: Reason candidate score = C C: Number of occurrences of the data item ID for the target reason input destination Next, the reason input candidate management unit 13 updates the reason candidate score of the target reason input destination acquisition data item ID for the target acquisition data item ID in the reason reference destination candidate ID management table 125-2 (FIG. 17) of the reason input candidate management DB 125 (S308). Specifically, the "reason candidate score" value of the record whose "acquired data item ID" value matches the target acquisition data item ID and whose "reason reference destination candidate ID" value matches the target reason input destination acquisition data item ID is updated by the reason candidate score calculated in step S307. If there is no corresponding record, the record may be newly registered.

[0096] Following step S306 or S308, the reason input candidate management unit 13 determines whether the reason candidate score of the record (hereinafter referred to as the "updated record") in the reason reference destination candidate ID management table 125-2 (FIG. 17) updated in step S306 or S308 is equal to or greater than threshold B (S309).

[0097] If the reason candidate score is equal to or greater than threshold B (Yes in S309), the reason input candidate management unit 13 updates the "reason reference destination ID" of the target acquired data item ID in the interview manual record item DB 123 (FIG. 9) based on the updated record (S310). Specifically, the reason input candidate management unit 13 adds the value of the "reason reference destination candidate ID" of the updated record to the "reason reference destination ID" of the record in the interview manual record item DB 123 (FIG. 9) whose value of the "acquired data item ID" matches the "acquired data item ID" of the updated record (i.e., the target acquired data item ID).

[0098] The values ​​of the thresholds A and B may be changed according to the number of interviews registered in the interview manual record item DB 123. As the number of interviews increases, the thresholds A and B may be increased.

[0099] [Interview case visualization part 14] First, we will explain the screen (hereinafter referred to as the "visualization screen 550") displayed by the interview case visualization unit 14. Fig. 18 is a diagram showing an example of the display of the visualization screen 550. As shown in Fig. 18, the visualization screen 550 is divided into multiple areas for each dialogue process element. Hereinafter, each divided area will be referred to as a "visualization area."

[0100] The visualization screen 550 visualizes how the interviewer understood the subject and how they intervened in each interview, thereby supporting reflection on each interview. This allows the interviewer to reflect on what characteristics were present in interviews that they conducted well, or what characteristics were present in interviews that their seniors or juniors conducted well. In order to display this visualization screen 550, the interview example visualization unit 14 executes the following processing procedure.

[0101] Fig. 19 is a flowchart for explaining an example of the processing procedure executed by the interview example visualization unit 14. The processing procedure in Fig. 19 is executed when the interviewer or coworkers reflect on the target interview at any timing after the interviewer has entered a record related to the target interview (after the processing procedure in Fig. 8 has ended). Examples of the target interview are visualized so that the reflection on the target interview can be useful for learning and discussion in the workplace.

[0102] In step S401, the interview example visualization unit 14 receives a visualization request for an interview example from a user. The visualization request specifies the interview ID (hereinafter referred to as the "target interview ID") of the interview to be visualized (hereinafter referred to as the "target interview").

[0103] Next, the interview example visualization unit 14 acquires the "placement position," "dialogue process element ID," and "dialogue process element name" for each visualization area from the visualization definition DB 126 (S402).

[0104] Fig. 20 is a diagram showing an example of the configuration of the visualization definition DB 126. As shown in Fig. 20, the visualization definition DB 126 stores in advance, for each visualization area, a "visualization area ID," a "placement position," a "dialogue process element ID," a "dialogue process element name," an "acquired data item ID to be included in the visualization of the causal structure," and the like.

[0105] "Visualization area ID" is identification information for the visualization area. "Placement position" is information indicating the position (range) where the visualization area is placed in the display area of ​​the visualization screen 550. "Dialogue process element ID" and "Dialogue process element name" are the dialogue process element ID and dialogue process element name corresponding to the visualization area. "Acquired data item ID to be placed in visualization of causal structure" is information indicating the acquired data item ID corresponding to the visualization area. In each visualization area, a figure corresponding to the acquired data item ID whose record is recorded in the individual interview manual record DB124 for the target interview is placed, and "Acquired data item ID to be placed in visualization of causal structure" is information indicating in which visualization area the acquired data item ID should be placed.

[0106] Next, the interview case visualization unit 14 divides the display area of ​​the visualization screen 550 based on the "placement position" of each visualization area (S403). At this time, scrolling of the display area may be assumed. In other words, a larger display area of ​​the visualization screen 550 may be defined.

[0107] Next, the interview example visualization unit 14 generates a title for each visualization area by connecting the "dialogue process element ID" and the "dialogue process element name," and arranges the generated title (S404).

[0108] Next, the interview example visualization unit 14 acquires the "acquired data item ID to be included in the visualization of the causal structure" of each visualization area from the visualization definition DB 126 (S405).

[0109] Next, the interview example visualization unit 14 identifies the "acquired data item ID to be included in the visualization of the causal structure" and its descendant acquired data item IDs by referring to the tree structure 123-2 (Figure 10), and acquires data (recording contents) registered in the individual interview manual record DB 124 (Figure 13) regarding the target interview (associated with the interview ID of the target interview) for each identified acquired data item ID (S406). At this time, the interview example visualization unit 14 acquires the acquired data item name of each acquired data item ID from the interview manual record item DB 123 (Figure 9).

[0110] Next, the interview case visualization unit 14 arranges graphic elements indicating the data (acquired data item name, recorded content) acquired for each acquired data item ID in step S406 in the visualization area corresponding to each acquired data item ID (S407). The visualization area corresponding to a certain acquired data item ID is the visualization area corresponding to a record in the visualization definition DB 126 that includes the certain acquired data item ID in its "acquired data item ID to be included in the visualization of the causal structure." If there is no corresponding visualization area, the visualization area corresponding to the record that includes the ancestor acquired data item ID of the certain acquired data item ID in its "acquired data item ID to be included in the visualization of the causal structure" becomes the visualization area corresponding to the certain acquired data item ID.

[0111] At this time, the interview example visualization unit 14 represents the acquired data item ID of the descendant node of "subject understanding" in the tree structure 123-2 (FIG. 10) as a rounded rectangle that includes the acquired data item name (e.g., "anxiety about the future") in the upper row and the "recorded content" (e.g., "high") in the lower row. Also, in the tree structure 123-2 (FIG. 10), the interview example visualization unit 14 represents the "recorded content" (e.g., "introduced the app") in the shape of a speech bubble for the acquired data item ID of the descendant node of "intervention." Furthermore, if the "reason" in the individual interview manual record DB 124 for that acquired data item ID is not null, the interview example visualization unit 14 connects the figure corresponding to that acquired data item ID and the figure corresponding to the acquired data item ID that corresponds to that "reason" with a curved line.

[0112] In addition, the graphic elements corresponding to the acquired data item IDs in each visualization area may be arranged in order of the acquired data item IDs, in alphabetical order of the acquired data item names, or in order of frequency of appearance in the interview manual record item DB123.

[0113] As described above, according to this embodiment, the user does not need to input records for all record candidate items, but only needs to input records for the record candidate items associated with the dialogue process elements that were actually performed in the dialogue process of the interview, thereby making it possible to efficiently input records related to the interview.

[0114] In addition, the reason for the intervention can be entered by selecting from the records entered for the candidate record items related to subject understanding. In this respect, too, the input of interview records can be made more efficient.

[0115] In addition to interviews related to health guidance, this embodiment may also be applied to learning about teacher-student interviews in educational settings for teachers, and learning about dialogues that promote community participation among local elderly people for caregivers and volunteers.

[0116] In this embodiment, the executed dialogue process management unit 11 is an example of a selection unit, and the interview content registration unit 12 is an example of a registration unit.

[0117] Although the embodiments of the present invention have been described in detail above, the present invention is not limited to such specific embodiments, and various modifications and variations are possible within the scope of the gist of the present invention as described in the claims. [Explanation of symbols]

[0118] 10 Interview record input support device 11 Implemented Dialogue Process Management Department 12 Interview Content Registration Section 13 Reason input candidate management section 14 Interview case visualization department 100 Drive device 101 Recording media 102 Auxiliary storage device 103 Memory Device 104 CPU 105 Interface Device 106 Display device 107 Input Device 121 Common Dialogue Process Model DB 122 Dialogue Process Implementation Record DB 123 Interview Manual Record Item DB 124 Individual interview manual record DB 125 Reason Input Candidate Management DB 126 Visualization definition DB B Bus

Claims

1. a selection unit configured to receive a selection of one or more elements made in relation to a certain interview from among a plurality of elements constituting a dialogue process between an interviewer and an interviewee; a registration unit configured to receive a record of an interview for an item associated with any of the elements selected from a plurality of items that are candidates for recording in order to review the interview, and to register the record in a storage unit; An interview record input support device comprising:

2. The element is associated with one of a plurality of categories into which the plurality of items are classified; the registration unit is configured to accept a record of the certain interview for the item belonging to the category associated with any of the selected elements; 2. The interview record input support device according to claim 1.

3. the plurality of categories includes a first category related to understanding of the interviewee and a second category related to intervention with the interviewee; The registration unit is configured to receive a record of what the interviewer understood about the interviewee in the interview for one or more first items among the plurality of items belonging to the first category, and to receive a record of an intervention made by the interviewer to the interviewee in the interview and a reason for the intervention for one or more second items among the plurality of items belonging to the second category.

3. The interview record input support device according to claim 2.

4. the registration unit is configured to present a record received for any of the first items as a possible reason for an intervention received for any of the second items; 4. The interview record input support device according to claim 3.

5. the registration unit is configured to present, as a candidate reason for an intervention received for any of the second items, a record received for the first item that has been selected as a reason for an intervention received for the second item in the past a number of times equal to or greater than a threshold.

5. The interview record input support device according to claim 4.

6. The plurality of categories have a parent-child relationship; the registration unit is configured to present, as candidates for the reason for the intervention received for any of the second items, records received for one or more other first items that are descendants of the same category as the first item and whose total number of times that the records have been selected as reasons for the intervention received for the second item in the past is equal to or greater than a threshold.

5. The interview record input support device according to claim 4.

7. a selection step for accepting a selection of one or more elements performed in a certain interview from among a plurality of elements constituting a dialogue process between an interviewer and an interviewee; a registration step of accepting a record of an interview for an item associated with one of the elements selected from a plurality of items that are candidates for recording in order to review the interview, and registering the record in a storage unit; An interview record input support method characterized by being executed by a computer.

8. a selection step for accepting a selection of one or more elements performed in a certain interview from among a plurality of elements constituting a dialogue process between an interviewer and an interviewee; a registration step of accepting a record of an interview for an item associated with one of the elements selected from a plurality of items that are candidates for recording in order to review the interview, and registering the record in a storage unit; A program characterized by causing a computer to execute the above.

Images