Method for assisting medical workers in interpreting genetic information, information management system, and integrated data management device

Abstract

The present invention relates to a method, an information management system, and an integrated data management device for assisting medical workers in interpreting genetic information. An expert meeting for assisting multiple medical workers in interpreting genetic information. The integrated data management device (A) is an integrated data management device (A) for assisting multiple medical workers in interpreting genetic information, i.e., an expert meeting, and comprises a control unit (10) and a storage unit (30). The control unit (10) receives the schedule setting of the expert meeting, extracts multiple medical workers who participated in the expert meeting and are recorded in association with the schedule of the accepted expert meeting from the storage unit, and sends the schedule of the expert meeting to the terminal devices (13) of the extracted multiple medical workers.

Description

Technical Field

[0001] The present invention relates to methods and the like for assisting medical workers in interpreting gene information. Background Art

[0002] In recent years, genetic tests to examine mutations in specific genes have been conducted to confirm the presence of genetic diseases, the effectiveness of drugs, etc. In particular, research on oncogenomic medicine is being promoted in cancer treatment, in which a genome panel test that can comprehensively examine mutations in multiple genes at once is performed on each patient using a next-generation sequencer or the like, and a treatment policy suitable for each patient is formulated based on the results.

[0003] Here, the electronic medical records, pathological images, and various test results of genome panels of patients, which are used as references when formulating treatment policies suitable for each patient, are managed by different systems in medical facilities. Patent document 1 discloses an information platform that aggregates the electronic medical records, pathological images, and test results of genome panels scattered in a certain medical facility and assists in formulating treatment policies for patients.

[0004] Prior art literature

[0005] Patent Literature:

[0006] Patent Document 1: Japanese Patent Application Publication No. 2018-533123 Summary of the invention

[0007] Problems to be solved by the invention

[0008] When formulating a treatment policy for each patient based on the results of a genome panel test, it is important to hold an expert meeting of a group of experts who can provide medical explanations, and have multiple experts formulate the most suitable treatment policy for the patient. This expert meeting is also called an "expert panel". When an expert meeting is held, multiple experts such as attending physicians, pathologists, bioinformatics experts, genetic counselors, molecular genetics researchers, and clinical inspectors of testing facilities participate. In the expert meeting, clinical information from medical facilities such as each patient's electronic medical records and pathological images, information from testing facilities such as genome panel test results, the patient's genetic background, the latest academic insights, etc. are comprehensively discussed, and a treatment policy for each patient is formulated. Sometimes, in addition to multiple experts affiliated with either medical facilities or testing facilities, experts who do not belong to specific facilities participate in the expert meeting.

[0009] In order to hold an expert meeting, it is necessary to provide each expert belonging to different facilities with the information required to formulate a treatment policy and adjust the schedule of the expert meeting so that each expert can participate, etc. It is predicted that the number of expert meetings will increase significantly as genomic medicine becomes more popular in the future. It is expected that it will take a huge amount of work to adjust the schedule of the expert meeting between the experts participating in the expert meeting or to accurately and appropriately provide the information referenced in the expert meeting to each expert.

[0010] An object of one aspect of the present invention is to assist an expert meeting attended by experts belonging to different facilities.

[0011] Means for solving problems

[0012] Reference Fig.32 In order to solve the above-mentioned problems, one embodiment of the present invention is a method for assisting an expert meeting in which a plurality of medical workers interpret genetic information, which comprises the following steps: a step of accepting the schedule setting of the expert meeting (S410); a step of extracting the plurality of medical workers who participated in the expert meeting and recorded in association with the accepted schedule of the expert meeting (S413); a step of transmitting the plurality of medical workers who participated in the expert meeting to the terminal devices (S414) of the plurality of medical workers who participated in the expert meeting Figure 2 B13) The process of sending the schedule of the expert meeting (S414).

[0013] In addition, refer to Figure 2 Another aspect of the present invention is an information management system (100) for assisting a specialist conference in which a plurality of medical workers interpret genetic information, comprising: a terminal device (B13) for medical workers, and a control unit ( Figure 3 10) and storage unit ( Figure 3 30) of the integrated data management device (A), the control unit ( Figure 3 10) accepting the schedule setting of the expert meeting, extracting the multiple medical workers who participated in the expert meeting and recorded in association with the accepted schedule of the expert meeting, and sending the schedule of the expert meeting to the terminal devices (B13) of the multiple medical workers who participated in the expert meeting.

[0014] In addition, refer to Figure 3 Another embodiment of the present invention is a comprehensive data management device (A) for assisting an expert meeting in which a plurality of medical workers interpret genetic information, the device comprising a control unit (10) and a storage unit (30), wherein the control unit (10) receives a schedule setting of the expert meeting, extracts a plurality of medical workers who have participated in the expert meeting and are recorded in association with the schedule of the accepted expert meeting, and transmits the data to the terminal devices ( Figure 2 13) Send the agenda of the expert meeting.

[0015] Effects of the Invention

[0016] According to the present invention, it is possible to facilitate an expert conference in which experts belonging to different facilities participate. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] Figure 1 This is a diagram showing an example of the flow of genetic testing and treatment.

[0018] Figure 2 It is a diagram showing a configuration example of an information management system.

[0019] Figure 3 This is a block diagram showing a configuration example of an integrated data management device.

[0020] Figure 4 This is a diagram showing an example of the flow of genetic testing to which the information management system according to one embodiment of the present invention is applied.

[0021] Figure 5 This is a flowchart showing an example of processing in the inspection request acceptance step.

[0022] Figure 6 This is a diagram showing an example of an authentication table.

[0023] Figure 7 This is a diagram showing an example of a GUI displayed on a terminal device for inputting inspection request information.

[0024] Figure 8 This is a diagram showing an example of a facility table.

[0025] Fig. 9 This is a diagram showing an example of a genome set table.

[0026] Fig.10 This is a diagram showing an example of a user registration form.

[0027] Fig.11 It is a diagram showing an example of an inspection facility table.

[0028] Fig.12 This is a diagram showing an example of the processing flow of the bonding step.

[0029] Fig.13 This is a diagram showing an example of a GUI including fields for inputting a patient's disease name and disease ID.

[0030] Fig.14 This is a diagram showing an example of a master table.

[0031] Fig.15 This is a diagram showing a configuration example in which there is an administrator having management authority over the integrated data management device A.

[0032] Fig.16 This is a flowchart showing an overview of a process in which the control unit associates a patient with experts who participate in the expert conference.

[0033] Fig.17 This is a diagram showing an example of a group table.

[0034] Fig.18 This is a diagram showing an example of a schedule.

[0035] Fig.19 It is a diagram showing an example of the integrated ID table.

[0036] Fig. 20 It is a diagram showing another example of the integrated ID table.

[0037] Fig.21 This is a diagram showing an example of a patient information table.

[0038] Fig. 22 This is a diagram showing an example of a disease table.

[0039] Fig.23 It is a diagram showing an example of a pathological image table.

[0040] Fig.24 This is a diagram showing an example of an inspection result table.

[0041] Fig.25 It is a diagram showing an example of a comment information table.

[0042] Fig.26 This is a diagram showing an example of a role table.

[0043] Fig. 27 It is a diagram showing an example of the access permission management table.

[0044] Fig.28 This is a diagram showing an example of a screen display that is displayed when logging into the data integration server from a terminal device of the transportation business department.

[0045] Fig.29 This is a diagram showing an example of a GUI displayed on a terminal device for accepting an input of a reservation for a specialist conference.

[0046] Fig.30 This is a diagram showing an example of a GUI displayed on a terminal device for accepting an input of a reservation for a specialist conference.

[0047] Fig.31 This is a diagram showing an example of a process flow for sending a notification of a scheduled specialist conference to the addresses of each medical worker.

[0048] Fig.32This is a diagram showing an example of a process flow performed by the control unit of the integrated data management device for transmitting information on the schedule of the expert meeting to the terminal device of each medical worker.

[0049] Fig.33 This is an example of a GUI in a terminal device used by a medical professional that includes information on a test request list and a specialist meeting schedule.

[0050] Fig.34 This is a diagram showing an example of a processing flow for causing a terminal device to display information on a list of examination requests and a schedule of a specialist meeting associated with a patient for which a medical worker is in charge.

[0051] Fig.35 This is a diagram showing an example of a process flow performed by the control unit of the integrated data management device for causing the terminal device of the medical worker to display information associating information on the progress of an examination with information on the schedule of a specialist meeting.

[0052] Fig.36 This is a diagram showing an example of a GUI displayed on a terminal device for accepting input of given information from experts attending an expert conference.

[0053] Fig.37 This is a diagram showing an example of a GUI displayed on a terminal device for accepting schedule settings for an expert meeting.

[0054] Fig.38 This is a diagram showing an example of a GUI in a terminal device of a medical worker that includes information related to the schedule of expert meetings and each expert meeting.

[0055] Fig.39 This is a diagram showing an example of a GUI in a terminal device of a medical worker that includes information related to the schedule of expert meetings and each expert meeting.

[0056] Fig.40 This is a diagram showing an example of a GUI including information related to each expert conference in a terminal device of a medical worker.

[0057] Fig.41 This is a diagram showing an example of a processing flow for causing a terminal device to display a schedule of specialist meetings related to a patient for which a medical worker is in charge and information related to each specialist meeting.

[0058] Fig.42 This is a diagram showing an example of a processing flow performed by the control unit of the integrated data management device for causing a terminal device of a medical worker to display a schedule of specialist meetings related to a patient for which the medical worker is responsible and information related to each specialist meeting.

[0059] Fig.43 This is a diagram showing an example of a process flow for displaying information related to a patient for which a medical staff is in charge.

[0060] Fig.44 This is a diagram showing an example of a process flow performed by the control unit of the integrated data management device for causing a terminal device of a medical worker to display clinical information and test results of a patient.

[0061] Fig.45 This is a diagram showing an example of a screen display that is displayed on the terminal device by the control unit in response to a received information acquisition request.

[0062] Fig.46 This is a diagram showing an example of a method in which the control unit associates each data input as inspection request information with the data in the integrated database.

[0063] Fig.47 This is a flowchart for explaining an example of processing in which the control unit associates information on mutations detected by the test and information on therapeutic drugs with the test results.

[0064] Fig.48 This is a diagram showing an example of a mutation table.

[0065] Fig.49 This is a diagram showing an example of a therapeutic drug table.

[0066] Fig.50 This is a flowchart for explaining an example of a process in which the control unit associates input annotation information with an inspection result.

[0067] Fig.51 This is a diagram showing an example of a display screen of a mutation database search portal.

[0068] Fig.52 This is a diagram showing an example of a screen display used for searching related information.

[0069] Fig.53 This is a diagram showing a configuration example of a medical facility including an information management device.

[0070] Fig.54 This is a diagram showing another example of the configuration of the information management system. DETAILED DESCRIPTION

[0071] An embodiment of the present invention will be described in detail below.

[0072] (Genetic Test)

[0073] First, use Figure 1 Genetic testing is explained. Figure 1This is a diagram showing an example of the process of genetic testing and treatment. Here, the process of performing a genome panel test as an example of a genetic test is described. A genome panel test is a test that can comprehensively investigate multiple gene mutations for each patient at one time using a next-generation sequencer or the like.

[0074] <Step I: Patient explanation (before requesting examination)>

[0075] Step I is a step in which the responsible physician H1a as a medical worker in the medical facility B1 explains the advantages and precautions of genome panel testing to the patient P1. When the patient P1 agrees to the genome panel testing, the process proceeds to step II.

[0076] <Step II: Preparation of specimen>

[0077] Step II is the following step: In the medical facility B1, the pathologist H1b as a medical worker prepares a specimen for genomic panel examination. The specimen is a diseased tissue specimen from which genes for genomic panel examination can be extracted, for example, the diseased tissue of the patient P1 is fixed in formalin and embedded in paraffin (FFPE). Before step II, if the pathologist H1b has prepared a diseased tissue specimen for pathological diagnosis, the diseased tissue specimen can also be used for genomic panel examination.

[0078] It should be noted that, in the medical facility B1, a blood sample can be further collected from the patient P1 as a sample for extracting wild-type genes, which will become a comparison object when detecting gene mutations in diseased tissues. In this case, multiple samples such as FFPE samples and blood samples are provided for a single genome panel test.

[0079] Patient P1's lesion tissue specimen and blood specimen are transported from the medical facility to the testing facility C1 for genome panel testing. It should be noted that the transportation of patient P1's FFPE specimen and blood specimen can be carried out by a transporter or directly by the testing facility C1 that accepts the genome panel testing request.

[0080] <Step III: Sequencing>

[0081] Step III is the following step: In the inspection facility C1 that receives the diseased tissue specimen and blood specimen of patient P1, clinical inspector H3, who is a medical worker, performs pre-processing to extract genes from the diseased tissue specimen and blood specimen, and uses the next-generation sequencer C13 to read the base sequence of the extracted genes.

[0082] <Step IV: Preparation of inspection result report>

[0083] Step IV is the following step: In the inspection facility C1, the clinical inspector H3 analyzes the base sequence read by the next generation sequencer C13, determines whether there is a mutation in the base sequence, the location of the mutation, the type of mutation, etc., and prepares a test result report.

[0084] The test result report includes information about the genome set used in the test, information about the test results, and information about quality evaluation indicators used to evaluate the quality of the test. Information about the test results includes, for example, whether there is a mutation in the base sequence, the location of the mutation, and the type of mutation. In addition, the test result report may include drug information and academic paper information related to the mutation detected by the genome set test.

[0085] Here, "mutation" includes: replacement, deletion or insertion of nucleotides of a gene; fusion of genes; or copy number polymorphism. "Replacement" refers to the phenomenon that at least one base in a gene sequence becomes a different base. "Replacement" includes point mutations and single nucleotide polymorphisms. "Deletion" and "insertion" are also recorded as "InDel (Insertion and / or Deletion)". InDel is the phenomenon of inserting and / or deleting at least one base in a gene sequence. "Gene fusion" refers to the phenomenon that the sequence on the 5' side of a gene is combined with the sequence on the 3' end side of another gene due to chromosomal ectopy, etc. "Copy number polymorphism" means that the number of copies on the genome in each cell is different between individuals. Specifically, VNTR (Variable Nucleotide of Tandem Repeat, repetitive sequence polymorphism) and STRP (Short Tandem Repeat Polymorphism, microsatellite polymorphism), gene amplification, etc. can be cited as examples.

[0086] In addition, "information on quality evaluation indexes" is an index for evaluating whether the genome set inspection has been appropriately performed, and examples thereof include: the ratio of the read base sequence to the total base sequence contained in the gene to be analyzed, the depth of coverage of the read base sequence, whether the variation of the standard gene contained in the quality control sample has been detected, etc. Here, the quality control sample refers to a gene sample containing known variations that should be read in the sequence determination using the next generation sequencer C13.

[0087] <Step V: Convening an expert meeting>

[0088] Step V is the following step: a plurality of medical workers, who are experts in providing medical interpretation of the results of the genome panel examination, participate in an expert meeting in medical facilities B1, B2, examination facilities C1, C2, and external facilities D1 and D2. In the expert meeting, a plurality of medical workers refer to the genome panel examination result report, the clinical information of the patient P1, the genetic background of the patient P1, the latest academic insights, etc. to conduct multi-angle discussions and formulate effective treatment strategies for each patient. The "clinical information" of the patient P1 referred to in the expert meeting is, for example, the electronic medical record prepared by the medical facility B1 where the patient P1 was treated, and the pathological image taken by the pathologist H1b.

[0089] Here, the "medical workers" who participate in the expert meeting include, for example: (1) the physician H1a in charge of the patient P1, the pathologist H1b, and the specialist in cancer drug therapy, who are affiliated with the medical facility B1; (2) the clinical examiner H3, who is affiliated with the examination facility C1; (3) the bioinformatics expert, genetic counselor, molecular genetics researcher, and specialist in genetic medicine, who are affiliated with external facilities D1 and D2 such as research institutions and universities. That is, the expert meeting may be attended by multiple medical workers who belong to different facilities and organizations. The expert meeting may be a meeting held by convening medical workers in a certain medical facility B1, or it may be a video conference attended by some or all of the medical workers via a communication network.

[0090] <Step VI: Patient explanation (after expert meeting)>

[0091] Step VI is a step in which the attending physician H1a explains to the patient P1 the treatment policy for the patient P1 determined through the discussion at the expert meeting in the medical facility B1. When the patient P1 agrees, the process proceeds to step VII.

[0092] <Step VII: Treatment>

[0093] Step VII is a step in which, in the medical facility B1, the patient P1 is treated based on the treatment policy established by the discussion at the expert meeting. When a treatment that requires highly specialized knowledge and experience is performed, the treatment may be performed not at the medical facility B1 where the patient P1 is treated, but in collaboration with another medical facility B2 that has a system that can smoothly perform the treatment.

[0094] In order to hold an expert meeting in step V, it is necessary to collect all kinds of information for reference by multiple medical workers without omission and provide them to each medical worker in advance. However, for example, clinical information such as the electronic medical record and pathological images of patient P1 is managed in medical facility B1, and the results of genome panel tests are managed in testing facility C1. Therefore, as preparation for holding an expert meeting, operations requiring a huge amount of work such as retrieving information for reference of the expert meeting from multiple facilities and providing it to each medical worker are indispensable.

[0095] In the present invention, the test results of the genomic test request of the patient P1 are associated with the clinical information about the patient P1, and the associated test results and clinical information are provided to medical workers, thereby assisting the preparation for holding an expert meeting.

[0096] <Configuration of the information management system 100>

[0097] First, use Figure 2 The configuration of an information management system 100 according to one embodiment of the present invention will be described. Figure 2 It is a diagram showing a configuration example of the information management system 100 .

[0098] The information management system 100 includes an integrated data management device A and at least one terminal device B13, B23, C14, C24, D11, D21, and E12 installed in various facilities. The integrated data management device A and the terminal devices B13, B23, C14, C24, D11, D21, and E12 are connected to each other via a communication network 90 in a communicable manner.

[0099] The information management system 100 only needs to include the integrated data management device A and at least one of the plurality of terminal devices B13, B23, C14, C24, D11, D21, and E12, and other devices installed in the medical facilities B1, B2, the inspection facilities C1, C2, the external facilities D1, D2, and the transportation department E1 are not essential. In addition, the details of other devices installed in the medical facilities B1, B2, the inspection facilities C1, C2, the external facilities D1, D2, and the transportation department E1 will be described in detail later.

[0100] [Integrated data management device A]

[0101] The integrated data management device A is a computer that functions as a server. The integrated data management device A is connected to various devices such as the terminal devices installed in the medical facilities B1, B2, the inspection facilities C1, C2, the external facilities D1, D2, and the transportation department E1, as well as the variation information management device F11, the drug information management device F21, and the academic paper information management device F31 in a communicable manner via the communication network 90. ​​It should be noted that in this embodiment, an example in which the integrated data management device A is a cloud server is shown, but it is not limited to this.

[0102] Figure 3 1 is a block diagram showing a configuration example of the integrated data management device A. The integrated data management device A includes a control unit 10 as a CPU (Central Processing Unit) and a storage unit 30. The storage unit 30 stores a program 301 used in the operation of the information management system 100 and an integrated database 302.

[0103] The functions executed by the integrated data management device A are realized as follows: the control unit 10 reads the program 301 stored in the storage unit 30, expands the program 301 in the RAM (Random Access Memory), and executes the program 301.

[0104] The integrated database 302 stores various tables and data used when the control unit 10 executes various functions. Details of the various tables and data stored in the integrated database 302 will be described later.

[0105] [Medical facilities B1, B2]

[0106] Back to Figure 2 Medical facilities B1 and B2 are medical institutions such as hospitals to which medical workers such as the responsible physician H1a of the patient P1 belong.

[0107] Medical facilities B1 and B2 may include a core node hospital with advanced functions leading cancer genome medicine. In addition, medical facilities B1 and B2 may include a joint node hospital, which is a medical institution with a system that can smoothly implement cancer treatment, etc. in conjunction with the core node hospital. When a genome panel examination is performed on patient P1 of the joint node hospital, the examination results of patient P1 of the joint node hospital can be explained and a treatment policy can be formulated in an expert meeting hosted by the core node hospital.

[0108] It should be noted that the responsible physician H1a and the pathologist H1b affiliated with the medical facilities B1 and B2 can become medical workers participating in the expert meeting.

[0109] Medical facilities B1 and B2 are provided with electronic medical record management devices B11 and B21, pathological image management devices B12 and B22, and terminal devices B13 and B23. In addition, medical facilities B1 and B2 are provided with LAN (Local Area Network). Hereinafter, the LAN in the medical facility is referred to as "LAN in the medical facility". The LAN in the medical facility is connected to the communication network 90 in a communicative manner. The electronic medical record management devices B11 and B21, pathological image management devices B12 and B22, and terminal devices B13 and B23 are respectively connected to the LAN in the medical facility of the medical facilities B1 and B2 in a communicative manner.

[0110] The electronic medical record management devices B11 and B21 are computers that function as servers for managing electronic medical record information of patients in the medical facility B1. In addition, the pathological image management devices B12 and B22 are computers that function as servers for managing pathological images captured in the medical facility B1.

[0111] The terminal devices B13 and B23 are computer terminals used by medical workers belonging to the medical facilities B1 and B2. The terminal devices B13 and B23 are, for example, personal computers, tablet terminals, smart phones, etc. The terminal devices B13 and B23 have a communication unit with other devices, an input unit such as a keyboard and a microphone, a display unit such as a monitor, an output unit such as a speaker, etc.

[0112] [Inspection facilities C1, C2]

[0113] The inspection facilities C1 and C2 are inspection entrusted institutions to which medical workers such as clinical inspector H3 belong, and who carry out genome inspections in response to inspection requests from medical facilities B1 and B2 and prepare inspection result reports.

[0114] If the medical facilities B1 and B2 have examination rooms capable of performing genome panel examinations, genome panel examinations can be performed in the medical facilities B1 and B2. In this case, the medical facilities B1 and B2 also have the functions of the examination facilities C1 and C2.

[0115] It should be noted that clinical examiner H3 affiliated with examination facilities C1 and C2 can become a medical worker participating in the expert meeting.

[0116] Inspection facilities C1 and C2 are provided with inspection information management devices C11 and C21, next generation sequencers C13 and C23, and terminal devices C14 and C24. In addition, LAN is provided in inspection facilities C1 and C2. Hereinafter, the LAN in the inspection facility is referred to as "LAN in the inspection facility". The LAN in the inspection facility is connected to the communication network 90 in a communicable manner. Inspection information management devices C11 and C21, next generation sequencers C13 and C23, inspection facilities C1 and C2, and terminal devices C14 and C24 are connected to the LAN in the inspection facility of inspection facilities C1 and C2 in a communicable manner, respectively.

[0117] The inspection information management devices C11 and C21 are computers that function as servers for managing inspection information.

[0118] The next generation sequencers C13 and C23 are various devices used in the inspection performed by the inspection facility C1, and are, for example, next generation sequencers that can simultaneously and in parallel measure the base sequences of cut DNA fragments.

[0119] The terminal devices C14 and C24 are computer terminals used by medical workers belonging to the inspection facilities C1 and C2. The terminal devices C14 and C24 are, for example, personal computers, tablet terminals, smart phones, etc. The terminal devices C14 and C24 have, for example, a communication unit with other devices, an input unit such as a keyboard and a microphone, a display unit such as a monitor, an output unit such as a speaker, etc.

[0120] [External facilities D1, D2]

[0121] External facilities D1 and D2 are administrative departments and research institutes other than medical facilities B1 and B2 and examination facilities C1 and C2, to which experts, etc. belong. Examples of medical workers affiliated with external facilities D1 and D2 include bioinformatics experts, genetic counselors, and molecular genetics researchers.

[0122] It should be noted that bioinformatics experts, genetic counselors, and molecular genetics researchers affiliated with external facilities D1 and D2 can become medical workers participating in expert meetings.

[0123] The external facilities D1 and D2 are provided with terminal devices D11 and D21. In addition, LANs are provided in the external facilities D1 and D2. Hereinafter, the LANs in the external facilities are referred to as "LANs in the external facilities". The LANs in the external facilities are connected to the communication network 90 in a communicable manner. The terminal devices D11 and D21 are connected to the LANs in the external facilities of the external facilities D1 and D2 in a communicable manner, respectively.

[0124] The terminal devices D11 and D21 are computer terminals used by medical workers belonging to the external facilities D1 and D2. The terminal devices D11 and D21 are, for example, personal computers, tablet terminals, smart phones, etc. The terminal devices D11 and D21 have a communication unit with other devices, an input unit such as a keyboard and a microphone, a display unit such as a monitor, an output unit such as a speaker, etc.

[0125] [Transport Affairs Department E1]

[0126] The transportation office E1 is an office of a transportation company to which transportation personnel belong, and the transportation personnel transport the specimen from the medical facilities B1 and B2 that are the test requesters of the genome panel test to the test facilities C1 and C2 that are the test request destinations.

[0127] When the inspection facilities C1 and C2 have the function of transporting the specimen, the transport personnel affiliated with the inspection facilities C1 and C2 may receive the specimen from the medical facilities B1 and B2 and transport it to the inspection facilities C1 and C2. In this case, the inspection facilities C1 and C2 also function as the transport department E1.

[0128] It should be noted that usually the transport personnel of the Transport Affairs Department are not medical workers and do not attend expert meetings.

[0129] The transport affairs department E1 is provided with a transceiver management device E11 and a terminal device E12. In addition, a LAN is provided in the transport affairs department E1. The LAN in the transport affairs department is hereinafter referred to as "LAN in the transport affairs department". The LAN in the transport affairs department is connected to the communication network 90 in a communicable manner. The transceiver management device E11 and the terminal device E12 are connected to the LAN in the transport affairs department of the transport affairs department E1 in a communicable manner.

[0130] The transmission and reception management device E11 is a computer that functions as a server for managing transmission and reception of a subject.

[0131] The terminal device E12 is a computer terminal used by the transportation personnel belonging to the transportation affairs department E1. The terminal device E12 is connected to the integrated data management device A and the like via the communication network 90 in a communicable manner. The terminal device E12 is, for example, a personal computer, a tablet terminal, a smart phone, etc. The terminal device E12 has a communication unit with other devices, an input unit such as a keyboard and a microphone, a display unit such as a monitor, an output unit such as a speaker, etc. It should be noted that an RFID reader and a barcode reader for obtaining identification information of a subject can be connected to the terminal device E12.

[0132] [External information management device]

[0133] The information management system 100 is communicatively connected to an external information management device via a communication network 90. ​​The external information management device is, for example, a variation information management device F11, a drug information management device F21, an academic paper information management device F31, and the like.

[0134] The mutation information management device F11, the drug information management device F21, and the academic paper information management device F31 are computers that function as servers. The information managed by the mutation information management device F11, the drug information management device F21, and the academic paper information management device F31 is used as annotation information given to mutations identified by genome panel inspections performed by the inspection facilities C1 and C2.

[0135] Examples of the information managed by the variation information management device F11 include the COSMIC database (website www.sanger.ac.uk / genetics / CGP / cosmic / ), the ClinVar database (website www.ncbi.nlm.nih.gov / clinvar / ), and dbSNP (website www.ncbi.nlm.nih.gov / SNP / ).

[0136] It should be noted that the information managed by the variation information management device F11 may be a database containing variation frequency information for each human race or each animal species. Examples of databases having such information include HapMapGenome Browser release#28, Human Genetic Variation Browser (web page www.genome.med.kyoto-u.ac.jp / SnpDB / index.html) and (1000Genomes (web page www.1000genomes.org / )). For example, variation frequency information for Japanese people can be obtained from these databases. It should be noted that variation information is not limited to information on gene variation, but may also include information on polymorphism and methylation.

[0137] The information managed by the drug information management device F21 may include, for example, information on the composition, structural formula, use, side effects, etc. of various approved drugs and information on treatment experience of unapproved drugs.

[0138] The information managed by the academic paper information management device F31 may include, for example, bibliographic information and text data of academic papers related to diseases, mutations, and therapeutic drugs submitted to scientific journals.

[0139] [Safety measures]

[0140] It is desirable to use VPN (Virtual Private Network) to communicate between the integrated data management device A and various devices of the medical facilities B1 and B2. Similarly, it is desirable to use VPN to communicate between the integrated data management device A and various devices of the examination facilities C1 and C2. By using VPN, clinical information of the patient P1 in the medical facilities B1 and B2 and the results of the genome examination of the patient P1 in the examination facilities C1 and C2 can be protected from threats such as theft or tampering by a third party.

[0141] In addition, the integrated data management device A is equipped with various APIs (application program interfaces). The integrated data management device A uses the APIs to provide the clinical information of the patient P1 discussed in the expert meeting and the results of the genome panel examination to the terminal devices B13, B23, C14, C24, D11, and D21 installed in various facilities.

[0142] It should be noted that it is desirable that the communication between the integrated data management device A and the terminal devices B13, B23, C14, C24, D11, and D21 installed in various facilities use encrypted communication such as SSL (Secure Socket Layer) as a security measure. In this way, the clinical information of the patient P1 discussed in the expert meeting and the results of the genome panel examination can be safely provided to medical workers.

[0143] (Flow of Genetic Examination Using the Information Management System 100)

[0144] Then, use Figure 4 The flow of gene testing using the information management system 100 will be described. Figure 4 1 is a diagram showing an example of a genetic test process using the information management system 100. Figure 4 and Figure 1 The steps I to IV shown in the figure correspond to each other and show the flow of the gene test. Hereinafter, the case where the medical facility B1 requests the test facility C1 to perform a gene panel test will be described as an example.

[0145] <Step Ia>

[0146] Step Ia is a step in which the integrated data management device A receives a request for genome panel testing from the terminal device B13 used by the responsible physician H1a.

[0147] use Figure 5 The processing in the inspection request acceptance step of step Ia is described. Figure 5 This is a flowchart showing an example of processing in the inspection request acceptance step.

[0148] In step Ia, the doctor in charge H1a first activates a program for logging into the information management system 100 using the terminal device B13 used by the doctor in the medical facility B1, and inputs login information.

[0149] The integrated data management device A receives login information including a login password from the terminal device B13 (step S11), and authenticates the login from the terminal device B13 used by the responsible physician H1a by referring to the authentication table 38 stored in the integrated database 302 of the integrated data management device A (step S12).

[0150] Figure 6 38 is a diagram showing an example of the authentication form 38. The authentication form 38 is stored in the integrated database 302. Figure 6 As shown, the authentication table 38 records a combination of a login password for authentication set by each user and a user ID of each user.

[0151] When the integrated data management device A performs login authentication, the control unit 10 of the integrated data management device A causes the display unit of the terminal device B 13 to display Figure 7 The control unit 10 receives the examination request information from the terminal device B13 based on the input of the responsible physician H1a to the GUI 130 (step S13).

[0152] [GUI 130 for inputting inspection request information]

[0153] The GUI 130 displayed on the display unit of the terminal device B13 that has been logged in and authenticated by the integrated data management device A, for the attending physician H1a to input examination request information, will be described. Figure 7 1 is a diagram showing an example of a GUI 130 displayed on the display unit of the terminal device B 13 for inputting inspection request information.

[0154] The GUI 130 includes an area R1 for receiving input of information of the medical facility B1 as a requesting facility for requesting examination, an area R2 for receiving input of examination request information, and a request button R3 for receiving an instruction to transmit the examination request information from the terminal device B13 to the integrated data management device A.

[0155] The region R1 is provided with fields for receiving input of information on the medical facility B1 , such as “facility name”, “facility ID”, “address”, and “contact information”.

[0156] Here, the "facility name" is the name of the medical facility B1 that requested the examination. The "facility ID" is identification information assigned to each medical facility B1. The integrated data management device A can refer to the medical facility ID stored in the integrated database 302. Figure 8 The medical facility table 21 shown automatically displays the facility ID corresponding to the input facility name in the facility ID column.

[0157] Figure 8 2 is a diagram showing an example of the medical facility table 21 stored in the integrated database 302. The medical facility table 21 records a plurality of facility IDs in association with facility names corresponding to the respective facility IDs.

[0158] The control unit 10 of the integrated data management device A retrieves the facility ID corresponding to the input facility name based on the input of the client's facility name via the GUI 130, and refers to the medical facility table 21. When the facility ID corresponding to the input facility name of the client does not exist, the integrated data management device A regenerates the facility ID of the input facility of the client, associates the facility name with the generated facility ID, and records them in the medical facility table 21.

[0159] Alternatively, the control unit 10 of the integrated data management device A may send a notification with the subject "the facility ID corresponding to the input facility name does not exist" to the administrator of the integrated data management device A. In this case, the administrator of the integrated data management device A sets the facility ID corresponding to the input facility name, associates the facility name with the facility ID, and re-records them in the medical facility table 21.

[0160] Back to Figure 7 The "address" input into the input area R1 for receiving the information of the client's facility is the address of the medical facility B1 as the facility of the inspection client. In addition, the "contact information" is the telephone number and electronic email address of the medical facility B1 as the facility of the inspection client.

[0161] In area R2, a column is provided for receiving input of examination request information, wherein the examination request information is, for example, "examination type", "patient's responsible physician", "responsible physician's user ID", "patient ID", "patient's consent", "patient's name", "patient's gender", "patient's date of birth", "examination facility", "examination request date", "facility that explains examination results" and "ID of the facility that explains examination results".

[0162] Here, the "examination type" is information about the type of the requested genome panel examination. The type of the genome panel examination may be, for example, the name of the examination or the name of the genome panel used in the requested genome panel examination.

[0163] The control unit 10 of the integrated data management device A refers to the genome set table 22 stored in the integrated database 302 and displays a list of genome set names scheduled to be used in the information management system 100 on the display unit of the terminal device B13 of the medical facility B1. The responsible physician H1a can select a genome set for the requested examination as the examination type from the list.

[0164] Fig. 9 3 is a diagram showing an example of a genome set table 22 stored in the integrated database 302. The genome set table 22 records the genome set IDs in association with the genome set names corresponding to the IDs. The control unit 10 of the integrated data management device A refers to the genome set table 22 to retrieve the genome set ID corresponding to the input genome set name.

[0165] Back to Figure 7 , the name of the "patient's responsible physician" inputted into the region R2 for receiving the input of the examination request information is the name of the responsible physician H1a of the patient P1.

[0166] In addition, the "user ID of the responsible physician" is identification information of the responsible physician H1a of the patient P1. The user ID is medical worker identification information for identifying the medical worker. The control unit 10 of the integrated data management device A can refer to Fig.10 The user registration form 23 stored in the integrated database 302 shown in the figure automatically displays the user ID corresponding to the input name of the responsible physician H1a in the user ID column.

[0167] Fig.10 302 is a diagram showing an example of a user registration form 23 stored in the integrated database 302. The user registration form 23 records the user ID, the name of the medical worker, the contact information of the medical worker, and the professional field of the medical worker in association with each other. Here, the professional field of the medical worker is, for example, the type of cancer that the medical worker specializes in, such as "lung cancer" and "colorectal cancer".

[0168] The control unit 10 of the integrated data management device A retrieves a user ID corresponding to the input name of the responsible physician H1a by referring to the user registration form 23 based on the input of the name of the responsible physician H1a via the GUI 130. When the user ID corresponding to the input name does not exist, the control unit 10 may regenerate a user ID of the medical worker, associate the name with the generated user ID, and record them in the user registration form 23.

[0169] Alternatively, the control unit 10 of the integrated data management device A may send a notification with the subject "The user ID corresponding to the input name does not exist" to the administrator of the integrated data management device A. In this case, the administrator of the integrated data management device A sets a user ID corresponding to the name of the medical worker, associates the name of the medical worker with the user ID, and records them in the user registration form 23.

[0170] Back to Figure 7 The "patient ID" input into the region R2 for receiving the examination request information is identification information assigned to the patient P1. The patient ID may be a patient ID assigned to each patient P1 by the medical facility B1 of the examination requester. Alternatively, the patient ID generated by the control unit 10 of the integrated data management device A may be notified from the control unit 10 to the terminal device B13 installed in the medical facility B1 before the examination request information is input.

[0171] The "patient name" input into the region R2 is the name of the patient P1. The "patient's gender" is the gender of the patient P1. The "patient's date of birth" is the date of birth of the patient P1. Here, the input field of "patient's age" can be displayed in the GUI 130 to input the age of the patient P1.

[0172] The "examination request date" inputted into the region R2 is the date on which the examination request is sent from the terminal device B13 installed in the medical facility B1 to the integrated data management device A. For example, the following configuration may be adopted: when the GUI 130 for inputting the examination request information is displayed on the display unit of the terminal device B13, the current date is automatically inputted as the examination request date.

[0173] The "inspection facility" inputted into the area R2 is the name of the inspection facility C1 that performs the genome inspection. Instead of the name, the inspection facility ID corresponding to the inspection facility C1 may be inputted.

[0174] The control unit 10 of the integrated data management device A can refer to the input of the inspection facility name through the GUI 130. Fig.11 The list of examination facility names that can be requested for examination is displayed on the display unit of the terminal device B13 of the medical facility B1 using the examination facility table 24 stored in the integrated database 302. The attending physician H1a can select the name of the facility to request for examination from the list.

[0175] Fig.11 3 is a diagram showing an example of the inspection facility table 24 stored in the integrated database 302. In the inspection facility table 24, the inspection facility ID and the inspection facility name corresponding to each inspection facility ID are associated and recorded.

[0176] Back to Figure 7 The "facility for explaining the test results" input into the region R2 for receiving the test request information is the name of the facility that holds an expert meeting for explaining the test results of the genome test. It should be noted that the expert meeting can be implemented by the medical facility B1 itself as the client of the test, or it can apply to participate in the expert meeting held in other medical facilities B2.

[0177] The "ID of the facility that interprets the examination result" input into the region R2 for receiving the input of the examination request information is identification information corresponding to the name of the examination facility that interprets the examination result. The control unit 10 of the integrated data management device A can refer to the medical facility table 21 stored in the integrated database 302 and automatically display the facility ID corresponding to the input name of the facility that interprets the examination result in the facility ID column.

[0178] When the facility ID corresponding to the facility name input as the facility for interpreting the test result does not exist, the facility ID generated by the control unit 10 may be associated with the facility name and recorded in the medical facility table 21. Alternatively, the control unit 10 may issue a notification to the administrator of the integrated data management device A with the subject "the facility ID corresponding to the facility name for interpreting the test result does not exist".

[0179] Alternatively, the following configuration may be adopted: the control unit 10 of the information management system 100 automatically assigns each patient ID, subject ID, and examination request ID as examination request identification information of each examination request to each patient, for all patients P1 who request examinations using the information management system 100. It should be noted that the patient ID and examination request ID may not be automatically assigned by the control unit 10 of the integrated data management device A, but may be input as examination request information by the responsible physician H1a. For example, the responsible physician H1a may input the patient ID, subject ID, and examination request ID assigned according to a rule pre-established in the medical facility B1.

[0180] [Modification of GUI for inputting inspection request information]

[0181] Fig.13 1 is a diagram showing an example of a GUI 130a having columns R22 and R23 for inputting the disease name and disease ID of the patient P1. Figure 7 As an alternative to the GUI 130 shown for inputting examination request information, a column R22 for inputting the disease name of the patient P1 and a column R23 for inputting the disease ID may be provided in the area R2, and a GUI 130a for allowing the responsible physician H1a to input the disease name and disease ID of the patient P1 may be displayed on the display unit of the terminal device B13 provided in the medical facility B1.

[0182] <Process Ib>

[0183] Back to Figure 4 , step Ib is the following step: the integrated data management device A sends a notification of "accepting the inspection request" to the terminal device B13 installed in the medical facility B1.

[0184] In step Ib, the control unit 10 of the integrated data management device A sends the patient ID and the examination request ID to the terminal device B13. It should be noted that, if the patient ID is not input in step Ia, the integrated data management device A may generate the patient ID and notify the terminal device B13 of the patient ID.

[0185] <Process Ic>

[0186] Step Ic is a step in which the integrated data management device A sends a notification of "acceptance of inspection request" to the inspection information management device C11 of the inspection facility C1.

[0187] In step Ic, the control unit 10 of the integrated data management device A sends information such as the patient ID, examination request ID, date of examination request, genome set name, genome set ID and disease ID of the patient P1 to the examination information management device C11.

[0188] <Process Id>

[0189] Step Id is a step in which the integrated data management device A sends a transport request for a specimen to the sending and receiving management device E11 of the transport business unit E1.

[0190] In step Id, the control unit 10 of the integrated data management device A transmits the patient ID, the examination request ID, the examination facility where the examination is to be performed, the date on which the examination is to be performed, and the like to the terminal device E12 of the transportation office E1.

[0191] <Process Ie>

[0192] Step Ie is a step in which the integrated data management device A receives clinical information of the patient P1 corresponding to the examination request from the terminal device B13 installed in the medical facility B1.

[0193] In step Id, the attending physician H1a uses the terminal device B13 to read the clinical information of the patient from the electronic medical record management device B11, and transmits it to the integrated data management device A together with the patient ID and the examination request ID.

[0194] It should be noted that, instead of the attending physician H1a transmitting the clinical information of the patient P1 , the control unit 10 of the integrated data management device A may automatically acquire the clinical information of the patient P1 from the electronic medical record management device B11 .

[0195] <Step IIa>

[0196] Step IIa is a step in which the terminal device B13 used by the responsible physician H1a in the medical facility B1 sends an instruction "prepare a blood sample of the patient P1" to another terminal device B13 used by a nurse or the like in the blood collection room in the medical facility B1. The instruction sent by the terminal device B13 used by the responsible physician H1a includes the patient ID and the examination request ID.

[0197] When the preparation of the blood sample in this process is completed, the nurse in the blood collection room transmits information such as the date and time of completion of blood collection from the terminal device B13 in the blood collection room to the electronic medical record management device B11, and updates the electronic medical record of the patient P1.

[0198] <Step IIb>

[0199] Step IIb is a step in which, in the medical facility B1, the terminal device B13 used by the responsible physician H1a sends an instruction "prepare the lesion tissue specimen of the patient P1" to another terminal device B13 of the pathology department in the medical facility B1. The instruction sent by the terminal device B13 used by the responsible physician H1a includes the patient ID and the examination request ID.

[0200] When the preparation of the lesion tissue specimen in this process is completed, the pathologist H1b transmits information such as the date and time of completion of the preparation of the lesion tissue specimen from the terminal device B13 of the pathology department to the electronic medical record management device B11 to update the electronic medical record of the patient P1.

[0201] <Step IIc>

[0202] Step IIc is a step in which the integrated data management device A receives a notification stating that "the preparation of the blood sample and the preparation of the lesion tissue sample have been completed" together with the patient ID, the examination request ID, and the like.

[0203] In step IIc, the control unit 10 of the integrated data management device A receives a notification with the subject "Preparation of the specimen of patient P1 has been completed" from the terminal device B13 used by the nurse in the blood collection room and the pathologist H1b in the pathology department. Not limited to this, the electronic medical record management device B11 may also notify the integrated data management device A that "Preparation of the specimen of blood and lesion tissue has been completed."

[0204] It should be noted that the following configuration may be adopted: the integrated data management device A regularly monitors the electronic medical record management device B11, and detects the update of the preparation status information of the blood specimen and the diseased tissue specimen in the electronic medical record management device B11 of the patient P1. In addition, the following configuration may be adopted: when the preparation of the specimen is not completed, a notification indicating the preparation status of the specimen is sent to the integrated data management device A. For example, when the preparation of the specimen is not completed, the terminal device B13 or the electronic medical record management device B11 used by the nurse in the blood collection room and the pathologist H1b in the pathology department sends the information "the specimen is being prepared" to the integrated data management device A.

[0205] <Step IId>

[0206] Step IId is a step in which the integrated data management device A receives the pathological image of the patient P1 together with the patient ID, the examination request ID, and the like from the terminal device B13 used by the pathologist H1b.

[0207] In this process, the control unit 10 of the integrated data management device A obtains information such as the pathological image of the lesion tissue specimen of the patient P1, the date and location of the lesion tissue specimen, and the findings of the pathologist from the pathological image management device B12.

[0208] It should be noted that the pathologist H1b may also send the pathological images and other information of the patient P1 to the integrated data management device A. In this case, the pathologist H1b uses the terminal device B13 used by the pathological image management device B12 to read the pathological images and other information of the patient P1 via the LAN in the medical facility, and sends them to the integrated data management device A together with the patient ID and the examination request ID.

[0209] <Step IIe>

[0210] Step IIe is the following step: the integrated data management device A entrusts the transport personnel of the transport business department E1 to transport the diseased tissue specimen and the blood specimen. The integrated data management device A notifies the sending and receiving management device E11 of the transport business department E1 that the preparation of the blood specimen and the diseased tissue specimen is completed in the medical facility B1 and that the specimen can be transported from the medical facility B1 to the inspection facility C1 together with the patient ID and the inspection entrustment ID.

[0211] <Process IIf and IIg>

[0212] Steps IIf and IIg are steps in which the blood sampling room and the pathology department of the medical facility B1 transfer the blood specimens and the diseased tissue specimens to the transport personnel of the transport office E1.

[0213] The sample container and the package containing the blood sample and the diseased tissue sample are given an RFID tag, and the RFID tag stores information indicating the medical facility B1 to which the sample is transferred, information indicating the delivery location of the sample, that is, the inspection facility C1, the patient ID of the patient P1 from whom the sample is collected, and the inspection request ID of the genome panel inspection to be implemented. Alternatively, as an alternative to the RFID, a sealing strip may be attached, and the sealing strip is printed with information indicating the medical facility B1, information indicating the inspection facility C1, and a barcode that can read the patient ID and the inspection request ID.

[0214] <Step IIh>

[0215] In step IIh, the terminal device E21 owned by the transport personnel of the transport department E1 reads the information indicating the medical facility B1, the information indicating the inspection facility C1, the patient ID, the inspection request ID, etc. from the RFID tag or barcode of the package of the blood specimen and the diseased tissue specimen received from the medical facility B1. Then, the terminal device E12 of the transport department E1 compares the read information with the information notified in advance in step Id.

[0216] The transport personnel of the transport department E1 receives, for example, from the medical facility B1 a blood sample and a diseased tissue sample whose information stored in the RFID tag is consistent with the information notified in the process ID. Then, the transport personnel inputs "receipt completed" into their own terminal device E12, and the terminal device E12 of the transport department E1 sends a "receipt completed notification" to the sending and receiving management device E11.

[0217] <Process IIi>

[0218] Step Iii is a step in which the integrated data management device A receives a notification with the subject "Transportation department E1 has completed receipt of the specimen and started transporting it to the examination facility C1" together with the patient ID and examination request ID from the transmission and reception management device E11.

[0219] <Process IIj>

[0220] Step IIj is a step in which the transport personnel of the transport department E1 transport the sample received from the medical facility B1 to the examination facility C1.

[0221] The inspection facility C1 that has received the specimen from the transporter confirms that the information stored in the RFID tag of the blood specimen and the diseased tissue specimen is consistent with the information notified in step III. After confirming that the correct specimen has been received, the terminal device E12 owned by the transporter of the transport affairs department E1 sends a notification of "transportation of the specimen has been completed" to the sending and receiving management device E11.

[0222] <Process IIk>

[0223] Step IIk is a step in which the integrated data management device A receives a notification with the subject "Transportation of the specimen completed" together with the patient ID and the examination request ID from the transmission and reception management device E11.

[0224] The control unit 10 of the integrated data management device A can obtain the transport log data including the time required for transporting the specimen, the temperature management information of the specimen during storage and transport, etc. from the transceiver management device E11. In this case, the transport personnel of the transport affairs department E1 will send the transport log data collected during the transport of the specimen from the terminal device E12 owned by the transport personnel to the transceiver management device E11 and record it in advance. It should be noted that the transport log data indicates the status of the specimen for genome testing and is related to the reliability of the test results. Therefore, the information of the transport log can be used as a reference at the expert meeting site.

[0225] <Step IIIa>

[0226] Step III is a step in which a genome panel test is performed using a blood sample and a diseased tissue sample in the test facility C1.

[0227] The genome panel test includes, for example, a pre-processing step including extracting DNA from the specimen, a sequence determination step using a next-generation sequencer to read the base sequence, and a step for extracting mutations in the diseased tissue. In addition, the inspection information management device C11 of the inspection facility C1 can give annotations to the extracted mutations based on the information obtained by the mutation information management device F11, the drug information management device F21, and the academic paper information management device F31. In this way, the inspection results of the commissioned genome panel test are obtained.

[0228] In step IIIa, the inspection information management device C11 of the inspection facility C1 may appropriately notify the integrated data management device A of inspection progress information indicating "at which step the genome panel inspection has been completed" together with the patient ID and inspection request ID.

[0229] <Step IVa>

[0230] Step Iva is a step in which the integrated data management device A receives the examination result performed in the examination facility C1 together with the patient ID, the examination request ID, and the like from the examination information management device C11 of the examination facility C1.

[0231] It should be noted that the clinical examiner H3 may also send the examination result to the integrated data management device A. In this case, the clinical examiner H3 uses the terminal device C14 of the examination facility C1 used by the clinical examiner H3 to read the examination result from the examination information management device C11 via the LAN in the examination facility, and sends it to the integrated data management device A together with the patient ID and the examination request ID.

[0232] The inspection results of the genome panel inspection can be summarized into an inspection result report containing related information such as mutation information, drug information, and academic paper information.

[0233] <Process Va>

[0234] Process Va is the following process: the integrated data management device A associates the examination request information obtained in process Ia, the clinical information of patient P1 obtained in process Ie and process IId, and the examination results obtained in process IVa, and records them in the main table 25 of the integrated data management device A.

[0235] Below, use Fig.12 The processing flow in the integration step is described, wherein the integration step integrates the data obtained in steps Ia, Ie, IId and Va. Fig.12 1 is a diagram showing an example of a processing flow of an integration step performed by the control unit 10 of the integrated data management device A.

[0236] The integrated data management device A receives the examination request information from the terminal device B13 of the medical facility B1 in the above-mentioned step Ia (step S13, see Figure 5 ). Then, in the above-mentioned step Ie, clinical information of the patient P1 associated with the inspection request is received from the terminal device B13 of the medical facility B1 (step S21). In addition, in the above-mentioned step IId, the inspection result for the inspection request is received from the terminal device C14 of the inspection facility C1 (step S22).

[0237] Then, the control unit 10 of the integrated data management device A associates the received clinical information of the patient P1 with the examination request ID, and records it in the main table 25 of the integrated database 302. In addition, the control unit 10 of the integrated data management device A associates the received examination result of the patient P1 with the examination request ID, and records it in the main table 25 of the integrated database 302. Thus, the clinical information of the patient P1 and the examination result of the patient P1 are associated with each other via the examination request ID, and are recorded in the main table 25 (step S23).

[0238] In this embodiment, an example is shown in which the control unit 10 of the integrated data management device A obtains the clinical information of the patient P1 from the medical facility B1 when requesting an examination, but the timing of obtaining the clinical information and the examination request information is not limited to this. The responsible physician H1a of the medical facility B1 may send the examination request information and the clinical information to the integrated data management device A when requesting an examination, or the integrated data management device A may receive the clinical information from the medical facility B1 after performing the examination based on the examination request information and before holding the expert meeting.

[0239] [Main table 25]

[0240] Fig.14 2 is a diagram showing an example of the main table 25 stored in the integrated database 302. Fig.14 As shown, the main table 25 records "patient ID", "subject ID", "examination request ID", "genome set ID", "patient name", "patient's gender", "patient's date of birth", "patient's consent", "examination request date", "medical worker's user ID", "medical worker's name", "team ID", "examination progress information", "clinical information", "examination results", "facility for holding expert meeting" and "date and time of holding expert meeting".

[0241] "Patient ID", "Patient name", "Patient's gender", "Patient's date of birth", "Patient's consent", "Test request date", "Medical worker's user ID", "Medical worker's name", and "Facility where the expert meeting was held" are used by the responsible physician H1a Figure 7 The information inputted in the GUI 130 shown in FIG. 130. It should be noted that the "name of the medical worker" is the name inputted in the column of "the patient's responsible physician" in the area R2 of the GUI 130. In addition, the "user ID of the medical worker" is the user ID of the medical worker inputted in the column of "the user ID of the responsible physician" in the area R2 of the GUI 130.

[0242] The information about "patient's consent" in area R2 of GUI130 includes consent for examination, provision of anonymous examination results to a third party organization, and a combination thereof, but is not limited thereto. The information about "patient's consent" in area R2 of GUI130 may be displayed in a manner of selecting from a drop-down menu or radio button, or in a manner of selecting any combination from a list.

[0243] The master table 25 records the content selected in the "patient's consent" area R2 of the GUI 130 as information on the "patient's consent". In addition, the master table 25 may also record a link to the scan data of the patient's consent form as information on the "patient's consent".

[0244] The "inspection request ID" is identification information generated for each inspection request by the control unit 10 of the integrated data management device A according to the inspection request information received from the terminal device B 13. It should be noted that the "inspection request ID" may be numbered by a numbering system of the facility receiving the inspection request, or may be randomly numbered by the person in charge of the facility receiving the inspection request, but is not limited thereto.

[0245] "Subject ID" is subject identification information given to each subject prepared in the medical facility B1. Figure 4 In step IIc, the control unit 10 of the integrated data management device A receives a notification with the subject "Completion of preparation of the specimen" from the terminal device B13 of the medical facility B1 that prepares the patient's specimen. It should be noted that as the specimen ID, a common ID for both blood specimens and diseased tissue specimens can be generated, or separate IDs can be generated for blood specimens and diseased tissue specimens. In addition, the specimen ID can also be numbered by the inspection facility C1 that performs the inspection. In this case, the clinical inspector H3, who is a medical worker at the inspection facility C1, can associate the numbered specimen ID with the inspection request ID and record it in the integrated database 302 stored in the integrated data management device A. Fig.14 In the main table 25 shown.

[0246] The "genome set ID" is identification information given to each type of genome set used in the genome set inspection. The control unit 10 of the integrated data management device A refers to Fig. 9 The genome set table 22 shown is used to extract the genome set identification information corresponding to the genome set name input in the “Test Type” column of region R2 of the GUI 130 .

[0247] "Group ID" is group identification information given to each group of medical workers participating in the expert meeting. First, the control unit 10 of the integrated data management device A refers to Fig.11 The inspection facility table 24 shown in the figure identifies the facility ID corresponding to the facility name input in the "facility for explaining inspection results" column of the area R2 of the GUI 130. Next, the control unit 10 of the integrated data management device A refers to Fig.17 The group table 26 shown in FIG. 24 determines the group ID corresponding to the determined facility ID. It should be noted that, as for the "group ID", Fig.14 The date and time information of the expert meeting recorded and associated with the inspection request ID is extracted from the master table 25 shown in FIG. Fig.18 The expert meeting schedule 27 shown is used to extract the group ID.

[0248] "Inspection progress information" is in Figure 4 In step IIIa, the control unit 10 of the integrated data management device A receives information on the progress status of the inspection from the inspection information management device C11 of the inspection facility C1.

[0249] "Examination progress information" may include information about the preparation status of the specimen for examination, the transportation status of the specimen, and the completion status of each process of the examination. As "examination progress information", "Specimen being prepared", "Specimen being transported", "Pretreatment process: not completed", "Pretreatment process: completed", "Sequencing process: not completed", "Sequencing process: completed", "Variation analysis process: not completed", "Variation analysis process: completed", etc. can be used. "Specimen being prepared" means the stage where the medical staff has completed the inspection request, but the acquisition of the specimen has not yet been completed, and "Specimen being transported" means the stage where the transportation department E1 has received the specimen from the medical facility B1, but the transportation to the inspection facility C1 has not yet been completed. "Pre-processing process: not completed" means: the transportation department E1 has sent the specimen to the inspection facility C1, but the pre-processing process of the specimen has not been completed yet; "Pre-processing process: completed", "Sequencing process: not completed", "Sequencing process: completed", "Variation analysis process: not completed" and "Variation analysis process: completed" respectively represent the stages before and after the pre-processing process, sequencing process and variation analysis process of the inspection at the inspection facility C1.

[0250] The “clinical information” may include, for example, information contained in the electronic medical records of the patient, pathological images of the pathological part, etc. Figure 7 When an inspection request is received through the GUI 130 shown in the figure, the patient ID contained in the inspection request is extracted. The control unit 10 of the integrated data management device A obtains the patient's clinical information from the electronic medical record management device B11 and the pathological image management device B12 of the medical facility B1 based on the extracted patient ID, and sets up respective folders in the integrated database 302 for storage. Back Fig.14 The control unit 10 of the integrated data management device A may also associate link information of the file data pointing to the clinical information as “clinical information” with the patient ID and the examination request ID, and record it in the master table 25 .

[0251] The "check result" is Figure 4In step IVa of the present invention, the control unit 10 of the integrated data management device A receives the inspection result of the genome panel inspection from the inspection information management device C11 of the inspection facility C1. The inspection result of the genome panel inspection includes a summary report, a sequencing report, a QC report and an inspection report, but is not limited to these. In addition, the summary report and the inspection report may include "type of specimen (FFPE, fresh frozen specimen, etc.)", "time of specimen collection (first time or recurrence)·site (primary·metastasis)", "pathological diagnosis name", "pathological specimen number", "proportion of tumor cells in the specimen (%)", "DNA quantity and quality", "acceptance date", "report date", "panel inspection method", "type of gene mutation, clinical significance", "type and version of reference database of annotation information", etc., but are not limited to these. The control unit 10 of the integrated data management device A sets the inspection results of the patient's genome panel inspection obtained from the inspection information management device C11 of the inspection facility C1 to their respective folders and saves them in the integrated database 302 of the integrated data management device A. The control unit 10 of the integrated data management device A may also record link information pointing to the file data of the inspection results stored in each folder as "inspection results" in the master table 25. It should be noted that the "inspection results" may also be sent to the integrated data management device A from the terminal device C14 used by the clinical inspector H3 of the inspection facility C1.

[0252] In addition, the "inspection result" may be sent from the inspection facility C1 together with the "inspection request ID" and received by the control unit 10 of the integrated data management device A. In this case, the control unit 10 of the integrated data management device A refers to the master table 25 and associates it with the record corresponding to the received "inspection request ID" upon receiving the "inspection result", thereby recording the "inspection result".

[0253] It should be noted that the inspection facility C1 can associate information about the "remaining amount of the specimen" with one or both of the "inspection request ID" and the "subject ID" and record it in the main table 25. In addition, the inspection facility C1 can associate information about the "location of the remaining specimen" with one or both of the "inspection request ID" and the "subject ID" and record it in the main table 25. It should be noted that here, an example is shown in which the inspection facility C1 is associated with the "remaining amount of the specimen" and the "location of the remaining specimen", but it can also be recorded in the main table 25 by the responsible physician H1a of the medical facility B1 that accepts the return of the remaining specimen, and it is not limited to this.

[0254] The “date and time of the expert meeting” is, for example, the scheduled date and time of a newly registered expert meeting or information about the schedule of an expert meeting that has already been held. For example, when a terminal device used by a medical worker who has the authority to determine the scheduled date and time of the expert meeting enters the registration, change, or deletion of the scheduled date and time, the control unit 10 records the entered scheduled date and time in the master table 25.

[0255] It should be noted that the scheduled date and time of the expert meeting can be determined and registered by adjusting the schedule among the medical workers constituting the group, or the medical worker who has the authority to set the expert meeting can register an arbitrary scheduled date and time.

[0256] In addition, information on the requirements for convening the expert meeting, which indicates whether the medical staff required for convening the expert meeting have confirmed their participation, can be recorded in the master table 25. For example, the expert meeting requires (1) the inclusion of one or more physicians in charge of the subject patients to be studied, (2) the inclusion of multiple pathologists, (3) the inclusion of multiple cancer drug therapy specialists, (4) the inclusion of one or more bioinformatics experts, (5) the inclusion of one or more genetic counselors, (6) the inclusion of one or more molecular genetics researchers, and (7) the inclusion of one or more genetic medicine specialists.

[0257] In this case, the integrated database of the integrated data management device A can be Fig.18 In the expert meeting schedule 27 shown, the above-mentioned elements (1) to (7) are associated and recorded. That is, the following information can be recorded about the schedule of each expert meeting: (1) Minimum number of participants of responsible physician (responsibility ID: R01): 1, and similarly, (2) Pathologist (responsibility ID: R02): 2, (3) Cancer drug therapy specialist (responsibility ID: R03): 2, (4) Bioinformatics expert (responsibility ID: R04): 1, (5) Genetic counselor (responsibility ID: R05): 1, (6) Molecular genetics researcher (responsibility ID: R06): 1, (7) Genetic medicine specialist (responsibility ID: R07): 1. It should be noted that these numerical values ​​are examples and are not limited to these.

[0258] When receiving approval for adjusting the schedule of a predetermined expert meeting from a medical professional, the control unit 10 of the integrated data management device A refers to the Fig.10 The user registration form 23 shown in FIG. 1 is used to extract the role ID recorded in association with the approved medical worker. Then, the control unit 10 of the integrated data management device A refers to Fig.18 The expert meeting schedule 27 shown performs the following processing on the above-mentioned elements (1) to (7) recorded in association with the schedule of the expert meeting.

[0259] That is, for example, if the role ID of the medical worker who approved the schedule adjustment is R05, that is, a genetic counselor, 1 is subtracted from the value recorded in (5) Genetic counselor (role ID: R05) recorded in the expert meeting schedule 27, which is 1, to obtain 0. This confirms that there are enough genetic counselors participating in the schedule of the expert meeting. The control unit 10 of the integrated data management device A performs the same processing for other medical workers.

[0260] The control unit 10 of the integrated data management device A confirms that all the numbers (1) to (7) have become 0. When all the numbers have become 0, the control unit 10 can record the "information on the requirements for convening" in the main table 25 as "can be convened". When all the numbers have not become 0, it can record "additional convening is required". In addition, when all the numbers have not become 0, the control unit 10 can display the message "can be convened" in the GUI 160. Fig.33 Icon 170 is shown to alert the user.

[0261] The master table 25 can be managed so as to be manually updateable by the administrator H8 who is given the management authority of the integrated data management device A, for example. Fig.15 1 is a diagram showing a configuration example in which there is a manager H8 who has management authority over the integrated data management device A. The manager H8 can use the integrated data management device A to create a master table 25 based on the notified patient ID, patient name, gender, patient date of birth, etc. before the control unit 10 of the integrated data management device A receives the examination request information from the responsible physician H1a. It should be noted that when the integrated data management device A is installed in the medical facility B1 (see Fig.54 ), the medical worker can be given the management authority of the integrated data management device A. For example, the medical worker such as the doctor H1a in charge of the patient can input the patient information into the master table 25.

[0262] [Patients are connected to a group that attends expert meetings]

[0263] The control unit 10 may associate the patient with a team of experts who participate in a meeting to formulate a treatment policy for the patient. Fig.16 1 is a flowchart showing an overview of a process in which the control unit 10 associates a patient with experts participating in the expert conference.

[0264] First, the control unit 10 refers to the medical facility table 21 stored in the integrated database 302 to identify the facility ID of the facility that is input as the examination request information and corresponds to the facility for interpreting the examination result (step S81). Then, the control unit 10 refers to the group table 26 stored in the integrated database 302 to identify the group ID corresponding to the identified facility ID and the user ID corresponding to the group ID (step S82).

[0265] Fig.17 2 is a diagram showing an example of the group table 26. Fig.17 As shown, the group table 26 records sets of a group ID, a facility ID, and a plurality of user IDs.

[0266] Here, list Fig.14 The record M1 shown is used as an example to illustrate the process of the control unit 10 associating a patient with a group participating in a specialist meeting. The control unit 10 refers to the medical facility table 21 to determine the facility ID "F01" corresponding to the facility "xx Cancer Research Center" that interprets the examination results and is input as the examination request information. Then, the control unit 10 refers to the group table 26 to determine the group ID "G01" or "G02" corresponding to the facility ID "F01". When the control unit 10 determines the group ID "G01", the user IDs "U01, U02, U03, U04, U05" corresponding to the group ID "G01" are determined. Thus, when there are multiple user IDs corresponding to the determined group ID, the control unit 10 can associate these multiple user IDs with the patient ID contained in the input examination request information. It should be noted that "determine" and "extract" have the same meaning.

[0267] It should be noted that, when there are multiple group IDs corresponding to the determined facility ID, the control unit 10 may randomly select one group from these groups. Alternatively, the control unit 10 may refer to the expert meeting schedule 27 stored in the integrated database 302 and give priority to a group with a small number of registrations for expert meetings (i.e., a large number of schedule gaps).

[0268] [Expert meeting schedule 27]

[0269] Fig.18 2 is a diagram showing an example of the expert meeting schedule 27. Fig.18 As shown in FIG. 1 , the expert meeting schedule 27 records the group ID, facility ID, scheduled date and time of the expert meeting, and the allowed number of patients. The allowed number of patients refers to the upper limit of the number of patients who can discuss the formulation of treatment methods in the expert meeting. The allowed number of patients can be set according to the length of time for holding the expert meeting. For example, Fig.18 In the specialist meeting schedule 27 shown, when the specialist meeting is scheduled for 4 hours (e.g., "1:00pm-5:00pm"), the number of allowed patients is set to "4", and when it is scheduled for 3 hours (e.g., "3:00pm-6:00pm"), it is set to "3".

[0270] List Fig.14The record M1 shown is used as an example to explain the processing of the control unit 10 to determine one of the multiple group IDs. The control unit 10 refers to the medical facility table 21 to determine the facility ID "F01" corresponding to the facility "xx Cancer Research Center" that interprets the examination results, which is input as the examination request information. Then, the control unit 10 refers to the group table 26 to determine the group IDs "G01" and "G02" corresponding to the facility ID "F01". Then, the control unit 10 refers to the expert meeting schedule 27 and compares the number of registrations of the expert meeting of the group ID "G01" and the number of registrations of the expert meeting of the group ID "G02", thereby determining the group ID with the smaller number of registrations.

[0271] [Comprehensive ID]

[0272] The control unit 10 can automatically generate a comprehensive ID (third identification information) each time it receives an inspection request information. The control unit 10 uses the generated comprehensive ID to associate the patient's clinical information and the inspection results of the genome set inspection with each inspection request information received. The comprehensive ID is identification information used to integrate each information for each inspection request information obtained by the control unit 10. It should be noted that the comprehensive ID can be numbered by a numbering system different from that of the control unit 10.

[0273] For example, the control unit 10 may generate a comprehensive ID using a random combination of letters and numbers. It should be noted that the control unit 10 may generate a new comprehensive ID in a manner that does not overlap with a comprehensive ID generated in the past, and the characters and number of characters used in generating the comprehensive ID may be arbitrary.

[0274] The integrated ID can be associated with the patient ID and the examination request ID. In this case, the control unit 10 records the generated integrated ID in the integrated ID table 28 stored in the integrated database 302. For example, Fig.19 28 is a diagram showing an example of the integrated ID table 28. Fig.19 As shown, in the integrated ID table 28, an integrated ID "oXy796K" is generated and recorded for the data of the patient "PA01" and the test request ID "T01".

[0275] Alternatively, the integrated ID may be associated with the patient ID, the facility ID, and the examination request ID. In this case, the control unit 10 records the generated integrated ID in the integrated ID table 28a stored in the integrated database 302. For example, Fig. 20 28a is a diagram showing an example of the integrated ID table 28a. Fig. 20As shown, in the comprehensive ID table 28a, the comprehensive ID "MyiYAm2" is generated and recorded for the data of the patient "PA04" and the examination request ID "T04". The control unit 10 records the information received by the control unit 10 for managing the transportation status of the specimen in the main table 25. The transportation of blood specimens and diseased tissue specimens is required to be carried out in a manner that does not affect the success of the examination performed in the examination facility, the quality and reliability of the examination results. According to this structure, it can be confirmed whether the blood specimens and diseased tissue specimens transported from the medical facility B1 to the examination facility C1 are correctly transported according to the specified conditions.

[0276] (Management of various data stored in the integrated database 302)

[0277] The control unit 10 can assign data IDs and data type IDs to the patient information, clinical information of the patient, and data on the examination results received by the integrated data management device A from the terminal device B13, the electronic medical record management device B11, the pathological image management device B12, and the examination information management device C11, and store them in the integrated database 302. In addition, the control unit 10 can assign data IDs and data type IDs to the related information obtained by searching each server of the information management facility group F, and store them in the integrated database 302.

[0278] The data ID is an ID assigned to each data. On the other hand, the data type ID is an ID assigned to distinguish the type of data. As the data type ID, the following data type IDs can be listed, for example.

[0279] "PA": ID assigned by the control unit 10 to the patient information received from the terminal device B13 and the electronic medical record management device B11.

[0280] "IM": ID assigned by the control unit 10 to the pathological image data of the patient received from the terminal device B13, the pathological image management device B12, and the like.

[0281] "TEST": ID assigned by the control unit 10 to the inspection result data received from the inspection information management device C11.

[0282] "ANN": ID assigned by the control unit 10 to annotation information acquired from the variation information management device F11, the drug information management device F21, and the academic paper information management device F31.

[0283] It should be noted that the data type ID can be assigned in a manner that more finely distinguishes the multiple data contained in the data type. For example, the control unit 10 can assign "ANN01" to the annotation information obtained from the variation information management device F11, assign "ANN02" to the annotation information obtained from the drug information management device F21, and assign "ANN03" to the annotation information obtained from the academic paper information management device F31. By refining the assignment of data type IDs in this way, the control unit 10 can perform more detailed access management.

[0284] <Patient Information Form 31>

[0285] Fig.21 is a diagram showing an example of a patient information table 31, the patient information table 31 includes Figure 4 In step 1a, the control unit 10 of the integrated data management device A receives the patient information from the terminal device B13. Fig.21 As shown in the patient information table 31, the patient information record includes the patient's gender, age, disease ID, condition (disease progression, for example, in the case of cancer, it is represented by stages I to IV) and treatment history (therapy information), and the data ID and data type ID are associated with these data groups. It should be noted that the patient information table 31 may include information about the patient's date of birth, disease name, reaction (side effects) to drugs used in the past, etc.

[0286] The control unit 10 may instruct the doctor in charge H1a to input the patient's gender, age, condition, treatment history, etc. from the terminal device B13. Alternatively, the control unit 10 may extract clinical information of the patient received from the electronic medical record management device B11.

[0287] For example, the control unit 10 can cause the terminal device B13 to display a GUI 130a having a column R22 for entering the patient's disease name and a column R23 for displaying the disease ID, and instruct the doctor in charge H1a to input the patient's disease name (see Fig.13 The control unit 10 may refer to the disease table 32 stored in the integrated database 302 and automatically display the disease ID corresponding to the disease name input in the disease name column R22 of the patient in the disease ID column R23. Fig. 22 3 is a diagram showing an example of the disease table 32. Fig. 22As shown, the disease table 32 records the correspondence between the disease ID and the disease name corresponding to each disease ID. The control unit 10 retrieves the disease ID corresponding to the input disease name by referring to the disease table 32. For example, according to the patient information table 31, the patient assigned with the data ID "PA01" and the data type ID "PA" is a 52-year-old male suffering from lung cancer, and the patient assigned with the data ID "PA03" and the data type ID "PA" is an 81-year-old female suffering from colorectal cancer.

[0288] <Pathological image table 33>

[0289] Fig.23 is a diagram showing an example of a pathological image table 33, wherein the pathological image table 33 is included in Figure 4 In step IId, the control unit 10 receives the pathological image from the pathological image management device B12. Fig.23 As shown in the pathological image table 33, the pathological image records respectively record the collection date of the specimen, the collection site, the link information pointing to the pathological image file data, and the pathologist's observation, and the data ID and data type ID are associated with these data groups. For example, according to the pathological image table 33, the pathological image assigned with the data ID "IM01" and the data type ID "IM" is a pathological image of the diseased tissue specimen collected on x year x month x day, and the pathological image data is managed as "Image 01". It should be noted that the pathological image file can refer to the pathological image stored in the comprehensive database 302 of the comprehensive data management device A, and can also refer to the pathological image stored in the management device B12.

[0290] <Test result table 34>

[0291] Fig.24 is a diagram showing an example of the inspection result table 34, which includes Figure 4 In step IVa, the control unit 10 receives the inspection result from the inspection information management device C11. Fig.24 As shown in the inspection result table 34, the inspection result records respectively record the link information of the file data pointing to the inspection result report, mutation information, therapeutic drug information, genome set ID, disease ID, subject quality information and DNA quantity, etc., and the data ID and data type ID are associated with these data groups.

[0292] like Fig.24 As shown, the test result table 34 includes a link to a report, mutation information, therapeutic drug information, disease ID, sample quality information, and DNA quantity information.

[0293] The link to the report is link information to the document data of the test result report created by the clinical tester H3 or the like of the test facility C1.

[0294] Variant information refers to information about variants detected through genome analysis. For example, Fig.24 The data "EGFR T790M" in the test result table 34 shows that in the amino acid sequence of the EGFR protein, the amino acid residue at position 790, which is threonine in the wild type, has mutated to methionine. On the other hand, the data "BRAF V600E" shows that in the amino acid sequence of the BRAF protein, the amino acid residue at position 600, which is valine in the wild type, has mutated to glutamic acid.

[0295] Therapeutic drug information refers to information about therapeutic drugs that are associated with the mutations detected by genome panel testing. Fig.24 The test result table 34 shown shows "Drug A" for the data of "EGFR T790M" and "Drug B" for the data of "BRAFV600E".

[0296] The genome set ID is identification information indicating the type of genome set used in the genome set inspection. The control unit 10 may refer to, for example, Fig. 9 The genome set table 22 shown is used to search and determine the genome set ID.

[0297] Disease ID is identification information corresponding to the disease name of each patient. For example, Fig.24 The data "LUNG" shown indicates that the patient's disease is lung cancer, and the data "CORON" indicates that the patient's disease is colon cancer (refer to Fig. 22 ).

[0298] The specimen quality information refers to information about the quality of the specimen of the patient sent from the medical facility B1 to the examination facility C1. The specimen quality information may be, for example, "good", "good" and "acceptable". Here, "good" and "good" indicate a state in which a sufficient amount of DNA can be extracted from the patient's diseased tissue in the pre-treatment process of the genomic panel examination, and "acceptable" indicates a state in which the genomic panel examination can be carried out without problems although it has been confirmed that DNA decomposition is in progress. It should be noted that in the case where most of the DNA is decomposed or the amount of DNA sufficient for the genomic panel examination cannot be extracted, the specimen status information such as "impossible" can be assigned.

[0299] The amount of DNA refers to information on the amount of DNA extracted from the patient's diseased tissue in the pre-treatment step of the genome panel test. The amount of DNA may be, for example, the weight (ng) of DNA extracted per 1 mg of pathological tissue.

[0300] <Annotation Information Table 35>

[0301] Fig.25 3 is a diagram showing an example of the comment information table 35, which includes the comment information acquired by the control unit 10 from each server of the information management facility group F. Fig.25 As shown in the annotation information table 35, the record of the annotation information records a group of the type of annotation, the link information pointing to the information source of the related information, the link information pointing to the data, and text information, and the data ID and the data type ID are associated with the group of these data. For example, according to the annotation information table 35, the annotation information assigned with the data ID "ANN01" and the data type ID "ANN" is information about the variation, the link information pointing to the information source of the related information is "https: / / xxx.yyy.com", and the data about the related information is managed as "Data A01".

[0302] <Responsibilities Form 36>

[0303] When a medical worker affiliated with medical facilities B1, B2, inspection facilities C1, C2, and external facilities D1, D2 applies to use the information management system 100, the control unit 10 generates a user ID for the medical worker. At this time, the control unit 10 can refer to the responsibility table 36 stored in the integrated database 302 to generate a responsibility ID for the medical worker together with the user ID. It should be noted that a responsibility ID can be generated for the employees of the transportation department group E included in the information management system 100. In addition, the generated responsibility ID can be used together with the user ID. Fig.10 The user ID of the user registration form 23 shown is associated and recorded.

[0304] Fig.26 36 is a diagram showing an example of the responsibility table 36. Fig.26As shown, the responsibility table 36 records the correspondence between the responsibility ID and the responsibility name corresponding to each responsibility ID. The control unit 10 refers to the responsibility table 36 and retrieves the responsibility ID corresponding to each medical worker based on the information input by the medical worker when applying to use the information management system 100. As the input information, for example, the name of the facility to which it belongs and the professional field can be listed. For example, the control unit 10 generates a responsibility ID "R01" for the responsible physician H1a of the patient P belonging to the medical facility B1, and generates a responsibility ID "R08" for the clinical examiner of the examination facility C1. For example, the control unit 10 generates a responsibility ID "R04" for a medical worker who is a bioinformatics expert belonging to the external facility D1. On the other hand, in the information management system 100, the control unit 10 generates a responsibility ID "R09" for the practitioners of the transportation affairs department group E who are responsible for transporting the specimens.

[0305] <Access Rights Management Table 37>

[0306] For example, the control unit 10 may refer to the access permission management table 37 stored in the integrated database 302 to limit the data that can be viewed and used by medical personnel and employees of the transportation department E1.

[0307] Fig. 27 37 is a diagram showing an example of the access permission management table 37. Fig. 27 As shown, the corresponding relationship between the role ID and the data type ID of the data that is allowed to be accessed by the person corresponding to each role ID is recorded in the access permission management table 37. The control unit 10 refers to the access permission management table 37 to limit the data type ID of the data that is allowed to be accessed in response to the access request from the terminal devices B13, B23, C14, C24, D11, D21 and E12.

[0308] [Access restrictions for employees of Transport Affairs Department E]

[0309] exist Figure 4 In step IIe, the control unit 10 may send a notification to the transceiver management device E11 that the subject has received the request, and then, for example, the integrated data management device A can be accessed through the terminal device E12 used by the practitioner. However, since the practitioner is not a medical worker, it is desired to allow the practitioner to use only some functions of the entire information processed by the integrated data management device A. Therefore, the control unit 10 refers to the access permission management table 37 and limits the data type ID of the data that the practitioner is allowed to access based on the fact that the role ID of the practitioner who sent the access request from the terminal device E12 is R07.

[0310] For example, if an employee logs in to the integrated data management device A, the terminal device E12 will display the following Fig.28 The screen display 140 is shown. Fig.28This is a diagram showing an example of a screen display displayed in the terminal device E12 of the transport business department. For example, a list of inspection requests received by the integrated data management device A is displayed in the terminal device E12. The practitioner can confirm the date when the integrated data management device A receives the screen inspection request, the inspection request ID, the preparation status of the subject, the inspection requester (e.g., the name of a medical facility), and the inspection facility that performs the inspection (e.g., the name of the inspection facility).

[0311] It should be noted that the following configuration may be adopted: by accepting an operation (e.g., a click operation) for selecting information displayed in the “subject preparation status” of the screen display 140, the preparation status of the subject can be updated from the terminal device E12. For example, information such as “subject transportation in progress” and “subject transportation completed” may be input by a practitioner using the terminal device E12. In this case, a candidate list of “subject preparation status” that can be input from the terminal device E12 may be displayed by pulling down the position of the selected “subject preparation status”.

[0312] (Agenda management of expert meetings)

[0313] <Reservation for expert meeting>

[0314] In the information management system 100 , when a medical worker requests an examination to be performed in the examination facility C1 , a reservation can be made for a specialist conference for formulating a treatment method for a patient based on the results of the examination.

[0315] For example, the control unit 10 may display a screen for accepting an input of a reservation for a specialist conference. Fig.29 The GUI 150 shown is Figure 7 An alternative to the GUI 130 shown. Fig.29 1 is a diagram showing an example of a GUI 150 displayed on the terminal device B 13 for accepting an input of a reservation for a specialist conference.

[0316] GUI150 includes: an area R1 for receiving input of information on the facility of the client requesting inspection, an area R2 for receiving input of inspection request information, an area R4 for receiving input of reservations for expert meetings, and a request button R3 for receiving an instruction to send the inspection request information from the terminal device B13 to the control unit 10 of the integrated data management device A.

[0317] Region R4 may include a list of scheduled dates and time periods for expert meetings at the facilities (and facility IDs) input as "facilities for explaining inspection results" in region R2, and a confirmation dialog box for selecting each scheduled date and time period. For example, the control unit 10 refers to the expert meeting schedule 27 (see FIG. 2 ) stored in the integrated database 302. Fig.18) and in area R4, the scheduled date and time of the expert meeting to be held in the facility "xx Cancer Research Center" input as the "facility for interpreting the test results" in area R2 are displayed.

[0318] For example, a medical worker who wishes to schedule an expert meeting scheduled for 10:00-12:00 on January 7, 2019 can click the corresponding confirmation dialog box as shown in the figure. Figure 7 The GUI 130 shown is the same.

[0319] For example, the control unit 10 may display in the region R4 only the scheduled date and time of the expert meeting scheduled to be held at least a predetermined time (eg, one month) after the inspection request date.

[0320] The control unit 10 can refer to Fig.18 The expert conference schedule 27 shown in the figure determines the group ID corresponding to the scheduled date and time of the expert conference selected by the medical worker, and manages the schedule of the expert conference. Fig.17 The group table 26 shown is used to extract the user ID corresponding to the determined group ID.

[0321] Then, the control unit 10 refers to Fig.10 The user registration form 23 shown in the figure determines the contact information of the medical worker of each user ID that has been determined, and sends a notice of convening a specialist meeting at the date and time to each medical worker. Thus, in addition to the input of the examination request information by the responsible physician H1a, the integrated data management device A can also accept the input of the appointment of the specialist meeting for explaining the examination results of the examination performed in the examination facility C1. Furthermore, the integrated data management device A can send a notice to each medical worker who is to participate in the specialist meeting for which the appointment is accepted, which is intended to be held.

[0322] <Processing of sending the notification of the scheduled specialist meeting to the addresses of each medical worker>

[0323] Next, use Fig.31 An example of a process flow for transmitting information on a schedule of a specialist conference reserved by a medical worker and a test result associated with the schedule to each medical worker constituting a group will be described. Fig.31 This is a diagram showing an example of a process flow for sending a notification of a scheduled specialist conference to the addresses of each medical worker.

[0324] First, the terminal device B13 receives an instruction from a medical worker to display a test request acceptance screen, and sends the display instruction to the integrated data management device A (step S1201). The test request acceptance screen may be, for example, Fig.29 GUI150 is shown.

[0325] The integrated data management device A receives a display instruction from the terminal device B13 (step S1202), obtains information about the type of genetic examination, information about the examination facilities, and information about the facilities that interpret the examination results from the integrated database 302, and sends it to the terminal device B13 (step S1203).

[0326] The terminal device B13 displays an inspection request acceptance screen based on the information received from the integrated data management device A (step S1204).

[0327] Then, the terminal device B13 receives the information about the facility that explains the examination result for the examination request selected by the medical worker in the examination request acceptance screen, and transmits it to the integrated data management device A (step S1205). The selection of the information about the facility that explains the examination result for the examination request can be selected from the displayed list or pull-down menu based on the information acquired by the control unit 10 of the data management device A in step S1203, but is not limited thereto.

[0328] The integrated data management device A receives information about the facility that interprets the inspection result for the inspection request (step S1206), acquires schedule information of a plurality of expert meetings held in the facility from the expert meeting schedule table 27, and transmits it to the terminal device B 13 (step S1207).

[0329] The terminal device B13 receives the schedule information of the plurality of expert meetings from the integrated data management device A and displays it in the area R4 of the GUI 150 (step S1208).

[0330] Then, the terminal device B13 receives the medical worker's selection of one expert meeting and receives an instruction to notify the medical workers who will participate in the selected expert meeting of "holding an expert meeting" and transmits it to the integrated data management device A (step S1209).

[0331] The integrated data management device A receives the schedule information of the selected expert conference. The integrated data management device A determines whether the application can be accepted for the selected expert conference schedule. That is, the integrated data management device A obtains the allowed number of patients for the selected expert conference schedule from the expert conference schedule table 27, and determines whether it is a number greater than 1. If the allowed number of patients is greater than 1, the application for the selected expert conference schedule is accepted, and 1 is subtracted from the allowed number of patients at that time. (Step S1210)

[0332] The comprehensive data management device A obtains the contact information of multiple medical workers associated with the selected expert meeting from the group table 26 (step S1211), and sends a convening notice to the contact information used by the multiple medical workers, wherein the convening notice includes information about the schedule of the selected expert meeting (step S1212).

[0333] Then, the terminal devices B13, B23, C14, C24, D11, and D21 used by the medical workers receive the notification of convening the expert meeting (step S1213).

[0334] Then, medical workers Fig.33 In the screen shown as an example of GUI160, the examination result of the examination commissioned for the patient's genetic information is registered for the applied expert meeting. That is, the medical worker refers to the GUI160 displayed in the terminal device B13 and confirms the status of the commissioned examination in the "Status of specimen preparation and examination" column. When the examination is completed, click the hyperlink assigned to the text column "Unregistered" displayed in the registration status of the examination result, and the registration screen of the examination result is displayed. The medical worker registers the examination result by dragging and dropping the file of the examination result report to the displayed registration screen of the examination result. The terminal device B13 receives the registration request of the examination result from the medical worker and sends it to the integrated data management device A (step S1214). It should be noted that the examination result registration request can be received from the examination information management device C11 of the examination facility C1, but is not limited to this. When receiving a request to register the examination results from the examination information management device C11 of the examination facility C1, the control unit 10 of the integrated data management device A creates and stores the examination results of the patient's genome set examination obtained from the examination information management device C11 of the examination facility C1 in separate folders in the storage unit 30 of the integrated data management device A. The control unit 10 of the integrated data management device A records the link information pointing to the folder in the integrated database 302 stored in the integrated data management device A. Fig.14 In the main table 25 shown.

[0335] The integrated data management device A records the inspection result received from the terminal device B13 in the corresponding record of the master table 25. Thus, the schedule of the expert meeting is associated with the inspection result and recorded. (Step S1215)

[0336] Then, when each medical worker clicks on the buttons displayed on the terminal devices B13, B23, C14, C24, D11 and D21 used, Fig.38 The "Related Information Display" column of the GUI 210 shown in FIG. 12 displays the inspection results recorded in association with the schedule of the expert meeting in step S1215. Fig.45 GUI240 shown (step S1216).

[0337] Then, use Fig.32 An example of a processing flow performed by the control unit 10 of the integrated data management device A for transmitting information on the schedule of a specialist meeting and examination results associated with the schedule to the terminal devices B13, B23, C14, C24, D11, and D21 of each medical worker will be described.

[0338] The control unit 10 of the integrated data management device A determines whether to receive the login information input when the medical worker requests authentication from the terminal device B13 (step S401). If the login information is received (YES in step S401), the control unit 10 refers to the integrated database 302 stored in the integrated data management device A. Figure 6 The authentication form 38 is shown (step S402). Here, the case where the login information is a combination of a user ID and a login password is described as an example, but the medical worker may also be authenticated by fingerprint authentication or facial recognition, and is not limited thereto.

[0339] Next, the control unit 10 determines whether the received login information is consistent with the information included in the authentication form 38 (step S403). For example, when the login information includes a login password, the control unit 10 determines whether the login password corresponding to the user ID included in the authentication form 38 is consistent with the login password included in the received login information. If they are inconsistent (NO in step S403), the control unit 10 refuses to authenticate the login (step S404). On the other hand, if they are consistent (YES in step S403), the login is authenticated (step S405).

[0340] After the login is authenticated, the control unit 10 determines whether a display request for the acceptance screen of the inspection request is received (step S406). When the control unit 10 receives the display request (YES in step S406), it sends a message for causing the terminal device B 13 to display the inspection request. Fig.29 The information of the inspection request acceptance screen shown in the GUI 150 is sent by the control unit 10 (step S407). It should be noted that the information sent by the control unit 10 to display a predetermined screen on the terminal device B 13 includes HTML (Hyper Text Markup Language), XML (eXtecsible Markup Language), and JavaScript (registered trademark) data, but is not limited thereto.

[0341] Then, the control unit 10 determines whether information about the facility for explaining the inspection results is received (step S408). When information about the facility for explaining the inspection results is received (YES in step S408), schedule information of a plurality of expert meetings held in the facility for explaining the inspection results is transmitted to the terminal device B13 (step S409).

[0342] That is, the control unit 10 refers to the information about the facility that interprets the received inspection result, stored in the integrated database 302 of the integrated data management device A, Fig.18 The expert meeting schedule 27 shown in the figure extracts the schedule information of multiple expert meetings held in the facility for interpreting the received examination results. It should be noted that the control unit 10 can refer to the allowed number of patients recorded in association with the extracted expert meetings, and exclude the expert meetings with an allowed number of patients of 0 before sending them to the terminal device B13.

[0343] Then, the control unit 10 determines whether the selection of the expert meeting and the notification of the convening are received (step S410). When the selection of the expert meeting and the notification of the convening are received (YES in step S410), the control unit 10 determines whether the selected expert meeting can accept the application (step S411). That is, the control unit 10 refers to the integrated database 302 stored in the integrated data management device A, Fig.18 The expert conference schedule 27 shown refers to the number of allowed patients recorded in association with the selected expert conference. When the number of allowed patients is greater than 1 (YES in step S411), an application for the selected expert conference is accepted. At this time, the control unit 10 decrements the number of allowed patients recorded in association with the selected expert conference by 1 (step S412). In addition, when the number of allowed patients recorded in association with the selected expert conference is 0 (NO in step S411), the control unit 10 returns to step S410 and determines whether to receive the selection and convening notification instructions of other expert conferences.

[0344] In addition, after determining whether the selected expert conference can accept the application (step S411), the control unit 10 can determine whether to accept the application for the expert conference approved by the medical worker who has the authority to set the expert conference. That is, when a medical worker who does not have the authority to set the expert conference, such as the responsible physician H1a affiliated with the medical facility B1, submits an application for the selected expert conference, the application is approved by the medical worker who has the authority to set the expert conference, such as the medical worker affiliated with the medical facility B2. The medical worker affiliated with the medical facility B2 approves the application for the expert conference from the terminal device B23. The terminal device B23 sends the approval information to the integrated data management device. When the control unit 10 of the integrated data management device receives the approval information, it decrements the number of allowed patients recorded in association with the selected expert conference (step S412). It should be noted that when the doctor H1a in charge of the medical facility B1 asks (applies for) multiple candidates for expert conferences to the medical staff of the medical facility B2, the medical staff of the medical facility B2 can select one expert conference from them to approve the application for the expert conference.

[0345] Then, the control unit 10 obtains the contact information of the plurality of medical workers associated with the selected expert conference (step S413). Fig.18 The control unit 10 then refers to the group ID recorded in the integrated database 302 stored in the integrated data management device A. Fig.17 The control unit 10 then refers to the group table 26 shown in the figure to extract the user IDs of the users constituting the group, which are recorded in association with the extracted group ID. Fig.10 The user registration form 23 shown is used to obtain the contact information associated with the extracted user ID. It should be noted that the example of referring to the expert meeting schedule 27 and the user registration form 23 is shown here, and the main table 25 and the user registration form 23 can also be referred to, and other tables combining the expert meeting schedule 27 and the user registration form 23 can also be made, but it is not limited to this.

[0346] Then, the control unit 10 transmits information on the schedule of the selected expert conference to the acquired contact information of the plurality of medical workers (step S414).

[0347] Furthermore, the control unit 10 determines whether a request for registration of the inspection result of the selected expert meeting is received (step S415). When a request for registration of the inspection result is received (YES in step S415), the integrated database 302 stored in the integrated data management device A is stored in the integrated database 302. Fig.14 In the main table 25 shown, the received test results are associated with the selected expert meeting and recorded (step S416). It should be noted that the test result registration request can also be received from the test information management device C11 of the test facility C1, but it is not limited to this. When the test result registration request is received from the test information management device C11 of the test facility C1, the control unit 10 of the integrated data management device A creates separate folders in the storage unit 30 of the integrated data management device A for the test results of the patient's genome set test obtained from the test information management device C11 of the test facility C1 and saves them. The control unit 10 of the integrated data management device A records the link information pointing to the folder in the integrated database 302 stored in the integrated data management device A. Fig.14 In the main table 25 shown.

[0348] In the selected expert conference, if each medical worker attending the expert conference displays each terminal device B13, B23, C14, C24, D11 and D21 Fig.38 210 shown in the figure and clicks "Related information display" in the "Related information" column, the control unit 10 sends the result information including the inspection result associated with the expert meeting (step S417). The terminal devices B13, B23, C14, C24, D11 and D21 that have received the result information display Fig.45 GUI240 shown.

[0349] It should be noted that the control unit 10 may be configured to detect that the medical worker such as the responsible physician H1a has registered the patient information of the patient P, and notify the detected patient information to a plurality of medical workers. Thus, the registration status of the patient information for reference by the expert meeting can be appropriately notified to a plurality of medical workers, and the discussion of the expert meeting can be appropriately assisted.

[0350] Therefore, the integrated data management device A can receive input of the appointment of a specialist meeting for explaining the examination results of the examination performed in the examination facility C1 in addition to the examination request information input by the responsible physician H1a. Furthermore, the integrated data management device A can send a notification with the subject "the specialist meeting is scheduled to be held" to the terminal devices B13, B23, C14, C24, D11 and D21 of each medical worker attending the specialist meeting for which the appointment is received.

[0351] <Display of the schedule of expert meetings>

[0352] The control unit 10 of the integrated data management device A can, for example, display information about the examination request information received by the control unit 10 and the schedule of the expert meeting on the terminal devices B13, B23, C14, C24, D11 and D21 used by medical workers participating in the expert meeting. Fig.33 This is an example of a GUI 160 for displaying information on a list of examination requests and a schedule of expert meetings in the form of a screen display on the terminal devices B13, B23, C14, C24, D11, and D21 used by medical personnel. The control unit 10 causes the display units of the terminal devices B13, B23, C14, C24, D11, and D21 to display the GUI 160 as an examination progress screen that displays both examination progress information and schedule information.

[0353] The GUI 160 includes an area R5 for displaying a list of inspection requests and an area R6 for displaying a schedule of expert meetings.

[0354] Area R5 displays, for example, "date of commission", "patient ID", "status of specimen preparation and examination", "registration status of patient information", and "registration status of examination results". It should be noted that area R5 may display "examination commission ID". Both patient information and examination result information are information for reference by multiple medical workers in expert meetings.

[0355] Examples of display of “subject preparation and examination status” include “subject preparation in progress”, “subject preparation completed”, “subject transport in progress”, “subject transport completed”, “subject re-acquisition”, “examination terminated”, “DNA extraction completed”, “pretreatment completed”, “sequencing completed”, “sequence analysis completed”, and “examination completed”. The date and time when the examination is expected to be completed may also be displayed.

[0356] Examples of display of “registration status of patient information” include “unregistered”, “partially registered”, “registration completed”, etc. It should be noted that “partially registered” means that the electronic medical record of the patient is registered, but the pathological image is not yet registered.

[0357] Examples of the display of “registration status of inspection results” include “not registered” and “registration completed”.

[0358] Based on the fact that the medical facility B1 and the examination facility C1 register patient information, examination results, etc. for reference by multiple medical workers in the expert meeting in the comprehensive data management device A, the registration status can be notified to the terminal devices B13, B23, C14, C24, D11 and D21, etc. corresponding to the multiple medical workers.

[0359] On the other hand, the region R6 displays, for example, “facility where the expert meeting is held”, “status”, and “date and time of the meeting”.

[0360] Information indicating the setting status of the expert meeting is displayed in the "Status". For example, if the schedule of the expert meeting has been determined and the medical staff participating in the expert meeting have been notified of the schedule, "Status" will display "Set". On the other hand, if the schedule of the expert meeting has not been determined or the medical staff participating in the expert meeting have not been notified, "Not Set" will be displayed.

[0361] Regarding the "date and time of convening", for expert meetings whose "status" is "set", "this expert meeting is being held" or the convening schedule is displayed in the form of date and time, and for expert meetings whose "status" is "not set", the subject of "not set" is displayed. Regardless of whether the "status" is "set" or "not set", you can make new settings for expert meetings and update the status of expert meetings by clicking on the display.

[0362] The control unit 10 of the integrated data management device A accepts attribute selection of information such as "inspection request ID", "inspection results", "date and time of expert meeting" stored in the integrated database 302 via GUI160, reads out information corresponding to the selected attributes from the integrated database 302 and outputs it.

[0363] The control unit 10 may acquire a record ID for each record, the record ID being record identification information for identifying each record of the outputted attribute information. In this case, the control unit 10 associates the record ID with the selected attribute information and outputs the resultant.

[0364] The control unit 10 may display an icon 170 for alerting the user in the GUI 160. For example, when it is highly likely that the examination cannot be completed before the scheduled date and time for holding the expert meeting, when the examination is about to be completed or has been completed but the "status" of the expert meeting is "not set", or when the implementation of the examination is expected to be delayed due to the status of the subject preparation and the examination, the control unit 10 may display the icon 170 in the GUI 160. Here, the case where the implementation of the examination is expected to be delayed due to the status of the subject preparation and the examination is, for example, "examination suspension" and "subject re-acquisition".

[0365] It should be noted that the icon 170 can be any icon that can alert medical workers and is not limited to "!". In addition, as an alternative to displaying the icon 170, the expert meeting and the date and time of the meeting may be displayed in a font and color different from the surroundings.

[0366] More specifically, the control unit 10 of the integrated data management device A causes the GUI 160 to display the icon 170 under the following circumstances: (1) when the "status of specimen preparation and examination" is "subject re-acquisition"; (2) when the "status of specimen preparation and examination" is "examination terminated"; (3) when the "status of specimen preparation and examination" has not become "examination completed" and the date of the expert meeting is less than 1 week; (4) when the "status of specimen preparation and examination" is "examination completed" and the "status" of the expert meeting is "not set"; (5) when the "status of specimen preparation and examination" has reached "sequence reading completed" and the "status" of the expert meeting is "not set".

[0367] The control unit 10 can determine whether the above conditions (1) to (5) are satisfied based on the information recorded in the master table 25 of the integrated data management device A, and display the icon 170 on the GUI 160 .

[0368] <Processing flow of display GUI 160>

[0369] Here, use Fig.34 The following describes a process flow for causing the terminal device B13 used by the medical staff of the medical facility B1 to display the GUI 160 including information on the examination request list and the schedule of the specialist conference. Fig.34 This is a diagram showing an example of a processing flow for causing the terminal device B13 to display a list of examination requests associated with patients for which a medical worker is in charge and information on a schedule of a specialist meeting.

[0370] First, the terminal device B13 receives an instruction to display the schedule of the expert meeting from the medical worker affiliated with the medical facility B1 (step S1301). Then, the terminal device B13 sends a request for information such as the patient ID of the patient for whom the medical worker is responsible, the examination date of the patient's examination request, the information on the preparation and examination of the specimen, the facility where the expert meeting is held and its date and time, etc., together with the user ID of the medical worker to the integrated data management device A (step S1302).

[0371] Then, the control unit of the integrated data management device A uses the received user ID as a key and refers to the master table 25 stored in the storage unit 30 to obtain the requested information (step S1303). The integrated data management device A transmits the obtained information to the terminal device B 13 (step S1304).

[0372] Then, the terminal device B13 displays the information received from the integrated data management device A on the display unit of the terminal device B13 in the form of the GUI 160 (step S1305).

[0373] use Fig.35The details of the process performed by the integrated data management device A for causing the terminal device B13 used by the medical staff to display the GUI 160 will be described. Fig.35 This is a diagram showing an example of a process flow performed by the control unit 10 of the integrated data management device A for causing the terminal device B13 of the medical worker to display information associating information on the progress of the examination and information on the schedule of the expert meeting.

[0374] The control unit 10 of the integrated data management device A determines whether to receive the login information from the terminal device B13 (step S501). If the login information is received (YES in step S501), the authentication table 38 stored in the integrated database 302 of the integrated data management device A is referenced (step S502). Next, it is determined whether the login password corresponding to the user ID contained in the authentication table 38 is consistent with the login password contained in the received login information (step S503). In the case of inconsistency (NO in step S503), the control unit 10 refuses to authenticate the login (step S504). On the other hand, in the case of consistency (YES in step S503), the login is authenticated (step S505).

[0375] Then, the control unit 10 determines whether a request to display information about the patient for which the authenticated medical worker is responsible and information about the expert conference is received (step S506). If a display request is received (YES in step S506), the information about the examination and the information about the expert conference associated with the user ID of the authenticated medical worker are extracted from the master table 25 (step S507).

[0376] Then, the control unit 10 extracts information on the progress of the examination associated with the extracted information on the examination (step S508 ).

[0377] Then, the control unit 10 associates the information on the progress of the examination with the information on the expert conference, and transmits the association to the terminal device B 13 (step S509 ).

[0378] <Registration of the Expert Meeting Schedule>

[0379] In the mediation Fig.29 When the GUI150 shown in the terminal device B13 of the medical facility B1 is used to accept the input of the appointment for the expert meeting, the control unit 10 of the integrated data management device A registers the information input as the appointment for the expert meeting in the master table 25 of the patient associated with the input examination request information.

[0380] In addition, the control unit 10 of the integrated data management device A retrieves the expert meeting schedule 27 (see Fig.18 ) extracts information displayed in the "date and time of the expert meeting" of the facility input as the facility for interpreting the inspection result.

[0381] The control unit 10 generates a list of scheduled dates and time periods for holding expert conferences based on the extracted information, and displays the list on the terminal devices B13, B23, C14, C24, D11, and D21 used by medical staff. Fig.33 GUI160 shown.

[0382] It should be noted that when the control unit 10 of the integrated data management device A extracts the date and time of the expert meeting from the expert meeting schedule 27 as a candidate schedule for the expert meeting to be held in the facility input as the "facility for interpreting the examination results", the extraction conditions can be changed according to the "conditions of the subject preparation and examination".

[0383] Examples of the extraction conditions include the following conditions (1) to (5).

[0384] (1) When the "specimen preparation and examination status" is "examination completed", a list of scheduled dates and time periods for expert meetings after the day after the date indicated by the current date and time is displayed, for example, a two-week schedule.

[0385] (2) When "Subject preparation and examination status" is "Subject re-acquisition", a list of scheduled dates and time periods for expert meetings to be held a specified number of days (eg, 40 days) from the current date and time is displayed, for example, a two-week schedule.

[0386] (3) When the "Status of specimen preparation and examination" is any of "Specimen preparation completed", "Specimen being transported", and "Specimen transport completed", a list of scheduled dates and time periods for expert meetings to be held a specified number of days (for example, 30 days) from the current date and time is displayed, for example, a two-week schedule.

[0387] (4) When the "Status of specimen preparation and examination" is either "DNA extraction completed" or "Preprocessing completed", a list of scheduled dates and time periods for expert meetings to be held a specified number of days (e.g., 15 days) from the current date and time is displayed, for example, a two-week schedule.

[0388] (5) When "Status of specimen preparation and examination" is either "Sequence reading completed" or "Analysis completed", a list of scheduled dates and time periods for expert meetings to be held a specified number of days (e.g., 10 days) from the current date and time is displayed, for example, a two-week schedule.

[0389] It should be noted that the conditions for extracting schedule candidates for the expert meeting are not limited to these, and can be appropriately changed according to the use of the medical facilities B1 and B2.

[0390] <Notify medical staff of the schedule of the expert meeting>

[0391] The control unit 10 of the integrated data management device A can notify the medical staff based not only on the “status of sample preparation and examination” but also on the “registration status of patient information” and the “registration status of examination information”.

[0392] For example, based on the fact that the patient information and the test results are registered in the master table 25 , the control unit 10 sends a notification of holding a specialist meeting to medical workers who participate in the specialist meeting for interpreting the test results.

[0393] For example, when the condition for displaying the icon 170 is satisfied, the control unit 10 sends a notification to the medical staff participating in the expert meeting, with the subject line "The schedule for holding the expert meeting may be changed." The notification may be a notification to prompt the medical staff to set the date and time for holding the expert meeting in advance, or a notification to prompt the medical staff to reset the date and time for holding the expert meeting or cancel the schedule for holding the expert meeting.

[0394] [GUI 180 for accepting input of selection information of experts participating in the expert meeting]

[0395] The control unit 10 of the integrated data management device A can cause the terminal devices B13, B23, C14, C24, D11 and D21 to display a GUI 180 for: Fig.29 In the region R4 of the GUI 150 shown, when a specialist meeting is selected from a list of scheduled dates and time periods for holding a specialist meeting and a reservation for the specialist meeting is input, input of selection information of a specialist to participate in the selected specialist meeting is accepted.

[0396] Fig.36 This is a diagram showing an example of a GUI 180 displayed on the terminal devices B13, B23, C14, C24, D11, and D21 for accepting given instructions from experts participating in the expert meeting. The GUI 180 includes an area R7 for accepting selection of a scheduled date and time period for holding the expert meeting, and an area R8 for accepting selection instructions from experts participating in the expert meeting.

[0397] Area R7 shows Fig.29 The list of appointments (schedule candidates) of the specialist meetings scheduled to be held in the facility selected in the region R4 of the GUI 150 shown is provided with a selection field for selecting each specialist meeting.

[0398] In addition, a selection bar is provided in region R8, and the selection bar is used to select the name, duties, professional field, and each medical worker as a candidate of a medical worker, i.e., an expert, who can participate in the expert meeting selected in region R7. For example, the candidate of an expert who can participate in the selected expert meeting can be a medical worker who does not participate in other expert meetings at the date and time of the selected expert meeting, i.e., a medical worker who has a free schedule at the date and time.

[0399] exist Fig.36 In the example shown, a specialist meeting scheduled to be held at "10:00-12:00" on "January 7, 2019" is selected in region R7, and a candidate list of medical professionals who will participate in the selected specialist meeting is displayed in region R8. A genetic counselor "XXXX" and a medical professional "ZZZZ" who specializes in lung cancer are further selected as participants of the specialist meeting.

[0400] The control unit 10 refers to, for example, the earliest expert meeting scheduled to be held after a predetermined number of days (e.g., 30 days) or more from the date indicated by the data of "inspection request date" in the main table 25 stored in the integrated database of the integrated data management device A from the expert meeting schedule 27. It should be noted that, for example, the time period of the meeting date to be set is set at intervals of one hour between 9:00 and 17:00.

[0401] The control unit 10 refers to the input examination request information to identify the patient ID corresponding to the "examination request date" of the master table 25 and the user ID corresponding to the examination request ID, etc. The control unit 10 refers to the expert meeting schedule 27 to extract the "expert meeting date and time" associated with the group ID corresponding to the identified user ID.

[0402] like Fig.18 As shown, the "allowed number of patients" is set in the date and time of each expert meeting in the expert meeting schedule 27 stored in the integrated database 302 of the integrated data management device A.

[0403] For example, when the control unit 10 receives the selection of a date and time for holding a certain expert meeting as a schedule for an expert meeting for establishing a treatment method for a predetermined patient, the control unit 10 decrements the number of patients allowed for the expert meeting.

[0404] When the number of patients allowed for the selected specialist conference is "0", the control unit 10 may accept a candidate for a specialist conference scheduled to be held sooner than the specialist conference scheduled to be held after the selected specialist conference as the selected specialist conference. The control unit 10 notifies the medical staff of the accepted specialist conference date.

[0405] [Joining with known applications]

[0406] The control unit 10 of the integrated data management device A may have a function of cooperating with known applications installed in the terminal devices B13, B23, C14, C24, D11, and D21 used by medical personnel. Examples of known applications include schedule management applications such as Microsoft Outlook (registered trademark).

[0407] In this case, the control unit 10 can not only display information about the date and time of the expert meeting on the screen of the terminal device B13, B23, C14, C24, D11 and D21 logged in to the integrated data management device A, but also send a notification for a known application installed in the terminal device. The notification for the known application can be a notification for prompting a new setting or change of the schedule of the expert meeting. For example, the control unit 10 can send information about the date and time of the expert meeting to the schedule table of the account managed by Microsoft Outlook (registered trademark) installed in the terminal device B13, B23, C14, C24, D11 and D21 of the medical worker, and register it in the schedule table. This notification is sent by the control unit 10 of the integrated data management device A in a file format compatible with the schedule management application installed in the terminal device B13, B23, C14, C24, D11 and D21 of the medical worker.

[0408] It should be noted that, for patients who meet specific conditions, the control unit 10 accepts the appointment of the expert conference even if the number of patients allowed to accept the selected expert conference is "0" or less. Here, the patient who meets the specific conditions refers to a patient who requires an emergency treatment, such as a patient who requests an urgent designated treatment method. In this case, when inputting the examination request information, a column for the medical staff to input whether there is urgency can be set.

[0409] [Set the date for the expert meeting based on the expected completion date of the inspection]

[0410] The control unit 10 of the integrated data management device A can receive information about the expected date and time of completion of the examination from the examination information management device C11 of the examination facility C1 that performs the gene information examination of the patient such as the genomic panel examination, and set the date and time of the expert meeting based on the information.

[0411] For example, the meeting date and time closest to the estimated completion date and time of the examination received from the examination information management device C11 may be referenced from the expert meeting schedule 27 to set the meeting date and time of the expert meeting.

[0412] The control unit 10 of the integrated data management device A can automatically set the estimated inspection completion date based on the update of the master table 25 by the terminal device C14 of the inspection facility C1. It should be noted that the control unit 10 can update the master table 25 immediately when receiving information from the inspection information management device C11. In this case, the integrated database of the control unit 10 sets, for example, a default value of the number of days required for each inspection process. For example, for the pre-processing process, it is set to 20 days, for the sequencing process, it is set to 1 day, and for the variation analysis process, it is set to 1 day.

[0413] The control unit 10 sets the initial value of the estimated inspection completion date by adding the default value of the number of days required for each process to the date indicated by the data of "inspection request date" in the master table 25. Then, the control unit 10 updates the estimated inspection completion date according to the master data update status.

[0414] For example, the control unit 10 adds the default value of the number of days required for the process registered as "completed" in the "progress status of inspection" of the master table 25. Then, the control unit 10 compares the date calculated by adding the total value to the inspection request date with the date when the master table 25 is updated. For example, when the update date of the master table 25 is later than the date calculated by adding the total value to the inspection request date, the number of days between the two dates is added to the latest estimated inspection completion date.

[0415] That is, when the inspection process is delayed from the schedule, the control unit 10 adds the number of days between the two dates to the latest estimated inspection completion date. It should be noted that, for example, when the update date of the master table 25 is earlier than or the same as the date calculated by adding the total value to the inspection request date, the control unit 10 does not change the estimated inspection completion date. That is, the control unit 10 does not change the estimated inspection completion date when the inspection process is not delayed.

[0416] It should be noted that when the inspection information management device C11 provided in the inspection facility C1 notifies the control unit 10 of the expected inspection completion date, the master table 25 may not include the inspection progress information.

[0417] When the estimated date for completion of the examination is updated, the control unit 10 resets the date and time of the most recent expert meeting in the expert meeting schedule 27 and the date and time when the number of allowed patients is available as the date and time of the expert meeting. The date and time when the number of allowed patients is available refers to the date and time when the number of allowed patients is not "0". The control unit 10 notifies the terminal devices B13, B23, C14, C24, D11 and D21 used by medical workers of the information about the reset date and time of the expert meeting. When resetting the date and time of the expert meeting, the control unit 10 increments the number of allowed patients corresponding to the date and time of the expert meeting before the reset.

[0418] <GUI 190 for accepting settings of expert meeting>

[0419] The control unit 10 of the integrated data management device A can cause the terminal device B13 of the medical facility B1 to display a GUI 190 for setting the date and time of a specialist meeting for formulating a treatment method for the patient P1. The control unit 10 can cause the terminal device B13 used by, for example, a specific medical worker who has the authority to set the specialist meeting to display a GUI 190 for setting the date and time of a specialist meeting. Fig.30 GUI150a is shown.

[0420] The GUI 150a is provided with a "meeting setting" button R23. When the medical worker clicks the "meeting setting" button R23, the terminal device B13 may display a GUI 190 ( Fig.37 ).

[0421] Fig.37 This is a diagram showing an example of a GUI 190 displayed on the terminal devices B13, B23, the terminal devices C14, C24, the terminal devices D11 and D21, etc., for accepting the schedule setting of the expert meeting.

[0422] The GUI 190 includes an area R9 for receiving input of patient information, an area R10 for displaying a list of medical professionals participating in the expert conference, an area R11 for receiving setting of a schedule for the expert conference, and a “Conference Notification” button.

[0423] Region R9 is provided with a field for accepting input of patient information such as the patient's name, the patient's gender, and the patient's date of birth. Region R10 displays the names of medical workers who will participate in the expert meeting selected in region R11. Region R12 displays a "meeting notification" button that accepts an operation for notifying the medical workers displayed in region R10 of the date and time of the selected expert meeting.

[0424] The control unit 10 may grant authority to set up expert meetings only to specified medical workers (e.g., the main person in charge of the group) in the group that participates in the expert meeting held in the facility to explain the test results of the patient. In this case, each medical worker in each group may be given a role ID corresponding to the role in the group.

[0425] In response to a click on the "Conference Notification" button in area R12, the control unit 10 sends a notification regarding the date and time of a specialist meeting selected from the dates and times of specialist meetings displayed in area R11 to the terminal devices B13, B23, C14, C24, D11, and D21 of the medical workers displayed in area R11.

[0426] The notification may be sent, for example, by e-mail. Alternatively, information on the date and time of the expert meeting may be sent to a schedule of an account managed by Microsoft Outlook (registered trademark) installed in the medical worker's terminal device B13, B23, C14, C24, D11, and D21, and registered in the schedule.

[0427] <GUI 210 for searching information related to expert conference>

[0428] The control unit 10 of the integrated data management device A can cause the terminal devices B13, B23, C14, C24, D11 and D21 of the medical worker to display the schedule of each specialist meeting related to the patient in charge of the medical worker and information related to each specialist meeting.

[0429] Fig.38 1 is a diagram showing an example of a GUI 210 including a patient ID, a test ID, a schedule of a specialist meeting, and information related to each specialist meeting in the terminal devices B13, B23, C14, C24, D11, and D21 of a medical worker.

[0430] GUI210 displays columns for "Patient ID", "Examination patient ID", "Patient name", "Gender", "Facility name where the expert meeting is held", "Date and time of the expert meeting" and "Related information" of the patient in charge of the medical worker logged into the integrated data management device A.

[0431] For example, a medical worker can confirm the patient ID, examination request ID, and the date and time of the expert conference associated with him / her using GUI 210. It should be noted that, instead of or in addition to the "patient ID" and the "examination request ID", the "comprehensive ID" may be displayed.

[0432] The "Related Information Display" in the "Related Information" column is displayed as link information pointing to the information about the patient that the medical worker is responsible for. For example, in response to the medical worker clicking the "Related Information Display" displayed in the "Related Information" column of GUI210, the control unit 10 of the integrated data management device A receives an information acquisition request from the terminal devices B13, B23, C14, C24, D11 and D21. The control unit 10 displays the information related to the expert meeting based on the received information acquisition request. The information related to the expert meeting includes, for example, the clinical information and test results of the patient P1 to be discussed in the expert meeting. Therefore, the medical worker who logs in to the integrated data management device A can easily confirm the clinical information and test results of the patient he is responsible for, for example, using the terminal device B13.

[0433] The GUI 210 displays not only the patient identification information such as the patient ID, but also the date and time of the specialist meeting and the name of the facility where the specialist meeting is held. Therefore, a medical worker who logs into the integrated data management device A can easily check information such as "when and where the specialist meeting for the patient he is responsible for is held" using the terminal device B13.

[0434] [Modification of GUI for Accepting Selection of Expert Meeting]

[0435] As Fig.38 Instead of the GUI 210 shown in FIG. 1 , the control unit 10 of the integrated data management device A can cause the terminal devices B13, B23, C14, C24, D11, and D21 of the medical worker to display Fig.39 GUI220 shown.

[0436] The GUI 220 displays information on the group holding the expert meeting and the date and time of the expert meeting on the terminal devices B13, B23, C14, C24, D11, and D21 of the medical worker.

[0437] Summary information of a group consisting of a plurality of medical workers is displayed in the "Group" column of GUI 220. Here, the summary information of the group may be information about a medical facility to which at least one medical worker constituting the group belongs, or information about a facility where a specialist meeting is held.

[0438] Alternatively, the summary information of the group may be information such as the facility ID associated with the "group ID" in the group table 26. For example, when the "group information" column is clicked, the control unit 10 may display information about the medical staff constituting the group as shown in the data of the "group information".

[0439] GUI220 first allows the medical worker to select information about the desired group. Then, the control unit 10 displays Fig.40 GUI 230 is shown containing information associated with each expert conference.

[0440] GUI 230 displays a list of patient IDs for the group selected in GUI 220. Fig.39 When "XX Hospital A Group" is selected in the illustrated GUI 220, the control unit 10 displays a GUI 230 including the patient ID, the test request ID, the patient's name, the gender, and related information related to the specialist conference for the patient in charge of the selected group.

[0441] It should be noted that the control unit 10 may associate the group (and group ID) displayed on the GUI 220 with the identification information of the facility to which at least one of the medical workers constituting the group belongs.

[0442] <Processing flow of display GUI 210>

[0443] Here we use Fig.41 The GUI 210 including the patient information about the patient P1 and the conference information about the expert conference is displayed on the terminal device B13 used by the medical staff (see FIG. 1 ). Fig.38 ) processing flow. Fig.41 This is a diagram showing an example of a processing flow for causing the terminal device B13 of the medical worker to display the schedule of the specialist conference related to the patient P1 for which the medical worker is in charge and the information related to each specialist conference.

[0444] First, the terminal device B13 sends a request to display a login screen to the integrated data management device A (step S1001). The integrated data management device A receives the request to display the login screen from the terminal device B13 (step S1002), and sends the login screen information to the terminal device B13 (step S1003). The terminal device B13 receives the login screen information from the integrated data management device and displays the login screen (step S1004).

[0445] Then, the terminal device B13 transmits the login information received from the medical worker to the integrated data management device A (step S1005). The login information includes, for example, the user ID of the medical worker.

[0446] Next, the integrated data management device A receives the login information from the terminal device B13 (step S1006), and authenticates the login of the medical worker by referring to the authentication table 38 stored in the integrated database 302 of the integrated data management device A (step S1007). Here, the authentication table 38 manages the user ID of the user who is allowed to log in to the integrated data management device A.

[0447] The integrated data management device A refers to the master table 25 using the user ID included in the login information as a key, obtains information on the patient associated with the user ID, and transmits it to the terminal device B 13 (step S1008).

[0448] Then, the terminal device B 13 creates the GUI 210 and displays the information on the patient associated with the user ID received from the integrated data management device A (step S1009 ).

[0449] use Fig.42 The details of the process performed by the integrated data management device A for causing the terminal device B13 used by the medical staff to display the GUI 210 including the patient information on the patient P1 and the conference information on the expert conference will be described. Fig.42This is a diagram showing an example of a processing flow performed by the control unit 10 of the integrated data management device A for causing the terminal device B13 of the medical worker to display the schedule of the specialist conferences related to the patients for which the medical worker is responsible and information related to each specialist conference.

[0450] The control unit 10 of the integrated data management device A determines whether to receive the login information from the terminal device B13 (step S201). If the login information is received (YES in step S201), the authentication table 38 stored in the integrated database 302 of the integrated data management device A is referenced (step S202). Next, it is determined whether the login password corresponding to the user ID contained in the authentication table 38 is consistent with the login password contained in the received login information (step S203). When they are inconsistent (NO in step S203), the control unit 10 refuses to authenticate the login (step S204). On the other hand, when they are consistent (YES in step S203), the login is authenticated (step S205).

[0451] Then, the control unit 10 extracts the patient information associated with the user ID included in the authenticated login information from the master table 25 (step S206 ).

[0452] Then, the control unit 10 extracts information on the expert conference associated with the extracted patient information from the master table 25 (step S207 ).

[0453] Then, the control unit 10 sends an HTML file containing the extracted patient information and information related to the expert meeting and a CSS (Cascading Style Sheets) file for displaying the information in a table format to the terminal of the authenticated user (step S208). It should be noted that the control unit 10 may also send a JSON (JavaScript Object Notation) file containing the extracted patient information and information related to the expert meeting to the terminal device B13, and the HTML and CSS are generated by the JavaScript possessed by the terminal device B13.

[0454] Then, when receiving patient information and selection information of the expert meeting from the terminal device B13 of the medical worker who has logged in and has been authenticated (YES in step S209), the control unit 10 sends information about the selected genetic examination and clinical information of the patient to the terminal device B13 of the medical worker who has logged in and has been authenticated (step S210).

[0455] <Processing flow of display GUI 240>

[0456] Here, use Fig.43The GUI 240 (see FIG. 1 ) for causing the terminal devices B13, B23, C14, C24, D11, and D21 of medical personnel participating in the expert conference to display the screen display including the examination result information and clinical information related to the patient P1 will be described. Fig.45 ) processing flow. Fig.43 This is a diagram showing an example of a process flow for displaying information related to a patient for which a medical staff is in charge.

[0457] First, the terminal device B13 installed in the medical facility B1 receives the Fig.38 The GUI 210 shown receives an information acquisition request from a medical worker. The terminal device B 13 sends the information acquisition request for related information and the patient ID and examination request ID corresponding to the "related information display" in the related information column of the GUI 210 that is clicked by the medical worker to the integrated data management device A (step S1101).

[0458] Reference Fig.43 , the integrated data management device A receives the information acquisition request for the associated information together with the patient ID and the inspection request ID (step S1102). Then, the master table 25 stored in the integrated database of the integrated data management device A is referenced using the received patient ID and the inspection request ID as a key (step S1103). The integrated data management device A obtains the inspection results corresponding to the patient ID and the inspection request ID and the clinical information of the patient from the master table 25, and sends them to the terminal device B 13 (step S1104).

[0459] Then, the terminal device B13 of the medical facility B1 displays the clinical information and test results of the patient received from the integrated data management device A as the GUI 240 (step S1105 ).

[0460] use Fig.44 The details of the processing performed by the integrated data management device A for causing the terminal device B13 used by the medical staff to display the GUI 240 including the examination result information of the patient P1 and the clinical information of the patient P1 will be described. Fig.44 This is a diagram showing an example of a process flow performed by the control unit 10 of the integrated data management device A for causing the terminal device B 13 of the medical worker to display the clinical information and the test results of the patient.

[0461] The control unit 10 of the integrated data management device A determines whether to accept the login information from the terminal device B13 of the medical facility B1 (step S301). If the login information is accepted (YES in step S301), the authentication table 38 stored in the integrated database 302 of the integrated data management device A is referred to (step S302), and it is determined whether the login password corresponding to the user ID contained in the authentication table 38 is consistent with the login password contained in the accepted login information (step S303). If they are inconsistent (NO in step S303), the control unit 10 refuses to authenticate the login (step S304). On the other hand, if they are consistent (YES in step S303), the login is authenticated (step S305).

[0462] Then, the control unit 10 determines whether a request for displaying a test request acceptance screen is received from the terminal device B13 of the medical facility B1 (step S306). If a request for displaying a test request acceptance screen is received (YES in step S306), the terminal device B13 is caused to display the test request acceptance screen (step S307).

[0463] Then, the control unit 10 determines whether the examination request information is received from the terminal device B13 of the medical facility B1 (step S308). If the examination request information is received (YES in step S308), an examination request ID corresponding to the examination request is generated (step S309).

[0464] Then, the control unit 10 associates the generated inspection request ID with the information related to the inspection request, and transmits the same to the terminal device C14 of the inspection facility C1 and the transmission and reception management device E11 of the transportation office E1 (step S310).

[0465] Then, the control unit 10 determines whether the subject ID of the subject collected by the patient P1 is received from the terminal device B13 of the medical facility B1 (step S311). If the subject ID is received (YES in step S311), the examination request ID is associated with the subject ID and recorded in the integrated database 302 (step S312).

[0466] Then, the control unit 10 determines whether the inspection request ID and inspection result are received from the terminal device C14 of the inspection facility C1 (step S313). If the inspection request ID and inspection result are received (YES in step S313), the inspection request ID and the inspection result are associated and stored in the integrated database 302 (step S314).

[0467] Here, the integrated database 302 associates the clinical information of the patient P1 with the examination request ID and records it in the main table 25 of the integrated database 302 ( Fig.12By associating the examination request ID with the examination result and storing them in the integrated database 302, the clinical information of the patient P1 and the examination result of the patient P1 are associated with each other via the examination request ID and recorded in the main table 25 of the integrated database 302 ( Fig.12 Step S23).

[0468] Reference Fig.44 , the control unit 10 of the integrated data management device A determines whether a display request for the examination results and clinical information of the specified patient P1 is received from the authenticated medical worker (step S315). If a display request for the examination results and clinical information of the specified patient P1 is received (YES in step S315), clinical information and information related to the expert conference are acquired from the integrated database 302 of the integrated data management device A based on the received patient ID of the patient P1 (step S316).

[0469] Then, the control unit 10 of the integrated data management device A transmits the examination result of the patient P1 and the clinical information of the patient P1 to the terminal device B13 of the authenticated medical worker (step S317).

[0470] <Screen display in response to information acquisition request>

[0471] Then, use Fig.45 The following describes screen displays displayed on the terminal devices B13, B23, C14, C24, D11, and D21 used by the participants of the expert conference in response to receipt of an information acquisition request. Fig.45 This is a diagram showing an example of a GUI 240 that the control unit 10 of the integrated data management device A displays on the terminal devices B13, B23, C14, C24, D11, and D21, etc., in response to receipt of an information acquisition request.

[0472] The GUI 240 displays “patient ID”, “patient’s medical history”, “examination results”, “pathological images” and “pathologist’s findings”. The patient’s medical history includes information about the patient P1, such as the patient’s current condition, family history, medical history, and treatment history.

[0473] In addition, the “test results” displayed in region R13 include information about the test results, such as “EGFR T790M”, including whether there is a mutation in the base sequence, the location of the mutation, and the type of mutation. In addition, region R13 includes information about therapeutic drugs associated with each detected mutation, such as “drug A”, as drug information associated with the mutation detected by the genome panel test.

[0474] The pathological image received by the integrated data management device A from the medical facility B1 associated with the patient is displayed in the region R14 as clinical information of the patient P1. In addition, the "pathologist's findings" button is displayed in the region R15 for inputting an instruction to enter a screen of the findings of the pathologist H1b who performs pathological diagnosis on the patient. By clicking the "pathologist's findings" button, the findings of the pathologist H1b based on the pathological image input by the pathologist H1b as clinical information of the patient P1 can be further confirmed.

[0475] By providing the GUI 240 including the examination results and clinical information of the patient P1 to the experts participating in the expert meeting before and during the expert meeting, the information required for formulating the most suitable treatment policy for the patient P1 can be comprehensively presented. This can make the expert meeting run smoothly and assist the discussion for formulating the treatment policy for the patient.

[0476] <Associating test results with information related to treatment drugs>

[0477] Fig.47 This is a flowchart for explaining an example of processing in which the control unit 10 of the integrated data management device A associates information on mutations detected by an examination and information on therapeutic drugs with the examination results.

[0478] The control unit 10 of the integrated data management device A receives the input of the inspection result from the terminal device C14 of the inspection facility C1 (step S131), and determines whether there is a detected variation in the inspection result (step S132). If there is a detected variation (YES in step S132), the control unit 10 refers to the variation table 250 stored in the integrated database 302 ( Fig.48 ), the identification information associated with each detected mutation (e.g., a mutation name such as "EGFR T790M" or a mutation ID assigned to each mutation, etc.) is associated with the test result (step S133). After step S133, the presence or absence of candidate therapeutic drugs is confirmed (step S134).

[0479] When the detected mutation does not exist (NO in step S132), the control unit 10 confirms whether there is a candidate therapeutic drug (step S134).

[0480] The control unit 10 refers to the therapeutic drug table 260 ( Fig.49 ) determines whether there is a candidate therapeutic drug (step S134). If there is a candidate therapeutic drug (YES in step S134), the identification information associated with the candidate therapeutic drug (such as the name of the therapeutic drug or the drug ID, etc.) is associated with the inspection result (step S135).

[0481] (Introduction of annotation information)

[0482] Refer to Figure 2 , the integrated data management device A assists in obtaining external information as annotation information for reference in the expert meeting. For example, the integrated data management device A provides links to information retrieval websites managed by the mutation information management device F11, the drug information management device F21, and the academic paper information management device F31.

[0483] Fig.50 It is a flowchart showing an example of the process in which the control unit 10 of the integrated data management device A associates the annotation information input from the mutation information management device F11, the drug information management device F21, and the academic paper information management device F31 with the examination results of the patient P1.

[0484] The control unit 10 first accepts the input of annotation information from the terminal devices B13, B23, C14, C24, D11, and D21 used by medical staff (step S141), and determines whether there is a mutation to be detected in the examination results of the patient P1 (step S142). When a detected mutation exists (YES in step S142), the control unit 10 associates the identification information about the mutation recorded in the annotation information with the mutation in the examination results (step S143). After step S143, it is determined whether there is a record of a therapeutic drug (step S144). Fig.51 It is a diagram showing an example of the GUI270 for the mutation database retrieval entry used to retrieve mutation information. The GUI270 is a retrieval screen for retrieving at least one of the annotation associated with the mutation information and the therapeutic drug information associated with the mutation. The area R16 is a column for inputting the mutation that becomes the retrieval key.

[0485] When the detected mutation does not exist (NO in step S142), the control unit 10 determines whether there is a record of a therapeutic drug (step S144). When there is a record of a therapeutic drug (YES in step S144), the control unit 10 associates the identification information associated with the annotation information about the therapeutic drug with the examination results (step S145).

[0486] The control unit 10, for example, attaches the keywords used in the retrieval as meta-information to the information obtained by the mutation information management device F11 and the drug information management device F21. Examples of the keywords attached as meta-information include, for example, "EGFRT790M" and the names of therapeutic drugs. The control unit 10 performs integration (Japanese: 名寄せ) based on the attached meta-information. During the integration, the data about mutations, therapeutic drugs, etc. in the main table 25 can be referred to. The integration method is, for example, the same as the above-mentioned integration of "names".

[0487] As described above, not only can the retrieval be performed from the screen display, for example, it can also be like Fig.52As shown, related information is retrieved using "gene information" input in area R17, "drug information" input in area R18, "disease information" input in area R19, "set information" input in area R20, etc. as search keys.

[0488] The associated information is not limited to the variation information and drug information managed by the variation information management device F11 and the drug information management device F21, but may also be, for example, the paper information and treatment experience information of the academic paper information management device F31. The control unit 10 performs a search in response to the "related information search" displayed in the click area R21. It should be noted that the "set information" input in the area R20 corresponds to the identification information indicating the type of gene set test and reagent, i.e., the gene set ID. The test result assigned with the information corresponding to the gene set ID input as the set information can be extracted.

[0489] [Variant 1]

[0490] The case where the control unit 10 of the integrated data management device A automatically generates an integrated ID each time the control unit 10 receives the input of the inspection request information in the data integration processing of the integrated data management device A has been described, but the integrated ID may not be automatically generated. In this case, the control unit 10 may associate each data input as the inspection request information with the data in the integrated database 302 by so-called "integration".

[0491] Specifically, first, the control unit 10 calculates an evaluation value for each key item of the input data based on an evaluation function according to the degree of consistency between the integration basis and the integration target (master table 25 ).

[0492] For example, Fig.46 As shown, when the input data includes key items such as "name", "gender" and "date of birth", the Levenshtein distance function is used as an example of the evaluation function fa() for "name". Then, in the comparison of the key item ("name") values ​​of the integration base and the integration target, the evaluation value is calculated based on the minimum number of edits when the text string of the integration target is transformed into the text string of the integration base. For example, the evaluation function fa() returns an evaluation value of "1" when no editing is required, returns an evaluation value of "0" when all text needs to be edited, and returns an evaluation value between 0 and 1 depending on the number of edits when some text needs to be transformed.

[0493] In addition, as an example of the evaluation function fb() of "gender" and the evaluation function fc() of "date of birth", the "completely consistent" function is used. The completely consistent function calculates an evaluation value indicating whether the key item values ​​of the integration basis and the integration target are completely consistent. For example, the completely consistent function returns "1" when the two values ​​are completely consistent, and returns an evaluation value "0" otherwise.

[0494] Then, the control unit 10 weights the evaluation values ​​calculated by the evaluation function. Fig.46 In the example of , the evaluation function fa() multiplies the calculated evaluation value by weight A, the evaluation function fb() multiplies the calculated evaluation value by weight B, and the evaluation function fc() multiplies the calculated evaluation value by weight C.

[0495] Then, the control unit 10 adds the weighted evaluation values ​​to calculate the comprehensive evaluation value. Then, the control unit 10 classifies the candidates for which the comprehensive evaluation value is calculated based on a predetermined threshold. Fig.46 In the example, there are three types ("White" (high comprehensive evaluation value), "Black" (low comprehensive evaluation value), and "Gray" (medium comprehensive evaluation value)).

[0496] The control unit 10 can integrate the variation information and the information on the therapeutic drug contained in the test results with reference to the master table 25. The integration method is, for example, Fig.46 The same is shown with regard to the integration of the input data "name".

[0497] [Variant 2]

[0498] Reference Fig.53 In the medical facility B1, an information management device B14 may be further connected to the LAN within the medical facility, and the information management device B14 manages various information and data communications of the electronic medical record management device B11, the pathological image management device B12, and the terminal device B13. In this case, the communication between the integrated data management device A and the electronic medical record management device B11, the pathological image management device B12, and the terminal device B13 installed in the medical facility B1 is performed via the information management device B14. Fig.53 1 is a diagram showing a configuration example of a medical facility B1 equipped with an information management device B14. The information management device B14 is a computer that performs reception processing of various information sent from an external device to the medical facility B1 and transmission processing of various information sent from the medical facility B1 to the external device. Examples of the reception processing include file decompression, classification of received data, and receipt of received notification. In addition, examples of the transmission processing include collection, compression, and format conversion of the data to be transmitted.

[0499] [Variant 3]

[0500] Reference Fig.54 The integrated data management device A is not necessarily a cloud server, but may be, for example, a server installed in the medical facility B1. Fig.54 1 is a diagram showing an example of the configuration of an information management system 100a according to one embodiment of the present invention. In this case, the terminal device of the other medical facility B2, the terminal devices C14 and C24 of the examination facilities C1 and C2, and the terminal devices D11 and D21 of the external facilities D1 and D2 communicate with the integrated data management device installed in the medical facility B1 via the communication network 90.

[0501] It should be noted that Fig.54 2 shows an example in which the integrated data management device A is connected to the medical facility LAN in the medical facility B1 , but a configuration in which the integrated data management device A is directly connected to the communication network 90 without interposing the medical facility LAN in the medical facility B1 .

[0502] [Variant 4]

[0503] The integrated data management device A may have a configuration that combines the functions of the inspection information management devices C11 and C21.

[0504] [Configuration of the Control Unit 10 of the Integrated Data Management Device A]

[0505] The control unit 10 of the integrated data management device A may be realized by a logic circuit (hardware) formed on an integrated circuit (IC chip) or the like, or may be realized by software.

[0506] In the latter case, the integrated data management device A includes a computer that executes program instructions, and the program is software that realizes each function. The computer includes, for example, one or more processors and a computer-readable recording medium that stores the program.

[0507] Furthermore, the object of the present invention is achieved by the processor reading and executing the program from the recording medium in the computer. As the processor, for example, a CPU (Central Processing Unit) can be used. As the recording medium, a "non-temporary tangible medium", for example, a ROM (Read Only Memory), a tape, a disk, a card, a semiconductor memory, a programmable logic circuit, etc. can be used. In addition, a RAM (Random Access Memory) for expanding the program can be further provided.

[0508] In addition, the program can be supplied to the computer via any transmission medium (communication network, radio wave, etc.) that can transmit the program. It should be noted that one aspect of the present invention can be implemented in the form of a data signal embedded in a carrier wave that implements the program by electronic transmission.

[0509] The present invention is not limited to the above-described embodiments, and various modifications can be made within the scope of the claims. Embodiments obtained by appropriately combining technical features disclosed in different embodiments are also included in the technical scope of the present invention.

[0510]

Explanation of symbols

[0511] A Comprehensive data management device

[0512] B1, B2 Medical Facilities

[0513] B11, B21 Electronic medical record management device

[0514] B12, B22 Pathology Image Management Device

[0515] B13, B23 terminal devices

[0516] C1, C2 Inspection Facilities

[0517] C11, C21 inspection information management device

[0518] C14, C24 terminal devices

[0519] D1, D2 External Facilities

[0520] D11, D21 terminal devices

[0521] E1 Transport Affairs Department

[0522] E11 Transceiver Management Device

[0523] E12 Terminal Device

[0524] F11 Mutation Information Management Device

[0525] F21 Drug Information Management Device

[0526] F31 Academic Paper Information Management Device

[0527] 10. Control Unit

[0528] 30 Storage

[0529] 301 Procedure

[0530] 302 Comprehensive Database

[0531] 100, 100a Information Management System

Claims

1. A method for assisting an expert meeting of a plurality of medical professionals in interpreting genetic information, characterized in that: The process includes the following steps: Authenticating medical workers who request authentication through terminal devices; sending information for displaying a first screen for accepting a genetic examination request of a patient to a terminal device of a certified medical worker, the first screen being configured to receive a facility for interpreting a genetic examination result of the examination request; in response to acceptance of the facility via the first screen displayed on the terminal device, extracting a candidate schedule of an expert meeting to be held at the facility from an expert meeting schedule, the date of the candidate schedule being after a predetermined time period from the date of the inspection request, The date of the inspection request is: the date on which the inspection request was accepted via the first screen, or date information input to the first screen through the terminal device, and wherein the expert meeting schedule stores candidate schedules associated with the facility; The extracted candidate schedule is sent to the terminal device of the certified medical worker, wherein the extracted candidate schedule is displayed on the terminal device, and wherein the terminal device is configured to accept a schedule of the expert conference by accepting a selection of one of the extracted candidate schedules displayed on the terminal device; extracting a plurality of medical workers who will participate in the received schedule of the expert meeting to be held on the selected candidate schedule, wherein the plurality of medical workers are recorded in association with the received schedule of the expert meeting; sending the received schedule of the expert meeting to the terminal devices of the extracted plurality of medical workers, recording the examination results of the requested examination and the patient's clinical information, including the patient's pathological images, in association with the facility and the schedule of the accepted specialist meeting; and sending information for displaying a second screen to the terminal devices of the plurality of medical workers participating in the expert meeting, wherein the second screen comprehensively presents information required for formulating the most appropriate treatment policy for the patient, wherein the second screen includes examination results and pathological images, The extracted multiple medical workers include a first medical worker affiliated with a first facility and a second medical worker affiliated with a second facility different from the first facility.

2. The method according to claim 1, characterized in that It also includes the following steps: A step of recording information on the test results of the patient's genetic information in association with the received schedule of the expert meeting; and The step of transmitting the information on the examination result associated with the received schedule of the expert meeting to the terminal devices of the extracted plurality of medical workers.

3. The method according to claim 2, characterized in that The information on the test results includes whether there is a mutation in the base sequence of the gene information, the position of the mutation, and the type of the mutation.

4. The method according to claim 1, characterized in that The step of accepting the schedule of the expert meeting includes the following steps: a process of requesting a schedule from the first medical worker affiliated with the first facility; and, The second medical worker affiliated with the second facility approves the application.

5. The method according to claim 4, characterized in that In the step of applying for a schedule of the expert conference by the first medical worker affiliated with the first facility, the first medical worker applies for a plurality of candidates for the schedule of the expert conference. In the step of the second medical worker affiliated with the second facility approving the request, the second medical worker selects any one schedule from the plurality of candidates.

6. The method according to claim 1, characterized in that In the step of accepting the schedule of the expert meeting, the schedule of the expert meeting is accepted by selecting any one of a plurality of candidates for the schedule of the expert meeting.

7. The method according to claim 6, characterized in that Applications for a plurality of expert meetings can be accepted for one candidate in the schedule of the expert meeting.

8. The method according to claim 7, characterized in that The upper limit of the number of applications that can be accepted is associated with one candidate in the schedule of the expert meeting and recorded.

9. The method according to claim 1, characterized in that: In the step of transmitting the received expert meeting schedule, The schedule of the expert meeting is transmitted in a file format compatible with a schedule management application installed in the terminal devices of the plurality of medical workers.

10. An information management system for assisting an expert meeting in which a plurality of medical workers interpret genetic information, characterized in that: have: at least one terminal device operated by the plurality of medical workers; and, An integrated data management device having a control unit and a storage unit, The control unit performs: Authenticating medical workers who request authentication through terminal devices; sending information for displaying a first screen for accepting a genetic examination request of a patient to a terminal device of a certified medical worker, the first screen being configured to receive a facility for interpreting a genetic examination result of the examination request; in response to acceptance of the facility via the first screen displayed on the terminal device, extracting a candidate schedule of an expert meeting to be held at the facility from an expert meeting schedule, the date of the candidate schedule being after a predetermined time period from the date of the inspection request, The date of the inspection request is: the date on which the inspection request was accepted via the first screen, or date information input to the first screen through the terminal device, and wherein the expert meeting schedule stores candidate schedules associated with the facility; The extracted candidate schedule is sent to the terminal device of the certified medical worker, wherein the extracted candidate schedule is displayed on the terminal device, and wherein the terminal device is configured to accept a schedule of the expert conference by accepting a selection of one of the extracted candidate schedules displayed on the terminal device; extracting a plurality of medical workers who will participate in the received schedule of the expert meeting to be held on the selected candidate schedule, wherein the plurality of medical workers are recorded in association with the received schedule of the expert meeting; sending the received schedule of the expert meeting to the terminal devices of the extracted plurality of medical workers, recording the examination results of the requested examination and the patient's clinical information, including the patient's pathological images, in association with the facility and the schedule of the accepted specialist meeting; and sending information for displaying a second screen to the terminal devices of the plurality of medical workers participating in the expert meeting, wherein the second screen comprehensively presents information required for formulating the most appropriate treatment policy for the patient, wherein the second screen includes examination results and pathological images, The extracted multiple medical workers include a first medical worker affiliated with a first facility and a second medical worker affiliated with a second facility different from the first facility.

11. The information management system according to claim 10, characterized in that: As for the control unit of the integrated data management device, associating information on the test results of the patient's genetic information with the received schedule of the expert meeting and recording them in the storage unit, The information on the examination result associated with the accepted schedule of the expert conference is transmitted to the terminal devices of the extracted plurality of medical workers.

12. The information management system according to claim 11, characterized in that: The information on the test results includes whether there is a mutation in the base sequence of the gene information, the position of the mutation, and the type of the mutation.

13. The information management system according to claim 10, characterized in that: As for the control unit of the integrated data management device, when the first medical worker belonging to the first facility applies for the schedule of the expert meeting, when the second medical worker belonging to the second facility approves the application, the schedule of the expert meeting is sent to the terminal devices of the extracted multiple medical workers.

14. The information management system according to claim 13, characterized in that: As for the control unit of the integrated data management device, when the first medical worker belonging to the first facility applies for multiple candidate schedules for the expert meeting, and the second medical worker belonging to the second facility selects any schedule from the multiple candidates for the expert meeting schedule, the selected schedule of the expert meeting is sent to the terminal devices of the extracted multiple medical workers.

15. The information management system according to claim 10, characterized in that: The control unit of the integrated data management device receives the schedule of the expert meeting by selecting any one of a plurality of candidates for the schedule of the expert meeting.

16. The information management system according to claim 15, characterized in that: The control unit of the integrated data management device can accept applications for a plurality of expert meetings with respect to one candidate of the schedule of the expert meeting.

17. The information management system according to claim 16, characterized in that: The upper limit of the number of applications that can be accepted is associated with one candidate of the schedule of the expert meeting and recorded in the storage unit.

18. The information management system according to claim 10, characterized in that: The control unit of the integrated data management device transmits the received schedule of the expert conference in a file format compatible with a schedule management application installed in the terminal devices of the plurality of medical workers.

19. A comprehensive data management device for assisting an expert meeting in which a plurality of medical workers interpret genetic information, characterized in that: have Control Department, and Storage Department, The control unit performs: Authenticating medical workers who request authentication through terminal devices; sending information for displaying a first screen for accepting a genetic examination request of a patient to a terminal device of a certified medical worker, the first screen being configured to receive a facility for interpreting a genetic examination result of the examination request; in response to acceptance of the facility via the first screen displayed on the terminal device, extracting a candidate schedule of an expert meeting to be held at the facility from an expert meeting schedule, the date of the candidate schedule being after a predetermined time period from the date of the inspection request, The date of the inspection request is: the date on which the inspection request was accepted via the first screen, or date information input to the first screen through the terminal device, and wherein the expert meeting schedule stores candidate schedules associated with the facility; The extracted candidate schedule is sent to the terminal device of the certified medical worker, wherein the extracted candidate schedule is displayed on the terminal device, and wherein the terminal device is configured to accept a schedule of the expert conference by accepting a selection of one of the extracted candidate schedules displayed on the terminal device; extracting a plurality of medical workers who will participate in the received schedule of the expert meeting to be held on the selected candidate schedule, wherein the plurality of medical workers are recorded in association with the received schedule of the expert meeting; sending the received schedule of the expert meeting to the terminal devices of the extracted plurality of medical workers, recording the examination results of the requested examination and the patient's clinical information, including the patient's pathological images, in association with the facility and the schedule of the accepted specialist meeting; and sending information for displaying a second screen to the terminal devices of the plurality of medical workers participating in the expert meeting, wherein the second screen comprehensively presents information required for formulating the most appropriate treatment policy for the patient, wherein the second screen includes examination results and pathological images, The extracted multiple medical workers include a first medical worker affiliated with a first facility and a second medical worker affiliated with a second facility different from the first facility.

Images