Medical assistance device, medical assistance method, and program

Abstract

Provided are a medical assistance device, a medical assistance method, and a program enabling accurate extraction of terminology used for analysis. This medical assistance device is provided with a processor. The processor: imports endoscopy-related procedure information which is configured in a predetermined format and which forms the predetermined format that includes at least a plurality of characters pertaining to endoscopic qualitative diagnosis or treatment; extracts a specific word by using a method of division corresponding to an attribute linked to an item of an examination type to divide the endoscopy-related procedure information, compares the specific word and a standard term defined in the predetermined format, and determines the specific word to be an attribute value if the specific word and the standard term match.

Description

Medical support device, medical support method, and program

[0001] The present disclosure relates to a medical support device, a medical support method, and a program for analyzing endoscopic procedure information.

[0002] In recent years, a technology has become known for endoscopic examinations in which, after an endoscopic examination, a medical data file including an examination report in which endoscopic images and doctor findings are associated with patient data is recorded and managed (see, for example, Patent Document 1). This technology allows doctors to efficiently diagnose and treat patients by searching for past examinations of the same patient, referring to past findings, and displaying images.

[0003] Patent No. 4350294

[0004] In the medical field, there is a demand for improving the quality of medical care and providing the best possible medical care to patients by compiling and analyzing endoscopic procedure information, including endoscopic techniques and procedures, in addition to patient data and doctor findings.

[0005] However, endoscopic procedure information has different output formats depending on the type of system, doctors' term selection and term input vary, and delimiters used to separate strings of characters differ, making it difficult to accurately extract, aggregate, and analyze the terms used in the analysis.

[0006] The present disclosure has been made in view of the above, and aims to provide a medical support device, a medical support method, and a program that are capable of accurately extracting terms used in analysis.

[0007] In order to solve the above-mentioned problems and achieve the objectives, the medical support device of the present disclosure is a medical support device equipped with a processor, which imports endoscopic-related procedure information in a predetermined format that includes multiple characters related to at least one of endoscopic qualitative diagnosis and treatment, extracts specific words by dividing the endoscopic-related procedure information in the predetermined format using a division method that corresponds to the content of the endoscopic-related procedure information in the predetermined format, compares the specific words with standard terms defined in the endoscopic-related procedure information in the predetermined format, and if the specific words match the standard terms, determines the specific words to be attribute values.

[0008] In addition, in the medical support device according to the present disclosure, in the above disclosure, the processor determines that the specific word is an attribute value of a facility-specific term if the specific word and the standard term do not match.

[0009] In addition, in the medical support device of the present disclosure, in the above disclosure, if the specific word and the standard term do not match, the processor stores the specific word as an attribute value of a facility-specific term, and updates the facility-specific term stored as an attribute value as the standard term.

[0010] In addition, in the medical support device of the present disclosure, in the above disclosure, when the processor stores the specific word as an attribute value of a facility-specific term, it counts the number of times the specific word is used and determines whether the number of times the specific word is used is greater than or equal to a predetermined number, and if the number of times the specific word is used is less than the predetermined number of times, it does not use the specific word as an attribute value of the facility-specific term.

[0011] In addition, in the medical support device of the present disclosure, in the above disclosure, the processor determines whether the number of times the specific word is used within a specified period of time is greater than or equal to a specified number of times, and if the number of times the specific word is used is not greater than or equal to the specified number of times, the specific word is not used as an attribute value of a facility-specific term.

[0012] In addition, in the medical support device according to the present disclosure, in the above disclosure, the division method includes a division method of dividing the attributes by characters that connect them together, and a division method of dividing the attributes by characters that connect them with additional information.

[0013] In addition, in the medical support device according to the present disclosure, in the above disclosure, the processor divides the endoscopic procedure information from the rear by characters that link attributes and additional information, sequentially acquires the front character strings from the array of multiple character strings obtained as a result of the division, and sequentially determines whether the front character strings match the standard term.

[0014] In addition, in the medical support device of the present disclosure, in the above disclosure, the processor determines whether the specific word, which is the target string, satisfies a condition regarding facility setting information that indicates the number of characters for identifying a facility-specific term, and if the condition is satisfied, determines the specific word to be an attribute value of the facility-specific term.

[0015] In addition, in the medical support device of the present disclosure, in the above disclosure, the processor determines whether the specific word, which is the target string, satisfies at least one of a second condition that the specific word is included in the first string when divided by at least a character that connects attributes, and a third condition that the target string does not contain a character that divides attributes and additional information, and if at least one of the second condition and the third condition is satisfied, determines that the specific word is an attribute value of a facility-specific term.

[0016] In addition, in the medical support device disclosed herein, in the above disclosure, the processor determines whether the specific word, which is the target string, satisfies at least one of the following conditions: a first condition related to facility setting information indicating at least the number of characters required to identify a facility-specific term; a second condition that the specific word is included in the first string when divided by a character that connects attributes; and a third condition that the target string does not contain a character that divides the attribute and additional information; and if at least one of the first condition, the second condition, and the third condition is satisfied, determines that the specific word is an attribute value of a facility-specific term.

[0017] In addition, in the medical support device disclosed herein, in the above disclosure, the endoscopic-related procedure information further includes an identifier that identifies the endoscopic system, and the processor obtains system setting information for the division method corresponding to each identifier, and extracts the specific word based on the system setting information for the division method.

[0018] In addition, in the medical support device of the present disclosure, in the above disclosure, the processor determines whether or not system setting information for the division method corresponding to the identifier has been obtained, and if system setting information for the division method corresponding to the identifier has not been obtained, outputs a warning to the effect that system setting information for the division method corresponding to the identifier has not been obtained.

[0019] In addition, in the medical support device of the present disclosure, in the above disclosure, the endoscopic-related procedure information further includes an identifier that identifies the endoscopic system, and the processor obtains system setting information of the division method corresponding to each identifier, and extracts the specific word based on the system setting information of the division method.

[0020] Furthermore, the medical support method according to the present disclosure is a medical support method executed by a medical support device having a processor, and includes the steps of: importing endoscopic-related procedure information in a predetermined format that includes a plurality of characters related to at least one of a qualitative diagnosis and a treatment using an endoscope; extracting specific words by dividing the endoscopic-related procedure information in the predetermined format using a division method according to the content of the endoscopic-related procedure information in the predetermined format; comparing the specific words with standard terms defined in the endoscopic-related procedure information in the predetermined format; and determining the specific words as attribute values ​​if the specific words match the standard terms.

[0021] In addition, in the medical support method according to the present disclosure, in the above disclosure, the processor determines that the specific word is an attribute value of a facility-specific term if the specific word and the standard term do not match.

[0022] In addition, in the medical support method of the present disclosure, in the above disclosure, if the specific word and the standard term do not match, the processor stores the specific word as an attribute value of a facility-specific term, and updates the facility-specific term stored as an attribute value as the standard term.

[0023] In addition, in the medical support method of the present disclosure, when the processor stores the specific word as an attribute value of a facility-specific term, it counts the number of times the specific word is used and determines whether the number of times the specific word is used is greater than or equal to a predetermined number, and if the number of times the specific word is used is less than the predetermined number of times, it does not use the specific word as an attribute value of the facility-specific term.

[0024] In addition, in the medical support method disclosed herein, in the above disclosure, the processor determines whether the number of times the specific word is used within a specified time period is greater than or equal to a specified number of times, and if the number of times the specific word is used is less than or equal to the specified number of times, the specific word is not used as an attribute value of a facility-specific term.

[0025] In addition, the medical support method according to the present disclosure, in the above disclosure, includes a division method of dividing the attributes by characters that connect the attributes together, and a division method of dividing the attributes by characters that connect the attributes and additional information.

[0026] In addition, in the medical support method according to the present disclosure, in the above disclosure, the processor divides the endoscopic procedure information from the rear by characters that link attributes and additional information, sequentially obtains the front character strings from the array of multiple character strings obtained as a result of the division, and sequentially determines whether the front character strings match the standard term.

[0027] Furthermore, in the medical support method according to the present disclosure, in the above disclosure, the processor determines whether the specific word, which is the target string, satisfies at least one of the following conditions: a first condition related to facility setting information indicating at least the number of characters required to identify a facility-specific term; a second condition that the specific word is included in the first string when the target string is divided by a character that connects attributes; and a third condition that the target string does not contain a character that divides the attribute and additional information; and if at least one of the first condition, the second condition, and the third condition is satisfied, the specific word is determined to be an attribute value of a facility-specific term.

[0028] In addition, the program according to the present disclosure is a program to be executed by a medical support device equipped with a processor, and causes the processor to import endoscopic-related procedure information in a predetermined format that includes a plurality of characters related to at least one of endoscopic qualitative diagnosis and treatment, extract specific words by dividing the endoscopic-related procedure information in the predetermined format using a division method according to the content of the endoscopic-related procedure information in the predetermined format, compare the specific words with standard terms defined in the endoscopic-related procedure information in the predetermined format, and if the specific words match the standard terms, determine the specific words to be attribute values.

[0029] According to the present disclosure, it is possible to accurately extract terms to be used in analysis.

[0030] FIG. 1 is a diagram illustrating an overall configuration of a medical support system according to a first embodiment of the present disclosure. FIG. 2 is a block diagram illustrating a functional configuration of a medical support device according to the first embodiment of the present disclosure. FIG. 3 is a diagram illustrating an example of endoscopic-related procedure information recorded in an endoscopic-related procedure information DB according to the first embodiment of the present disclosure. FIG. 4 is a diagram illustrating an example of system setting information recorded in a system setting DB according to the first embodiment of the present disclosure. FIG. 5 is a diagram illustrating an example of standard terms (qualitative diagnosis) according to the first embodiment of the present disclosure. FIG. 6 is a diagram illustrating an example of standard terms (treatment) according to the first embodiment of the present disclosure. FIG. 7 is a diagram illustrating an example of a JED-format database for endoscopic-related procedure information according to the first embodiment of the present disclosure. FIG. 8 is a flowchart illustrating an outline of processing executed by the medical support device according to the first embodiment of the present disclosure. FIG. 9 is a sub-flowchart illustrating an outline of standard term processing in step S106 of FIG. 8. FIG. 10 is a diagram schematically illustrating an example of standard term extraction processing performed by a standard term extraction unit included in the medical support device according to the first embodiment of the present disclosure. FIG. 11 is a diagram schematically illustrating another example of standard term extraction processing performed by the standard term extraction unit included in the medical support device according to the first embodiment of the present disclosure. FIG. 12 is a diagram schematically illustrating another example of standard term extraction processing performed by the standard term extraction unit included in the medical support device according to the first embodiment of the present disclosure. FIG. 13 is a diagram schematically illustrating another example of standard term extraction processing performed by the standard term extraction unit included in the medical support device according to the first embodiment of the present disclosure. FIG. 14 is a diagram illustrating an example of an analysis result analyzed by the analysis unit included in the medical support device according to the first embodiment of the present disclosure. FIG. 15 is a diagram illustrating another example of an analysis result analyzed by the analysis unit included in the medical support device according to the first embodiment of the present disclosure. FIG. 16 is a diagram illustrating another example of an analysis result analyzed by the analysis unit included in the medical support device according to the first embodiment of the present disclosure. FIG. 17 is a diagram illustrating another example of an analysis result analyzed by the analysis unit included in the medical support device according to the first embodiment of the present disclosure. 18 is a diagram illustrating another example of an analysis result obtained by the analysis unit included in the medical support device according to the first embodiment of the present disclosure. FIG. 19 is a block diagram illustrating a functional configuration of the medical support device according to the second embodiment of the present disclosure.FIG. 20 is a diagram illustrating an example of system setting information recorded in a system setting DB of a medical support device according to embodiment 2 of the present disclosure. FIG. 21 is a flowchart illustrating an outline of processing executed by the medical support device according to embodiment 2 of the present disclosure. FIG. 22 is a sub-flowchart illustrating an outline of standard terminology processing in step S306 of FIG. 21. FIG. 23 is a diagram schematically illustrating an example of standard terminology extraction processing performed by a standard terminology extraction unit included in the medical support device according to embodiment 2 of the present disclosure. FIG. 24 is a diagram schematically illustrating another example of standard terminology extraction processing performed by a standard terminology extraction unit included in the medical support device according to embodiment 2 of the present disclosure. FIG. 25 is a diagram schematically illustrating another example of standard terminology extraction processing performed by a standard terminology extraction unit included in the medical support device according to embodiment 2 of the present disclosure. FIG. 26 is a diagram schematically illustrating another example of standard terminology extraction processing performed by a standard terminology extraction unit included in the medical support device according to embodiment 2 of the present disclosure. FIG. 27 is a sub-flowchart illustrating an outline of facility-specific terminology extraction processing in step S307 of FIG. 21. FIG. 28 is a diagram schematically illustrating an example of facility-specific term extraction processing by a facility-specific term extraction unit included in a medical support device according to Embodiment 2 of the present disclosure. FIG. 29 is a diagram illustrating an example of data input when storing attribute values ​​of captured data in an attribute value storage DB included in a medical support device according to Embodiment 2 of the present disclosure. FIG. 30 is a diagram illustrating an example of standard terms (qualitative diagnoses) stored in a standard term storage DB included in a medical support device according to Embodiment 2 of the present disclosure. FIG. 31 is a diagram illustrating an example of standard terms (treatments) stored in a standard term storage DB included in a medical support device according to Embodiment 2 of the present disclosure. FIG. 32 is a diagram illustrating an example of qualitative diagnoses and treatments of attribute values ​​stored in an attribute value storage DB included in a medical support device according to Embodiment 2 of the present disclosure. FIG. 33 is a block diagram illustrating a functional configuration of a medical support device according to Embodiment 3 of the present disclosure. FIG. 34 is a diagram illustrating an example of system setting information recorded in a system setting DB 141B included in a medical support device according to Embodiment 3 of the present disclosure. 35 is a flowchart illustrating an outline of processing executed by a medical support device 10B included in a medical support device according to Embodiment 3 of the present disclosure. FIG. 36 is a block diagram illustrating a functional configuration of a medical support device according to Embodiment 4 of the present disclosure.FIG. 37 is a diagram illustrating an example of standard term (treatment) usage information of a medical support device according to Embodiment 4 of the present disclosure. FIG. 38 is a diagram illustrating an example of facility setting information of a medical support device according to Embodiment 4 of the present disclosure. FIG. 39 is a flowchart illustrating an outline of processing executed by a medical support device according to Embodiment 4 of the present disclosure. FIG. 40 is a diagram illustrating a schematic diagram of a situation in which the number of uses is counted up when an attribute extracted in the standard term extraction processing is acquired by a standard term extraction unit included in a medical support device according to Embodiment 4 of the present disclosure. FIG. 41 is a sub-flowchart illustrating an outline of facility-specific term extraction processing in step S710 of FIG. 39. FIG. 42 is a diagram illustrating a schematic diagram of an example of facility-specific term extraction processing performed by a facility-specific term extraction unit included in a medical support device according to Embodiment 4 of the present disclosure. FIG. 43 is a diagram illustrating a schematic diagram of standard term adjustment performed by a standard term adjustment unit included in a medical support device according to Embodiment 4 of the present disclosure. FIG. 44 is a block diagram illustrating a functional configuration of a medical support device according to Embodiment 5 of the present disclosure. FIG. 45 is a flowchart illustrating an outline of standard term extraction processing performed by a medical support device according to Embodiment 5 of the present disclosure. FIG. 46 is a diagram illustrating an example of a character string extracted by a standard term extraction unit included in a medical support device according to embodiment 5 of the present disclosure and stored in a standard term temporary storage DB. FIG. 47 is a flowchart illustrating an outline of adjustment processing executed by a standard term adjustment unit included in a medical support device according to embodiment 5 of the present disclosure. FIG. 48 is a diagram illustrating an example of an analysis result analyzed by an analysis unit included in a medical support device according to an embodiment of the present disclosure. FIG. 49 is a diagram illustrating another example of an analysis result analyzed by the analysis unit 166. FIG. 50 is a diagram illustrating another example of an analysis result analyzed by an analysis unit included in a medical support device according to an embodiment of the present disclosure. FIG. 51 is a diagram illustrating another example of an analysis result analyzed by an analysis unit included in a medical support device according to an embodiment of the present disclosure. FIG. 52 is a diagram illustrating another example of an analysis result analyzed by an analysis unit included in a medical support device according to an embodiment of the present disclosure. FIG. 53 is a diagram illustrating another example of an analysis result analyzed by an analysis unit included in a medical support device according to an embodiment of the present disclosure.

[0031] Hereinafter, embodiments for carrying out the present disclosure will be described in detail with reference to the drawings. Note that the present disclosure is not limited to the following embodiments. Furthermore, each drawing referred to in the following description merely shows a schematic representation of the shape, size, and positional relationship to the extent that the contents of the present disclosure can be understood. In other words, the present disclosure is not limited to only the shape, size, and positional relationship exemplified in each drawing. Furthermore, in the description of the drawings, the same parts are denoted by the same reference numerals.

[0032] (First Embodiment) [Overall Configuration of Medical Support System] Fig. 1 is a diagram showing the overall configuration of a medical support system according to a first embodiment of the present disclosure. The medical support system 1 shown in Fig. 1 includes a medical support device 10 and an endoscope management device 20.

[0033] The medical support device 10 extracts and analyzes specific words from the patient data by importing endoscopic-related procedure information from the endoscope management device 20, which includes endoscopic images captured by an endoscope, doctor's findings, and multiple characters related to at least one of endoscopic qualitative diagnosis and treatment.

[0034] The endoscope management device 20 records and manages endoscopic procedure information (hereinafter simply referred to as "endoscopic procedure information") including endoscopic images captured by an endoscope, doctor's findings, and multiple characters related to either endoscopic qualitative diagnoses or treatments, in addition to patient data. While Fig. 1 illustrates a single endoscope management device 20, this is not limiting and multiple endoscope management devices 20 may be used, or one or more endoscope management devices 20 may be provided for each facility. The endoscope management device 20 may be configured using, for example, a facility server or an endoscope server.

[0035] The medical support device 10 and the endoscope management device 20 are bidirectionally connected via a network N100. This network N100 may be configured to acquire endoscopic procedure information from the endoscope management device 20 via a storage medium such as a memory card, rather than via the network N100. The medical support device 10 may also be configured to perform part of its processing on a separate server (not shown) connected to the network.

[0036] [Functional Configuration of Medical Support Device] Next, a description will be given of the functional configuration of the medical support device 10. Fig. 2 is a block diagram showing the functional configuration of the medical support device 10. The medical support device 10 shown in Fig. 2 includes a communication unit 11, a display unit 12, an input unit 13, a database 14 (hereinafter simply referred to as "DB14"), a recording unit 15, and a control unit 16.

[0037] The communication unit 11, under the control of the control unit 16, transmits various types of information to the endoscope management device 20 via the network N100, and receives various types of information from the endoscope management device 20. The communication unit 11 is configured using a communication module.

[0038] The display unit 12 displays various information related to the medical support device 10 under the control of the control unit 16. The display unit 12 is configured using a liquid crystal display, an organic electroluminescent display (EL display), or the like.

[0039] The input unit 13 receives various inputs in response to external operations and outputs them to the control unit 16. The input unit 13 is configured using buttons, a keyboard, switches, a touch panel, and the like.

[0040] The DB 14 records various types of information. The DB 14 is configured using a hard disk drive (HDD), a solid state drive (SSD), etc. The DB 14 includes an endoscopic procedure information DB 140, a system setting DB 141, a standard term storage DB 142, and an attribute value storage DB 143.

[0041] The endoscope-related procedure information DB 140 records the endoscope-related procedure information that is acquired by a data acquisition unit 161 (described later) from the endoscope management device 20 via the communication unit 11 and the network N100.

[0042] FIG. 3 is a diagram showing an example of endoscopic procedure information recorded in the endoscopic procedure information DB 140. As shown in FIG.

[0043] The endoscopic procedure information D1 shown in FIG. 3 is data in a predetermined format, including data related to endoscopic qualitative diagnoses and procedures, including at least multiple characters (text, symbols, spaces, commas, etc.). The endoscopic procedure information D1 is, for example, JED (Japan Endoscopic Database) format data or CSV data. The endoscopic procedure information D1 is data formed by combining endoscopic examination types and output format types defined by the Japan Gastroenterological Endoscopy Society. Here, the endoscopic examination types include at least upper endoscopy, colonoscopy, small intestine endoscopy, and biliary-pancreatic endoscopy. The output formats include at least Type 1, Type 2, and Type 4. Furthermore, the endoscopic procedure information D1 includes qualitative diagnosis text data T1 and procedure text data T2. For example, the first line of the qualitative diagnosis text data T1 contains the following: "Suspected adenoma, description, macroscopic type: Type 0-1 (protruding), location: U, M." Furthermore, the first line of the procedure text data T2 stores "Biopsy...P1, P2." For simplicity of explanation, the patient data and doctor's findings data are omitted from the endoscopic procedure information D1 in FIG.

[0044] The system setting DB 141 stores system setting information that associates the character segmentation method, attributes, and additional information extracted from the endoscopic procedure information. The additional information includes lower-level information associated with the attributes, such as the attribute value "1" (first attribute) and the attribute value "2" (second attribute) of the JED format data.

[0045] FIG. 4 is a diagram showing an example of system setting information recorded in the system setting DB 141. As shown in FIG.

[0046] The system setting information T3 shown in FIG. 4 stores information for separating and extracting linking characters between items, linking characters between attributes, and linking characters between attributes and additional information related to endoscopic procedure information. Specifically, the system setting information T3 stores a division method, data, and remarks in association with each major item. For example, the division method "Inter-item division character," data ",", and remark "Half-width comma" are stored in association with the major item "Common" in the system setting information T3. Furthermore, the division method "Divide by character linking between attributes" and "Divide by character linking between attributes and additional information," data ",",","\s," and "...," and remark "Half-width comma," "Half-width comma," and "Half-width space" are stored in association with the major item "Standard term extraction" in the system setting information T3.

[0047] The standard term storage DB 142 stores standard terms for comparison with characters extracted from endoscopic procedure information.

[0048] 5 is a diagram showing an example of standard terms (qualitative diagnosis), and FIG. 6 is a diagram showing an example of standard terms (treatment).

[0049] The standard terminology T4 shown in Figure 5 and the standard terminology T5 shown in Figure 6 store terms (attributes) defined in the JED format. For example, in the first row of the standard terminology T4 shown in Figure 5, "adenoma" is stored in the standard terminology (qualitative diagnosis). Note that the standard terminology T4 shown in Figure 5 and the standard terminology T5 shown in Figure 6 show examples of terms (attributes) defined by the JED, but are not limited to these, and terms (attributes) defined in each industry can be set as standard terms as appropriate.

[0050] The attribute value storage DB 143 stores, as attribute values, specific words (divided characters) that the standard term extraction unit 164 has determined to match a standard term using the storage control unit 165 (described later).

[0051] The recording unit 15 is configured using a volatile memory, a non-volatile memory, a HDD, an SSD, etc. The recording unit 15 has a program recording unit 151.

[0052] The program recording unit 151 records various programs and parameters for operating the medical support device 10 .

[0053] The control unit 16 corresponds to the processor according to the present disclosure. The control unit 16 is implemented using a processor having hardware such as an FPGA (Field-Programmable Gate Array), a GPU (Graphics Processing Unit), or a CPU (Central Processing Unit), and a memory serving as a temporary storage area used by the processor. The control unit 16 comprehensively controls the components constituting the medical support device 10. The control unit 16 includes a data acquisition unit 161, a determination unit 162, a setting unit 163, a standard term extraction unit 164, a storage control unit 165, and an analysis unit 166.

[0054] The data acquisition unit 161 acquires endoscopic procedure information in a predetermined format, including a plurality of characters relating to at least one of a qualitative diagnosis and a treatment using an endoscope, from the endoscope management device 20 via the communication unit 11 .

[0055] The determination unit 162 determines whether or not there is data captured by the data capture unit 161. Specifically, the determination unit 162 determines whether or not there is one line of captured data for one lesion unit in the data captured by the data capture unit 161.

[0056] The setting unit 163 retrieves system setting information recorded in the system setting DB 141. Specifically, the setting unit 163 retrieves from the system setting DB 141 system setting information T3 (see FIG. 4 ) that stores information for dividing and extracting linked characters between items, linked characters between attributes, and linked characters between attributes and additional information related to endoscopic procedure information.

[0057] The standard term extraction unit 164 extracts specific words (segmented characters or character strings) by dividing the endoscopic-related procedure information using the system setting information T3. The standard term extraction unit 164 also determines whether the specific words (segmented characters) match standard terms. Furthermore, the standard term extraction unit 164 divides the endoscopic-related procedure information from the rear at characters that link attributes and additional information in accordance with the standard terms T4 (see FIG. 5 ) or standard terms T5 set by the setting unit 163.

[0058] The storage control unit 165 registers the specific word that the standard term extraction unit 164 has determined to match the standard term in the attribute value storage DB 143 as an attribute value.

[0059] The analysis unit 166 analyzes the attribute value accumulation data accumulated in the attribute value accumulation DB 143 and displays the analysis results on the display unit 12 .

[0060] [Details of the JED Format Database] Next, details of the JED format database for endoscopic procedure information will be described. Fig. 7 is a diagram showing an example of the JED format database for endoscopic procedure information.

[0061] Here, JED is a database specialized for endoscopy promoted by the Japan Society of Fire Extinguisher Endoscopy. In the JED-format format T10 of endoscopic procedure information shown in Figure 7, items, attributes, attribute "1" and attribute "2" are stored in association with each examination type. For example, the first line of the JED-format format T10 stores the examination type "upper endoscopy" in association with the item "neoplastic disease," attribute "tumor," and additional information "suspect," "describe (free input)."

[0062] However, there are multiple manufacturers that have systems capable of outputting JED format data, and each system has different output formats, term selection, and term input. For example, one manufacturer defines the attributes for gastric cancer diagnosis in its system as early gastric cancer and advanced gastric cancer. Meanwhile, another manufacturer defines the attribute as gastric cancer. As a result, the terminology used in the JED format T10 varies from manufacturer to manufacturer and system to system.

[0063] For this reason, in the past, when using the hierarchical structure of items, attributes, and additional information (attribute "1" and attribute "2") used appropriately in JED, it was difficult to determine which words in which locations should be analyzed (extracted). In other words, even when output in JED format, it was difficult to accurately extract, aggregate, and analyze all input terms due to the following two reasons. Reason 1 is that the delimiters used to separate hierarchies differ depending on the system or manufacturer. Reason 2 is that input methods, such as multiple choice or free input, are inconsistent depending on the system or manufacturer, resulting in inconsistent data.

[0064] Therefore, since the medical support device 10 outputs endoscopic terms in the JED format linked by items, attributes, and additional information (attributes "1" and "2"), one lesion per line, it can extract terms (character strings) linked to "attributes" as specific words from the endoscopic procedure information, and accurately extract and determine them by comparing the extracted terms (attribute values) with standard terms.

[0065] [Processing of Medical Support Device] Next, the processing executed by the medical support device 10 will be described. Fig. 8 is a flowchart showing an outline of the processing executed by the medical support device 10.

[0066] 8, the data acquisition unit 161 acquires endoscopic procedure information from the endoscope management device 20 via the communication unit 11 (step S101). For example, the data acquisition unit 161 acquires the above-mentioned endoscopic procedure information D1 (JED format data) shown in FIG. 3 from the endoscope management device 20 and records this endoscopic procedure information D1 in the endoscopic procedure information DB 140.

[0067] Next, the determination unit 162 determines whether or not there is data imported by the data import unit 161 (step S102). Specifically, the determination unit 162 determines whether or not there is one row of imported data, one row per lesion, in the data imported by the data import unit 161. If the determination unit 162 determines that there is data imported by the data import unit 161 (step S102: Yes), the medical support device 10 proceeds to step S103, which will be described later. On the other hand, if the determination unit 162 determines that there is no data imported by the data import unit 161 (step S102: No), the medical support device 10 ends this process.

[0068] In step S103, the setting unit 163 retrieves system setting information recorded in the system setting DB 141. Specifically, the setting unit 163 retrieves from the system setting DB 141 system setting information T3 (see FIG. 4 ) that stores information for dividing and extracting linked characters between items, linked characters between attributes, and linked characters between attributes and additional information related to endoscopic procedure information.

[0069] Next, the setting unit 163 retrieves the standard term information recorded in the standard term accumulation DB 142 (step S104). Specifically, the setting unit 163 retrieves the standard term T4 (see FIG. 5) and the standard term T5 (see FIG. 6) from the standard term accumulation DB 142.

[0070] Thereafter, the determination unit 162 determines whether the captured data captured by the data capturing unit 161 contains one row of captured data (step S105). If the determination unit 162 determines that the captured data captured by the data capturing unit 161 contains one row of captured data (step S105: Yes), the medical support device 10 proceeds to step S106, which will be described later. On the other hand, if the determination unit 162 determines that the captured data captured by the data capturing unit 161 does not contain one row of captured data (step S105: No), the medical support device 10 terminates this process.

[0071] In step S106, the standard term extraction unit 164 executes standard term processing to extract standard terms from one line of imported data.

[0072] [Details of Standard Term Extraction Processing] FIG. 9 is a sub-flowchart showing an outline of the standard term processing in step S106 of FIG.

[0073] As shown in Figure 9, the standard term extraction unit 164 divides the imported data of endoscopic procedure information imported by the data import unit 161 using the dividing characters of the linked characters in accordance with the system setting information T3 (see Figure 4) set by the setting unit 163, and obtains qualitative diagnostic strings of specific words (step S201).

[0074] Next, the standard term extraction unit 164 divides the imported data of the endoscopic procedure information imported by the data import unit 161 at characters that connect attributes according to the system setting information T3 set by the setting unit 163 (step S202).

[0075] Thereafter, the standard term extraction unit 164 determines whether the specific word matches the standard term loaded into the setting unit 163 (step S203). If the standard term extraction unit 164 determines that the specific word matches the standard term loaded into the setting unit 163 (step S203: Yes), the medical support device 10 proceeds to step S208, which will be described later. On the other hand, if the standard term extraction unit 164 determines that the specific word does not match the standard term loaded into the setting unit 163 (step S203: No), the medical support device 10 proceeds to step S204, which will be described later.

[0076] In step S204, the standard term extraction unit 164 divides the imported data of endoscopic procedure information imported by the data import unit 161 from the back using characters that link attributes and additional information, in accordance with the system setting information T3 set by the setting unit 163.

[0077] In step S205, the standard term extraction unit 164 determines whether the captured data of endoscopic-related procedure information was able to be segmented from the rear by the characters that link the attributes and additional information. If the standard term extraction unit 164 determines that the captured data of endoscopic-related procedure information was able to be segmented from the rear by the characters that link the attributes and additional information (step S205: Yes), the medical support device 10 proceeds to step S206. On the other hand, if the standard term extraction unit 164 determines that the captured data of endoscopic-related procedure information was not able to be segmented from the rear by the characters that link the attributes and additional information (step S205: No), the medical support device 10 proceeds to step S207, which will be described later.

[0078] In step S206, the standard term extraction unit 164 extracts the first divided character from the extracted characters divided from the rear as a specific word. After step S206, the medical support device 10 returns to step S203.

[0079] In step S207, the standard term extraction unit 164 determines whether all processing has been completed for the specific words generated during the segmentation in step S202. If it is determined that the standard term matching determination for all specific words extracted by the standard term extraction unit 164 through segmentation using characters associated with each attribute has been completed (step S207: Yes), the medical support device 10 returns to the main routine of FIG. 8 and proceeds to step S107. On the other hand, if it is determined that the standard term matching determination for all specific words extracted by the standard term extraction unit 164 through segmentation using characters associated with each attribute has not been completed (step S207: No), the medical support device 10 returns to step S203.

[0080] In step S208, the storage control unit 165 registers the specific word determined to match the standard term in step S203 in the attribute value storage DB 143. For example, in the case shown in FIG. 10 , the standard term extraction unit 164 stores and registers the attribute of the first line of the qualitative diagnostic text data T1 as "adenoma" in the attribute value storage DB 143 because the specific word "adenoma" matches the standard term T4 "adenoma." After step S208, the medical support device 10 proceeds to step S207. Note that while the flow in FIG. 9 has been described as an example of a qualitative diagnostic string, a similar flow is also executed for treatment strings.

[0081] [Specific Example of Standard Term Extraction Processing] Here, a specific example of the standard term extraction processing performed by the standard term extraction unit 164 will be described. Figure 10 is a diagram for schematically explaining an example of the standard term extraction processing performed by the standard term extraction unit 164.

[0082] 10 , the standard term extraction unit 164 extracts and divides the first line of the qualitative diagnostic text data T1 as a qualitative diagnostic character string in accordance with the system setting information T3 (see FIG. 4 ), which divides the data by the dividing character of linked characters set by the setting unit 163 (process “1”). In this case, the standard term extraction unit 164 attempts to divide “suspected adenoma, describe, macroscopic type: 0-1 type (protruding type), occupied area: U, M” by dividing the data based on the half-width comma “,” in the system setting information T3, which divides the data by the character connecting attributes. However, since the character does not contain a half-width comma “,”, the standard term extraction unit 164 extracts the original character string “suspected adenoma, describe, macroscopic type: 0-1 type (protruding type), occupied area: U, M.”

[0083] Next, the standard term extraction unit 164 determines whether the specific words "suspected adenoma, describe, macroscopic type: type 0-1 (protruding type), location: U, M" exactly match the standard term T4 (see FIG. 5). The standard term extraction unit 164 determines that the specific word does not exactly match the standard term, for example, because the specific word does not exactly match "adenoma" in the standard term T4 (process "2").

[0084] The standard term extraction unit 164 then divides the remarks in the system setting information T3 based on the half-width space "￥s" (half-width space) and "...", and extracts the attribute and additional information from the end of "adenoma, suspected, describe, macroscopic type: 0-1 type (protruding), location: U, M" by using characters that link the attribute and additional information. The standard term extraction unit 164 then extracts the first divided characters from the extracted end as a specific word (process "3"). Specifically, in FIG. 10, the standard term extraction unit 164 extracts the first specific word, "adenoma."

[0085] Next, the standard term extraction unit 164 determines whether the specific word "adenoma" exactly matches standard term T4 (see FIG. 5). For example, since "adenoma" in standard term T4 exactly matches, the standard term extraction unit 164 acquires the specific word "adenoma" as an attribute (process "4").

[0086] The standard term extraction unit 164 determines whether all character strings separated by characters connecting attributes have been processed. Specifically, since the only character string separated by characters connecting attributes is "suspected adenoma,,describe,,macroscopic type: type 0-1 (protruding type),,occupation area: U,,M," it is determined that all character strings have been processed.

[0087] FIG. 11 is a diagram for explaining another example of the standard term extraction process performed by the standard term extraction unit 164. In FIG.

[0088] 11 , the standard term extraction unit 164 extracts and divides the second line of the qualitative diagnostic text data T1 as a qualitative diagnostic character string in accordance with the system setting information T3 (see FIG. 4 ) set by the setting unit 163 for dividing by the dividing character of linked characters (process "1"). In this case, the standard term extraction unit 164 divides the data based on the half-width comma "," in the system setting information T3 for dividing by the character connecting attributes. In this case, the standard term extraction unit 164 divides and extracts the entire content of "adenoma XX" as a qualitative diagnostic character string.

[0089] Next, the standard term extraction unit 164 determines whether the specific word "adenoma XX" exactly matches the standard term T4 (see FIG. 5). Since the specific word does not exactly match any of the standard terms T4, the standard term extraction unit 164 determines that the specific word does not exactly match the standard term (process "2").

[0090] Thereafter, the standard term extraction unit 164 attempts to split the string from the back at the characters that link the attribute and additional information, using the half-width spaces "\s" and "..." in the remarks of the system setting information T3 as criteria. In this case, the standard term extraction unit 164 determines that "adenoma XX" cannot be split (process "3"). Then, the standard term extraction unit 164 ends the process because the only character string split by the characters that link the attribute is "adenoma XX."

[0091] FIG. 12 is a diagram for explaining another example of the standard term extraction process performed by the standard term extraction unit 164. In FIG.

[0092] 12 , the standard term extraction unit 164 extracts and divides the second line of the procedure text data T2 as a procedure character string in accordance with the system setting information T3 (see FIG. 4 ), which divides the data by the dividing character of linked characters set by the setting unit 163 (process "1"). In this case, the standard term extraction unit 164 divides the data based on the half-width comma "," in the system setting information T3, which divides the data by the character connecting attributes, thereby extracting "Biopsy...P1,P2,Mucosal resection, Endoscopic total resection, Relative total resection, Snare" as "Biopsy...P1," "P2," and "Mucosal resection, Endoscopic total resection, Relative total resection, Snare" (process "1").

[0093] Next, the standard term extraction unit 164 performs the following process for each of "Biopsy...P1" (a), "P2" (b), and "Mucosal resection endoscopic complete resection, relatively complete resection, snare" (c).

[0094] First, the case of "biopsy...P1" (a) will be described. The standard term extraction unit 164 determines whether the specific word "biopsy...P1" exactly matches the standard term T5 (procedure) (see FIG. 6). Because the specific word "biopsy...P1" does not exactly match any of the standard terms T5, the standard term extraction unit 164 determines that the specific word does not exactly match the standard term (process "2").

[0095] The standard term extraction unit 164 then divides the remarks in the system setting information T3 based on the half-width space "￥s" (half-width space) and "...", and extracts "biopsy...P1" by dividing it from the end into "biopsy" and "P1" using characters that link attributes and additional information. The standard term extraction unit 164 then acquires the first divided character from the extracted characters divided from the end as a specific word (process "3"). Specifically, the standard term extraction unit 164 acquires the first divided character, "biopsy", as a specific word.

[0096] Next, the standard term extraction unit 164 determines whether the specific word "biopsy" exactly matches the standard term T5 (see FIG. 6). For example, since the specific word "biopsy" exactly matches the standard term T5, the standard term extraction unit 164 acquires the specific word "biopsy" as an attribute (process "4").

[0097] Next, the case of "P2" (b) will be described. The standard term extraction unit 164 determines whether the specific word "P2" exactly matches the standard term T5 (treatment) (see FIG. 6). Because the specific word "P2" does not exactly match any of the standard terms T5, the standard term extraction unit 164 determines that the specific word does not exactly match the standard term (process "2").

[0098] Next, the standard term extraction unit 164 divides the remarks in the system setting information T3 based on the half-width spaces "\s" and "...", and attempts to divide the specific word "P2" from the rear using the characters that link the attribute and additional information. In this case, the standard term extraction unit 164 determines that the specific word "P2" cannot be divided (process "3").

[0099] The standard term extraction unit 164 ends the process because the character string divided by the characters linking the attributes is only the specific word "P2."

[0100] Next, the case of "mucosal resection, endoscopic complete resection, relatively complete resection, snare" (c) will be described. The standard term extraction unit 164 determines whether the specific words "mucosal resection, endoscopic complete resection, relatively complete resection, snare" exactly match the standard term T5 (procedure) (see FIG. 6). Because the specific words "mucosal resection, endoscopic complete resection, relatively complete resection, snare" do not exactly match any of the standard terms T5, the standard term extraction unit 164 determines that the specific words do not exactly match the standard terms (process "2").

[0101] Next, the standard term extraction unit 164 divides the remarks in the system setting information T3 based on the half-width spaces "\s" and "...", and extracts "mucosal resection, endoscopic complete resection, relatively complete resection, snare" by dividing it into "mucosal resection" and "endoscopic complete resection, relatively complete resection, snare" from the end using the characters that link the attributes and additional information.The standard term extraction unit 164 then acquires the first divided character from the extracted characters divided from the end as a specific word (process "3"). Specifically, in FIG. 12, the standard term extraction unit 164 acquires the first divided character, "mucosal resection," as a specific word.

[0102] Thereafter, the standard term extraction unit 164 determines whether the specific word "mucosal resection" exactly matches any of the standard terms T5 (see FIG. 6). The standard term extraction unit 164 determines that the specific word "mucosal resection" does not exactly match any of the standard terms T5 (see FIG. 6) (process "4").

[0103] Next, the standard term extraction unit 164 divides "mucosal resection" from the end based on the half-width spaces "\s" and "..." in the remarks of the system setting information T3, and extracts and acquires "mucosal resection" as the preceding character string (process "5"). In this case, the standard term extraction unit 164 determines that the preceding character string "mucosal resection" cannot be divided any further.

[0104] FIG. 13 is a diagram for explaining another example of the standard term extraction process performed by the standard term extraction unit 164. In FIG.

[0105] The standard term extraction unit 164 extracts and divides the fifth line of the treatment text data T2 as a treatment character string in accordance with the half-width comma "," in the remarks of the system setting information T3 (see FIG. 4 ), which divides the text by the dividing character of the linked characters set by the setting unit 163 (process "1"). In this case, the standard term extraction unit 164 divides the text based on the half-width comma "," in the system setting information T3, which divides the text by the character connecting attributes, and extracts "Biopsy, Cold Snare Polypectomy (3 or more), Endoscopic Complete Resection, Relative Complete Resection, Resected, but Follow-up Required for a Period of Time" as "Biopsy," "Cold Snare Polypectomy (3 or more), Endoscopic Complete Resection, Relative Complete Resection, Resected, but," and "Follow-up Required for a Period of Time" (process "1"). Note that since "biopsy" is the same process as that shown in FIG. 12 described above, detailed explanation will be omitted. Below, we will explain "Cold snare polypectomy (three or more) endoscopic complete resection, relatively complete resection, resected but" and "needs follow-up observation for a while."

[0106] First, the case of "Cold snare polypectomy (3 or more) endoscopic complete resection, relatively complete resection, resected, but" (a) will be described. The standard term extraction unit 164 determines whether the specific words "Cold snare polypectomy (3 or more) endoscopic complete resection, relatively complete resection, resected, but" exactly match any of the standard terms T5 (treatment) (see FIG. 6). Because the specific words "Cold snare polypectomy (3 or more) endoscopic complete resection, relatively complete resection, resected, but" do not exactly match any of the standard terms T5 (treatment) (see FIG. 6), the standard term extraction unit 164 determines that the specific words do not exactly match any of the standard terms (process "2").

[0107] Next, the standard term extraction unit 164 divides the remarks in the system setting information T3 based on the half-width spaces "\s" and "...", and attempts to divide "Cold snare polypectomy (3 or more) endoscopic complete resection, relatively complete resection, resected, but" from the end using characters that link the attributes and additional information. In this case, the standard term extraction unit 164 extracts the specific word "Cold snare polypectomy (3 or more)" (process "3").

[0108] Thereafter, the standard term extraction unit 164 determines whether the specific word "Cold Snare Polypectomy (3 or more)" exactly matches any of the standard terms T5 (see FIG. 6). The standard term extraction unit 164 determines that the specific word "Cold Snare Polypectomy (3 or more)" does not exactly match any of the standard terms T5 (process "4").

[0109] Next, the standard term extraction unit 164 divides the remarks in the system setting information T3 based on the half-width spaces "\s" and "...", and extracts "Cold Snare Polypectomy (3 or more)" by dividing it from the end using the characters that link the attributes and additional information, into "Cold Snare" and "Polypectomy (3 or more)".The standard term extraction unit 164 then acquires the first divided characters from the extracted characters divided from the end as a specific word (process "5"). Specifically, the standard term extraction unit 164 extracts the first specific word, "Cold Snare" (process "5").

[0110] Thereafter, the standard term extraction unit 164 determines whether the specific word "Cold Snare" exactly matches any of the standard terms T5 (see FIG. 6). The standard term extraction unit 164 determines that the specific word "Cold Snare" does not exactly match any of the standard terms T5 (process "6").

[0111] Next, the standard term extraction unit 164 divides the remarks in the system setting information T3 based on the half-width spaces "\s" and "...", and extracts "Cold Snare" by dividing it from the rear by the characters that link the attribute and additional information.The standard term extraction unit 164 then acquires the front divided characters from the extracted characters divided from the rear as a specific word (process "7"). Specifically, the standard term extraction unit 164 extracts the front specific word "Cold" (process "7").

[0112] Thereafter, the standard term extraction unit 164 determines whether the specific word "Cold" exactly matches any of the standard terms T5 (see FIG. 6). The standard term extraction unit 164 determines that the specific word "Cold" does not exactly match any of the standard terms T5 (process "8").

[0113] Next, using the half-width spaces "\s" and "..." in the remarks of the system setting information T3 as criteria, the standard term extraction unit 164 attempts to split "Cold" from the rear using characters that link the attribute and additional information. In this case, the standard term extraction unit 164 determines that the specific word "Cold" cannot be split (process "9").

[0114] The segmented characters processed in S202 above still contain "needs to be monitored for a while" (determined in S207 above), so the case of "needs to be monitored for a while" will now be described. The standard term extraction unit 164 determines whether "needs to be monitored for a while" exactly matches any of the standard terms T5 (treatment) (see FIG. 6 ). Because "needs to be monitored for a while" does not exactly match any of the standard terms T5, the standard term extraction unit 164 determines that the specific word does not exactly match a standard term (process "2").

[0115] Next, the standard term extraction unit 164 attempts to split "needs to be monitored for a while" from the end using the half-width spaces "\s" and "..." in the remarks of the system setting information T3 as criteria. In this case, the standard term extraction unit 164 determines that the specific word "needs to be monitored for a while" cannot be split (process "3").

[0116] Thereafter, the standard term extraction unit 164 ends the standard term extraction process because the string divided by the characters linking the attributes has reached the specific word "needs to be monitored for a while" and has completed processing of all the specific words (divided characters) divided in the above-mentioned step S202, specifically, "biopsy," "cold snare polypectomy (3 or more) endoscopic complete resection, relatively complete resection, resected, but," and "needs to be monitored for a while."

[0117] 8, the description of step S107 and subsequent steps will be continued. In step S107, the analysis unit 166 analyzes the attribute value accumulation data accumulated in the attribute value accumulation DB 143, and displays the analysis results on the display unit 12.

[0118] 14 is a diagram showing an example of the analysis results obtained by the analysis unit 166. As shown in Fig. 14, the analysis unit 166 analyzes the treatment information included in the attribute value accumulation data based on the attribute value accumulation data accumulated in the attribute value accumulation DB 143, analyzes the examination ratio using attribute items in the second hierarchy, and displays the analysis result P1 on the display unit 12. This allows users such as doctors to intuitively understand the examination ratio.

[0119] 15 is a diagram showing another example of the analysis results obtained by the analysis unit 166. As shown in FIG. 15, the analysis unit 166 analyzes the qualitative diagnostic information included in the attribute value accumulation data based on the attribute value accumulation data accumulated in the attribute value accumulation DB 143, further classifies the data into "cancer" and "adenoma" based on the extracted second-level attribute items, and displays an analysis result P2 obtained by analyzing the diagnostic rate (number of tests diagnosed / total number of tests) on the display unit 12. This allows users such as doctors to intuitively understand the diagnostic rate.

[0120] 16 is a diagram showing another example of the analysis results obtained by the analysis unit 166. As shown in Fig. 16, the analysis unit 166 analyzes various information including each examination item, the number of examinations, the number of biopsies, findings, etc. based on the endoscope-related procedure information acquired from the endoscope management device 20, and displays the analysis results P3 on the display unit 12. This allows users such as doctors to intuitively understand the number of examinations.

[0121] 17 is a diagram showing another example of the analysis results obtained by the analysis unit 166. As shown in Fig. 17, the analysis unit 166 displays an analysis result P4 relating to adenoma analysis on the display unit 12 based on the endoscope-related procedure information acquired from the endoscope management device 20. This allows users such as doctors to intuitively understand the number of tests according to attributes.

[0122] 18 is a diagram showing another example of the analysis results obtained by the analysis unit 166. As shown in FIG. 18, the analysis unit 166 analyzes various information, including each examination item, the number of examinations, the number of biopsies, and findings, based on the endoscope-related procedure information acquired from the endoscope management device 20, and displays the analysis results P5 on the display unit 12. This allows a user, such as a doctor, to intuitively understand the number of examinations. After step S108, the medical support device 10 returns to step S105.

[0123] According to the embodiment 1 described above, the accumulation control unit 165 registers specific words that are determined to match the standard terms extracted by the standard term extraction unit 164 as attribute values ​​in the attribute value accumulation DB 143, thereby making it possible to accurately extract terms to be used in analysis.

[0124] Furthermore, according to the first embodiment, the analysis unit 166 analyzes and displays the attribute value accumulation data accumulated by the attribute value accumulation DB 143 on the display unit 12, so that users such as doctors can intuitively grasp the examination rate.

[0125] In the first embodiment, a specific word determined as an attribute value by analysis is stored in the attribute value storage DB 143, but the present invention is not limited to this. For example, in the first embodiment, a specific word determined as an attribute value may be output to another system or server and used for processing, analysis, etc., without being stored in the present device.

[0126] In addition, in the first embodiment, the standard term extraction unit 164 divides the endoscopic-related procedure information from the rear by characters that link attributes and additional information in accordance with the standard term T4 (see FIG. 5 ) or standard term T5 set by the setting unit 163. However, the present invention is not limited to this, and for example, specific words to be evaluated may be obtained by sequentially removing information added to the rear. Specifically, the standard term extraction unit 164 may divide all of the endoscopic-related procedure information and sequentially combine the evaluation targets.

[0127] In the first embodiment, step S107 of analyzing and displaying the data is connected in series with the data processing, but this is not limiting. For example, after completing the data import process as the flow returning from S106 to S105, step S107 may analyze and analyze the data stored in the attribute value storage DB 143 as a separate flowchart.

[0128] (Embodiment 2) Next, embodiment 2 will be described. In the above-described embodiment 1, it was determined whether or not the specific word extracted by the standard terminology extraction unit 164 matches the standard terminology. However, in embodiment 2, if the specific word does not match the standard terminology, it is determined whether or not the specific word is a facility-specific terminology. If it is a facility-specific terminology, this specific word is determined to be a facility-specific terminology and stored. Therefore, hereinafter, the functional configuration of the medical support device according to embodiment 2 will be described, followed by a description of the processing executed by the medical support device according to embodiment 2. Note that the same components as those in the medical support device 10 according to embodiment 1 above will be assigned the same reference numerals, and detailed description thereof will be omitted.

[0129] [Functional Configuration of Medical Support Device] Fig. 19 is a block diagram showing the functional configuration of a medical support device according to embodiment 2. The medical support device 10A shown in Fig. 19 includes a DB 14A and a control unit 16A instead of the DB 14 and the control unit 16 of the medical support device 10 according to embodiment 1 described above.

[0130] The DB 10A records various types of information. The DB 14A is configured using an HDD, an SSD, etc. The DB 10A has a system setting DB 141A instead of the system setting DB 141 of the DB 1A according to the first embodiment described above.

[0131] The system setting DB 141A records system setting information that associates a method for dividing characters of a specific word extracted from endoscopic procedure information, attributes, and additional information.

[0132] FIG. 20 is a diagram showing an example of system setting information recorded in the system setting DB 141A.

[0133] The system setting information T31 shown in FIG. 20 stores information for separating and extracting linking characters between items, linking characters between attributes, and linking characters between attributes and additional information related to endoscopic procedure information. Specifically, the system setting information T31 stores a division method, data, and remarks in association with each major item. For example, the division method "Inter-item division character," data ",", and remark "Half-width comma" are stored in association with the major item "Common" in the system setting information T31. Furthermore, the division method "Separate by characters linking attributes" and "Separate by characters linking attributes and additional information" are stored in association with the major item "Standard Terminology Extraction Facility-Specific Extraction" in the system setting information T31.

[0134] The control unit 16A corresponds to the processor according to the present disclosure. The control unit 16A is realized using a processor having hardware such as a GPU or CPU, and a memory that is a temporary storage area used by the processor. The control unit 16A comprehensively controls each unit constituting the medical support device 10A. The control unit 16A includes a storage control unit 165A instead of the storage control unit 165. Furthermore, the control unit 16A further includes a facility-specific term extraction unit 167 in addition to the configuration of the control unit 16 according to the first embodiment described above.

[0135] The storage control unit 165A registers specific words that the standard term extraction unit 164 has determined to match standard terms as attribute values ​​in the attribute value storage DB 143. The storage control unit 165A also registers specific words that the facility-specific term extraction unit 167 has determined to match the facility-specific term extraction conditions as attribute values ​​in the standard term storage DB 142 and the attribute value storage DB 143.

[0136] The facility-specific terminology extraction unit 167 extracts and acquires divided characters that are specific words of facility-specific terminology by dividing the endoscopic procedure information using the system setting information T31.

[0137] As described in the first embodiment, there are multiple manufacturers with systems capable of outputting JED-format data, and each system has its own output format, term selection, and term input. For this reason, it was previously difficult to determine which location should be analyzed (extracted) in the hierarchical structure of items, attributes, and additional information (attributes "1" and "2") used appropriately in JED. Furthermore, in addition to reasons 1 and 2 mentioned above, there was a desire for further aggregation and analysis of facility-specific terms due to reason 3. Reason 3 is that term names are changed based on the preferences of users, such as doctors, and therefore do not necessarily match the names of the additional information (items, attributes, attributes "1" and "2") defined in the JED format exactly.

[0138] Therefore, because the medical support device 10A outputs endoscopic terms in the JED format linked by items, attributes, and additional information (attributes "1" and "2"), one lesion per line, it determines the extracted specific word string terms (attribute values) as facility-specific terms, accumulates them, and registers them, even if the terms do not match the standard terms. This allows the medical support device 10A to further contribute to improving the quality of medical care and providing the best possible medical care to patients.

[0139] [Processing of Medical Support Device] Next, the processing executed by the medical support device 10A will be described. Fig. 21 is a flowchart showing an outline of the processing executed by the medical support device 10A. Steps S301 to S305 and step S309 in Fig. 21 correspond to steps S101 to S105 and step S107, respectively, in Fig. 8 described above, but steps S306 to S308 are different. For this reason, steps S306 to S308 will be described below.

[0140] In step S306, the standard term extraction unit 164 executes standard term processing to extract standard terms from one line of imported data.

[0141] [Details of Standard Term Extraction Processing] FIG. 22 is a sub-flowchart showing an outline of the standard term processing in step S306 of FIG.

[0142] 22 are similar to steps S201 to S208 in Fig. 9, respectively, but the processing performed on the captured data of endoscopic procedure information differs from that in the above-described embodiment 1. For this reason, a specific example of standard term extraction processing by the standard term extraction unit 164 will be described below.

[0143] [Specific Example of Standard Term Extraction Processing] FIG. 23 is a diagram for schematically explaining an example of standard term extraction processing by the standard term extraction unit 164. In FIG.

[0144] 23, the standard term extraction unit 164 performs processes "1" to "4" similar to those shown in Fig. 10 on the first line of the qualitative diagnostic text data T1 in accordance with the system setting information T3 (see Fig. 4) for dividing by the dividing character of linked characters set by the setting unit 163. In the case shown in Fig. 23, the standard term extraction unit 164 determines whether the specific word "adenoma" exactly matches the standard term T4 (see Fig. 5), and since "adenoma" in the standard term T4 exactly matches, the standard term extraction unit 164 acquires the specific word "adenoma" as an attribute.

[0145] The standard term extraction unit 164 determines whether all the character strings separated by the characters connecting the attributes have been processed. Specifically, since the only character string separated by the characters connecting the attributes is "suspected adenoma,,describe,,macroscopic type: type 0-1 (protruding type),,occupation area: U,,M," it is determined that all the character strings have been processed.

[0146] FIG. 24 is a diagram for explaining another example of the standard term extraction process performed by the standard term extraction unit 164. In FIG.

[0147] 24, the standard term extraction unit 164 performs processes "1" to "3" similar to those shown in FIG. 11 on the second line of the qualitative diagnostic text data T1 in accordance with the system setting information T3 (see FIG. 4) for dividing the text by the dividing character of the linked character set by the setting unit 163. The standard term extraction unit 164 then determines that the specific word "adenoma XX" cannot be divided because it does not exactly match any of the standard terms T4 (see FIG. 5), and outputs the character string "adenoma XX" resulting from process "1" to the facility-specific term extraction unit 167 (described later) (process "process 4"). The standard term extraction unit 164 then terminates the process because the only character string divided by the linked character is "adenoma XX."

[0148] FIG. 25 is a diagram for explaining another example of the standard term extraction process performed by the standard term extraction unit 164. In FIG.

[0149] 25, the standard term extraction unit 164 performs the same process "1" as in FIG. 12 on the second line of the procedure text data T2 to extract and separate the procedure character string (process "1") in accordance with the system setting information T3 (see FIG. 4) set by the setting unit 163 for separating linked characters by a dividing character. In this case, the standard term extraction unit 164 separates the string based on the half-width comma "," in the system setting information T3 for separating attributes by a character connecting them, thereby extracting "Biopsy...P1,P2,Mucosal resection, Endoscopic total resection, Relative total resection, Snare" as "Biopsy...P1," "P2," and "Mucosal resection, Endoscopic total resection, Relative total resection, Snare."

[0150] Next, the standard term extraction unit 164 performs the following process for each of "Biopsy...P1" (a), "P2" (b), and "Mucosal resection endoscopic complete resection, relatively complete resection, snare" (c).

[0151] First, the case of "biopsy...P1" (a) will be described. The standard term extraction unit 164 performs processes "2" to "4" similar to those shown in FIG. 12 on the specific word "biopsy...P1" (a). In the case shown in FIG. 25, the standard term extraction unit 164 acquires the first divided character from the extracted characters divided from the rear as the specific word, and determines whether the acquired specific word "biopsy" exactly matches the standard term T5 (see FIG. 6). Since it exactly matches the standard term T5 "biopsy," the specific word "biopsy" is acquired as an attribute.

[0152] Next, the case of "P2" (b) will be described. The standard term extraction unit 164 performs processes "2" to "3" on the specific word "P2" in the same manner as in FIG. 12 described above. Then, since the specific word "P2" does not exactly match any of the standard terms T5 (see FIG. 5) and the standard term extraction unit 164 attempts to split the specific word "P2" from the rear using characters that link attributes and additional information but is unable to do so, the standard term extraction unit 164 outputs the character string "P2" resulting from process "1" to the facility-specific term extraction unit 167 (described later) (process "4").

[0153] Next, the case of "Mucosal resection, endoscopic complete resection, relatively complete resection, snare" (c) will be explained.

[0154] The standard term extraction unit 164 performs processes "2" to "5" on the specific word "mucosal resection, endoscopic complete resection, relatively complete resection, snare" in the same manner as in Fig. 12. Then, because the specific word "mucosal resection" does not exactly match any of the standard terms T5 (see Fig. 5), the standard term extraction unit 164 attempts to split it from the back using characters that link the attribute and additional information, but is unable to do so. Therefore, it outputs the character string resulting from process "1," "mucosal resection, endoscopic complete resection, relatively complete resection, snare," to the facility-specific term extraction unit 167 (described later) (process "6").

[0155] FIG. 26 is a diagram for explaining another example of the standard term extraction process performed by the standard term extraction unit 164. In FIG.

[0156] The standard term extraction unit 164 extracts and divides the fifth line of the treatment text data T2 as a treatment character string in accordance with the half-width comma "," in the remarks of the system setting information T3 (see FIG. 4 ), which divides the text by the dividing character of the linked characters set by the setting unit 163 (process "1"). In this case, the standard term extraction unit 164 divides the text based on the half-width comma "," in the system setting information T3, which divides the text by the character connecting attributes, and extracts "Biopsy, Cold Snare Polypectomy (3 or more), Endoscopic Complete Resection, Relative Complete Resection, Resected, but Follow-up Required for a Period of Time" as "Biopsy," "Cold Snare Polypectomy (3 or more), Endoscopic Complete Resection, Relative Complete Resection, Resected, but," and "Follow-up Required for a Period of Time" (process "1"). Note that since "biopsy" is the same process as that shown in FIG. 12 described above, detailed explanation will be omitted. Below, we will explain "Cold snare polypectomy (three or more) endoscopic complete resection, relatively complete resection, resected but" and "needs follow-up observation for a while."

[0157] First, the case of "Cold snare polypectomy (three or more), endoscopic complete resection, relatively complete resection, resected, but" (a) will be described. As shown in FIG. 26 , the standard term extraction unit 164 performs processes "2" to "9" similar to those shown in FIG. 13 on the specific word "Cold snare polypectomy (three or more), endoscopic complete resection, relatively complete resection, resected, but." Then, based on the half-width spaces "￥s" and "..." in the remarks of the system setting information T3, the standard term extraction unit 164 attempts to split the specific word "Cold" from the rear using characters that link attributes and additional information. Since this splitting is not possible, the standard term extraction unit 164 outputs the character string resulting from process "1," "Cold snare polypectomy (three or more), endoscopic complete resection, relatively complete resection, resected, but" to the facility-specific term extraction unit 167 (described later) (process "10").

[0158] Next, the case of "needs to be monitored for a while" will be described. Similarly, the standard term extraction unit 164 performs processes "2" to "3" similar to those shown in FIG. 13 on the specific word "needs to be monitored for a while." Then, the standard term extraction unit 164 attempts to split "needs to be monitored for a while" from the rear using characters that link attributes and additional information, based on the half-width spaces "\s" and "..." in the remarks of the system setting information T3. Since this fails to split the string, the result of process "1," "needs to be monitored for a while," is output to the facility-specific term extraction unit 167 (described later) (process "4").

[0159] 21 , the description of step S307 and subsequent steps continues. In step S307, the facility-specific term extraction unit 167 executes a facility-specific term extraction process for extracting facility-specific terms from the imported data (specific words) that is imported by the data import unit 161 and that is divided by the standard term extraction unit 164.

[0160] [Facility-specific term extraction processing] Fig. 27 is a sub-flowchart showing an overview of the facility-specific term extraction processing in step S307 of Fig. 21. Fig. 28 is a diagram schematically illustrating an example of the facility-specific term extraction processing performed by the facility-specific term extraction unit 167.

[0161] 27 , the facility-specific terminology extraction unit 167 determines whether the specific word input from the standard terminology extraction unit 164 matches the facility-specific terminology extraction condition in accordance with the system setting information T31 set by the setting unit 163 (step S501). Specifically, as shown in FIG. 28 , the facility-specific terminology extraction unit 167 uses the half-width commas "," and "..." in the system setting information T31 as criteria to divide the specific words "P2" and "mucosal resection endoscopic complete resection, relatively complete resection, snare" that were input after being split by the standard terminology extraction unit 164, starting from the back at the characters that link the attribute and additional information, extracts and acquires the specific word "mucosal resection" as the preceding character string, and determines whether this "mucosal resection" matches the facility-specific terminology extraction condition. If the facility-specific terminology extraction unit 167 determines that the specific word input from the standard terminology extraction unit 164 matches the facility-specific terminology extraction condition (step S501: Yes), the medical support device 10A proceeds to step S502, which will be described later. On the other hand, if the facility-specific terminology extraction unit 167 determines that the specific word input from the standard terminology extraction unit 164 does not match the facility-specific terminology extraction condition (step S501: No), the medical support device 10A returns to the main routine of FIG. 21 and proceeds to step S308.

[0162] In step S502, the storage control unit 165 registers the character string acquired by the facility-specific term extraction unit 167 in step S501 in the standard term storage DB 142. Specifically, as shown in FIG. 28 , the storage control unit 165 registers "mucosal resection" as a new standard term (procedure) in the standard term T4 recorded in the standard term storage DB 142.

[0163] Next, the storage control unit 165A registers the character string acquired by the facility-specific term extraction unit 167 in step S501 in the attribute value storage DB 143 (step S503).

[0164] FIG. 29 is a diagram showing an example of data (bold parts are stored as attribute values) input when storing attribute values ​​of imported data in the attribute value storage DB 143. FIG. 30 is a diagram showing an example of standard terms (qualitative diagnoses) stored in the standard term storage DB 142. FIG. 31 is a diagram showing an example of standard terms (treatments) stored in the standard term storage DB 142. FIG. 32 is a diagram showing an example of qualitative diagnoses and treatments of attribute values ​​stored in the attribute value storage DB 143.

[0165] As shown in the accumulated data table T20 of Fig. 29, the standard term (qualitative diagnosis) data table T21 of Fig. 30, the standard term (treatment) data table T22 of Fig. 31, and the attribute value tables T23 for qualitative diagnosis and treatment of attribute values ​​of Fig. 32, the accumulation control unit 165 accumulates the attribute values ​​extracted by the standard term extraction unit 164 and the facility-specific term extraction unit 167. After step S503, the medical support device 10A returns to the main routine of Fig. 21 and proceeds to step S308.

[0166] Returning to FIG. 21 , the description of step S308 and subsequent steps will be continued. In step S308, the facility-specific terminology extraction unit 167 determines whether all processing for the specific words generated during the division has been completed. If the facility-specific terminology extraction unit 167 determines that all processing for the specific words generated during the division has been completed (step S308: Yes), the medical support device 10A proceeds to step S309. On the other hand, if the facility-specific terminology extraction unit 167 determines that all processing for the specific words generated during the division has not been completed (step S308: No), the medical support device 10A returns to step S306.

[0167] According to the above-described embodiment 2, in addition to the effects of the above-described embodiment 1, the accumulation control unit 165A accumulates the attribute values ​​extracted by the facility-specific term extraction unit 167, so that even if a specific word that is different from a standard term is extracted, it can be accumulated as a facility-specific term, and as a result, the terms to be used in the analysis can be accurately extracted.

[0168] In this embodiment, the system setting information T3 (see FIG. 4) and the system setting information T31 (see FIG. 20) are treated as independent pieces of information. However, in an actual configuration, it is generally not necessary to use different divided characters in the standard terminology extraction unit 164 and the facility-specific terminology extraction unit 167. Therefore, these may be treated as the same information. In this case, the same effect can be obtained with a simpler configuration.

[0169] (Embodiment 3) Next, embodiment 3 of the present disclosure will be described. In the above-described embodiments 1 and 2, JED-format data of endoscopic procedure information was divided using preset system setting information regardless of the system type. However, in embodiment 3, a value (identifier) ​​identifying the system is stored in the JED-format data, and one of multiple preset system setting information is selected based on this value. Therefore, hereinafter, the configuration of the medical support device according to embodiment 2 will be described, followed by the processing executed by the medical support device according to embodiment 3. Note that the same components as those in the medical support devices 10 and 10A according to the above-described embodiments 1 and 2 will be assigned the same reference numerals, and detailed description thereof will be omitted.

[0170] [Functional Configuration of Medical Support Device] Fig. 33 is a block diagram showing the functional configuration of a medical support device according to embodiment 3 of the present disclosure. The medical support device 10B shown in Fig. 33 includes a DB 14B and a control unit 16B instead of the DB 14A and the control unit 16A of the medical support device 10A according to embodiment 2 described above.

[0171] The DB 14B includes a system setting DB 141B instead of the system setting DB 141 of the DB 14A according to the second embodiment described above.

[0172] The system setting DB 141B records system setting information that associates, for each system identification, a method for dividing characters extracted from endoscopic procedure information, attributes, and additional information.

[0173] Fig. 34 is a diagram showing an example of system setting information recorded in the system setting DB 141B. The system setting information T30 shown in Fig. 34 stores, for each system identifier, information for dividing and extracting concatenated characters between items related to endoscopic procedure information, concatenated characters between attributes, and concatenated characters between attributes and additional information. Specifically, the system setting information T30 stores, in association with the major item "common" for each of identifier A and identifier B, the division method "inter-item dividing character," the data ",", and the remark "half-width comma."

[0174] The control unit 16B corresponds to the processor according to the present disclosure. This control unit 16B is realized using a processor having hardware such as an FPGA, GPU, or CPU, and a memory that serves as a temporary storage area used by the processor. The control unit 16B comprehensively controls each unit constituting the medical support device 10B. The control unit 16B further includes a display control unit 168 in addition to the configuration of the control unit 16A according to the second embodiment described above.

[0175] The display control unit 168 displays a warning on the display unit 12 to the effect that the setting unit 163 was unable to retrieve from the system setting DB 141B the system setting information corresponding to the identifier for identifying the system included in the file.

[0176] [Processing of Medical Support Device] Next, the processing executed by the medical support device 10B will be described. Fig. 35 is a flowchart showing an outline of the processing executed by the medical support device 10B. In Fig. 35, step S602 and steps S606 to S611 are the same processing as step S302 and steps S304 to S309, respectively, in Fig. 21 described above, but steps S601, S603, S604, and S605 are different. Therefore, steps S601, S603, S604, and S605 will be described below.

[0177] 35 , the data import unit 161 imports endoscope-related procedure information from the endoscope management device 20 via the communication unit 11 (step S601). In this case, the data import unit 161 imports from the endoscope management device 20 via the communication unit 11 a file containing JED format data of endoscope-related procedure information and an identifier for identifying the system.

[0178] In step S603, the setting unit 163 retrieves from the system setting DB 141B the system setting information that corresponds to the identifier for identifying the system included in the file.

[0179] Next, the determination unit 162 determines whether the setting unit 163 was able to retrieve, from the system setting DB 141B, system setting information corresponding to the identifier identifying the system included in the file (step S604). If the determination unit 162 determines that the setting unit 163 was able to retrieve, from the system setting DB 141B, system setting information corresponding to the identifier identifying the system included in the file (step S604: Yes), the medical support device 10B proceeds to step S606. On the other hand, if the determination unit 162 determines that the setting unit 163 was not able to retrieve, from the system setting DB 141B, system setting information corresponding to the identifier identifying the system included in the file (step S604: No), the medical support device 10B proceeds to step S605, which will be described later.

[0180] In step S605, the display control unit 168 displays a warning on the display unit 12 to the effect that the setting unit 163 was unable to retrieve from the system setting DB 141B system setting information corresponding to the identifier for identifying the system contained in the file. This allows a user such as a doctor to understand that the JED-format data for the endoscope-related procedure information from the endoscope management device 20 is incompatible data. After step S605, the medical support device 10B terminates this process.

[0181] According to the third embodiment described above, the display control unit 168 displays a warning on the display unit 12 to the effect that it was unable to import system setting information corresponding to the identifier that identifies the system contained in the file from the system setting DB 141B, so that a doctor or other user can understand that the JED format data for the endoscope-related procedure information from the endoscope management device 20 is incompatible data.

[0182] Furthermore, according to the third embodiment, the setting unit 163 retrieves system setting information corresponding to the identifier that identifies the system contained in the file from the system setting information recorded in the system setting DB 141B, and therefore, it is possible to perform system settings according to the system being used in the facility.

[0183] (Fourth Embodiment) Next, a fourth embodiment of the present disclosure will be described. In the above-described first to third embodiments, standard terms are updated sequentially, but in the fourth embodiment, standard terms are updated according to a certain usage history (extraction history). For this reason, the configuration of the medical support device according to the fourth embodiment will be described first, followed by a description of the processing executed by the medical support device according to the fourth embodiment. Note that the same components as those in the medical support devices 10, 10A, and 10B according to the above-described first to third embodiments will be assigned the same reference numerals, and detailed description thereof will be omitted.

[0184] [Functional Configuration of Medical Support Device] Fig. 36 is a block diagram showing the functional configuration of a medical support device according to embodiment 4 of the present disclosure. The medical support device 10C shown in Fig. 36 includes a DB 14C and a control unit 16C instead of the DB 14B and the control unit 16B of the medical support device 10B according to embodiment 3 described above.

[0185] DB14C includes a standard term accumulation DB142C instead of the standard term accumulation DB142 of DB14B according to the above-described embodiment 3. Furthermore, DB14C further includes a facility setting information DB144 in addition to the configuration of DB14B according to the above-described embodiment 3.

[0186] In addition to the standard terms defined in the JED format described above (see standard terms T4 in Figure 5 and standard terms T5 in Figure 6), the standard term accumulation DB 142C also stores usage information that associates the number of uses of facility-specific terms with categories (standard) defined in the JED format or categories (specific) that indicate categories extracted as facility-specific terms.

[0187] 37 is a diagram showing an example of standard term (procedure) usage information. The standard term (procedure) table T40 shown in FIG. 37 stores standard term terms in association with a category (standard) defined in the JED format or a category (specific) indicating a category extracted as a facility-specific term, and the number of uses of the facility-specific term. For example, the fifth row of standard term T6 stores the term "biopsy" in association with the category "specific" and the number of uses "5."

[0188] The facility setting information DB 144 records facility setting information for each facility that corresponds setting items for identifying facility-specific terms (e.g., number of characters or more, less than, etc.) with information for identifying standard terms (e.g., usage history).

[0189] 38 is a diagram showing an example of facility setting information. The facility setting information T41 shown in FIG. 38 stores setting items for identifying facility-specific terms (e.g., a minimum or maximum number of characters, an incomplete number of characters, etc.), data for identifying standard terms, and remarks (number of uses) in association with each other (first condition). For example, the setting item "information for identifying standard terms (number of uses)" in the third line of the facility setting information T41 is stored in association with the data "5" and the remark "five or more times."

[0190] In addition to the first condition, the facility setting information T41 also includes the following second condition (2) and third condition (3). (Second condition) The target character string must be the first character string when the standard term extraction unit 164 divides the target character string by characters that connect attributes. (Third condition) The character string must not contain any character string that divides the attribute and additional information.

[0191] The control unit 16C corresponds to the processor according to the present disclosure. This control unit 16C is realized using a processor having hardware such as an FPGA, GPU, or CPU, and a memory that serves as temporary storage used by the processor. The control unit 16C comprehensively controls each unit constituting the medical support device 10C. The control unit 16C further includes a standard terminology adjustment unit 169 in addition to the configuration of the control unit 16B according to the third embodiment described above.

[0192] If the information (number of uses) specifying a standard term is not satisfied according to the facility setting information set by the setting unit 163, the standard term adjustment unit 169 adjusts the standard term by deleting it from the standard term accumulation DB 142C.

[0193] [Processing of Medical Support Device] Next, the processing executed by the medical support device 10C will be described. Figure 39 is a flowchart showing an outline of the processing executed by the medical support device 10C. In Figure 39, steps S701 to S703, steps S705 to S708, steps S711, and step S713 are similar to steps S601 to S603, steps S604 to S607, and steps S610 to S611, respectively, in Figure 34 described above, but steps S704, S709, S710, and S712 are different. Therefore, steps S704, S709, S710, and S712 will be described below, respectively.

[0194] In step S704, the setting unit 163 retrieves facility setting information from the facility setting information DB 144. After step S704, the medical support device 10C proceeds to step S705.

[0195] In step S709, the standard term extraction unit 164 executes a standard term extraction process for extracting standard terms from one line of imported data. This standard term extraction process is similar to the standard term extraction process shown in Fig. 9, except that the number of uses (extraction history or use history) is counted up.

[0196] FIG. 40 is a diagram illustrating the situation in which the standard term extraction unit 164 counts up the number of uses of an attribute extracted during the standard term extraction process. As shown in FIG. 40 , when the standard term extraction unit 164 extracts a term from the imported data of endoscopic procedure information imported by the data import unit 161 and registers it in the attribute value accumulation DB 143, it counts up the number of uses of the term, for example, "biopsy" in the standard term (procedure) table T40 from "5" to "6" and registers it. In this case, the standard term extraction unit 164, in accordance with the facility setting information set by the setting unit 163, does not add "Cold Snare Polypectomy (3 or more)" in the imported data (procedure) D2 to the standard term list because it does not correspond to information identifying a facility-specific term that is two or more characters and less than 21 characters. Therefore, the standard term extraction unit 164 terminates the standard term extraction process. After step S709, the medical support device 10C proceeds to step S710.

[0197] In step S710, the facility-specific term extraction unit 167 performs a facility-specific term extraction process to extract facility-specific terms from the imported data (specific words) that has been imported by the data import unit 161 and separated from the standard term extraction unit 164.

[0198] [Facility-Specific Term Extraction Processing] Figure 41 is a sub-flowchart showing an overview of the facility-specific term extraction processing in step S710 of Figure 39. Figure 42 is a diagram schematically explaining an example of the facility-specific term extraction processing by the facility-specific term extraction unit 167. Note that in Figure 41, steps S802 and S803 are similar to the processing of steps S502 and S503, respectively, of Figure 27 described above, with only step S801 being different. Therefore, step S801 will be described below.

[0199] 41 , the facility-specific terminology extraction unit 167 determines whether the specific word input from the standard terminology extraction unit 164 matches the facility-specific terminology extraction condition in accordance with the facility setting information (see facility setting information T41 in FIG. 38 ) set by the setting unit 163 (step S801). Specifically, as shown in FIG. 28 , the facility-specific terminology extraction unit 167 splits the specific word "P2" and the specific word "mucosal resection, endoscopic total resection, relatively complete resection, snare" split from the end and input by the standard terminology extraction unit 164 based on the half-width commas "," and "..." in the system setting information T3 (see FIG. 4 ), extracts and acquires "mucosal resection" as the preceding character string, and determines whether this "mucosal resection" matches the facility-specific terminology extraction condition.

[0200] 42 is a diagram showing an example of the extraction results obtained by the facility-specific term extraction unit 167 in accordance with the facility setting conditions. As shown in the extraction result table T50 in Fig. 42, the target character strings are "adenoma X," "P2," "Cold snare polypectomy (three or more) endoscopic complete resection, relatively complete resection, resected, but," and "needs follow-up for a while," but these character strings are excluded by applying the second condition (2) and the third condition (3) above.

[0201] 26 described above, it cannot be ruled out that the second and subsequent character strings split by characters linking attributes may be character strings split in an unexpected way by characters in the free input section or character strings split in an unexpected way by characters linking additional information (such as linking attribute values ​​"1" and "2", or linking attribute values ​​"1" and "2", which are additional information). For this reason, the facility-specific term extraction unit 167 targets only the first character string as a specific word, thereby making it possible to avoid registering character strings split in an unexpected way (character strings that the facility does not expect to be facility-specific terms).

[0202] Furthermore, in the case of Figure 26 described above, the target character string "Cold Snare Polypectomy (three or more) Endoscopic complete resection, relatively complete resection, resected" includes "characters that separate attributes and additional information," so the facility-specific term extraction unit 167 does not identify it as a facility-specific term. The reason for this is to deal with the fact that the facility-specific term extraction unit 167 cannot determine whether a facility-specific term that includes "characters that separate attributes and additional information" has been set or whether the data structure includes "characters that separate attributes and additional information."

[0203] As a result, in the above case, the facility-specific terminology extraction unit 167 does not register facility-specific terms, thereby avoiding the registration of character strings that are unexpected specific words.

[0204] 41 , if the facility-specific terminology extraction unit 167 determines in step S801 that the specific word input from the standard terminology extraction unit 164 matches the facility-specific terminology extraction condition (step S801: Yes), the medical support device 10C proceeds to step S502, which will be described later. On the other hand, if the facility-specific terminology extraction unit 167 determines that the specific word input from the standard terminology extraction unit 164 does not match the facility-specific terminology extraction condition (step S801: No), the medical support device 10C returns to the main routine of FIG. 39 and proceeds to step S712.

[0205] 39, the description of step S712 and subsequent steps will be continued. In step S712, if the standard term adjustment unit 169 does not satisfy the information (number of uses) that identifies the standard term in accordance with the facility setting information set by the setting unit 163, it adjusts the standard term by deleting it from the standard term accumulation DB.

[0206] FIG. 43 is a diagram illustrating the adjustment of standard terms by the standard term adjuster 169. As shown in FIG. 43 , the standard term is adjusted by deleting terms with a usage count of less than five from the standard term (procedure) table T40 in accordance with the facility setting information set by the setting unit 163 (see the facility setting information T41 in FIG. 25 ). For example, the standard term adjuster 169 adjusts the standard term by deleting "mucosal resection" from the standard term (procedure) table T40, since the usage count in the standard term (procedure) table T40 is "3." This prevents the proliferation of infrequently used terms and enables accurate term extraction. After step S712, the medical support device 10C proceeds to step S713.

[0207] According to the above-described embodiment 4, the standard term adjustment unit 169 adjusts the standard term by deleting it from the standard term accumulation DB if the information identifying the standard term (number of uses) is not met in accordance with the facility setting information set by the setting unit 163, thereby avoiding the accumulation of unnecessary terms.

[0208] (Embodiment 5) Next, embodiment 5 will be described. In the above-described embodiment 4, a predetermined number of uses of a standard term was counted, and if the number of uses did not satisfy the information identifying the standard term (number of uses), the standard term was deleted from the standard term accumulation DB. However, in embodiment 4, the standard term extraction unit temporarily accumulates specific words extracted, and after a specific period of time has passed, it determines whether the number of uses satisfies the information identifying the standard term (number of uses) set by the facility setting unit. If the information identifying the standard term (number of uses) is satisfied, the standard term is registered in the standard term accumulation unit. That is, in embodiment 5, the configuration of the medical support device and the standard term extraction process executed by the medical support device are different, and a process for registering in the standard term accumulation unit is further included. Therefore, hereinafter, after describing the configuration of the medical support device according to embodiment 5, the standard term extraction process and the process for registering in the standard term accumulation unit executed by the medical support device according to embodiment 5 will be described. Note that the same components as those of the medical support device 10, medical support device 10A, medical support device 10B, and medical support device 10C according to embodiments 1 to 4 are designated by the same reference numerals, and detailed description thereof will be omitted.

[0209] [Functional Configuration of Medical Support Device] Fig. 44 is a block diagram showing the functional configuration of a medical support device according to embodiment 5 of the present disclosure. The medical support device 10D shown in Fig. 44 includes a DB 14D and a control unit 16D instead of the DB 14C and the control unit 16C of the medical support device 10C according to embodiment 4 described above.

[0210] The DB 14D includes a standard term temporary storage DB 145 in addition to the configuration of the DB 14C according to the third embodiment described above.

[0211] The standard term temporary storage DB 145 temporarily stores the specific words extracted by the standard term extraction unit 164 .

[0212] The control unit 16D corresponds to the processor according to the present disclosure. This control unit 16D is realized using a processor having hardware such as an FPGA, GPU, or CPU, and a memory that serves as temporary storage used by the processor. The control unit 16D comprehensively controls each unit constituting the medical support device 10C. The control unit 16D includes a standard terminology adjustment unit 169D instead of the standard terminology adjustment unit 169 of the control unit 16C according to the fourth embodiment described above.

[0213] The standard terminology adjuster 169D determines whether the number of times a facility-specific term temporarily stored in the standard terminology temporary storage DB 145 has been used is equal to or greater than a predetermined number of times. The standard terminology adjuster 169D also registers, in the standard terminology storage DB 142C, facility-specific terms that have been temporarily stored in the standard terminology temporary storage DB 145 and that have been used equal to or greater than the predetermined number of times, while not accepting for registration in the standard terminology storage DB 142C facility-specific terms that have been used less than the predetermined number of times.

[0214] [Processing of Medical Support Device] Next, the processing executed by the medical support device 10D will be described. Figure 45 is a flowchart showing an outline of the standard term extraction processing executed by the medical support device 10D. Steps S901 to S902 and steps S905 to S909 are the same as steps S201 to S202 and steps S204 to S208, respectively, in Figure 9 described above, with only steps S903, S904, and S908 being different. Therefore, steps S903, S904, and S908 will be described below.

[0215] In step S903, the standard term extraction unit 164 determines whether the specific word matches a standard term stored in the standard term storage DB 142C. If the standard term extraction unit 164 determines that the specific word matches a standard term stored in the standard term storage DB 142C (step S903: Yes), the medical support device 10 proceeds to step S909, which will be described later. On the other hand, if the standard term extraction unit 164 determines that the specific word does not match a standard term stored in the standard term storage DB 142C (step S903: No), the medical support device 10D proceeds to step S904, which will be described later.

[0216] In step S904, the storage control unit 165A stores the specific word (facility-specific term) determined not to match the standard term in step S903 in the standard term temporary storage DB 145. At this time, if the same specific word has already been registered in the standard term temporary storage unit 145, it may be stored so as to increase the number of times it has been used. After step S904, the medical support device 10D proceeds to step S905.

[0217] FIG. 46 is a diagram showing an example of a character string extracted by the standard term extraction unit 164 and stored in the standard term temporary storage DB 145.

[0218] As shown in the extraction result table T60 in FIG. 46 , the standard term temporary accumulation DB 145 also registers words such as "Cold" that are equivalent to parts of standard terms or facility-specific terms. However, the processing by the standard term extraction unit 164 splits the endoscopic procedure information from the end at the character connecting the attribute and additional information, and evaluates the character string before that. Therefore, if a long term containing that word is registered, it will match that term exactly. As a result, the standard term adjustment unit 169D, which will be described later, organizes standard terms by the number of times they are used, thereby preventing them from being registered in the standard term accumulation DB 142C and avoiding the generation of unnecessary analysis results.

[0219] [Adjustment Process by Standard Terminology Adjustment Unit] Next, the adjustment process executed by the standard term adjustment unit 169D will be described. Fig. 47 is a flowchart showing an outline of the adjustment process executed by the standard term adjustment unit 169D.

[0220] As shown in FIG. 46 , the standard term adjuster 169D determines whether a specific period of time has elapsed for the facility-specific term temporarily stored in the standard term temporary storage DB 145 (step S1001). Here, the specific period can be set appropriately for each facility and can be changed as needed, such as overnight, one week, one month, or one day. Of course, other factors, such as the number of examinations or changes in surgeons, may also be taken into account. If the standard term adjuster 169D determines that the specific period of time has elapsed for the facility-specific term temporarily stored in the standard term temporary storage DB 145 (step S1001: Yes), the medical support device 10D proceeds to step S1002, which will be described later. On the other hand, if the standard term adjuster 169D determines that the specific period of time has not elapsed for the facility-specific term temporarily stored in the standard term temporary storage DB 145 (step S1001: No), the medical support device 10D terminates this process.

[0221] In step S1002, the standard terminology adjuster 169D determines whether the number of uses of the facility-specific term temporarily stored in the standard terminology temporary storage DB 145 is equal to or greater than a predetermined number of uses. If the standard terminology adjuster 169D determines that the number of uses of the facility-specific term temporarily stored in the standard terminology temporary storage DB 145 is equal to or greater than the predetermined number of uses (step S1002: Yes), the medical support device 10D proceeds to step S1003, which will be described later. On the other hand, if the standard terminology adjuster 169D determines that the number of uses of the facility-specific term temporarily stored in the standard terminology temporary storage DB 145 is not equal to or greater than the predetermined number of uses (step S1002: No), the medical support device 10D proceeds to step S1004, which will be described later.

[0222] In step S1003, the standard term adjustment unit 169D registers facility-specific terms that have been temporarily stored in the standard term temporary storage DB 145 and have been used a predetermined number of times or more in the standard term storage DB 142C, and deletes them from 145. After step S1003, the medical support device 10D terminates this process.

[0223] In step S1004, the standard term adjustment unit 169D rejects facility-specific terms that are temporarily stored in the standard term temporary storage DB 145 and have not been used a predetermined number of times or more from the standard term storage DB 142C. In this case, the standard term extraction unit 164 may delete facility-specific terms that are temporarily stored in the standard term temporary storage DB 145 and have not been used a predetermined number of times or may add a log indicating that they have been rejected. After step S1004, the medical support device 10D terminates this processing.

[0224] According to the fifth embodiment described above, the standard term adjustment unit 169D temporarily stores facility-specific terms in the standard term temporary storage DB 145, and registers facility-specific terms that have been used a predetermined number of times or more in the standard term storage DB 142C, while facility-specific terms that have not been used a predetermined number of times or more are not adopted for registration in the standard term storage DB 142C, thereby making it possible to avoid the storage of unnecessary terms and the storage of attribute values ​​(unnecessary analysis results) due to unnecessary terms.

[0225] In the fifth embodiment, if a term is registered as a standard term in step S1003, the stored past endoscopic procedure information may be reprocessed. By performing retroactive processing, it is possible to update the analysis and interpretation of the period in which the term was temporarily stored to a more appropriate one. Furthermore, in order to efficiently perform retroactive processing, it is useful to store information indicating the order of the data registered in the standard term temporary storage DB, as well as dates, and to limit the retroactive range to the time from when the term was registered in the standard term temporary storage DB to when the term is registered as a standard term.

[0226] (Disclosed embodiments) In the above-described embodiments 1 to 5, the analysis unit 166 analyzes and parses the attribute value accumulation data accumulated in the attribute value accumulation DB 143, and displays the results of this analysis and parse on the display unit 12. However, without being limited to this, the analysis unit 166 may analyze and parse various contents based on information such as endoscope-related procedure information acquired from the endoscope management device 20, and display the results of this analysis on the display unit 12.

[0227] 48 is a diagram showing an example of the analysis results obtained by the analysis unit 166. As shown in Fig. 48, the analysis unit 166 may, for example, acquire the endoscope usage history from the endoscope management device 20, analyze the number of times each endoscope model is used and the number of times each model is used weekly or monthly based on this usage history, and display this analysis result P10 on the display unit 12.

[0228] Fig. 49 is a diagram showing another example of the analysis results analyzed by the analysis unit 166. As shown in Fig. 49, the analysis unit 166 may, for example, acquire the usage history of the endoscope from the endoscope management device 20, and based on this usage history, analyze various information related to the status, power-on time, number of power-on times, total number of times used, number of times used after maintenance, and repair / maintenance, and display this analysis result P11 on the display unit 12.

[0229] 50 is a diagram showing another example of the analysis results obtained by the analysis unit 166. As shown in Fig. 50, the analysis unit 166 may, for example, acquire the endoscope usage history from the endoscope management device 20, analyze various information related to the cumulative number of times an endoscope has been used based on this usage history, and display this analysis result P12 on the display unit 12.

[0230] Fig. 51 is a diagram showing another example of the analysis result obtained by the analysis unit 166. As shown in Fig. 51, the analysis unit 166 may, for example, acquire the endoscope usage history from the endoscope management device 20, analyze various information related to the maintenance status of one endoscope based on this usage history, and display on the display unit 12 an analysis result P13 indicating the period for regular maintenance.

[0231] Fig. 52 is a diagram showing another example of the analytical results obtained by the analytical unit 166. As shown in Fig. 52, the analytical unit 166 may, for example, acquire usage history from the endoscope washer, analyze various information related to the endoscope washer based on this usage history, and display analytical results P14 that visualize the operating status of the endoscope washer on the display unit 12.

[0232] Fig. 53 is a diagram showing another example of the analytical results obtained by the analytical unit 166. As shown in Fig. 53, the analytical unit 166 may, for example, acquire usage history from the endoscope washer, analyze various information related to the endoscope washer based on this usage history, and display analytical results P15 that visualize the operating status of the endoscope washer on the display unit 12.

[0233] (Other Embodiments) Various inventions can be formed by appropriately combining multiple components disclosed in the medical support system according to the above-mentioned embodiment of the present disclosure. For example, some components may be omitted from all of the components described in the medical support system according to the above-mentioned embodiment of the present disclosure. Furthermore, the components described in the medical support system according to the above-mentioned embodiment of the present disclosure may be appropriately combined.

[0234] In addition, in the embodiment of the present disclosure, the medical support device is equipped with a DB, but this is not limited to this, and the medical support device and the DB on the server may be separate entities, and the judgment results of the standard term extraction unit and the facility-specific term extraction unit may be sent to the DB on the server.

[0235] In addition, in the embodiment of the present disclosure, the functions of the control unit may be realized by a plurality of servers. For example, the function of the standard term extraction unit and the function of the storage control unit may be realized by separate servers.

[0236] Furthermore, in the embodiment of the present disclosure, the function of the analysis unit is included in the medical support device, but for example, the function of the analysis unit may be provided in a separate server, and the analysis results may be obtained from this server through a service such as a subscription that provides periodic analysis.

[0237] Furthermore, in the medical support system according to the embodiment of the present disclosure, the above-mentioned "unit" can be read as "means" or "circuit," etc. For example, a control unit can be read as control means or a control circuit.

[0238] In addition, the program to be executed by the medical support system according to the embodiment of the present disclosure is provided as file data in an installable or executable format recorded on a computer-readable recording medium such as a CD-ROM, a flexible disk (FD), a CD-R, a DVD (Digital Versatile Disk), a USB medium, or a flash memory.

[0239] In addition, the program executed by the medical support system according to the embodiment of the present disclosure may be configured to be stored on a computer connected to a network such as the Internet and provided by being downloaded via the network.

[0240] In the description of the flowcharts in this specification, expressions such as "first," "then," and "continue" are used to clearly indicate the order of processing between steps, but the order of processing required to implement the present invention is not uniquely determined by these expressions. In other words, the order of processing in the flowcharts described in this specification can be changed within a consistent range. Furthermore, programs are not limited to those consisting of simple branching processing, and branching can be achieved by comprehensively determining more judgment items.

[0241] Although some of the embodiments of the present application have been described in detail above with reference to the drawings, these are merely examples, and the present invention can be implemented in other forms that have undergone various modifications and improvements based on the knowledge of those skilled in the art, including the aspects described in the disclosure of the present invention.

[0242] 1 Medical support system 10, 10A, 10B, 10C, 10D Medical support device 11 Communication unit 12 Display unit 13 Input unit 14 Database 15 Recording unit 16, 16A, 16B, 16C, 16D Control unit 20 Endoscope management device 140 Endoscopy-related procedure information DB 141, 141A System setting DB 142, 142B, 142C Standard term storage DB 142B Standard term storage DB 143 Attribute value storage DB 144 Facility setting information DB 145 Standard term temporary storage unit 151 Program recording unit 161 Data import unit 162 Determination unit 163 Setting unit 164 Standard term extraction unit 165, 165A Storage control unit 166 Analysis and analysis unit 167 Facility-specific term extraction unit 168 Display control unit 169,169D Standard Terminology Coordination Department N100 Network

Claims

1. A medical support device having a processor, wherein the processor: imports endoscopic related procedure information in a prescribed format including a plurality of characters relating to at least one of a qualitative diagnosis and a treatment by an endoscope; extracts specific words by dividing the endoscopic related procedure information in the prescribed format using a division method according to the content of the endoscopic related procedure information in the prescribed format; compares the specific words with standard terms defined in the endoscopic related procedure information in the prescribed format; and, if the specific words match the standard terms, determines the specific words to be attribute values.

2. A medical support device according to claim 1, wherein the processor determines that the specific word is an attribute value of a facility-specific term if the specific word does not match the standard term.

3. A medical support device as described in claim 2, wherein the processor, when the specific word and the standard term do not match, stores the specific word as an attribute value of a facility-specific term, and updates the facility-specific term stored as the attribute value to the standard term.

4. A medical support device as described in claim 2, wherein the processor, when storing the specific word as an attribute value of a facility-specific term, counts the number of uses of the specific word, determines whether the number of uses of the specific word is greater than or equal to a predetermined number of times, and if the number of uses of the specific word is less than the predetermined number of times, does not use the specific word as an attribute value of the facility-specific term.

5. A medical support device as described in claim 2, wherein the processor determines whether the number of times the specific word is used within a specified time period is equal to or greater than a specified number of times, and if the number of times the specific word is used is not equal to or greater than the specified number of times, does not use the specific word as an attribute value of a facility-specific term.

6. A medical support device according to claim 1, wherein the division method includes a division method for dividing the attribute by a character that links the attribute with the additional information, and a division method for dividing the attribute by a character that links the additional information with the attribute.

7. A medical support device as described in claim 6, wherein the processor divides the endoscopic procedure information from the rear by characters that link attributes and additional information, sequentially obtains the front character strings from the array of multiple character strings obtained as a result of the division, and sequentially determines whether the front character strings match the standard term.

8. A medical support device as described in claim 2, wherein the processor determines whether the specific word, which is the target string, satisfies a condition related to facility setting information indicating the number of characters required to identify a facility-specific term, and if the condition is satisfied, determines the specific word to be an attribute value of the facility-specific term.

9. A medical support device as described in claim 6, wherein the processor determines whether the specific word, which is a target string, satisfies at least one of a second condition that the specific word is included in at least the first string when divided by a character that connects attributes together, and a third condition that the target string does not contain a character that divides attributes and additional information, and if at least one of the second condition and the third condition is satisfied, determines the specific word to be an attribute value of a facility-specific term.

10. A medical support device as described in claim 1, wherein the endoscopic-related procedure information further includes an identifier for identifying an endoscopic system, and the processor obtains system setting information of the division method corresponding to each of the identifiers, and extracts the specific word based on the system setting information of the division method.

11. A medical support device as described in claim 10, wherein the processor determines whether or not system setting information for the division method corresponding to the identifier has been obtained, and if the system setting information for the division method corresponding to the identifier has not been obtained, outputs a warning to the effect that the system setting information for the division method corresponding to the identifier has not been obtained.

12. A medical support method executed by a medical support device having a processor, the medical support method including the processor: importing endoscopic related procedure information in a prescribed format including a plurality of characters relating to at least one of a qualitative diagnosis and a treatment by an endoscope; extracting specific words by dividing the endoscopic related procedure information in the prescribed format using a division method according to the content of the endoscopic related procedure information in the prescribed format; comparing the specific words with standard terms defined in the endoscopic related procedure information in the prescribed format; and determining the specific words as attribute values ​​if the specific words match the standard terms.

13. A medical support method according to claim 12, wherein the processor determines that the specific word is an attribute value of a facility-specific term if the specific word does not match the standard term.

14. A medical support method as described in claim 13, wherein the processor, if the specific word and the standard term do not match, stores the specific word as an attribute value of a facility-specific term, and updates the facility-specific term stored as the attribute value to the standard term.

15. A medical support method as described in claim 13, wherein when the processor stores the specific word as an attribute value of a facility-specific term, it counts the number of uses of the specific word, determines whether the number of uses of the specific word is equal to or greater than a predetermined number of times, and if the number of uses of the specific word is not equal to or greater than the predetermined number of times, does not use the specific word as the attribute value of the facility-specific term.

16. A medical support method as described in claim 13, wherein the processor determines whether the number of times the specific word is used within a specified time period is equal to or greater than a specified number of times, and if the number of times the specific word is used is not equal to or greater than the specified number of times, does not use the specific word as an attribute value of a facility-specific term.

17. A medical support method according to claim 12, wherein the division method includes a division method for dividing the attribute by a character that links the attribute with the additional information, and a division method for dividing the attribute by a character that links the additional information with the attribute.

18. A medical support method as described in claim 17, wherein the processor divides the endoscopic procedure information from the rear by characters that link attributes and additional information, sequentially obtains the front character strings from the array of multiple character strings obtained as a result of the division, and sequentially determines whether the front character strings match the standard term.

19. A medical support method as described in claim 13, wherein the processor determines whether the specific word, which is a target string, satisfies at least one of the following conditions: a first condition related to facility setting information indicating at least the number of characters required to identify a facility-specific term; a second condition that the specific word is included in the first string when the target string is divided by a character that connects attributes; and a third condition that the target string does not contain a character that divides the attribute and additional information; and if at least one of the first condition, the second condition, and the third condition is satisfied, the specific word is determined to be an attribute value of a facility-specific term.

20. A program to be executed by a medical support device equipped with a processor, the program causing the processor to: import endoscopic related procedure information in a prescribed format including a plurality of characters relating to at least one of a qualitative diagnosis and a treatment by endoscopy; extract specific words by dividing the endoscopic related procedure information in the prescribed format using a division method according to the content of the endoscopic related procedure information in the prescribed format; compare the specific words with standard terms defined in the endoscopic related procedure information in the prescribed format; and determine the specific words to be attribute values ​​if the specific words match the standard terms.

Images