Medical data evaluation practical application system and medical data evaluation practical application method

Abstract

The present invention provides a medical data evaluation practical application system and a medical data evaluation practical application method. Data that matches the user's purpose is efficiently determined, collected and managed from a large amount of medical data. When the given medical data is worthy of evaluation for the user operating the user terminal, the communication unit receives the evaluation result. The database generation unit selectively reads the medical data for which the communication unit receives the evaluation result from the medical data accumulated in the medical information storage device, and stores it in the storage unit. The database is generated by repeating this process each time an evaluation result is received.

Description

Technical Field

[0001] The present invention relates to a system for evaluating and applying medical data, and in particular to a system for managing and operating processes related to the provision and use of medical data. Background Art

[0002] Due to the environment full of huge information and the progress of network technology, advanced information processing technologies such as the collection / accumulation of big data, the utilization and practical application of data, and data analysis based on artificial intelligence have been developed one after another. On the other hand, it is known that the more data there is, the more valuable information processing can be performed. In such a technical background, in order to derive meaningful analysis results, it becomes important to collect / accumulate correct data. In particular, in the medical field where data utilization and practical application are expected, data collection, processing process, processing results, scope of application, etc. are considered to be very important.

[0003] Patent Document 1 discloses a rating information collection system that analyzes evaluations of information on products and the like based on voting information from evaluation groups ranging from general users to experts, and provides accurate rating information.

[0004] In addition, Patent Document 2 discloses a system in which reconstruction parameter values ​​used by doctors who receive images to reconstruct medical images reconstructed from temporary images using different reconstruction parameter values ​​as needed are stored in a database for each doctor. Thus, when reconstructing an image, the reconstruction parameter values ​​corresponding to the doctor who received the image are read from the database and used, so that the image preferred by the doctor can be reconstructed, and re-construction can be avoided. The reconstruction parameters are updated based on feedback from the doctor.

[0005] Prior art literature

[0006] Patent Literature

[0007] Patent Document 1: Japanese Patent Application Publication No. 2003-316925

[0008] Patent Document 2: JP 2015-510157

[0009] The purpose of data collection and actual application required for medical treatment is diverse. For example, there are people who want to collect high-quality medical images for research, while there are also people who want to collect poor-quality medical images for research to improve image quality. Thus, what kind of data is expected to be collected and actually applied varies greatly depending on the purpose of data use by the user.

[0010] However, it takes time and effort to collect a large amount of pre-classified data. In particular, it is difficult for medical practitioners to collect, evaluate, and classify data themselves because they are very busy. Therefore, in the medical field, the mechanism of classifying data according to the purpose and applying it is only carried out for limited purposes.

[0011] In the information rating system disclosed in Patent Document 1, since the reliability of information is calculated by voting of experts and evaluators other than experts, there is a problem that the reliability of information may be biased depending on the members of the evaluators. In addition, there is a problem that the evaluators must be called together to vote.

[0012] Since the technology disclosed in Patent Document 2 provides medical images optimized for each user, it is unclear whether it meets the purpose of use of other people. Summary of the invention

[0013] An object of the present invention is to efficiently identify, collect and manage data that meets the user's purpose from a large amount of medical data.

[0014] In order to achieve the above-mentioned object, according to the present invention, there are: a communication unit that receives an evaluation result for given medical data from a user operating a user terminal; a database generation unit connected to a medical information storage that has medical data stored in advance; and a storage unit. The database generation unit generates a database by repeatedly performing a process of selectively reading the medical data for which the communication unit receives the evaluation result from the medical data stored in the medical information storage and storing it in the storage unit each time an evaluation result is received.

[0015] Effects of the Invention

[0016] According to the present invention, when the purpose of use varies among users, data that matches the user's purpose can be efficiently identified, collected, and managed from a large amount of medical data. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] Figure 1 It is a block diagram showing the structure of the medical data evaluation application system 1 according to the embodiment of the present invention.

[0018] Figure 2 It is a diagram showing the hardware configuration of the medical data evaluation application system 1 according to the embodiment.

[0019] Figure 3 It is a diagram showing the structure of a storage area in the storage unit 1 according to the embodiment.

[0020] Figure 4 This is a flowchart showing the processing operation of the database generating unit 24 according to the first embodiment.

[0021] Figure 5 This is a diagram showing an example of a screen (image) on which “good” is superimposed and displayed on the data evaluation / utilization terminal 12 in the first embodiment.

[0022] Figure 6 This is a flowchart showing the processing operation of the data use request processing unit 25 according to the second embodiment.

[0023] Figure 7 It is a diagram showing an example of a data search input screen according to the second embodiment.

[0024] Figure 8 It is a flowchart showing the processing operation of the feedback processing unit 27 according to the second embodiment.

[0025] Fig. 9 It is a diagram showing an example of a feedback screen according to the second embodiment.

[0026] Fig.10 This is a flowchart showing the processing operation of the data matching unit according to the second embodiment.

[0027] Fig.11 This is a flowchart showing processing operations when a data use request is made by the data user 33b according to the third embodiment.

[0028] Fig.12 This is a flowchart showing a charge determination process when a data use request is made by a data user 33b according to the third embodiment.

[0029] Fig.13 It is a diagram showing an example of an evaluation screen (patient, attending physician) according to the fourth embodiment.

[0030] Fig.14 It is a diagram showing an example of an evaluation screen (diagnosis report) according to the fourth embodiment.

[0031] Fig.15 This is a diagram showing an example of an evaluation screen (radiographer, photographer, model) according to the fourth embodiment.

[0032] Description of Reference Numerals

[0033] 1...Medical Data Evaluation Practical Application System

[0034] 10...Medical data evaluation management device

[0035] 11...Medical Information System

[0036] 12...Data evaluation / utilization terminal

[0037] 13a...Data Utilization Terminal

[0038] 13b...Data utilization terminal (outside the facility)

[0039] 14...Medical meter memory

[0040] 15...Storage

[0041] 16...In-facility network

[0042] 20...Internal facilities

[0043] 21...External facilities

[0044] 24...Database Generation Department

[0045] 25...Data Utilization Request Processing Department

[0046] 26...Data Matching Department

[0047] 27...Feedback Processing Department

[0048] 28...Charge Determination Department

[0049] 32...Data evaluation / user

[0050] 33a...Data Utilizer

[0051] 33b...Data Utilizer

[0052] 41...CPU

[0053] 42...Memory

[0054] 43...Storage device

[0055] 49...communication device

[0056] 50...Communication interface

[0057] 51...Database storage area

[0058] 52...Search condition summary storage area

[0059] 53...User information storage area

[0060] 54...Feedback information storage area DETAILED DESCRIPTION

[0061] A medical data evaluation application system according to an embodiment of the present invention will be described below.

[0062] <System Structure>

[0063] Figure 1 It is an overall structural diagram of a network including the medical data evaluation practical application system 1 of this embodiment and other systems and terminals connected thereto. Figure 2 It is a diagram showing the internal structure of the medical data evaluation management device 10.

[0064] like Figure 1 As shown, the medical data evaluation application system 1 of the present embodiment includes a medical data evaluation management device 10, a storage unit 15 for storing a database, a data evaluation / utilization terminal 12, and a data utilization terminal 13a.

[0065] Medical data evaluation management device 10 Figure 2 As shown, the communication device 49 is connected to the data evaluation / utilization terminal 12, the data utilization terminal 13a, the storage unit 15, the medical information system 11, and the medical information storage 14 via the in-facility network 16. In addition, the communication device 49 is also connected to the data utilization terminal 13b outside the facility via the out-facility network 17.

[0066] Meanwhile, the medical data evaluation management device 10 includes a database generation unit 24, a data use request processing unit 25, a data matching unit 26, a feedback processing unit 27, and a charge determination unit 28. The functions of these units 24 to 28 are described in detail in the first to fourth embodiments described below.

[0067] The hardware structure of the medical data evaluation management device 10 is as follows: Figure 2 As shown, in addition to the communication device 49, it also includes a CPU 41, a memory 42 and a storage device 43. The storage device 43 stores a database generation program 44, a data utilization request program 45, a data matching program 46, a feedback processing program 47 and a charge determination program 48 in advance. The storage device 43 is composed of a suitable non-volatile storage element such as an SSD and a hard disk drive. The memory 42 is composed of a volatile storage element such as a RAM. The CPU 41, the memory 42, the storage device 43 and the communication device 49 are connected via a communication interface 50.

[0068] The CPU 41 reads out the programs stored in the storage device 43 to the memory 42 and executes them, thereby realizing the functions of the database generation unit 24, the data use request processing unit 25, the data matching unit 26, the feedback processing unit 27 and the charging determination unit 28 by software.

[0069] In addition, in the present embodiment, a part or all of the functions of each unit 24 to 28 can also be realized by hardware. For example, a circuit design can be performed so that a custom IC such as an ASIC (Application Specific Integrated Circuit) or a programmable IC such as an FPGA (Field-Programmable Gate Array) is used to constitute the medical data evaluation management device 10 and realize the functions of each unit 24 to 28.

[0070] The storage unit 15 stores the database generated by the database generating unit 24 of the medical data evaluation management device 10 .

[0071] Figure 3 1 is a diagram for explaining storage areas of a database in the storage unit 15. The database in the storage unit 15 includes a database storage area 51, a search condition summary storage area 52, a user information storage area 53, and a feedback information storage area 54.

[0072] On the other hand, the medical information system 11 connected to the medical data evaluation practical application system 1 of the present embodiment via a network is an existing system such as an electronic medical record and an image management system, and stores medical data such as electronic medical record data and image data captured by a camera in a medical information storage 14. Therefore, medical data is accumulated in the medical information storage 14. The user can operate the medical information system 11 via the terminal 12, 13a, thereby using the medical information system 11 to read the medical data in the medical information storage 14 and display it on the display screen of the terminal 12, 13a.

[0073] To explain in more detail, the medical information system 11 is a general term for systems related to the records of medical treatment and business support used in hospitals. The medical information system 11 includes electronic medical records, medical affairs billing systems, inspection systems, image management systems, physical examination systems, ordering systems, film reading and diagnosis systems, reporting systems, and document creation systems.

[0074] The medical information storage 14 is a storage for receiving and storing medical data integrated in accordance with IHE (Integrating the Healthcare Enterprise) from the medical information system 11. Examples of the stored medical data include medical image data, basic patient information, insurance information, hospitalization and discharge history, external medical history, disease name information, allergy information, prescription / injection order information, test results, reports, etc.

[0075] <First Embodiment>

[0076] The medical data evaluation application system according to the first embodiment will be described.

[0077] In the first embodiment, a user operates the medical information system 11 via the data evaluation / utilization terminal 12, and while observing the medical data in the medical information storage device 14 on the display screen of the terminal 12, when specific medical data among the medical data being displayed is "data worthy of evaluation" for the user, the communication device 49 of the medical data evaluation practical application system receives the evaluation result from the user.

[0078] The database generator 24 selectively receives medical data evaluated according to the evaluation results received by the communication device 49 from the medical data accumulated in the medical information storage 14, and stores it in the storage unit 15. By repeating this process each time the communication device 49 receives the evaluation results, a database of the evaluated data is generated in the storage unit 15.

[0079] Therefore, when the user uses the terminal 12 to observe medical data, if he or she subjectively judges that the data is "worthy of evaluation", the evaluation can be performed solely in this way, and based on the evaluation result, only useful medical data can be selected from the medical data in the huge medical information storage and stored in the database of the storage unit 15.

[0080] Therefore, as described in the second embodiment, data required by the user can be extracted from useful medical data in the database of the storage unit 15 based on the received search keyword and provided to the user.

[0081] Furthermore, information of the user who has performed the evaluation may be stored in the storage unit 15 as part of the data of the database in correspondence with the medical data stored in the storage unit 15 .

[0082] This will be described in detail below. In this embodiment, an example will be described in which an evaluator 32 who is a worker in the internal facility 20 evaluates a medical image.

[0083] Figure 4 This is a flowchart showing the operation of the database generating unit 24 .

[0084] In step 401, the evaluator 32 of the internal facility 20 operates the medical information system 11 via the evaluation / utilization terminal 12, connects to the medical information storage 14 and stores the medical images such as Figure 5In the state displayed in that way, the medical image is evaluated. That is, if the evaluator 32 subjectively judges that "it is a medical image worthy of evaluation" and selects the medical image, the database generation unit 24 receives information such as the ID number that determines the medical image (evaluation result) via the communication device 49. For example, a function for displaying a mark such as a character string representing "good" is pre-embedded in the medical information system 11. When the user judges that the medical image is worthy of evaluation, the user operates the medical information system 11 to add a "good" mark to the specific medical image. That is, the medical information system 11 overlaps the "good" mark on the medical image through its own control. As a result, the database generation unit 24 can receive the evaluation results (selection of medical images with "good" marks) from the user via the medical information system 11.

[0085] In addition, the so-called "medical images worthy of evaluation" here are the user's subjective judgment, such as whether the image data has good image quality, needs to be improved, is a typical disease image, is a rare disease image, hopes to use it in one's own research, or is tentatively marked and hopes to be confirmed later.

[0086] In steps 402 and 403, the database generation unit 24 searches the medical information storage unit 14 for medical images with a "good" mark attached, retrieves the image data and related information (data on the imaging site, type and model of the medical imaging device (medical imaging modality)), and saves them to the corresponding items in the database storage area 51 of the database storage unit 15.

[0087] More specifically, the database generation unit 24 searches for the corresponding image in the medical information storage 14 with reference to the ID of the image to which "good" is attached, and downloads the image data in the DICOM format from the medical information storage 14 (step 402).

[0088] Next, the database generation unit 24 extracts related information (imaging site, image type (type of imaging device), camera type, etc.) from the DICOM format image (step 403 ).

[0089] In step 404, the database generation unit 24 receives the user ID registered in the terminal 12 via the communication device 49 and searches the corresponding user in the medical information storage 14, thereby retrieving the evaluator information such as the evaluator's name, evaluator's occupation type, and evaluator's professional field.

[0090] In step 405 , the image data, related information, and evaluator information retrieved in steps 402 , 403 , and 404 are stored in corresponding locations of the table in the database storage area 51 of the storage unit 15 .

[0091] Table 1 is an example of a table storing related information in the database storage area 51. The ID of the image data (evaluation data) to be evaluated, the type of image, the imaging site, and the camera type are stored in association with each other.

[0092]

Table 1

[0093] Table 1

[0094]

[0095] Table 2 is an example of a table storing the evaluator information in the database storage area 51 .

[0096]

Table 2

[0097] Table 2

[0098]

[0099] As shown in Table 2, the table of evaluator information has areas for storing data for items such as evaluation object, evaluation date and time, evaluator name, evaluator occupation type, and evaluator professional field, using the evaluation data ID that can uniquely identify the evaluation object, namely image data (evaluation data), as a keyword.

[0100] In addition, in Table 2, the evaluation objects are not limited to images, but can also be evaluated for objects other than medical images, such as medical practitioners such as photographers, diagnostic reports, models of medical imaging equipment, patients, etc. Evaluation objects other than images are explained in the fourth embodiment.

[0101] By repeating the above steps 401 to 405 , the database generation unit 24 selects and stores the image data to which “good” is added in the database storage area 51 , and sequentially registers the related information and the evaluator information in association with the image data, thereby generating the databases of Tables 1 and 2 .

[0102] Therefore, by using the medical data evaluation practical application system 1 of the first embodiment, the evaluator can simply evaluate images and easily generate a database that collects image data with "good" attached and its related information, etc., and can centrally manage useful data.

[0103] In addition, the evaluation / use terminal 12 and data use terminal 13a of the internal facility 20 and the data use terminal 13b of the external facility 21 are all information processing terminals and follow the security rules for terminals that process medical data, and PCs, smartphones, tablet terminals, etc. are targets.

[0104] <Second Embodiment>

[0105] The medical data evaluation application system of the second embodiment is described. In the medical data evaluation application system of the second embodiment, the medical data evaluation management device 10 includes a data use request processing unit 25, a data matching unit 26, and a feedback processing unit 27 in addition to the database generation unit 24 of the first embodiment.

[0106] When the data use request processing unit 25 receives a data use request together with one or more search keywords from the user via the user terminal 12 or 13a, the data use request processing unit 25 causes the data matching unit 26 to extract medical data including words and phrases that match the search keywords from the database of the storage unit 15. The data use request processing unit 25 outputs the extracted medical data from the communication device 49 to the user terminal 12 or 13a.

[0107] Thus, the medical data evaluation application system can extract and provide the medical data required by the data evaluator / user 32 or the data user 33a from the database.

[0108] The following is a detailed description.

[0109] Figure 6 It is a flowchart showing the operations of the data use request processing unit 25 , the data matching unit 26 , and the feedback processing unit 27 .

[0110] The facility 20 has signed a contract with the authorized personnel in the facility to allow the provision and use of medical data. The data user 33a or the data evaluator / user 32 is a person who has signed the contract and has the data use authority. In addition, the facility 20 can also set the data use authority to multiple levels.

[0111] In step 601, the data user 33a operates the data use terminal 13a to access the data search input screen ( Figure 7 ) and input the search condition. The data use request processing unit 25 receives the input of the search condition.

[0112] like Figure 7 Thus, the data search input screen includes an area 71 for selecting the type of data to be searched, an area 72 for inputting the purpose of use of the data, and an area 73 for inputting a search keyword. The data user 33a inputs in each of these areas in step 601. In addition, the data search input screen also includes an area 74 for inputting a plurality of conditions for advanced search. When the data user 33a sets more specific search conditions, he / she also inputs the search conditions in the area 74 for advanced search.

[0113] In step 602, the data utilization request processing unit 25 causes the data matching unit 26 to extract medical data that matches the search condition received in step 601 from the database of the storage unit 15. Specifically, the data matching unit 26 performs a process of searching and extracting medical data of the data type input in step 601 that contains words and phrases that match the input search keyword from the database.

[0114] If the result of the data matching process in step 602 is that there is no medical data matching the search condition in the database (no corresponding data), the data use request processing unit 25 proceeds to step 604 (step 603). In step 604, the data use request processing unit 25 notifies (outputs) information indicating that there is no corresponding data to the terminal 13a used by the data user 33a via the communication device 49, and ends.

[0115] On the other hand, if the result of step 602 is that medical data that matches the search condition exists in the database (corresponding data exists), the data use request processing unit 25 proceeds to step 605. In step 605, the data use request processing unit 25 performs a part of the medical data extracted in step 602 to be hidden according to the data use permission level of the data user 33a. The so-called hiding process is, for example, a process of anonymizing the name of the evaluator or not displaying the camera type. In the hiding process, which item is hidden according to the data use permission level of the data user 33a is performed according to a predetermined rule.

[0116] In step 606 , the data use request processing unit 25 outputs the medical data extracted in step 602 to the terminal 13 a used by the data user 33 a via the communication device 49 , thereby providing the medical data to the user 33 a .

[0117] In step 607, the feedback processing unit 27 receives an evaluation of whether one or more search keywords received from the data user 33a in step 601 are useful. The feedback processing unit 27 adds a useful label to the search keywords evaluated as useful, and adds a non-useful label to the search keywords determined to be not useful, and stores them in the storage unit 15 as part of the data in the database in correspondence with the medical data extracted in step 602.

[0118] The feedback information (search keywords with tags added) stored in the database is used in the subsequent data matching process. In this way, the feedback information can be accumulated and the accuracy of data matching can be improved.

[0119] use Figure 8 The operation of the feedback processing unit 27 in step 607 will be described in further detail.

[0120] In step 801, the feedback processing unit 27 causes the terminal 13a to display a feedback screen to receive evaluation from the data user 33a.

[0121] exist Fig. 9 An example of a feedback screen is shown. The feedback screen is displayed on the terminal 13a of the data user 33a. The screen displays: one or more corresponding data (image data) 71 provided to the user by the data use request processing unit 25 in step 606; a keyword 72 input by the user 33a as a search condition for the data 71 in step 601; and an input field 73 for inputting a check (mark, etc.) for selecting a useful keyword and an unuseful keyword from the keywords.

[0122] The user 33a selects a useful keyword and enters a mark in the input field 73. In addition, the user selects a keyword that is not useful and enters another mark in the input field 73. In this way, useful and useless keywords can be fed back for each corresponding data. For example, the following structure is set: when the user 33a enters a check mark in the input field 73, the keyword is fed back as useful, when the user enters an × mark, the keyword is fed back as not useful, and when nothing is entered in the input field 73, the fact that no feedback is given to the keyword is fed back.

[0123] exist Fig. 9 In the example of Figure 7 An example of a feedback screen of corresponding data (image data) obtained by searching by inputting "research" as "data use purpose" in the search condition input screen of the advanced search, inputting "heart" as "part" in search condition 1 of the advanced search, and inputting "septal defect" as "disease name" in search condition 2. In addition, the user 33a can also Fig. 9 All data can be uniformly fed back in the feedback screen.

[0124] In step 802, the feedback processing unit 27 determines whether the evaluation made by the user is useful for each keyword. If the evaluation is useful, the process proceeds to step 803, and a "useful tag" is added to the keyword, and the keyword is stored in the feedback information storage area 54 of the database of the storage unit 15 in correspondence with the corresponding data (image data). On the other hand, if the evaluation is not useful, the feedback processing unit 27 proceeds to step 804, and a "non-useful tag" is added to the keyword, and the keyword is stored in the feedback information storage area 54 in correspondence with the corresponding data (image data).

[0125] In step 805, the number of times the corresponding data (image data) is extracted (corresponding to the search condition) by the data matching unit 26 in step 602 is counted. The counted number of times is stored in the feedback information storage area 54 in association with the corresponding data (image data).

[0126] Through the above, the processing of the feedback processing unit 27 is completed.

[0127] Table 3 shows an example of a table of the feedback information storage area 54 for storing feedback information. As shown in Table 3, the feedback information storage area 54 stores information in a table format. In this table, evaluation data ID, evaluation data type, number of matches (corresponding to the search condition), feedback keywords with useful tags attached, and keywords with non-useful tags attached are stored in correspondence.

[0128]

Table 3

[0129] Table 3

[0130]

[0131] For example, in the example of Table 3, image data No. 284748 has a history of being matched 10 times (corresponding to the search condition). It can be seen that in this image data, the searched keywords "brain" and "research" are fed back with useful tags, and "septal defect" is fed back with a non-useful tag. As described above, keywords with useful tags and non-useful tags are registered in sequence to form the feedback information table of Table 3.

[0132] The information of useful labels and non-useful labels is used in the corresponding data matching evaluation process next time.

[0133] Here, use Fig.10 To explain in detail Figure 6 In step 602, the data matching unit 26 extracts the medical data consistent with the search keyword through data matching processing.

[0134] In step 1001, the data matching unit 26 Figure 6 The search conditions (data type, search keyword) received in step 601 and the information of the data user 33a who input the search conditions are registered in the corresponding items of the table in the search condition summary storage area 52 of the database of the storage unit 15.

[0135] Table 4 is an example of a table in the search condition summary storage area 52. Figure 7 The search condition input screen enters each item such as the search keyword, and registers the ID of the data user 33a as the user ID.

[0136]

Table 4

[0137] Table 4

[0138]

[0139] Next, in step 1002 , the data matching unit 26 uses the information of the search condition summary table in Table 4 and the information of the table of feedback information of the previous data matching stored in Table 3 to evaluate the data matching degree.

[0140] Here, the data matching evaluation process is a process of counting the number of hits of each item in the table of the search condition summary of Table 4 (search data type, search conditions, data purpose, search keywords) in the string search against each item in the table of the database of the storage unit 15 of Table 1 and each item in the table of Table 3 fed back when the image data (evaluation data) (corresponding to the search conditions) of Table 1 was extracted in the past (before the previous time).

[0141] For example, when the search data type is "image", the data purpose is "research", the search condition 1 is "heart", and the search condition 2 is "septal defect", the data matching unit 26 searches for the character strings of "research", "heart", and "septal defect" from the contents of each item in the table of Table 1 and the table of feedback information in Table 3 (the type is image data) of the image stored in the database for the same image data (evaluation data), and counts the number of hits (matching) hits.

[0142] Since the data matching degree (suitability) is higher as the number of search hits is larger, the data matching unit 26 preferentially extracts image data with a high data matching degree as image data that matches the search condition.

[0143] Furthermore, when a character string other than a useful tag matches the search condition, the data matching unit 26 reduces the degree of data matching and does not perform extraction.

[0144] Finally, the data matching unit 26 extracts the matched corresponding data, proceeds to step 603, and displays the matching result to the data user.

[0145] As described above, the medical data evaluation management device 10 can efficiently aggregate and provide corresponding data in accordance with specific purposes and conditions, thereby improving the accuracy of the provided data.

[0146] In the second embodiment, since useful or useless search keywords are registered through a simple feedback process of the data user 33a, the accuracy of providing image data required by the user can be improved.

[0147] In the second embodiment, before outputting the image data matching the search condition to the data utilization terminal 13 a , a part of the data can be concealed in step 605 .

[0148] For example, in the present embodiment, the terminal 13a for the internal facility 20 and the terminal 13b for the external facility 21 are connected to the medical data evaluation management device 10 via different in-facility networks (intranets) 16 or out-facility networks (Internet) 17. Therefore, the data use request processing unit 25 can change the level of anonymization depending on whether the data use terminal 13a, 13b that transmits the medical data is the data use terminal 13a for the internal facility 20 or the data use terminal 13b for the external facility 21.

[0149] In addition, for example, the purpose of use (application) of the data user who operates the data use terminal 13a of the internal facility 20 is to collect data for clinical research, to collect information for business management, personnel evaluation, etc. The purpose of use of data by the data user of the external facility 21 is to collect data for research, etc. The data use request processing unit 25 can also change the level of anonymization in accordance with these purposes of use (application) by the medical data evaluation management device 10.

[0150] According to the first and second embodiments described above, the user evaluates the medical image via the evaluation / utilization terminal 12, and a mark such as "good" is added (displayed in an overlapping manner) as the evaluation result. Thus, although the user's subjective evaluation opinions are not directly recorded in the database, a database that can grasp the subjective evaluation opinions of the user who performed the evaluation can be generated based on the keywords and feedback entered by the user when requesting data.

[0151] For example, when a user wishes to collect images that need to be improved in image quality, he or she may search using keywords such as "image", "heart", and "poor image quality". As search results, images including images such as "good image quality", "need to be improved in image quality", "typical disease images", and "rare disease images" are provided. If a user selects an image from the provided images and provides feedback, for example, information such as "poor image quality" is added to the information of the target image, thereby adding the subjective evaluation point of view of the user who has made the evaluation.

[0152] In addition, in the present embodiment, an example is described in which a mark such as a character string representing "good" is displayed in the evaluated image, but the present embodiment is not limited to the mark of the character string "good" and can be changed to another form of mark by user setting.

[0153] <Third Embodiment>

[0154] As a third embodiment of the medical data evaluation application system 1, Fig.11The processing of the data use request processing unit 25, the data matching unit 26 and the feedback processing unit 27 when the external facility data user 33b requests the use of data will be described. If the user is the external facility data user 33b, the charge determination unit 28 further determines whether to charge.

[0155] Fig.11 2 is a flowchart showing the processing operations of the data use request processing unit 25, the data matching unit 26, the feedback processing unit 27 and the charge determination unit 28 of the third embodiment. Fig.11 In that case, except for adding external user authentication and billing determination, everything else is the same as Figure 6 The process is the same, so add the same action Figure 6 The same reference numerals are used for brief description.

[0156] First, in step 601, the data user 33b inputs a search condition, and the data use request processing unit 25 receives the input of the search condition.

[0157] In the next step 1101, the data use request processing unit 25 confirms whether the data user 33b has the certification of the facility 20. When the internal facility 20 has signed a service provision contract with the external data user 33b, the data use request of the storage unit 15 of the internal facility 20 can be made through the medical data evaluation management device 10.

[0158] In step 1102, if the external data user 33b does not have authentication and use is not permitted, the process proceeds to step 1103, the authentication confirmation result is notified to the user 33b, and the process ends.

[0159] On the other hand, in the case of permission to use, Figure 6 Steps 602 to 607 are performed in the same manner. However, between step 603 and step 605, a process of determining whether to charge the data user 33b is performed (step 1104). The charge determination unit 28 determines whether the user is subject to charge based on whether there is a charge contract, whether there is a past charge history, and whether there is a history of feedback information on providing data stored in the user information storage area 53 of the storage unit 15.

[0160] If charging is necessary, the process proceeds to step 1105 and the data user 33b is charged (step 1105).

[0161] Table 5 shows an example of a table of user information stored in the user information storage area 53. As shown in Table 5, user information that uses the present system 1 is stored in the user information table in advance.

[0162]

Table 5

[0163] Table 5

[0164]

[0165] The user information that has concluded a contract with the internal facility 20 is input into Table 5. When the external facility 21 is first registered in the system, the user information of the external facility 21 is input into Table 5. Thus, the user information table of Table 5 is formed.

[0166] A unique user ID is assigned to each user who uses the present system 1. The data structure of the user information table in Table 5 is a collection of records that uses the user ID as a key and is composed of data such as name, occupation type, affiliated facility, and professional field, and further records whether or not there is a paid contract based on the usage history of the present system.

[0167] use Fig.12 The process is used to illustrate the charging determination in step 1104.

[0168] The billing determination unit 28 refers to the user information table in Table 5 to search for information on the data user 33b of the corresponding external facility 21, and determines whether or not a billing contract exists (step 1201).

[0169] In step 1201, if the corresponding data user 33b is recorded as having a charge contract in Table 5, the process proceeds to step 1204 and determines that no charge is required. In step 1201, if there is no charge contract, the process proceeds to step 1202. If there is a past charge history, the process further proceeds to step 1203. If there is feedback information, the process proceeds to step 1204 and determines that no charge is required.

[0170] On the other hand, for the external data user 33b, if there is no past charging history, or if there is a past charging history but no feedback is given, it is determined that charging is necessary (step 1205).

[0171] According to the above, if it is determined that charging is necessary, in step 1105, the charging determination unit 28 charges the user. Figure 6 Steps 605 to 607 are performed in the same manner.

[0172] In addition, the system 1 can also be configured to change the charging conditions through the charging operation form set individually by the internal facility 20, thereby setting a more complex charging determination process. For example, the following operation can be performed: when a user without a charging contract gives a feedback ( Figure 8In step 801), in the next use, the download of 100 pieces of data is made free, or for users with paid contracts, the more feedback they receive, the greater the discount they will get when they sign the contract next time.

[0173] The data use fee charged for the use of the above-mentioned medical data may be determined according to the contract content of the data user. For example, the following structure may be adopted: when the data user 33a of the internal facility 20 uses the data evaluated by the data evaluator / user 32, no data use fee is required, and when the data user of the external facility 21 uses the data evaluated by the internal evaluator 32, the data use fee is charged.

[0174] As a result, a business model is established in which a manager of the internal facility 20 operating the system 1 signs a data provision contract with a manager of the external facility 21, and the internal facility 20 operates the system 1 using the profits obtained from the data provision as capital.

[0175] In the case where the above-mentioned business model is assumed, regarding stakeholders related to the collection and use of data information, medical practitioners of the internal facility 20 are assumed to be the evaluators 32 and users 33a of the internal facility 20. In addition, medical practitioners of other medical facilities, clinical trial institutions, practitioners of medical and pharmaceutical companies, etc. are assumed to be the users 33b of the external facility 21. For example, in the case where hospital A, which is the internal facility 20, has signed a contract with an IT company (external facility 21) that develops image diagnosis support software based on artificial intelligence, the system 1 can provide the IT company with medical images of the image quality level required by the IT company (external facility 21) from among the medical images evaluated by the evaluators 32 of hospital A.

[0176] In the second embodiment described above, the feedback processing unit 27 displays a feedback screen on the terminal 13a of the internal facility 20 and receives evaluations from the data user 33a. However, it is also possible to receive evaluations from the data user 33b of the external facility 21 of the third embodiment via the terminal 13b.

[0177] <Fourth Embodiment>

[0178] In the first to third embodiments, examples in which the evaluation target is image data are described. The fourth embodiment describes a case in which the evaluation target is an object other than an image.

[0179] Table 6 is a table showing examples of evaluation objects of different types such as images, patients, medical practitioners, diagnostic reports, and models, and their evaluation purposes, etc. As shown in Table 6, since there are differences in the attributes of the evaluation objects of different types, the implementation screens of the evaluation objects, the evaluation purposes, the information to be retrieved, and the data utilization purposes become various.

[0180]

Table 6

[0181] Table 6

[0182]

[0183] In addition, the types and usage environments of the medical information systems 11 of general medical facilities vary depending on the manufacturer of the medical information system 11 and the internal facilities that use the medical information system 11. For example, the attending physician information is displayed in the electronic medical record and document creation system (refer to Fig.13 , Fig.14 ), the photographer and the doctor who read the film are displayed on the film reading diagnosis system (reference Fig.15 ). Therefore, the medical data evaluation management device 10 of the present embodiment is preferably configured to be operable in accordance with various types and usage environments of the medical information system 11 using internal facilities.

[0184] In addition, in the medical information system 11, there are various methods for the operation method of adding a mark such as a character string of "good" described in step 401 of the second embodiment. For example, a method of "right-clicking the evaluation object" can be considered ( Fig.13 ), the method of "clicking the evaluation button located in the menu" ( Fig.14 ), the method of "marking a character and clicking it" ( Fig.15 ) etc. Therefore, the medical data evaluation management device 10 is expected to be configured to be able to cope with these various operation methods. That is, the medical data evaluation management device 10 of this embodiment is expected to be configured to be able to cope with methods other than the embodiments shown in Table 6.

[0185] Next, an example of an evaluation method in a case where the evaluation objects are patients, medical practitioners, diagnosis reports, and equipment models will be described.

[0186] When the evaluation target is a patient, the data evaluator / user 32 of the internal facility 20 adds "good" to the patient who deserves evaluation on the display screen of the medical information system 11. This allows evaluation of a rare patient or a typical patient, for example. Fig.13 2 is an example of a display screen. In this example, the medical information system 11 is an electronic medical record.

[0187] The medical data evaluation management device 10 refers to the patient ID displayed in the electronic medical record, searches for patient information with the word "good" attached in the medical information storage 14, reads out patient information such as patient ID, age, gender, disease name, heart rate, blood pressure, diagnostic images, diagnostic reports, etc., and saves it in the database storage area 51 in the storage unit 15.

[0188] Table 7 shows an example of the patient information evaluation information table registered in the database storage area 51 .

[0189]

Table 7

[0190] Table 7

[0191]

[0192] Next, the case where the evaluation target is a medical practitioner will be described. When the evaluation target is a medical practitioner, the data evaluator / user 32 of the internal facility 20 adds "good" to the medical practitioner worthy of evaluation on the display screen of the medical information system 11. This allows, for example, the evaluation of a medical practitioner with high skills.

[0193] The medical data evaluation management device 10 refers to the medical practitioner information displayed on the medical information system 11, searches for medical practitioner information with the tag "good" from the medical practitioner list stored in the medical information storage device 14 or the medical practitioner list prepared in advance by the internal facility 20, reads out information such as the medical practitioner ID, continuous working years, department to which he belongs, and occupation type, and saves it in the database storage area 51 of the storage unit 15.

[0194] exist Fig.13 An example of a screen showing a doctor being rated "good" is shown. Fig.15 An example of a screen in which a “good” comment is given to the doctor who interprets the image is shown.

[0195] Table 8 shows an example of the medical practitioner evaluation information table stored in the database storage area 51 .

[0196]

Table 8

[0197] Table 8

[0198] Evaluation data ID Medical Practitioner ID Continuous production years Department Occupational Type … 234576 301 9 years Gastroenterology Physician … 431646 302 3 years Radiology Diagnostic Radiographer … … … … … …

[0199] Next, the case where the evaluation object is a diagnostic report will be described. In the case where the evaluation object is a diagnostic report, the evaluator of the internal facility 20 adds "good" to the diagnostic report that deserves evaluation on the display screen of the medical information system 11. In this way, the diagnostic report with good structure and text can be evaluated. Fig.14 An example of a screen in which "good" is added to the diagnosis report is shown.

[0200] The medical data evaluation management device 10 refers to the patient ID recorded in the diagnosis report with "good" attached on the display screen of the medical information system 11, searches for the corresponding patient in the medical information storage 14, retrieves the diagnosis report, diagnosis report type, report maker and other information, and saves it in the database storage area 51 of the storage unit 15.

[0201] Table 9 shows an example of the diagnosis report evaluation information table registered in the database storage area 51 .

[0202]

Table 9

[0203] Table 9

[0204] Evaluation data ID Types of diagnostic reports Report creator ID Continuous working years … 583945 Cardiac echo 601 5 years … 125764 Brain MRI 602 8 years … … … … … …

[0205] Finally, the case where the evaluation object is a model of a medical imaging device (medical imaging equipment) is described. When the evaluation object is a model of a medical imaging equipment, the data evaluator / user 32 of the internal facility 20 adds "good" to the model worthy of evaluation in the medical information system 11. In this way, models with good performance can be evaluated. Fig.15 An example of a screen in which "good" is added to the model is shown.

[0206] The medical data evaluation management device 10 refers to the model name displayed on the display screen of the medical information system 11, searches for the model with the word "good" attached from the model information list stored in the medical information storage 14 or the model information list prepared in advance by the internal facility 20, retrieves the information such as the medical imaging equipment name, model, and manufacturing year, and saves it in the database storage area 51 of the storage unit 15.

[0207] Table 10 shows an example of the model evaluation information table registered in the database storage area 51 .

[0208]

Table 10

[0209] Table 10

[0210]

[0211] As described above, by using the medical data evaluation management device 10, it is possible to simply evaluate medical data in accordance with various usage purposes in a variety of information infrastructure environments, collect the evaluated data to create a database, and manage it.

Claims

1. A medical data evaluation practical application system, characterized in that: have: a communication unit for receiving an evaluation result for given medical data from a user operating the user terminal via the connected user terminal; A database generating unit connected to a medical information storage device storing medical data in advance; and Storage Department, The database generating unit generates a database by repeatedly performing a process of selectively reading out the medical data for which the communication unit receives the evaluation result from the medical data accumulated in the medical information storage and storing the medical data in the storage unit each time the evaluation result is received.

2. The medical data evaluation practical application system according to claim 1, characterized in that: The evaluation result includes information of the user who has made the evaluation. The database generating unit stores the user information as a part of the data of the database in the storage unit in correspondence with the medical data.

3. The medical data evaluation practical application system according to claim 1, characterized in that: The medical data includes one or more information of an image of a patient, an imaged part, a type of an image pickup device, and a type of camera.

4. The medical data evaluation practical application system according to claim 1, characterized in that: The medical data evaluation actual application system also has a data utilization request processing unit and a data matching unit. The communication unit receives a data utilization request together with one or more search keywords from a user via the user terminal. When the communication unit receives the data utilization request, the data utilization request processing unit causes the data matching unit to extract medical data containing words and phrases consistent with the search keyword from the database, and outputs the medical data extracted by the data matching unit from the communication unit to the user terminal.

5. The medical data evaluation practical application system according to claim 4, characterized in that: The communication unit receives information of the user who makes the data utilization request together with the data utilization request. The data use request processing unit performs processing to hide a part of information included in the output medical data based on the user information before outputting the extracted medical data.

6. The medical data evaluation practical application system according to claim 4, characterized in that: The medical data evaluation practical application system also has a feedback processing unit. After outputting the extracted medical data to the user terminal, the communication unit receives the evaluation of whether one or more of the search keywords are useful together with the data utilization request from the user who made the data utilization request. The feedback processing unit adds a label of usefulness to the search keyword evaluated as useful, adds a label of non-usefulness to the search keyword determined as not useful, and stores it in the storage unit corresponding to the medical data as part of the data of the database.

7. The medical data evaluation practical application system according to claim 6, characterized in that: When the data matching unit extracts medical data containing words and phrases consistent with the search keyword from the database, and in the case where the useful tag is attached and stored to the consistent search keyword, the medical data corresponding to the search keyword to which the useful tag is attached is set to have a high degree of consistency and is extracted with priority.

8. The medical data evaluation practical application system according to claim 7, characterized in that: When the data matching unit extracts medical data containing words and phrases consistent with the search keyword from the database, if the useless label is attached and stored to the consistent search keyword, the matching degree of the medical data corresponding to the search keyword to which the useless label is attached is reduced and the extraction is not performed.

9. The medical data evaluation practical application system according to claim 4, characterized in that: When the data matching unit extracts the medical data, the data utilization request processing unit uses the number of times the medical data is extracted as part of the data in the database and stores it in the storage unit corresponding to the medical data. When extracting medical data including words and phrases matching the search keyword from the database, the data matching unit determines that the medical data extracted more times has a high degree of matching and preferentially extracts the medical data.

10. The medical data evaluation practical application system according to claim 4, characterized in that: The medical data evaluation practical application system further comprises a charging determination unit. When the data use request processing unit receives the data use request from the user via the communication unit, the charge determination unit charges a fee for the data use request if the user is an external user.

11. The medical data evaluation practical application system according to claim 1, characterized in that: The medical data includes at least one of an image, a patient, a medical practitioner, a diagnosis report, and a model of a medical imaging device.

12. A practical application method for medical data evaluation, characterized in that: receiving evaluation results for given medical data via a connected user terminal, A database is created by repeatedly performing a process of selectively reading the medical data for which the evaluation result is received from the medical data accumulated in the medical information storage and storing the medical data in the storage unit each time the evaluation result is received.

Images