Genome data processing system, genome data processing method, and genome data processing program

Abstract

This genome data processing system comprises enterprise servers that are each in charge of a part of a series of processes for personalized medicine with respect to genome data obtained from a specimen of a user, and a management device that manages information relating to the series of processes performed on the genome data. The enterprise servers submit a process application to the management device before executing processes. The management device, on the basis of a permission condition representing processes permitted by a user, notifies the enterprise servers regarding the result of whether the processes for which the process application has been received can be executed.

Description

Genome data processing system, genome data processing method, and genome data processing program

[0001] The present invention relates to a genome data processing system, a genome data processing method, and a genome data processing program.

[0002] Until now, medical care has been disease-centered, with the main objectives being to identify the causes of disease and develop treatments. It has long been known that the same treatment is not guaranteed to be effective even for the same disease, but individual differences in treatment effectiveness can only be understood by observing the treatment and its effects, making it difficult to create optimal treatment plans for each individual.

[0003] Meanwhile, advances in technologies such as DNA sequencing and identification of single nucleotide polymorphisms (SNPs) within DNA sequences have made it possible to observe how individuals differ from others. Therefore, using this information, it has become practical to select optimal treatments for individual patients and to select and formulate therapeutic drugs optimized for each individual. For example, Patent Document 1 describes a method for obtaining highly reliable genome mutation information from read information obtained from a next-generation sequencer.

[0004] Japanese Patent Application Laid-Open No. 2017-016665

[0005] The disclosures of the above-mentioned prior art documents are incorporated herein by reference. The following analysis has been carried out by the present inventors.

[0006] Incidentally, genome data, which represents the base sequence of DNA obtained from an individual, is in many cases considered to be a "personal identification code" in the conventional sense of the word, and must be strictly managed as personal information. Furthermore, it is expected that there are many cases in which "genomic information," which is genome data obtained from a patient and to which medical interpretations, such as information on mutations, are added, is considered to be sensitive personal information and requires special care in its handling.

[0007] Furthermore, because such genome data is considered to be personal information, it is not enough to simply protect it from leaks, tampering, etc. Specifically, companies that receive genome data must only process it as agreed upon by the data provider, and companies that receive genome data must not only protect it from leaks, tampering, etc., but also strictly manage the processing they perform on the genome data themselves.

[0008] In view of the above-mentioned problems, an object of the present invention is to provide a genome data processing system, a genome data processing method, and a genome data processing program that contribute to managing a series of processes for personalized medicine on genome data obtained from a user's specimen.

[0009] In a first aspect of the present invention, there is provided a genome data processing system comprising a corporate server that is responsible for part of a series of processes for personalized medicine on genome data obtained from a user's sample, and a management device that manages information related to the series of processes to be performed on the genome data, wherein the corporate server submits a processing request to the management device before executing the processing, and the management device notifies the corporate server of the result of whether or not the processing requested can be carried out based on permission conditions that represent the processing authorized by the user.

[0010] In a second aspect of the present invention, there is provided a genome data processing method that uses a corporate server that is responsible for part of a series of processes for personalized medicine on genome data obtained from a user's sample, and a management device that manages information related to the series of processes to be performed on the genome data, in which the corporate server submits a processing request to the management device before executing the processing, and the management device notifies the corporate server of the result of whether or not the processing requested can be carried out based on permission conditions that represent the processing authorized by the user.

[0011] In a third aspect of the present invention, there is provided a genome data processing program for causing a company server responsible for part of a series of processes for personalized medicine on genome data obtained from a user's specimen and a management device that manages information regarding the series of processes to be performed on the genome data to execute genome data processing. The genome data processing program causes the company server to submit a processing request to the management device before executing the processing, and causes the management device to notify the company server of the result of whether the requested processing is permitted based on permission conditions indicating the processing permitted by the user. This program can be recorded on a computer-readable storage medium. The storage medium can be a non-transient medium such as a semiconductor memory, a hard disk, a magnetic recording medium, or an optical recording medium. The present invention can also be embodied as a computer program product.

[0012] According to each aspect of the present invention, it is possible to provide a genome data processing system, a genome data processing method, and a genome data processing program that contribute to managing a series of processes for personalized medicine on genome data obtained from a user's specimen.

[0013] FIG. 1 is a diagram showing an example of the schematic configuration of a genome data processing system. FIG. 2 is a conceptual diagram showing an example of a series of processes for genome data in personalized medicine. FIG. 3 is a diagram showing an example of processing for personalized medicine for genome data obtained from a user's sample. FIG. 4 is a diagram showing an example of the schematic configuration of a genome data processing system. FIG. 5 is a diagram showing an example of processing for personalized medicine for genome data obtained from a user's sample. FIG. 6 is a diagram showing an example of the schematic configuration of a genome data processing system. FIG. 7 is a diagram showing an example of querying the history of processing for personalized medicine for genome data obtained from a user's sample. FIG. 8 is a diagram showing an example of processing history related to a user and user permission conditions. FIG. 9 is a diagram showing an example display of the results of matching the processing history with the permission conditions. FIG. 10 is a diagram showing an example of the schematic configuration of a genome data processing system. FIG. 11 is a diagram showing an example of querying the history of processing for personalized medicine for genome data obtained from a user's sample. FIG. 12 is a diagram showing an example of the schematic configuration of a genome data processing system. FIG. 13 is a diagram showing an example of querying the history of processing for personalized medicine for genome data obtained from a user's sample. FIG. 14 is a diagram illustrating an example of the hardware configuration of a company server and a management device used in the embodiment.

[0014] Hereinafter, embodiments of the present invention will be described with reference to the drawings. However, the present invention is not limited to the embodiments described below. In addition, the same or corresponding elements in each drawing are appropriately designated by the same reference numerals. Furthermore, it should be noted that the drawings are schematic, and the dimensional relationships and ratios of each element may differ from those in reality. There may also be parts in which the dimensional relationships and ratios differ between the drawings.

[0015] First Embodiment Fig. 1 is a diagram showing an example of the schematic configuration of a genome data processing system. As shown in Fig. 1, the genome data processing system 10a includes multiple enterprise servers 11, 12, and 13, a management device 2, a blockchain 3, a genome database 4, and a user database 5.

[0016] The multiple corporate servers 11, 12, and 13 are responsible for part of a series of processes for personalized medicine on genome data obtained from a user's specimen. Furthermore, the multiple corporate servers 11, 12, and 13 submit a processing request to the management device 2 before executing the processing. Furthermore, the multiple corporate servers 11, 12, and 13 report the processing to the management device 2 after executing the processing. As will be described in detail later, the processing up to implementing personalized medicine on genome data obtained from a user's specimen is composed of multiple consecutive processes. Therefore, although it is conceivable that a single corporate server will execute the series of processes up to implementing personalized medicine on genome data obtained from a user's specimen, it is also conceivable that the execution of the process is shared among the multiple corporate servers 11, 12, and 13.

[0017] The management device 2 manages information related to a series of processes performed on genome data. The management device 2 also notifies multiple corporate servers 11, 12, and 13 of the results of whether or not a requested process is permitted based on permission conditions that indicate the process permitted by the user. In this configuration, the management device 2 stores permission conditions in advance in the user database 5, and the management device 2 determines whether or not a requested process is permitted. Furthermore, the management device 2 registers and records the processing history reported from the corporate servers 11, 12, and 13 in the blockchain 3.

[0018] The genome database 4 stores genome data obtained from user samples and mutation information obtained by performing a series of processes on the genome data. The user database 5 stores a list of permission conditions indicating processes authorized by the user. Note that while the genome data processing system 10a shown in FIG. 1 is configured to include multiple corporate servers 11, 12, and 13 and a separate management device 2, the management device 2 may be implemented as part of the functions of the multiple corporate servers 11, 12, and 13, and each of the multiple corporate servers 11, 12, and 13 may execute the processing of the management device 2.

[0019] Figure 2 is a conceptual diagram showing an example of a series of processes for genome data in personalized medicine. As shown in Figure 2, personalized medicine is generally carried out by multiple companies, with each company sharing the responsibility.

[0020] Samples such as blood and tissue samples collected from users at medical institutions are sent to sequencing companies. The sequencing companies sequence the samples they receive and obtain genome data (read information) that represents the base sequence of the genome contained in the sample. However, because genome data (read information) is merely the base sequence of the genome, it alone cannot be used to perform personalized medicine. Therefore, the sequencing companies send the genome data (read information) to data analysis companies.

[0021] Data analysis companies analyze genome data (read information) to generate mutation information that identifies the locations containing mutations. Here, mutation information refers to information about mutations in the genome's base sequence, including the location of the base sequence containing the mutation and the type of mutation, such as a single-base mutation, insertion, or deletion in the base sequence. This mutation information is related to the biological characteristics of each individual user and is important information for personalized medicine. However, even if mutation information for each individual user is obtained, it cannot be used to determine a treatment plan for personalized medicine. Therefore, data analysis companies add mutation information to the genome data and send the resulting genome information to ICT (Information and Communication Technology) companies.

[0022] ICT companies use genomic information, which adds mutation information to genomic data, to perform neoantigen analysis and determine treatment strategies. Neoantigens are cancer antigens (markers) that emerge due to genetic mutations in cancer cells, for example, and are important information for determining personalized medicine strategies. Furthermore, since the occurrence of cancer cells does not necessarily mean that these genetic mutations will occur, analysis is necessary through neoantigen analysis of genomic information, which adds mutation information to genomic data. Meanwhile, once neoantigen information is obtained, neoantigens become targets for personalized medicine.

[0023] ICT companies send treatment plans derived from neoantigen analysis of genomic information, which adds mutation information to genomic data, to biotechnology companies. The biotechnology companies manufacture medicines and other products suited to the treatment plans derived from neoantigen analysis. The medicines and other products manufactured by the biotechnology companies are sent to medical institutions where personalized medical treatment is administered to the users.

[0024] Note that the above-described processing is an example of a series of processes performed on genome data in personalized medicine, and in actual personalized medicine, processes different from those described above may be performed. For example, neoantigen analysis is an example of a process performed in personalized medicine, and cancer gene panel testing may be performed instead of neoantigen analysis. Cancer gene panel testing is a test that examines mutations in base sequences to obtain information on therapeutic drugs and clinical trials that are expected to be effective. When an ICT company performs a cancer gene panel test, the information obtained from the test on therapeutic drugs and clinical trials that are expected to be effective is sent to a biotechnology company. The biotechnology company manufactures medicines and other products that are appropriate for the treatment plan obtained from the cancer gene panel test, and the medicines and other products manufactured by the biotechnology company are sent to medical institutions where the user receives treatment as personalized medicine.

[0025] In this way, personalized medicine does not simply acquire genome data, which is simply the base sequence of the genome, from a specimen, but also performs multiple processes afterwards. Therefore, it is common to have multiple corporate servers 11, 12, and 13, as in the genome data processing system 10a shown in Figure 1, and to share the work among the multiple corporate servers 11, 12, and 13.

[0026] 3 is a diagram showing an example of processing for personalized medicine for genome data obtained from a user's sample. As shown in Fig. 3, the series of processing for personalized medicine for genome data obtained from a user's sample includes a processing request process (S1), a condition inquiry process (S2), a process of checking the requested processing against the permission conditions (S3), a process of determining whether the processing is possible (S4), a process of actually executing the processing and notifying the results (S5), and a process of recording the notified processing history (S6).

[0027] The processing request process (S1) is a process in which the company server 11, which executes one of the processes for personalized medicine on genome data obtained from a user's sample, submits a processing request to the management device 2 before the processing.

[0028] The condition inquiry process (S2) is performed by the management device 2 that has received a processing request to inquire about the permission conditions that indicate the processing permitted by the user. Here, it is assumed that the management device 2 stores the permission conditions in advance in the user database 5, and that the management device 2 inquires about the user database 5.

[0029] In the process of comparing the requested process with the permission conditions (S3), the process requested by the company server 11 is compared with the permission conditions obtained from the user database 5. In the process of determining whether the process can be carried out (S4), the permission of the requested process is determined based on the result of comparing the requested process with the permission conditions. If the process is permitted to be carried out, the management device 2 notifies the company server 11 of the permission, and if the process is not permitted, the management device 2 notifies the company server 11 of the denial.

[0030] In the process (S5) of actually executing the process and notifying the result, the enterprise server 11 that has received the permission notification actually executes the process and notifies the management device 2 of the result. In the process (S6) of recording the history of the notified process, the management device 2 that has received the notification of the execution of the process registers the history of the process in the blockchain 3. It should be noted that the blockchain 3 can also be an ordinary database.

[0031] In addition, if the execution of the process is not permitted, the management device 2 may notify the company server 11 of the denial and terminate the process, but it is also possible for the management device 2 to register in the blockchain 3 the history of the process in which the process application was not permitted.

[0032] Furthermore, the information registered in the blockchain 3 can include not only information that processing has been performed, but also, for example, a hash value or a combination of hash values ​​of a combination of specimen ID, user ID, processing date, processing program name, program version, and processing results (product, evaluation result). Note that, although it is preferable to register and record the processing history in the blockchain, it is also possible to include the hash value of genome data.

[0033] As described above, in processing for personalized medicine on genome data obtained from a user's sample, an application for processing is made before the processing is executed, and whether the processing can be executed is determined in accordance with the permission conditions that represent the processing authorized by the user, so that the series of processing for personalized medicine can be managed so that only processing that the user has agreed to is performed.

[0034] Second Embodiment Fig. 4 is a diagram showing an example of the schematic configuration of a genome data processing system. As shown in Fig. 4, the genome data processing system 10b includes multiple enterprise servers 11, 12, and 13, a management device 2, a blockchain 3, a genome database 4, a user database 5, and a user terminal 6.

[0035] The multiple corporate servers 11, 12, and 13 are responsible for part of a series of processes for personalized medicine on genome data obtained from user samples. Furthermore, the multiple corporate servers 11, 12, and 13 submit a processing request to the management device 2 before executing the processing. Furthermore, the multiple corporate servers 11, 12, and 13 report the processing to the management device 2 after executing the processing. It is possible that a single corporate server executes the series of processes up to the implementation of personalized medicine on genome data obtained from user samples, but it is also possible that the multiple corporate servers 11, 12, and 13 share the execution of the processes.

[0036] The management device 2 manages information related to a series of processes performed on genome data. The management device 2 also notifies multiple corporate servers 11, 12, and 13 of the results of whether or not a requested process is permitted based on permission conditions that indicate the process permitted by the user. In this configuration, the user terminal 6 stores the permission conditions in advance, and the user terminal 6 determines whether or not a requested process is permitted. Furthermore, the management device 2 registers and records the processing history reported from the corporate servers 11, 12, and 13 in the blockchain 3.

[0037] The genome database 4 records genome data obtained from user samples and mutation information obtained by performing a series of processes on the genome data. The user database 5 records the location of a list of permission conditions indicating processes permitted by the user. In other words, in this configuration, the user terminal 6 holds the permission conditions, and therefore the user database 5 records that the user terminal 6 is the contact point for inquiries regarding whether or not a process can be executed.

[0038] The genome data processing system 10b shown in Figure 4 is configured to have a management device 2 separate from multiple corporate servers 11, 12, and 13, but the management device 2 may also be implemented as part of the functions of the multiple corporate servers 11, 12, and 13, and each of the multiple corporate servers 11, 12, and 13 may be configured to execute the processing of the management device 2.

[0039] 5 is a diagram showing an example of processing for personalized medicine for genome data obtained from a user's sample. As shown in Fig. 5, the series of processing for personalized medicine for genome data obtained from a user's sample includes a processing request process (S1), a process of querying a judgment destination (S2), a process of querying a user terminal (S3), a process of checking the requested processing against permission conditions (S4), a process of determining whether the processing is possible (S5), a process of actually executing the processing and notifying the result (S6), and a process of recording the notified processing history (S7).

[0040] The processing request process (S1) is a process in which the company server 11, which executes one of the processes for personalized medicine on genome data obtained from a user's sample, submits a processing request to the management device 2 before the processing.

[0041] In the process of querying the judgement destination (S2), the management device 2 queries the user database 5 for information on the referral destination that has the right to judge whether or not the requested process can be executed. Here, the user terminal 6 holds the permission conditions, and the management device 2 learns from the user database 5 that it should query the user terminal 6.

[0042] In the process of inquiring of the user terminal (S3), the management device 2 inquires of the user terminal 6 whether or not the requested process can be executed.

[0043] In the process of comparing the requested process with the permission conditions (S4), the user terminal 6 compares the process requested by the company server 11 with the permission conditions held by the user terminal 6 or inputs a user decision. In the process of determining whether the process can be carried out (S5), the user terminal 6 determines whether the requested process can be carried out based on the result of comparing the requested process with the permission conditions. If the process is to be carried out, the user terminal 6 notifies the management device 2 of the permission, and if the process is not to be carried out, the user terminal 6 notifies the management device 2 of the denial. After receiving notification of the determination result on whether the process can be carried out from the user terminal 6, the determination result is transferred to the company server 11.

[0044] In the process (S6) of actually executing the process and notifying the result, the enterprise server 11 that has received the permission notification actually executes the process and notifies the management device 2 of the result. In the process (S7) of recording the history of the notified process, the management device 2 that has received the notification of the execution of the process registers the history of the process in the blockchain 3. It should be noted that the blockchain 3 can also be an ordinary database.

[0045] In addition, if the execution of the process is not permitted, the user terminal 6 may notify the management device 2 of the denial and terminate the process, but it is also possible for the management device 2 to register in the blockchain 3 the history of the process in which the process application was not permitted.

[0046] Furthermore, the information registered in the blockchain 3 can include not only information that processing has been performed, but also, for example, a hash value or a combination of hash values ​​of a combination of specimen ID, user ID, processing date, processing program name, program version, and processing results (product, evaluation result). Note that, although it is preferable to register and record the processing history in the blockchain, it is also possible to include the hash value of genome data.

[0047] As described above, in processing for personalized medicine on genome data obtained from a user's sample, an application for processing is made before the processing is executed, and whether the processing can be executed is determined in accordance with the permission conditions that represent the processing authorized by the user, so that the series of processing for personalized medicine can be managed so that only processing that the user has agreed to is performed.

[0048] Third Embodiment Fig. 6 is a diagram showing an example of the schematic configuration of a genome data processing system 10c. As shown in Fig. 6, the genome data processing system 10c includes a management device 2, a blockchain 3, a genome database 4, a user database 5, and a user terminal 6.

[0049] The management device 2 manages information related to a series of processes performed on genome data. As described in the first embodiment, the management device 2 registers and records the history of processes reported from the company server in the blockchain 3. That is, although a description is omitted in this embodiment, the history of a series of processes performed on genome data in the genome data processing system is recorded in the blockchain 3 using the method described in the first embodiment.

[0050] The genome database 4 stores genome data obtained from user samples and mutation information obtained by performing a series of processes on the genome data. The user database 5 stores a list of permission conditions indicating the processes permitted by the user, as well as the ID and password of the user who queries the processing history.

[0051] 7 is a diagram showing an example of querying the history of personalized medicine processing of genome data obtained from a user's sample. As shown in Fig. 7, the process of querying the history of personalized medicine processing of genome data obtained from a user's sample includes a user authentication process (S1), a process of querying permission conditions (S2), a process of querying the processing history (S3), a process of comparing the processing history with the permission conditions (S4), and a process of notifying the result of the comparison (S5).

[0052] In the user authentication process (S1), the user terminal 6 transmits the user's ID and password to the management device 2, and the management device 2 references the user's ID and password stored in the user database 5 and performs user authentication by comparing the user's ID and password received from the user terminal 6 with the user's ID and password stored in the user database 5. The result of the user authentication is notified to the user terminal 6 from the management device 2.

[0053] In the process of querying permission conditions (S2), the user terminal 6 instructs the management device 2 to query permission conditions, and the management device 2, upon receiving the instruction, acquires the permission conditions of the user stored in the user database 5. In the process of querying processing history (S3), the management device 2 acquires the processing history of the user stored in the blockchain 3.

[0054] In the process of comparing the processing history with the permission conditions (S4), the management device 2 compares the processing history of the user with the permission conditions of the user. The processing history of the user and the permission conditions of the user are stored in a format such as that shown in Fig. 8, and the management device 2 compares the processing history of the user with the permission conditions of the user to determine whether only processing permitted by the user is being executed.

[0055] In the process of notifying the result of the matching (S5), the result of matching the processing history related to the user with the user's permission conditions is notified from the management device 2 to the user terminal 6. The content of the notification may be, for example, as shown in Fig. 9, such that if only processing permitted by the user is being executed, a display indicating that there is no violation of the conditions is displayed, and if processing other than that permitted by the user is being executed, a list of processing that is not permitted is displayed.

[0056] In the genome data processing system 10c and genome data processing method of the third embodiment described above, as in the first embodiment, an application for processing is made before the processing is executed, and whether or not the processing can be executed is determined in accordance with the permission conditions that represent the processing authorized by the user. Therefore, in addition to ensuring that only processing that the user agrees to is performed, the user can also inquire about the history of processing that has been executed, allowing for even stricter management of the series of processing for personalized medicine.

[0057] 10 is a diagram showing an example of the schematic configuration of a genome data processing system 10d. As shown in FIG. 10, the genome data processing system 10d includes a management device 2, a blockchain 3, a genome database 4, a user database 5, and a user terminal 6.

[0058] The management device 2 manages information related to a series of processes performed on genome data. As described in the first embodiment, the management device 2 registers and records the history of processes reported from the company server in the blockchain 3. That is, although a description is omitted in this embodiment, the history of a series of processes performed on genome data in the genome data processing system is recorded in the blockchain 3 using the method described in the first embodiment.

[0059] The genome database 4 stores genome data obtained from user samples and mutation information obtained by performing a series of processes on the genome data. The user database 5 stores a list of permission conditions indicating the processes permitted by the user, as well as the ID and password of the user who queries the processing history.

[0060] 11 is a diagram showing an example of querying the history of personalized medicine processing of genome data obtained from a user's sample. As shown in Fig. 11, the process of querying the history of personalized medicine processing of genome data obtained from a user's sample includes a user authentication process (S1), a process of querying permission conditions (S2), a process of querying the processing history (S3), a process of checking the processing history against the permission conditions (S4), and a process of outputting the checking result (S5).

[0061] In the user authentication process (S1), the user terminal 6 transmits the user's ID and password to the management device 2, and the management device 2 references the user's ID and password stored in the user database 5 and performs user authentication by comparing the user's ID and password received from the user terminal 6 with the user's ID and password stored in the user database 5. The result of the user authentication is notified to the user terminal 6 from the management device 2.

[0062] In the process of inquiring about permission conditions (S2), the user terminal 6 instructs the management device 2 to inquire about the permission conditions, and the management device 2, upon receiving the instruction, acquires the permission conditions of the user stored in the user database 5 and transmits the permission conditions to the user terminal 6. In the process of inquiring about the processing history (S3), the user terminal 6 instructs the management device 2 to inquire about the processing history, and the management device 2 acquires the processing history related to the user stored in the blockchain 3 and transmits the processing history to the user terminal 6.

[0063] In the process of comparing the processing history with the permission conditions (S4), the user terminal 6 compares the processing history of the user with the permission conditions of the user. The processing history of the user and the permission conditions of the user are stored in a format such as that shown in Fig. 8, and the management device 2 compares the processing history of the user with the permission conditions of the user to determine whether only processing permitted by the user is being executed.

[0064] In the process of outputting the matching results (S5), the results of matching the processing history related to the user with the user's permission conditions are output to the user terminal 6. As shown in Fig. 9, for example, the output contents are such that if only processing permitted by the user is being executed, a display indicating that there is no violation of the conditions is displayed, and if processing other than that permitted by the user is being executed, a list of processing that is not permitted is displayed.

[0065] In the genome data processing system 10d and genome data processing method of the fourth embodiment described above, as in the first embodiment, an application for processing is made before the processing is executed, and whether or not the processing can be executed is determined in accordance with the permission conditions that represent the processing authorized by the user. Therefore, in addition to ensuring that only processing that the user agrees to is performed, the user can also inquire about the history of processing that has been executed, allowing for even stricter management of the series of processing for personalized medicine.

[0066] Fifth Embodiment Fig. 12 is a diagram showing an example of the schematic configuration of a genome data processing system 10e. As shown in Fig. 12, the genome data processing system 10e includes a management device 2, a blockchain 3, a genome database 4, a user database 5, and a user terminal 6.

[0067] The management device 2 manages information related to a series of processes performed on genome data. As described in the first embodiment, the management device 2 registers and records the history of processes reported from the company server in the blockchain 3. That is, although a description is omitted in this embodiment, the history of a series of processes performed on genome data in the genome data processing system is recorded in the blockchain 3 using the method described in the second embodiment.

[0068] The genome database 4 records genome data obtained from user samples and mutation information obtained by performing a series of processes on the genome data. The user database 5 records the location of a list of permission conditions indicating processes permitted by the user. In other words, in this configuration, the user terminal 6 holds the permission conditions, and the user database 5 records that the user terminal 6 is the contact point for inquiries regarding whether or not a process can be executed.

[0069] 13 is a diagram showing an example of querying the history of personalized medicine processing of genome data obtained from a user's sample. As shown in Fig. 13, the process of querying the history of personalized medicine processing of genome data obtained from a user's sample includes a user authentication process (S1), a process of querying the processing history (S2), a process of reading out permission conditions (S3), a process of comparing the processing history with the permission conditions (S4), and a process of outputting the comparison result (S5).

[0070] In the user authentication process (S1), the user terminal 6 transmits the user's ID and password to the management device 2, and the management device 2 references the user's ID and password stored in the user database 5 and performs user authentication by comparing the user's ID and password received from the user terminal 6 with the user's ID and password stored in the user database 5. The result of the user authentication is notified to the user terminal 6 from the management device 2.

[0071] In the process of querying the processing history (S2), the user terminal 6 instructs the management device 2 to query the processing history, and the management device 2 acquires the processing history related to the user stored in the blockchain 3 and transmits the processing history to the user terminal 6. In the process of reading the permission conditions (S3), the permission conditions recorded in the user terminal 6 are read.

[0072] In the process of comparing the processing history with the permission conditions (S4), the user terminal 6 compares the processing history of the user with the permission conditions of the user. The processing history of the user and the permission conditions of the user are stored in a format such as that shown in Fig. 8, and the management device 2 compares the processing history of the user with the permission conditions of the user to determine whether only processing permitted by the user is being executed.

[0073] In the process of outputting the matching results (S5), the results of matching the processing history related to the user with the user's permission conditions are output to the user terminal 6. As shown in Fig. 9, for example, the output contents are such that if only processing permitted by the user is being executed, a display indicating that there is no violation of the conditions is displayed, and if processing other than that permitted by the user is being executed, a list of processing that is not permitted is displayed.

[0074] In the genome data processing system 10e and genome data processing method of the fifth embodiment described above, as in the second embodiment, an application for processing is made before the processing is executed, and whether or not the processing can be executed is determined in accordance with the permission conditions that represent the processing authorized by the user. Therefore, in addition to ensuring that only processing that the user agrees to is performed, the user can inquire about the history of processing that has been executed, thereby enabling even stricter management of the series of processing for personalized medicine.

[0075] (Hardware Configuration Example) Figure 14 is a diagram showing an example of the hardware configuration of the enterprise server and management device used in the embodiment. That is, the enterprise servers 11, 12, 13 and management device 2 are enabled to realize the respective functions of the enterprise servers 11, 12, 13 and management device 2 by executing the above-described genome data processing method as a program on an information processing device (computer) 20 employing the hardware configuration shown in Figure 14. However, the hardware configuration example shown in Figure 14 is an example of a hardware configuration that realizes the respective functions of the enterprise servers 11, 12, 13 and management device 2, and is not intended to limit the hardware configuration of the enterprise servers 11, 12, 13 and management device 2. The enterprise servers 11, 12, 13 and management device 2 may include hardware not shown in Figure 14.

[0076] As shown in FIG. 14, the hardware configuration that can be adopted by the corporate servers 11, 12, 13 and the management device 2 includes a CPU (Central Processing Unit) 21, a main memory device 22, an auxiliary memory device 23, and an IF (Interface) unit 24, which are interconnected by, for example, an internal bus.

[0077] The CPU 21 executes each command included in the genome data processing program executed by the information processing device (computer) 20. The main storage device 22 is, for example, a RAM (Random Access Memory), and temporarily stores various programs, such as the genome data processing program executed by the information processing device (computer) 20, for processing by the CPU 21.

[0078] The auxiliary storage device 23 is, for example, a hard disk drive (HDD), and is capable of storing, for the medium to long term, various programs such as a genome data processing program executed by the information processing device (computer) 20. Various programs such as a genome data processing program can be provided as a program product recorded on a non-transitory computer-readable storage medium.

[0079] The IF unit 24 provides an interface for input and output between the company servers 11 , 12 , and 13 and the management device 2 , for example.

[0080] The information processing device (computer) 20 employing the above-described hardware configuration implements the functions of the company servers 11, 12, and 13 and the management device 2 by executing the genome data processing method described above as a program.

[0081] Some or all of the above embodiments can be described as, but are not limited to, the following supplementary notes. [Supplementary Note 1] A genome data processing system comprising: a company server responsible for part of a series of processes for personalized medicine on genome data obtained from a user's specimen; and a management device that manages information related to the series of processes to be performed on the genome data, wherein the company server submits a processing request to the management device before executing the process, and the management device notifies the company server of the result of whether the requested process is acceptable or not, based on permission conditions that represent the process authorized by the user. [Supplementary Note 2] The genome data processing system according to Supplementary Note 1, wherein the management device stores the permission conditions in advance and determines whether the requested process is acceptable or not. [Supplementary Note 3] The genome data processing system according to Supplementary Note 1, wherein the user's terminal stores the permission conditions, and the management device determines whether the requested process is acceptable or not by inquiring about the user's terminal. [Supplementary Note 4] The genome data processing system of any one of Supplementary Note 1 to Supplementary Note 3, wherein the company server reports the processing to the management device after executing the processing, and the management device registers and records the reported processing history in a blockchain. [Supplementary Note 5] The genome data processing system of Supplementary Note 4, wherein the management device registers and records the result of whether the processing requested is permitted or not in the blockchain. [Supplementary Note 6] The genome data processing system of Supplementary Note 4 or Supplementary Note 5, wherein the management device stores the permission conditions in advance, and upon receiving an inquiry about the processing history from the user's terminal, compares the processing history with the permission conditions and notifies the user's terminal of the comparison result. [Supplementary Note 7] The genome data processing system of Supplementary Note 4 or Supplementary Note 5, wherein the management device stores the permission conditions in advance, and upon receiving an inquiry about the processing history from the user's terminal, notifies the user's terminal of the processing history, and the user's terminal compares the processing history with the permission conditions.[Supplementary Note 8] A genome data processing method performed using a corporate server that is responsible for part of a series of processes for personalized medicine on genome data obtained from a user's specimen, and a management device that manages information related to the series of processes to be performed on the genome data, wherein the corporate server makes a processing request to the management device before executing the processing, and the management device notifies the corporate server of the result of whether the requested processing is permitted based on permission conditions that indicate the processing permitted by the user. [Supplementary Note 9] The genome data processing method described in Supplementary Note 8, wherein the corporate server reports the processing to the management device after executing the processing, and the management device registers and records the reported processing history in a blockchain. [Supplementary Note 10] A genome data processing program that causes a corporate server that is responsible for part of a series of processes for personalized medicine on genome data obtained from a user's sample and a management device that manages information related to the series of processes to be performed on the genome data to execute genome data processing, the genome data processing program causing the corporate server to submit a processing request to the management device before executing the processing, and causing the management device to notify the corporate server of the result of whether or not the processing requested can be carried out, based on permission conditions that represent the processing authorized by the user.

[0082] The disclosures of the above-cited patent documents and other documents are incorporated herein by reference. Modifications and adjustments of the embodiments and examples are possible within the scope of the entire disclosure of the present invention (including the claims), and further based on the basic technical concepts thereof. Furthermore, various combinations and selections (including partial deletions) of various disclosed elements (including elements of each claim, each element of each embodiment or example, each element of each drawing, etc.) are possible within the scope of the entire disclosure of the present invention. In other words, the present invention naturally embraces various modifications and alterations that would be possible by a person skilled in the art in accordance with the entire disclosure and technical concepts, including the claims. In particular, with regard to the numerical ranges described herein, any numerical value or subrange within the range should be construed as specifically described, even if not otherwise specified. Furthermore, the disclosures of the above-cited documents, when used in part or in whole in combination with the disclosures herein as part of the disclosure of the present invention, in accordance with the spirit of the present invention, are also deemed to be included in the disclosures of this application.

[0083] 10a, 10b, 10c, 10d, 10e Genome data processing system 11, 12, 13 Corporate server 2 Management device 3 Blockchain 4 Genome database 5 User database 6 User terminal 20 Information processing device 21 CPU 22 Main memory device 23 Auxiliary memory device 23 IF unit

Claims

1. A genomic data processing system comprising an enterprise server responsible for part of a series of processes for personalized medicine for genomic data obtained from a user's specimen, and a management device for managing information regarding a series of processes performed on the genomic data, wherein the enterprise server submits a process application to the management device before the execution of the process, and the management device notifies the enterprise server of the result of whether the process application is approved or not based on an approval condition representing a process permitted by the user.

2. The genomic data processing system according to claim 1, wherein the management device holds the approval condition in advance and determines whether the process application is approved or not.

3. The genomic data processing system according to claim 1, wherein the user's terminal holds the approval condition, and the management device makes an inquiry to the user's terminal to determine whether the process application is approved or not.

4. The enterprise server reports the process to the management device after the execution of the process, and the management device registers and records the history of the reported process in a blockchain. The genomic data processing system according to any one of claims 1 to 3.

5. The genomic data processing system according to claim 4, wherein the management device registers and records the result of whether the process application is approved or not in the blockchain.

6. The genomic data processing system according to claim 4 or claim 5, wherein the management device holds the approval condition in advance, and when receiving an inquiry regarding the history of the process from the user's terminal, collates the history of the process with the approval condition and notifies the user's terminal of the result of the collation.

7. The genomic data processing system according to claim 4 or claim 5, wherein the user's terminal holds the approval condition, and when receiving an inquiry regarding the history of the process from the user's terminal, notifies the user's terminal of the history of the process, and the user's terminal collates the history of the process with the approval condition.

8. A genomic data processing method performed using an enterprise server responsible for part of a series of processes for personalized medicine for genomic data obtained from a user's specimen, and a management device that manages information regarding the series of processes performed on the genomic data, wherein the enterprise server makes a process application to the management device before execution of the process, and the management device notifies the enterprise server of the result of whether the process application is approved or not based on approval conditions representing processes permitted by the user.

9. The genomic data processing method according to claim 8, wherein the enterprise server reports the process to the management device after execution of the process, and the management device registers and records the history of the reported process in a blockchain.

10. A genomic data processing program for causing an enterprise server responsible for part of a series of processes for personalized medicine for genomic data obtained from a user's specimen, and a management device that manages information regarding the series of processes performed on the genomic data, to execute genomic data processing, wherein the enterprise server is caused to make a process application to the management device before execution of the process, and the management device is caused to notify the enterprise server of the result of whether the process application is approved or not based on approval conditions representing processes permitted by the user.

Images