Network Bandwidth Architecture for Computing Systems

Abstract

The network bandwidth architecture controls data transfers between the life sciences service provider, the local network data repository, and the remote data repository. The data transfers may include patient data and patient metadata analyzed by a bioinformatics system of the life sciences service provider. In one or more aspects, the technology described herein relates to a method that includes performing, by a bioinformatics system implemented by a computing system, an analysis of a portion of the patient data and one or more portions of the patient metadata, and determining, by the computing system, based on the analysis, one or more characteristics of a subject corresponding to the portion of the patient data and the one or more portions of the patient metadata.

Description

[Technical Field]

[0001] Priority claim This application claims the benefit of priority to U.S. Provisional Patent Application No. 63 / 485,201, filed February 15, 2023, entitled "Network Bandwidth Architecture for Bioinformatics Systems," which is incorporated herein by reference in its entirety.

[0002] Technical Field Embodiments of the present disclosure relate generally to the field of high performance computer architectures, and more particularly to embodiments of high performance computer architectures for controlling network bandwidth in connection with data transfers in various systems, such as media streaming systems, scientific research systems, bioinformatics systems, content creation systems, and the like. [Background technology]

[0003] Transferring large amounts of data and performing calculations using large amounts of data can be performed by high-performance computing systems. For example, bioinformatics can involve the analysis of large amounts of data to analyze the causes of various biological conditions and identify treatments for some biological conditions. Often, bioinformatics can involve the computational analysis of genomics data. Genomics data can include nucleotide sequences of genetic material obtained from individual samples. Genomics data from a single individual can accommodate many megabytes of data storage space, while genomics data from various cohorts of individuals can accommodate hundreds of gigabytes to many terabytes of data storage space. In other examples, high-performance computing systems can be used for forecasting and modeling scenarios related to meteorological and geological data, as well as for running machine learning algorithms and fraud detection. Due to the large amounts of data accessed and analyzed by bioinformatics systems and other systems utilizing high-performance computing, storing and transferring this data can be inefficient in terms of network resources utilized and can result in performance delays. Summary of the Invention [Means for solving the problem]

[0004] In one or more aspects, the techniques described herein include: obtaining, by a computing system of a life sciences service provider including processing circuitry and memory, a first amount of data including patient data and a second amount of data including patient metadata, the patient data including genomic information for a plurality of subjects; storing, by the computing system, the first amount of data by a local network data repository controlled, maintained, or managed by the life sciences service provider; and controlling, by the computing system, an allocation of network resources of a physical communications network to the life sciences service provider from the first amount of network resources to the second amount of network resources. a first bandwidth modification request to modify an allocation of network resources of a physical communication network to the life sciences service provider, wherein a second amount of the network resources is greater than the first amount of the network resources; causing, by a computing system, to transfer at least a portion of the second amount of data to a remote data repository while the second amount of the network resources is allocated to the life sciences service provider; determining, by the computing system, that the transfer of at least a portion of the second amount of data to the remote data repository is completed; and generating, by the computing system, a second bandwidth modification request to modify an allocation of network resources of a physical communication network to the life sciences service provider from the second amount to the first amount.

[0005] In one or more aspects, the techniques described herein relate to a method that includes receiving, by a computing system, a request to retrieve a portion of patient data; determining, by the computing system, one or more portions of patient metadata that correspond to the portion of the patient data; sending, by the computing system, a request to a database management system to access the portion of the patient data stored by a local network data repository and the one or more portions of the patient metadata stored by a remote data repository; and retrieving, by the computing system, the portion of the patient data and the one or more portions of the patient metadata.

[0006] In one or more embodiments, the technology described herein relates to a method that includes performing, by a bioinformatics system implemented by a computing system, an analysis of a portion of the patient data and one or more portions of the patient metadata, and determining, by the computing system based on the analysis, one or more characteristics of the subject that correspond to the portion of the patient data and the one or more portions of the patient metadata.

[0007] In one or more embodiments, the technology described herein relates to methods wherein the one or more characteristics comprise one or more genomic mutations present in nucleic acid derived from a sample obtained from the subject, the nucleic acid corresponding to cell-free deoxyribonucleic acid (DNA) extracted from a bodily fluid sample obtained from the subject.

[0008] In one or more embodiments, the technology described herein relates to methods, wherein one or more characteristics comprise a biological condition present in a subject that, in combination with the biological condition present in the subject, results in the development of resistance to a treatment provided to said subject.

[0009] In one or more embodiments, the technology described herein relates to methods wherein the biological condition corresponds to a form of cancer.

[0010] In one or more embodiments, the technology described herein relates to methods wherein the analysis comprises determining a treatment recommendation to provide to the subject to treat a biological condition present in the subject.

[0011] In one or more embodiments, the technology described herein relates to a method in which a portion of the patient data is transferred to a local network data repository in addition to transferring at least a portion of the patient metadata to a remote data repository.

[0012] In one or more aspects, the techniques described herein relate to a method including determining, by a computing system, an amount of memory storage space to store at least a portion of patient metadata, and determining, by the computing system, the amount of memory storage space to be at least a threshold amount of memory storage space, wherein a first bandwidth modification request is generated based on the amount of memory storage space being at least the threshold amount of memory storage space.

[0013] In one or more embodiments, the technology described herein relates to a method, wherein the second amount of network resources corresponds to a minimum transfer rate of at least a portion of the patient metadata over a physical communication network from a life sciences service provider to a remote data repository.

[0014] In one or more embodiments, the technology described herein relates to a method, wherein the second amount of network resources corresponds to transferring at least a portion of the patient metadata from the life sciences service provider to the remote data repository in less than a threshold amount of time.

[0015] In one or more aspects, the technology described herein relates to a method in which the first bandwidth modification request and the second bandwidth modification request include one or more calls to an application programming interface (API) of a cloud storage service provider.

[0016] In one or more aspects, the technology described herein relates to a system that includes one or more hardware processing units, and that when executed by the one or more hardware processing units, includes: obtaining, by a life sciences service provider, a first amount of data including patient data and a second amount of data including patient metadata, the patient data including genomic information for a plurality of subjects; storing the first amount of data by a local network data repository that is at least one of controlled, maintained, or managed by the life sciences service provider; and allocating network resources of a physical communication network to the life sciences service provider from the first amount of network resources to the second amount of network resources. one or more computer-readable storage media storing computer-executable instructions that cause a system to perform operations including generating a first bandwidth modification request to modify the allocation of network resources of the physical communications network to the life sciences service provider, wherein a second amount of the network resources is greater than the first amount of the network resources; causing at least a portion of the second amount of data to be transferred to a remote data repository while the second amount of network resources is allocated to the life sciences service provider; determining that the transfer of at least a portion of the second amount of data to the remote data repository is completed; and generating a second bandwidth modification request to modify the allocation of network resources of the physical communications network to the life sciences service provider from the second amount to the first amount.

[0017] In one or more aspects, the technology described herein relates to a system in which one or more computer-readable storage media store additional computer-executable instructions that, when executed by one or more hardware processing units, cause the system to perform additional operations including receiving a request to retrieve a portion of patient data; determining one or more portions of patient metadata that correspond to the portion of patient data; sending a request to a database management system to access the portion of patient data stored by a local network data repository and the one or more portions of patient metadata stored by a remote data repository; and retrieving the portion of patient data and the one or more portions of patient metadata.

[0018] In one or more aspects, the technology described herein relates to a system in which one or more computer-readable storage media store additional computer-executable instructions that, when executed by one or more hardware processing units, cause the system to perform additional operations including performing, by a bioinformatics system of a life sciences service provider, an analysis of a portion of the patient data and one or more portions of the patient metadata, and determining, based on the analysis, one or more characteristics of the subject corresponding to the portion of the patient data and the one or more portions of the patient metadata.

[0019] In one or more embodiments, the technology described herein relates to a system in which the one or more characteristics comprise one or more genomic mutations present in nucleic acid derived from a sample obtained from a subject, the nucleic acid corresponding to cell-free deoxyribonucleic acid (DNA) extracted from a bodily fluid sample obtained from the subject.

[0020] In one or more embodiments, the technology described herein relates to a system in which one or more characteristics comprise a biological condition present in the subject that, in conjunction with the biological condition present in the subject, results in the development of resistance to a treatment provided to the subject.

[0021] In one or more embodiments, the technology described herein relates to a system in which the biological state corresponds to a form of cancer.

[0022] In one or more embodiments, the technology described herein relates to a system in which one or more computer-readable storage media store additional computer-executable instructions that, when executed by one or more hardware processing units, cause the system to perform additional operations, including determining, as part of the analysis, a treatment recommendation to provide to the subject to treat a biological condition present in the subject.

[0023] In one or more aspects, the technology described herein relates to a system in which one or more computer-readable storage media store additional computer-executable instructions that, when executed by one or more hardware processing units, cause the system to perform additional operations, including transferring a portion of the patient data to a local network data repository in conjunction with transferring at least a portion of the patient metadata to a remote data repository.

[0024] In one or more aspects, the technology described herein relates to a system in which one or more computer-readable storage media store additional computer-executable instructions that, when executed by one or more hardware processing units, cause the system to perform additional operations including determining an amount of memory storage space for storing at least a portion of the patient metadata and determining that the amount of memory storage space is at least a threshold amount of memory storage space, and wherein the first bandwidth modification request is generated based on the amount of memory storage space being at least the threshold amount of memory storage space.

[0025] In one or more embodiments, the technology described herein relates to a system in which the second amount of network resources corresponds to a minimum transfer rate of at least a portion of the patient metadata over a physical communication network from a life sciences service provider to a remote data repository.

[0026] In one or more embodiments, the technology described herein relates to a system in which the second amount of network resources corresponds to transferring at least a portion of the patient metadata from the life sciences service provider to the remote data repository in less than a threshold amount of time.

[0027] In one or more aspects, the technology described herein relates to a system in which the first bandwidth modification request and the second bandwidth modification request include one or more calls to an application programming interface (API) of a cloud storage service provider.

[0028] In one or more aspects, the techniques described herein, when executed by one or more hardware processing units, include: obtaining, by a life sciences service provider, a first amount of data including patient data and a second amount of data including patient metadata, wherein the patient data includes genomic information for a plurality of subjects; storing the first amount of data by a local network data repository that is at least one of controlled, maintained, or managed by the life sciences service provider; and performing a first process to modify an allocation of network resources of a physical communication network to the life sciences service provider from the first amount of network resources to the second amount of network resources. one or more non-transitory computer-readable storage media storing computer-executable instructions that cause a system to perform operations including generating a bandwidth modification request, wherein a second amount of network resources is greater than the first amount of network resources; causing at least a portion of the second amount of data to be transferred to a remote data repository while the second amount of network resources is allocated to the life sciences service provider; determining that the transfer of at least a portion of the second amount of data to the remote data repository is completed; and generating a second bandwidth modification request to modify an allocation of network resources of a physical communication network to the life sciences service provider from the second amount to the first amount.

[0029] In one or more aspects, the techniques described herein relate to one or more non-transitory computer-readable storage media including additional computer-executable instructions that, when executed by one or more hardware processing units, cause the system to perform additional operations including receiving a request to retrieve a portion of patient data; determining one or more portions of patient metadata that correspond to the portion of patient data; sending a request to a database management system to access the portion of patient data stored by a local network data repository and the one or more portions of patient metadata stored by a remote data repository; and retrieving the portion of patient data and the one or more portions of patient metadata.

[0030] In one or more aspects, the techniques described herein relate to one or more non-transitory computer-readable storage media including additional computer-executable instructions that, when executed by one or more hardware processing units, cause a bioinformatics system of a life sciences service provider to perform additional operations including performing an analysis of the portion of the patient data and one or more portions of the patient metadata, and determining, based on the analysis, one or more characteristics of the subject corresponding to the portion of the patient data and the one or more portions of the patient metadata.

[0031] In one or more embodiments, the technology described herein relates to one or more non-transitory computer-readable storage media, wherein the one or more characteristics comprise one or more genomic mutations present in nucleic acid derived from a sample obtained from the subject, and the nucleic acid corresponds to cell-free deoxyribonucleic acid (DNA) extracted from a bodily fluid sample obtained from the subject.

[0032] In one or more embodiments, the technology described herein relates to one or more non-transitory computer-readable storage media, wherein the one or more characteristics comprise a biological condition present in the subject in conjunction with developing resistance to a treatment provided to the subject.

[0033] In one or more embodiments, the technology described herein relates to one or more non-transitory computer-readable storage media, wherein the biological condition corresponds to a form of cancer.

[0034] In one or more embodiments, the technology described herein relates to one or more non-transitory computer-readable storage media that include additional computer-executable instructions that, when executed by one or more hardware processing units, cause the system to perform additional operations, including determining, as part of the analysis, a treatment recommendation to provide to the subject to treat a biological condition present in the subject.

[0035] In one or more aspects, the techniques described herein relate to one or more non-transitory computer-readable storage media that include additional computer-executable instructions that, when executed by one or more hardware processing units, cause the system to perform additional operations, including transferring a portion of the patient data to a local network data repository in conjunction with transferring at least a portion of the patient metadata to a remote data repository.

[0036] In one or more aspects, the techniques described herein relate to one or more non-transitory computer-readable storage media that include additional computer-executable instructions that, when executed by one or more hardware processing units, cause the system to perform additional operations including determining an amount of memory storage space for storing at least a portion of the patient metadata and determining that the amount of memory storage space is at least a threshold amount of memory storage space, wherein a first bandwidth modification request is generated based on the amount of memory storage space being at least the threshold amount of memory storage space.

[0037] In one or more embodiments, the technology described herein relates to one or more non-transitory computer-readable storage media, wherein the second amount of network resources corresponds to a minimum transfer rate of at least a portion of the patient metadata over a physical communications network from a life sciences service provider to a remote data repository.

[0038] In one or more aspects, the technology described herein relates to one or more non-transitory computer-readable storage media, wherein the second amount of network resources corresponds to transferring at least a portion of the patient metadata from the life sciences service provider to the remote data repository in less than a threshold amount of time.

[0039] In one or more aspects, the technology described herein relates to one or more non-transitory computer-readable storage media, wherein the first bandwidth modification request and the second bandwidth modification request include one or more calls to an application programming interface (API) of a cloud storage service provider.

[0040] In one or more aspects, techniques described herein relate to a method that includes: obtaining, by a high-performance computing system including processing circuitry and memory, a first amount of system data and a second amount of data including metadata; causing, by the high-performance computing system, a local network data repository to store, by the high-performance computing system, the first amount of system data; generating, by the high-performance computing system, a first bandwidth modification request to modify an allocation of network resources of a physical communications network from the first amount of network resources to a second amount of network resources, wherein the second amount of network resources is greater than the first amount of network resources; causing, by the high-performance computing system, to transfer at least a portion of the second amount of data to a remote data repository while the second amount of network resources is allocated; determining, by the high-performance computing system, that the transfer of at least a portion of the second amount of data to the remote data repository has been completed; and generating, by the high-performance computing system, a second bandwidth modification request to modify an allocation of network resources of the physical communications network from the second amount to the first amount.

[0041] In one or more aspects, the techniques described herein relate to a method that includes receiving, by a high-performance computing system, a request to retrieve a portion of system data; determining, by the high-performance computing system, one or more portions of metadata corresponding to the portion of the system data; sending, by the high-performance computing system, a request to a database management system to access the portion of the system data stored by a local network data repository and the one or more portions of metadata stored by a remote data repository; and retrieving, by the high-performance computing system, the portion of the system data and the one or more portions of metadata.

[0042] In one or more aspects, the technology described herein relates to a method that includes performing, by a high performance computing system, an analysis of a portion of the system data and one or more portions of the metadata; and determining, by the high performance computing system, based on the analysis, one or more characteristics of information corresponding to the portion of the system data and the one or more portions of the metadata.

[0043] In one or more aspects, the technology described herein relates to a method in which the system data includes media content, and the high performance computing system and the local network data repository are at least one of controlled, maintained, or managed by at least one of a media content provider, a communications company, or a content streaming service.

[0044] In one or more aspects, the technology described herein relates to a method where the system data includes scientific data and the high performance computing system and the local network data repository are at least one of controlled, maintained, or managed by at least one of a research institution or an academic institution.

[0045] In one or more embodiments, the technology described herein relates to a method, wherein the system data comprises patient data, the metadata comprises patient metadata, and the patient data comprises genomic information for a plurality of subjects.

[0046] In one or more aspects, the technology described herein relates to a method in which the high performance computing system and the local network data repository are at least one of controlled, maintained, or managed by a life sciences service provider.

[0047] In one or more embodiments, the technology described herein relates to methods wherein the one or more characteristics comprise one or more genomic mutations present in nucleic acid derived from a sample obtained from the subject, the nucleic acid corresponding to cell-free deoxyribonucleic acid (DNA) extracted from a bodily fluid sample obtained from the subject.

[0048] In one or more embodiments, the technology described herein relates to methods, wherein one or more characteristics comprise a biological condition present in the subject that, in conjunction with the biological condition present in the subject, results in the development of resistance to a treatment provided to the subject.

[0049] In one or more embodiments, the technology described herein relates to methods wherein the biological condition corresponds to a form of cancer.

[0050] In one or more embodiments, the technology described herein relates to methods wherein the analysis comprises determining a treatment recommendation to provide to the subject to treat a biological condition present in the subject.

[0051] In one or more aspects, the technology described herein relates to a method, wherein the analysis includes determining media content recommendations to be provided to users of at least one of a media content provider, a communications company, or a content streaming service.

[0052] In one or more embodiments, the technology described herein relates to a method in which a portion of the system data is transferred to a local network data repository in addition to transferring at least a portion of the metadata to a remote data repository.

[0053] In one or more aspects, the techniques described herein relate to a method including determining, by a high performance computing system, an amount of memory storage space to store at least a portion of the metadata, and determining, by the high performance computing system, the amount of memory storage space to be at least a threshold amount of memory storage space, wherein a first bandwidth modification request is generated based on the amount of memory storage space being at least the threshold amount of memory storage space.

[0054] In one or more aspects, the technology described herein relates to a method, wherein the second amount of network resources corresponds to a minimum transfer rate of at least a portion of the metadata over a physical communication network to a remote data repository.

[0055] In one or more aspects, the technology described herein relates to a method, wherein the second amount of network resources corresponds to transferring at least a portion of the metadata to a remote data repository in less than a threshold amount of time.

[0056] In one or more aspects, the technology described herein relates to a method in which the first bandwidth modification request and the second bandwidth modification request include one or more calls to an application programming interface (API) of a cloud storage service provider. [Brief explanation of the drawings]

[0057] [Figure 1] 1 illustrates an example architecture for transferring patient data and patient metadata between one or more data repositories and computing systems that analyze the patient data and patient metadata, according to one or more embodiments.

[0058] [Figure 2] 1 illustrates an example framework for increasing network resource allocation during transfer of patient data and patient metadata from local and remote data repositories, according to one or more embodiments.

[0059] [Figure 3] FIG. 1 is a flow diagram of an example process for increasing network resource allocation during transfer of system data and metadata from local and remote data repositories according to one or more embodiments.

[0060] [Figure 4] FIG. 1 is a block diagram illustrating components of a machine in the form of a computer system that can read and execute instructions from one or more machine-readable media to perform any one or more of the methodologies described herein, in accordance with one or more exemplary implementations.

[0061] [Figure 5] FIG. 1 is a block diagram illustrating a representative software architecture that may be used in conjunction with one or more hardware architectures described herein, in accordance with one or more exemplary implementations. DETAILED DESCRIPTION OF THE INVENTION

[0062] The following description and drawings sufficiently illustrate specific embodiments to enable those skilled in the art to practice them. Other embodiments may incorporate structural, logical, electrical, process, and other changes. Portions and features of some embodiments may be included in, or substituted for, portions and features of other embodiments. Embodiments set forth in the claims encompass all available equivalents of those claims.

[0063] FIG. 1 illustrates an example architecture 100 for transferring data and metadata between one or more data repositories and computing systems that analyze data and patients, according to one or more embodiments. The architecture 100 can include a life sciences service provider 102 and can be used to provide high-performance computing services to the life sciences service provider 102. The high-performance computing system can include a cluster of processors that can perform calculations in a massively parallel manner. In at least some examples, the high-performance computing system can calculate and transfer hundreds, thousands, or even millions of times more data than a typical desktop, laptop, or server system. The high-performance computing system can perform calculations using thousands, up to tens of thousands, or even millions of processors, and can perform up to quintillion floating-point operations per second.

[0064] The life sciences service provider 102 may include an entity that provides goods or services to individuals. The life sciences service provider 102 may include at least one of an educational institution, a non-profit organization, a private company, or a public company. In one or more examples, the life sciences service provider 102 may include an entity that develops treatments for one or more biological conditions. For example, the life sciences service provider 102 may include a pharmaceutical company that develops and / or manufactures pharmaceutical substances for treating one or more biological conditions. Furthermore, the life sciences service provider 102 may include a diagnostic organization that develops tests to detect the presence of one or more biological conditions in a subject. The life sciences service provider 102 may also include a medical equipment entity that develops and / or manufactures medical equipment to treat and / or detect one or more biological conditions. Furthermore, the life sciences service provider 102 may include an organization that develops or manufactures instruments, devices, supplies, or combinations thereof used in the detection and / or treatment of one or more biological conditions. In yet other examples, the life sciences service provider 102 may include a medical service provider that offers at least one of testing, medical services, or treatments for one or more biological conditions. In various examples, the life sciences service provider 102 may include one or more healthcare providers.

[0065] As used herein, a healthcare provider may refer to an entity, individual, or group of individuals involved in providing care to an individual regarding at least one of the treatment or prevention of one or more biological conditions. Furthermore, as used herein, a biological condition may refer to an abnormality in an individual's function and / or structure to the extent that it produces or is likely to produce detectable characteristics of abnormality. A biological condition may be characterized by external and / or internal characteristics, signs, and / or symptoms that represent a deviation from biological norms in one or more populations. A biological condition may include at least one of one or more diseases, illnesses, injuries, syndromes, disorders, infections, isolated symptoms, or other atypical variations in an individual's biological structure and / or function. Furthermore, a treatment, as used herein, may refer to a substance, procedure, routine, device, and / or other intervention that may be administered or performed with the intent of alleviating one or more effects of a biological condition in an individual. In one or more examples, a treatment may include a substance that is metabolized by an individual. A substance may include a composition of matter, such as a pharmaceutical composition. The substance may be delivered to the individual in several ways, such as ingestion, injection, absorption, or inhalation. Treatment may also involve physical intervention, such as one or more surgeries.

[0066] In at least some examples, the life sciences service provider 102 may store, access, and / or analyze data corresponding to a plurality of subjects 104. In one or more examples, a sample 106 may be extracted from the subject 104. The sample 106 may be derived from at least one of a bodily fluid or tissue obtained from the subject 104. The sample 106 may be subjected to at least one of one or more diagnostic tests or one or more analytical tests in operation 108. In various examples, the one or more diagnostic tests and / or one or more analytical tests performed in operation 108 may be performed to detect one or more biological conditions that may be present in the subject 104. In one or more illustrative examples, the one or more diagnostic tests or one or more analytical tests performed in operation 108 may include one or more assays related to the detection of one or more forms of cancer.

[0067] The one or more diagnostic tests and / or one or more analytical tests performed in act 108 may generate patient data 110. The patient data 110 may include data derived from the one or more diagnostic tests and / or analytical tests performed in act 108. For example, the patient data 110 may include genomic information, genetic information, metabolomic information, transcriptomic information, fragmentiomic information, immune receptor information, methylation information, epigenomic information, and / or proteomic information, immunohistochemistry (IHC), and immunofluorescence (IF).

[0068] As used herein, "fragmentomic information" may include, among other things, information related to analyzing the length of DNA or RNA fragments to determine the presence or absence of a tumor and to characterize the tumor. In at least some examples, fragmentomic information may correspond to nucleosome structure and transcription factor binding sites. In one or more illustrative examples, fragmentomic information may include fragment endpoint density, plasma DNA size, endpoint, nucleosome footprint, DNA fragments aligning with base positions in the genome, the number of DNA fragments starting or ending at specific base positions in the genome, fragment starts and lengths associated with specific conditions, heterogeneous patterns of cfDNA location in cancer, nucleosome occupancy, nucleosome dynamics, chromatin organization, structure and function, chromatin state, consequences of genomic abnormalities, and / or epigenetic changes in DNA associated with health and disease.

[0069] Furthermore, the "genomic information" can correspond to a nucleic acid sequence derived from the sample 106. The genomic information can represent one or more mutations corresponding to a gene of the subject 104. The mutations to the gene of the subject 104 can correspond to differences between the sequence of the nucleic acid of the subject 104 and one or more reference genomes. The reference genome may include a known reference genome, such as hg19. In various examples, the mutations to the gene of the subject 104 can correspond to differences in the germline gene of the subject 104 relative to the reference genome. In one or more further examples, the reference genome may include the germline genome of the subject 104. In one or more further examples, the mutations to the gene of the subject 104 can include somatic mutations. The mutations to the gene of the subject 104 can be associated with insertions, deletions, single nucleotide variants, loss of heterozygosity, duplications, amplifications, translocations, fusion genes, or one or more combinations thereof. In at least some examples, the genomic information can correspond to non-coding regions of the genome. The non-coding regions can be associated with the regulation of one or more genes. In one or more examples, analysis of the non-coding regions can detect one or more epigenetic signatures of one or more patients.

[0070] In one or more illustrative examples, the genomic information included in the patient data 110 may include a genomic profile of tumor cells present in one or more subjects 104. In these situations, the genomic information may be derived from an analysis of genetic material, such as deoxyribonucleic acid (DNA) and / or ribonucleic acid (RNA), found in a blood sample of one or more subjects 104 that is present due to the degradation of tumor cells present in the one or more subjects 104. In one or more examples, the genomic information of the tumor cells of one or more subjects 104 may correspond to one or more target regions. One or more mutations present with respect to the one or more target regions may be indicative of the presence of tumor cells in the one or more subjects 104.

[0071] In one or more illustrative examples, the genetic material analyzed to generate genomic information may be derived from one or more samples 106, including, but not limited to, tissue samples or tumor biopsies, circulating tumor cells (CTCs), exosomes or efferosomes, or circulating nucleic acids. In various examples, circulating nucleic acids may be referred to herein as "cell-free DNA." "Cell-free DNA," "cfDNA molecules," or simply "cfDNA" includes DNA molecules that occur in a subject 104 in an extracellular form (e.g., in blood, serum, plasma, or other bodily fluids such as lymph, cerebrospinal fluid, urine, or sputum) and include DNA that is not contained within or otherwise associated with cells at the time of isolation from the subject 104. The DNA was originally present in one or more cells of a large, complex organism (e.g., a mammal) or other cells, such as bacteria, that colonize the organism, but the DNA has been released from the cells into fluids found in the organism. cfDNA includes, but is not limited to, cell-free genomic DNA of a subject 104 (e.g., genomic DNA of a human subject) and cell-free DNA of microorganisms, e.g., bacteria, that inhabit the subject 104 (regardless of whether the pathogenic bacteria or bacteria are normally found in commonly colonized locations, such as the intestine or skin of a healthy subject), but does not include cell-free DNA of microorganisms that merely contaminate a sample of bodily fluid. Typically, cfDNA can be obtained by obtaining a volume of fluid without the need for an in vitro cell lysis step, which also includes the removal of cells present in the fluid (e.g., centrifugation of blood to remove cells).

[0072] The patient metadata 112 may also be generated based on at least one of the one or more diagnostic tests or one or more analytical tests performed in operation 108. The patient metadata 112 may correspond to the patient data 110 of an individual subject 104. For example, for an individual subject 104, the patient metadata 112 may be generated in conjunction with generating the patient data 110 by one or more diagnostic tests and / or one or more analytical tests in operation 108. The patient metadata 112 may be generated by one or more machines, one or more instruments, one or more medical devices, one or more computing devices, or one or more combinations thereof in association with generating the patient data 110 in operation 108. In one or more examples, the patient metadata 112 may represent information about the one or more machines, one or more instruments, one or more medical data, one or more computing devices, or one or more combinations thereof used to generate the patient data 110, such as a model number, a serial number, a software version number, the technology used to generate the patient data 110, the settings used to generate the patient data 110, the date and / or time the patient data 110 was generated, or one or more combinations thereof.

[0073] Additionally, the patient metadata 112 may include information about the subject 104. In one or more illustrative examples, the patient metadata 112 may include an identifier for the subject 104, physical characteristics of the subject 104 (e.g., weight, height), the age of the subject 104, personal information about the subject 104, the ethnic background of the subject 104, one or more combinations thereof, etc. Additionally, the patient metadata 112 may include medical records corresponding to the patient data 110. By way of example, the medical record for the subject 104 may accompany and / or be generated in conjunction with the patient data 110. The medical record may include imaging information, laboratory test results, diagnostic test information, clinical findings, dental health information, healthcare provider notes, medical history forms, diagnosis request forms, medical procedure order forms, medical information charts, one or more combinations thereof, etc. The medical record may also represent lifestyle information such as smoking status, alcohol intake, sleep habits, one or more combinations thereof, etc.

[0074] The life sciences service provider 102 may include a bioinformatics system 114 that analyzes at least one of the patient data 110 or the patient metadata 112. The bioinformatics system 114 may implement one or more statistical techniques for analyzing at least one of the patient data 110 or the patient metadata 112. In one or more additional examples, the bioinformatics system 114 may implement one or more machine learning techniques for analyzing at least one of the patient data 110 or the patient metadata 112. In various examples, the bioinformatics system 114 may analyze at least one of the patient data 110 or the patient metadata 112 to determine characteristics of the subject 104 in which a biological condition exists. For example, the bioinformatics system 114 may analyze at least one of the patient data 110 or the patient metadata 112 to determine one or more genomic features of at least a portion of the subject 104 in which at least one form of cancer exists. For example, the bioinformatics system 114 may analyze at least one of the patient data 110 or the patient metadata 112 to determine one or more mutations present in the samples 106 provided by at least some of the subjects 104. In one or more further examples, the bioinformatics system 114 may analyze at least one of the patient data 110 or the patient metadata 112 to identify one or more cohorts corresponding to groups of the subjects 104. In yet another example, the bioinformatics system 114 may analyze at least one of the patient data 110 or the patient metadata 112 to determine the effectiveness of one or more treatments provided to at least some of the subjects 104 with respect to one or more biological conditions present in the group of subjects 104. Furthermore, the bioinformatics system 114 may analyze at least one of the patient data 110 or the patient metadata 112 to determine treatment recommendations for at least some of the subjects 104 associated with one or more biological conditions present in the group of subjects 104.Additionally, the bioinformatics system 114 may analyze at least one of the patient data 110 or the patient metadata 112 to determine the progression of a biological condition present in at least a portion of the subject 104. In at least some examples, the bioinformatics system 114 may analyze at least one of the patient data 110 or the patient metadata 112 to determine a biological condition present in at least a portion of the subject 104. In one or more example scenarios, the bioinformatics system 114 may analyze at least one of the patient data 110 or the patient metadata 112 to determine a diagnosis for at least a portion of the subject 104.

[0075] The life sciences service provider 102 may include one or more computing devices 116 that can access the bioinformatics system 114. The one or more computing devices 116 may include at least one of one or more desktop computing devices, one or more laptop computing devices, one or more tablet computing devices, one or more mobile computing devices, one or more smartphones, one or more wearable computing devices, or one or more combinations thereof. The life sciences service provider 102 may also include and / or be coupled to a local network data repository 118. In one or more examples, the local network data repository 118 may include one or more data stores located at at least one site of the life sciences service provider 102. In various examples, the local network data repository 118 may be coupled to at least one of the one or more computing devices 116 or the bioinformatics system 114 via one or more physical network connections maintained, controlled, or managed by the life sciences service provider 102. The local network data repository 118 may store at least a portion of the patient data 110 or at least a portion of the patient metadata 112 .

[0076] Additionally, the life sciences service provider 102 may communicate with a remote data repository 120. The remote data repository 120 may be located remotely with respect to one or more locations of the life sciences service provider 102 and may be controlled, maintained, or managed by an entity different from the life sciences service provider 102. In one or more examples, the remote data repository 120 may be controlled, maintained, or managed by a third-party cloud computing service provider. In various examples, the remote data repository 120 may store at least one of a portion of the patient data 110 or at least a portion of the patient metadata 112. The life sciences service provider 102 may communicate with the remote data repository 120 via a physical communication network 122. The physical communication network 122 may include a communication network infrastructure that is controlled, maintained, or managed by an entity other than the life sciences service provider 102. For example, the physical communication network 122 may include physical network equipment that is controlled, maintained, or managed by a network management system 124 of a network service provider. Network management system 124 may control network resources utilized by several different entities that utilize physical communication network 122 for the transfer and / or access of data. For example, network management system 124 may allocate bandwidth of physical communication network 122 for entities that use physical communication network 122 for the transfer and / or access of data, where bandwidth corresponds to the amount of network resources allocated to one or more entities. Network management system 124 may also implement one or more techniques and / or protocols to facilitate the efficient transfer of data between endpoints of physical communication network 122.

[0077] In one or more examples, a virtual communication network 126 may couple the life sciences service provider 102 with the remote data repository 120. The virtual communication network 126 may correspond to a portion of the physical communication network 122 that is allocated to the life sciences service provider 102 at a given time. Illustratively, different portions of the network resources of the physical communication network 122 may be allocated to several different entities at a given time. In at least some examples, the amount of network resources of the physical communication network 122 dedicated to the virtual communication network between the remote data repository 120 and the life sciences service provider 102 may change over time. In one or more illustrative examples, the bandwidth of the virtual communication network 126 may be modified depending on the amount of data to be transferred between the remote data repository 120 and the life sciences service provider 102.

[0078] The architecture 100 may also include a database management system 128. The database management system 128 may be coupled to the remote data repository 120 and the local network data repository 118. In one or more examples, the computing device 116 may use the database management system 128 to access data stored by the local network data repository 118 and the remote data repository 120. In various examples, the database management system 128 may facilitate access of at least one of files or objects stored by the local network data repository 118 and the remote data repository 120 in response to requests generated by at least one of the computing device 116 or the bioinformatics system 114.

[0079] The life sciences service provider 102 may utilize memory resources of one or more cloud memory storage providers to store at least one of a portion of the patient data 110 or at least a portion of the patient metadata 112 in the remote data repository 120. In one or more examples, the life sciences service provider 102 may acquire and / or generate an amount of data that may exceed the capacity of the local network data repository 118. In these scenarios, the excess data may be stored by the remote data repository 120. Additionally, at least one of at least a portion of the patient data 110 or at least a portion of the patient metadata 112 may be stored by the remote data repository 120 for other reasons, such as storing medical record information to comply with one or more regulatory frameworks. In one or more additional examples, at least one of at least a portion of the patient data 110 or at least a portion of the patient metadata 112 may be stored by the remote data repository 120 to minimize costs and / or increase efficiency with respect to storing and retrieving information by the life sciences service provider 102.

[0080] In at least some examples, memory resources for storing patient data 110 may be greater than memory resources for storing patient metadata 111. In various examples, memory resources for storing patient data 110 may be 2 times, 5 times, 10 times, 20 times, 50 times, up to 100 times, up to 1000 times, up to 10,000 times, up to 100,000 times, or more than memory resources for storing patient metadata 112. In one or more illustrative examples, patient data 110 may include DNA sequences and expression values ​​for several genomic regions for an individual patient, such as tens of genomic regions, hundreds of genomic regions, or thousands of genomic regions, and may consume up to hundreds of gigabytes of memory resources. In one or more additional illustrative examples, the patient metadata 112 for an individual patient may include sample identifiers, batch information, and patient characteristics that may be stored in a text file consuming memory resources on the order of hundreds of kilobytes, although in at least some examples, the amount of memory resources used to store the patient metadata 112 for an individual patient may be much larger, such as on the order of tens of megabytes to hundreds of megabytes or more.

[0081] In one or more examples, the local network data repository 118 may store the patient data 110, and the remote data repository 120 may store the patient metadata 112. In one or more additional examples, the remote data repository 120 may store at least a portion of the patient data 110, and the local network data repository 118 may store at least a portion of the patient metadata 112. In one or more illustrative examples, the local network data repository 118 may include a cache memory that stores at least a portion of the patient data 110 and / or a portion of the patient metadata 112 while analysis of at least one of the patient data 110 or the patient metadata 112 is performed by the bioinformatics system 114.

[0082] In various examples, the computing device 116 may be used to generate a request for at least one of transferring or accessing at least a portion of the patient data 110 and at least a portion of the patient metadata 112. The request for at least one of transferring or accessing at least a portion of the patient data 110 and at least a portion of the patient metadata 112 may be generated for analyzing at least a portion of the patient data 110 and / or at least a portion of the patient metadata 112 using the bioinformatics system 114. In one or more illustrative examples, the request may be generated according to one or more application programming interface (API) calls of the database management system 128 for transferring or accessing at least a portion of the patient data 110 and at least a portion of the patient metadata 112. In response to determining that the request is for at least one of transferring or accessing data stored by the local network data repository 118 and the remote data repository 120 that exceeds a threshold amount of memory resources, the life sciences service provider 102 may send a request to the network management system 124 to temporarily increase the amount of network resources of the physical communication network 122 allocated by the network management system 124 for the life sciences service provider 102. In these circumstances, the request sent to the network management system 124 may include one or more API calls to the network management system 124 to increase the virtual communication network 126 to increase the rate at which data is transferred to and / or from the remote data repository 120. In one or more examples, the amount of network resources of the physical communication network 122 allocated to the life sciences service provider 102 by the network management system 124, such as the virtual communication network 126, may be increased to transfer and / or access at least one of the patient data 110 or the patient metadata 112 at a rate of at least the threshold rate.Then, after the requested data has been transferred to and / or from the remote data repository 120 to the life sciences service provider 102, the network resources allocated to the life sciences service provider 102 may be reduced. In this manner, the network resources of the network management system 124 are allocated efficiently. That is, because a temporary increase in the amount of network resources used to transfer at least a portion of the patient metadata 112, and possibly at least a portion of the patient data 110, between the remote data repository 120 and the life sciences service provider 102 occurs, the architecture 100 avoids allocating network resources that are not utilized by the life sciences service provider 102; the unused network resources may be allocated to other entities that transfer data using the physical communication network 122 of the network management system 124.

[0083] In one or more examples, at least a portion of the patient metadata 112, and possibly at least a portion of the patient data 110, may be transferred to the remote data repository 120 for storage. In one or more additional examples, at least a portion of the patient metadata 112, and possibly at least a portion of the patient data 110, may be transferred from the remote data repository 120 to the life sciences service provider 102. In these cases, the data transferred from the remote data repository 120 to the life sciences service provider 102 may be analyzed by the bioinformatics system 114. In one or more further examples, the transfer of at least one of the patient data 110 or the patient metadata 112 from the life sciences service provider 102 to the remote data repository 120 may occur in association with an increase in network resources allocated to the virtual communication network 126, while the access of one or more portions of at least one of the patient data 110 or the patient metadata 112 stored by the remote data repository 120 to be analyzed by the bioinformatics system 114 may be transferred without an increase in network resources allocated to the virtual communication network 126 in scenarios where the amount of data transferred for storage in the remote data repository 120 is greater than the amount of data accessed for analysis. That is, the amount of data accessed for analysis by the bioinformatics system 114 may be a subset of the data transferred to the remote data repository 120 for storage.

[0084] 2 illustrates an example framework 200 for increasing network resource allocation during transfer of data and metadata from local and remote data repositories, according to one or more embodiments. The framework 200 may include a life sciences service provider 102, a computing device 116, a local network data repository 118, a remote data repository 120, a physical communication network 122, a network management system 124, and a database management system 128 as described with respect to FIG. 1. In the illustrative example of FIG. 2, the life sciences service provider 102 includes a data access and control system 202 that monitors requests to transfer data between the life sciences service provider 102 and at least one of the local network data repository 118 or the remote data repository 120. In one or more examples, the data access and control system 202 may analyze requests to transfer data between the life sciences service provider 102 and at least one of the local network data repository 118 or the remote data repository 120 for a threshold amount of data. In at least some examples, the threshold amount of data may correspond to an amount of data that increases the time to transfer the data and / or the speed at which the data is transferred to a level that is deemed by the life sciences service provider 102 to be too slow to facilitate efficient computational operations by the life sciences service provider 102.

[0085] In various examples, the computing device 116 may generate a local data transfer request 204 for at least one of access data stored by the local network data repository 118 or transfer data to be stored by the local network data repository 118. The computing device 116 may also generate a remote data transfer request 206 for at least one of access data stored by the remote data repository 120 or transfer data to be stored by the remote data repository 120. In one or more examples, the local data transfer request 204 and the remote data transfer request 206 may correspond to at least one of accessing or storing at least one of the patient data 110 or the patient metadata 112.

[0086] The local data transfer requests 204 and the remote data transfer requests 206 may be monitored by the data access and control system 202. The data access and control system 202 may analyze the local data transfer requests 204 and the remote data transfer requests 206 for a threshold amount of data transfer. In situations where the amount of data to be transferred is at least the threshold amount of data, the data access and control system 202 may generate one or more bandwidth modification requests 208. The one or more bandwidth modification requests 208 may represent a request representing an amount of network resources of the physical communication network 122 to be allocated to the life sciences service provider 102. Furthermore, the one or more bandwidth modification requests 208 may represent a time for the network management system 124 to increase the allocation of the network resources of the physical communication network 122 to the life sciences service provider 102. In this manner, the virtual communication network dedicated to the life sciences service provider 102 may be increased. In one or more illustrative examples, the one or more bandwidth modification requests 208 may include one or more calls to an application programming interface (API) 210. The API 210 may be provided by the network management system 124 and may include at least one of one or more scripts, one or more formats, one or more commands, or one or more combinations thereof to modify the amount of network resources of the physical communication network 122 to be allocated to the life sciences service provider 102.

[0087] In response to one or more bandwidth modification requests 208, the network management system 124 may increase the amount of network resources of the physical communication network 122 allocated to the virtual communication network dedicated to the life sciences service provider 102. In this manner, the transfer of data associated with the local data transfer request 204 and / or remote data transfer request 206 that triggered the bandwidth modification request 208 may occur at a faster rate and / or in a shorter time than if the bandwidth modification request 208 had not been generated by the data access and control system 202.

[0088] The data access and control system 202 may send a data transfer request 214 to the database management system 128 in association with at least one of the local data transfer request 204 or the remote data transfer request 206 that triggered the bandwidth modification request 208. The one or more data transfer requests 214 may correspond to additional APIs provided by the database management system 128. In one or more examples, the data access and control system 202 may send the data transfer request 214 to the database management system 128 in response to sending the bandwidth modification request 208 to the network management system 124. In one or more additional examples, the data access and control system 202 may send the data transfer request 214 to the database management system 128 in response to receiving confirmation from the network management system 124 that an increase in the allocation of network resources of the physical communication network 122 to the life sciences service provider 102 has occurred.

[0089] In response to the one or more data transfer requests 214, the database management system 128 may cause the transfer of patient data 110 between at least one of the local network data repository 118 or the remote data repository to the life sciences service provider 102. Further, in response to the one or more data transfer requests 214, the database management system 128 may cause the transfer of patient metadata 112 between at least one of the local network data repository 118 or the remote data repository 120 and the life sciences service provider 102. In situations where data is being transferred from the life sciences service provider 102 and at least one of the local network data repository 118 or the remote data repository 120, the one or more data transfer requests 214 may represent a storage location of the data. In one or more illustrative examples, the storage location may represent the local network data repository 118 and / or the remote data repository 120, or one or more particular portions of the local network data repository 118 and / or the remote data repository 120 that store the data being transferred. In a scenario where data is being retrieved by the life sciences service provider 102 from at least one of a local network data repository 118 or a remote data repository 120, the one or more data transfer requests 214 may represent one or more identifiers of storage locations in the local network data repository 118 and / or the remote data repository 120 for the data being accessed by the life sciences service provider 102.

[0090] In one or more illustrative examples, the life sciences service provider 102 may obtain a certain amount of patient data 110 and a certain amount of patient metadata 112. In various examples, a greater amount of memory resources may be allocated to storing the patient data 110 than the patient metadata 112. In one or more additional examples, the patient metadata 112 may be accessed less frequently by the life sciences service provider 102 than the patient data 110. In one or more examples, at least a portion of the patient data 110 may be stored by a local network data repository 118, and the patient metadata 112 may be stored by a remote data repository 120. In at least some examples, at least a portion of the patient data 110 may be stored by the remote data repository 120.

[0091] Continuing with the above example, the computing device 116 may generate a local data transfer request 204 to store at least a portion of the patient data 110 in a local network data repository 118 and a remote data transfer request 206 to store the patient metadata 112 in a remote data repository 120. The data access and control system 202 may analyze the remote data transfer request 206 and determine that an amount of memory resources associated with storing at least a portion of the patient data 110 and / or the patient metadata 112 is at least a threshold amount of memory resources. In response, the data access and control system 202 may generate a bandwidth modification request 208 and send the bandwidth modification request to the network management system 124. The bandwidth modification request 208 may represent an amount of additional network resources of the physical communication network 122 to allocate to the life sciences service provider 102, and, in at least some examples, an amount of time the additional network resources should remain allocated to the life sciences service provider 102. In one or more examples, pursuant to one or more calls to the API 210, the network management system 124 may be provided with an amount of additional resources to be allocated to the life sciences service provider 102 and a time period during which the additional resources may be allocated. In various examples, the amount of additional network resources to be allocated to the life sciences service provider 102 may correspond to a transfer rate of the patient metadata 112 from the life sciences service provider 102 to the remote data repository 120 and / or an amount of storage space, such as megabytes, gigabytes, or terabytes of data, corresponding to the transfer of the patient metadata 112 from the life sciences service provider 102 to the remote data repository 120. The data transfer rate may correspond to kilobytes per second, megabits per second, megabytes per second, or terabits per second.

[0092] In response to the bandwidth modification request 208, the network management system 124 may cause additional network resources of the physical communication network 122 to be allocated to the life sciences service provider 102. The data access and control system 202 may send a data transfer request 214 to the database management system 128 to cause the transfer of at least a portion of the patient data 110 and / or patient metadata 112 from the life sciences service provider 102 for storage by the remote data repository 120 using a portion of the physical communication network 122 dedicated to the life sciences service provider 102.

[0093] In at least some examples, the initial bandwidth modification request 208 may not represent a time when additional network resources of the physical communication network are allocated to the life sciences service provider 102. In these scenarios, the data access and control system 202 may determine when to transfer the patient metadata 112 from the life sciences service provider 102 to the remote data repository 120. In one or more examples, the data access and control system 202 may receive an indication from the database management system 128 that the transfer of the patient metadata 112 to the remote data repository 120 is complete. In response to determining that the transfer of the patient metadata 112 to the remote data repository 120 is complete, the data access and control system 202 may generate an additional bandwidth modification request 208. The additional bandwidth modification request 208 may represent a request to reduce the amount of network resources of the physical communication network 122 allocated to the life sciences service provider 102. In one or more illustrative examples, the additional bandwidth modification request 208 may represent a return to the amount of network resources of the physical communication network 122 allocated to the life sciences service provider 102 prior to the initial bandwidth modification request 208. In this manner, the initial bandwidth modification request 208 may be directed to augmenting the network resources of the physical communication network 122 allocated to the life sciences service provider 102 for transferring at least a portion of the patient data 110 and / or patient metadata 112 to the remote data repository 120, which culminates with the additional bandwidth modification request 208 being sent by the life sciences service provider 102 to the network management system 124 after the transfer of the patient metadata 112 is complete.

[0094] FIG. 3 is a flow diagram of an example process 300 for increasing network resource allocation during transfer of system data and metadata from local and remote data repositories, according to one or more embodiments. At operation 302, process 300 may include obtaining a first amount of system data and a second amount of data including metadata. The system data may be generated and / or obtained by an entity utilizing the network resources to at least one of transfer information and store information in at least one of a local data repository and a remote data repository. In one or more examples, the entity may include a service provider, an academic institution, a non-profit organization, a research organization, a commercial enterprise, or one or more combinations thereof. In one or more illustrative examples, the system data may be generated by several sensors and may include weather data, molecular data, transportation-related data such as data generated by autonomous vehicle sensors, geological data, etc. The system data may also include media content, communications data, financial data, etc. The metadata may include timing information associated with the data, source information associated with the data, identification information, prioritization information, destination information, parameters used in generating the data, etc.

[0095] In one or more additional illustrative examples, the system data and metadata can relate to patients undergoing at least one of testing and treatment for one or more biological conditions. The patient data can include genomic information for multiple subjects. In one or more examples, the genomic information can be derived from one or more samples obtained from the multiple subjects. In one or more illustrative examples, the genomic information can be derived from cell-free nucleic acid obtained from one or more bodily fluid samples from the multiple subjects. The patient metadata can include information related to the patient data, such as information about the patient from whom the patient data is derived, information about an apparatus used to generate at least a portion of the patient data from the sample, information about the sample, or one or more combinations thereof.

[0096] Process 300 may also include storing the first amount of system data by a local data repository at operation 304. The local data repository may be controlled, maintained, or managed by an entity utilizing the network resources to at least one of transfer information and store information in the high-performance computing system. In at least some examples, the local data repository may store at least a portion of the system data. In one or more additional examples, the local data repository may store at least a portion of the metadata.

[0097] Further, at operation 306, process 300 may include generating a first bandwidth modification request to modify an allocation of network resources of the physical communication network from a first amount of network resources to a second amount of network resources. The second amount of network resources may be greater than the first amount of network resources. In one or more examples, an amount of memory storage space in the remote data repository to be occupied by the portion of the metadata and / or the portion of the system data may be determined and analyzed with respect to a threshold amount of memory storage space. In at least some examples, the first bandwidth modification request may be generated based on the amount of memory storage space to be occupied by at least one of the portion of the system data or the portion of the metadata being at least the threshold amount of memory storage space. In one or more illustrative examples, the first bandwidth modification request and the second bandwidth modification request may include one or more calls to an application programming interface (API) of a cloud storage service provider that controls, maintains, or manages at least one of the remote data repository. In one or more examples, the second amount of network resources may correspond to a minimum transfer rate of metadata over the physical communication network from the service provider to the remote data repository. In one or more additional examples, the second amount of network resources may correspond to transferring at least one of a portion of the system data or a portion of the metadata from the service provider to the remote data repository in less than a threshold amount of time.

[0098] Further, process 300 may include, at operation 308, causing a second amount of data to be transferred to the remote data repository while a second amount of network resources is allocated to the entity or network resource user. For example, at least one of at least a portion of the system data or a portion of the metadata is transferred from the entity to the remote data repository during a period in which the amount of network resources allocated to the life sciences service provider is increasing from the first amount of resources to the second amount of network resources. In at least some examples, a portion of the system data may be transferred to the remote data repository and a portion of the system data may be transferred to the local data repository.

[0099] At 310, the process may include determining that the transfer of the second amount of data to the remote data repository is complete. In one or more illustrative examples, after the second amount of data corresponding to at least one of the portion of the system data or the portion of the metadata is stored by the remote data repository, a request may be generated to retrieve the specified portion of the system data and the portion of the metadata corresponding to the specified portion of the system data. In these scenarios, a request may be sent to the database management system to access the portion of the system data stored by the local network data repository and / or the remote data repository and the portion of the metadata stored by the remote data repository. The portion of the system data and the portion of the metadata may then be retrieved by the entity. In situations where the entity is a life sciences service provider and / or a research entity, at least one of the system data or the metadata can subsequently be analyzed.

[0100] In at least some examples where the system data includes patient data, an analysis of the portion of the patient data and the portion of the patient metadata may be performed. The analysis may determine one or more characteristics of the subject from which the portion of the patient data and the portion of the patient metadata are derived. In one or more examples, the one or more characteristics include one or more genomic mutations present in nucleic acid from a sample obtained from the subject. The nucleic acid may correspond to cell-free DNA extracted from a bodily fluid sample obtained from the subject. In one or more additional examples, the one or more characteristics include a biological condition present in the subject in conjunction with developing resistance to a treatment provided to the subject. In various examples, the biological condition corresponds to a form of cancer. In one or more further examples, the analysis may include determining a treatment recommendation to provide to the subject to treat the biological condition present in the subject.

[0101] In one or more further examples, the system data includes user data regarding users of at least one of the media content provider, the telecommunications company, or the content streaming service. In these scenarios, the user characteristics can be determined by analysis, which can include determining media content recommendations to be provided to the users of the at least one of the media content provider, the telecommunications company, or the content streaming service.

[0102] Additionally, process 300 may include generating a second bandwidth modification request to modify an allocation of network resources of the physical communications network to the entity or network resource user from the second amount to the first amount at operation 312. In this manner, the amount of network resources allocated to the entity may revert to a previous allocation of network resources prior to transferring the metadata to the remote data repository.

[0103] 4 is a block diagram illustrating components of a machine 400 in the form of a computer system that may read and execute instructions from one or more machine-readable media to perform any one or more of the methodologies described herein, according to one or more exemplary embodiments. Specifically, FIG. 4 shows a schematic diagram of the machine 400 in the example form of a computer system within which instructions 402 (e.g., software, programs, applications, applets, apps, or other executable code) may be executed to cause the machine 400 to perform any one or more of the methodologies described herein. Thus, the instructions 402 may be used to implement modules or components described herein. The instructions 402 transform a general, unprogrammed machine 400 into a specialized machine 400 that is programmed to perform the functions described and illustrated in the described manner. In alternative embodiments, the machine 400 may operate as a standalone device or may be coupled (e.g., networked) to other machines. In a networked deployment, machine 400 may operate in the capacity of a server machine or a client machine in a server-client network environment, or as a peer machine in a peer-to-peer (or distributed) network environment. Machine 400 may comprise, without limitation, a server computer, a client computer, a personal computer (PC), a tablet computer, a laptop computer, a netbook, a set-top box (STB), a personal digital assistant (PDA), an entertainment media system, a mobile phone, a smartphone, a mobile device, a wearable device (e.g., a smart watch), a smart home device (e.g., a smart appliance), other smart devices, a web appliance, a network router, a network switch, a network bridge, or any machine capable of sequentially or otherwise executing instructions 402 that specify operations to be performed by machine 400. Moreover, while only a single machine 400 is illustrated, the term "machine" should also be interpreted to include a collection of machines that individually or collectively execute instructions 402 to perform any one or more of the methodologies described herein.

[0104] Machine 400 may include processor 404, memory / storage 406, and I / O components 408, which may be configured to communicate with each other, such as via bus 410. In an exemplary embodiment, processor 404 (e.g., a central processing unit (CPU), a reduced instruction set computing (RISC) processor, a complex instruction set computing (CISC) processor, a graphics processing unit (GPU), a digital signal processor (DSP), an application specific integrated circuit (ASIC), a radio frequency integrated circuit (RFIC), another processor, or any suitable combination thereof) may include, for example, processor 412 and processor 414, which may execute instructions 402. The term "processor" is intended to include multi-core processor 404, which may include two or more independent processors (sometimes referred to as "cores") that may execute instructions 402 simultaneously. Although FIG. 4 shows multiple processors 404, the machine 400 may include a single processor 412 with a single core, a single processor 412 with multiple cores (e.g., a multi-core processor), multiple processors 412, 414 with a single core, multiple processors 412, 414 with multiple cores, or any combination thereof.

[0105] Memory / storage 406 may include memory, such as main memory 416, or other memory storage, and storage unit 418, both accessible to processor 404, such as via bus 410. Storage unit 418 and main memory 416 store instructions 402 that embody any one or more of the methodologies or functions described herein. Instructions 402 may also reside, completely or partially, within main memory 416, within storage unit 418, within at least one of processors 404 (e.g., within a processor's cache memory), or any suitable combination thereof during execution thereof by machine 400. Thus, main memory 416, storage unit 418, and memory of processor 404 are examples of machine-readable media.

[0106] I / O components 408 may include a wide variety of components for receiving input, providing output, generating output, transmitting information, exchanging information, capturing measurements, etc. The particular I / O components 408 included in a particular machine 400 will depend on the type of machine. For example, a handheld device such as a mobile phone will likely include a touch input device or other such input mechanism, while a headless server machine will likely not include such a touch input device. It will be understood that components 408 may include many other components not shown in FIG. 5 . I / O components 408 are grouped according to function merely to simplify the following description, and grouping is in no way limiting. In various exemplary embodiments, I / O components 408 may include a user output component 420 and a user input component 422. User output components 420 may include visual components (e.g., a display such as a plasma display panel (PDP), light-emitting diode (LED) display, liquid crystal display (LCD), projector, or cathode ray tube (CRT)), acoustic components (e.g., speakers), haptic components (e.g., vibration motors, resistance mechanisms), other signal generators, etc. User input components 422 may include alphanumeric input components (e.g., a keyboard, a touchscreen configured to receive alphanumeric input, an optical keyboard, or other alphanumeric input component), point-based input components (e.g., a mouse, touchpad, trackball, joystick, motion sensor, or other pointing device), tactile input components (e.g., physical buttons, a touchscreen that provides the location or force of a touch or touch gesture, or other tactile input component), audio input components (e.g., a microphone), etc.

[0107] In further exemplary embodiments, I / O component 408 may include a biometric component 424, a motion component 426, an environmental component 428, or a position component 430, among a wide variety of other components. For example, biometric component 424 may include components for detecting facial expressions (e.g., hand expressions, facial expressions, vocal expressions, body gestures, or eye tracking), measuring biosignals (e.g., blood pressure, heart rate, body temperature, sweat, or brain waves), identifying people (e.g., voice identification, retinal identification, face identification, fingerprint identification, or brain wave-based identification), etc. Motion component 426 may include an acceleration sensor component (e.g., an accelerometer), a gravity sensor component, a rotation sensor component (e.g., a gyroscope), etc. The environmental components 428 may include, for example, an illuminance sensor component (e.g., a photometer), a temperature sensor component (e.g., one or more thermometers that detect ambient temperature), a humidity sensor component, a pressure sensor component (e.g., a barometer), an acoustic sensor component (e.g., one or more microphones that detect background noise), a proximity sensor component (e.g., an infrared sensor that detects nearby objects), a gas sensor (e.g., a gas detection sensor for detecting concentrations of harmful gases for safety purposes or for measuring pollutants in the air), or other components that can provide an indication, measurement, or signal corresponding to the surrounding physical environment. The location component 430 may include a location-determining sensor component (e.g., a GPS receiver component), an altitude sensor component (e.g., an altimeter or barometer that detects air pressure from which altitude can be derived), an orientation sensor component (e.g., a magnetometer), etc.

[0108] Communications may be implemented using a wide variety of technologies. I / O component 408 may include a communications component 432 operable to couple machine 400 to a network 434 or a device 436. For example, communications component 432 may include a network interface component or other suitable device for interfacing with network 434. In further examples, communications component 432 may include a wired communications component, a wireless communications component, a cellular communications component, a near field communications (NFC) component, a Bluetooth® component (e.g., Bluetooth® Low Energy), a Wi-Fi® component, and other communications components for providing communications via other modalities. Device 436 may be another machine 400 or any of a wide variety of peripheral devices (e.g., a peripheral coupled via USB).

[0109] Additionally, communication component 432 may detect an identifier or may include a component operable to detect an identifier. For example, communication component 432 may include a radio frequency identification (RFID) tag reader component, an NFC smart tag detection component, an optical reader component (e.g., an optical sensor for detecting one-dimensional barcodes such as Universal Product Code (UPC) barcodes, multidimensional barcodes such as Quick Response (QR) Code, Aztec Code, Data Matrix, Data Glyph, MaxiCode, PDF417, UltraCode, UCC RSS-2D barcodes, and other optical codes), or an acoustic detection component (e.g., a microphone for identifying tagged audio signals). Additionally, various information may be derived via communication component 432, such as location by Internet Protocol (IP) geolocation, location by Wi-Fi® signal triangulation, location by detection of NFC beacon signals that may represent a special location, etc.

[0110] As used herein, a "component" refers to a device, physical entity, or logic having boundaries defined by function or subroutine calls, branch points, APIs, or other techniques that provide division or modularization of particular processing or control functions. Components may be combined with other components through their interfaces to implement machine processes. A component may also be a packaged functional hardware unit designed for use with other components and portions of a program that typically perform a particular function among the associated functions. A component may constitute either a software component (e.g., code embodied on a machine-readable medium) or a hardware component. A "hardware component" is a tangible unit capable of performing certain operations and may be configured or arranged in a certain physical manner. In various exemplary embodiments, one or more hardware components of one or more computer systems (e.g., a stand-alone computer system, a client computer system, or a server computer system) or computer systems (e.g., a processor or group of processors) may be configured by software (e.g., an application or application portion) as hardware components that operate to perform certain operations described herein.

[0111] A hardware component may also be implemented mechanically, electronically, or any suitable combination thereof. For example, a hardware component may include dedicated circuitry or logic permanently configured to perform certain operations. A hardware component may be a dedicated processor, such as a field programmable gate array (FPGA) or an ASIC. A hardware component may also include programmable logic or circuitry temporarily configured by software to perform certain operations. For example, a hardware component may include software executed by a general-purpose processor 404 or other programmable processor. Once configured by such software, the hardware component becomes a specific machine (or a specific component of machine 400) uniquely tailored to perform the configured function and is no longer a general-purpose processor 404. It will be appreciated that the decision to implement a hardware component mechanically, with dedicated permanently configured circuitry, or with temporarily configured circuitry (e.g., configured by software) may be determined by cost and time considerations. Thus, the phrase "hardware component" (or "hardware implementation") should be understood to encompass a tangible entity that is physically constructed, permanently configured (e.g., hardwired), or temporarily configured (e.g., programmed) to operate in a certain manner or perform certain operations described herein. Considering embodiments in which the hardware components are temporarily configured (e.g., programmed), each of the hardware components need not be configured or instantiated at any one time. For example, if the hardware components include a general-purpose processor 404 that is configured by software to be a special-purpose processor, the general-purpose processor 404 may be configured at different times as different special-purpose processors (e.g., including different hardware components).Thus, for example, software may configure a particular processor 412, 414 or processor 404 to configure a particular hardware component at one time and a different hardware component at a different time.

[0112] Hardware components can provide information to and receive information from other hardware components. Thus, the described hardware components may be considered to be communicatively coupled. When multiple hardware components are present simultaneously, communication may be achieved by signal transmission (e.g., via appropriate circuits and buses) between two or more of the hardware components. In embodiments in which multiple hardware components are configured or instantiated at different times, communication between such hardware components may be achieved, for example, by storing and retrieving information in memory structures accessed by the multiple hardware components. For example, one hardware component may perform an operation and store the output of that operation in a memory device to which it is communicatively coupled. An additional hardware component may then access the memory device to retrieve and process the stored output.

[0113] Hardware components may also initiate communications with input or output devices and operate on resources (e.g., collections of information). Various operations of the example methods described herein may be performed, at least in part, by one or more processors 404 configured, temporarily (e.g., by software) or permanently, to perform the associated operations. Whether temporarily or permanently configured, such processors 404 may constitute processor-implemented components that operate to perform one or more operations or functions described herein. As used herein, a "processor-implemented component" refers to a hardware component implemented using one or more processors 404. Similarly, the methods described herein may be at least in part processor-implemented, with a particular processor 412, 414, or processor 404 being an example of hardware. For example, at least a portion of the operations of a method may be performed by one or more processors 404 or processor-implemented components. Furthermore, one or more processors 404 may operate to support execution of associated operations in a "cloud computing" environment or as "software as a service" (SaaS). For example, at least some of the operations may be performed by a group of computers (e.g., machine 400 including processor 404), and these operations may be accessible via network 434 (e.g., the Internet) and one or more appropriate interfaces (e.g., APIs). Performance of certain operations may reside within a single machine 400, or may be distributed among processors deployed across multiple machines. In some exemplary implementations, processor 404 or processor-implemented components may be located in a single geographic location (e.g., in a home environment, an office environment, or a server farm). In other exemplary implementations, processor 404 or processor-implemented components may be distributed across multiple geographic locations.

[0114] FIG. 5 is a block diagram illustrating a system 500 including an example software architecture 502 that may be used in conjunction with various hardware architectures described herein. It is understood that FIG. 5 is a non-limiting example software architecture, and many other architectures may be implemented to facilitate the functionality described herein. The software architecture 502 may execute on hardware such as the machine 400 of FIG. 4 , which includes, among other things, a processor 404, memory / storage 406, and input / output (I / O) components 408. An exemplary hardware layer 504 is illustrated, which may represent, for example, the machine 400 of FIG. 4 . The exemplary hardware layer 504 includes a processing unit 506 having associated executable instructions 508. The executable instructions 508 correspond to the executable instructions of the software architecture 502, including implementations of methods, components, and the like, described herein. The hardware layer 504 also includes at least one of a memory or storage module memory / storage 510 that also has the executable instructions 508. The hardware layer 504 may also include other hardware 512.

[0115] In the example architecture of FIG. 5 , software architecture 502 may be conceptualized as a stack of layers, with each layer providing specialized functionality. For example, software architecture 502 may include layers such as operating system 514, libraries 516, framework / middleware 518, application 520, and presentation layer 522. In operation, application 520 or other components within a layer may invoke API calls 524 through the software stack and receive messages 526 in response to API calls 524. The illustrated layers are representative in nature, and not all software architectures have all layers. For example, some mobile or dedicated operating systems may not provide framework / middleware 518, while others may provide such a layer. Other software architectures may include additional or different layers.

[0116] The operating system 514 may manage hardware resources and provide common services. The operating system 514 may include, for example, a kernel 528, services 530, and drivers 532. The kernel 528 may act as an abstraction layer between the hardware and other software layers. For example, the kernel 528 may be responsible for memory management, processor management (e.g., scheduling), component management, networking, security configuration, etc. The services 530 may provide other common services to the other software layers. The drivers 532 are responsible for controlling or interfacing with the underlying hardware. For example, the drivers 532 may include a display driver, a camera driver, a Bluetooth® driver, a flash memory driver, a serial communications driver (e.g., a Universal Serial Bus (USB) driver), a Wi-Fi® driver, an audio driver, a power management driver, etc., depending on the hardware configuration.

[0117] Libraries 516 provide a common infrastructure used by applications 520 and / or other components or layers. Libraries 516 provide functions that allow other software components to perform tasks in an easier manner than by directly interfacing with the underlying operating system 514 functions (e.g., kernel 528, services 530, drivers 532). Libraries 516 may include system libraries 534 (e.g., the C standard library) that may provide functions such as memory allocation functions, string manipulation functions, and mathematical functions. Additionally, libraries 516 may include API libraries 536 such as a media library (e.g., a library that supports the presentation and manipulation of various media formats such as MPEG4, H.264, MP3, AAC, AMR, JPG, and PNG), a graphics library (e.g., an OpenGL framework that may be used to render two-dimensional and three-dimensional graphical content on a display), a database library (e.g., SQLite that may provide various relational database functions), and a web library (e.g., WebKit that may provide web browsing functions). The library 516 may also include a wide variety of other libraries 538 for providing many other APIs to the application 520 and other software components / modules.

[0118] The framework / middleware 518 (also called middleware) provides a high-level common infrastructure that can be used by the applications 520 or other software components / modules. For example, the framework / middleware 518 may provide various graphical user interface functionality, high-level resource management, high-level location services, etc. The framework / middleware 518 may provide a wide range of other APIs, some of which may be specific to a particular operating system 514 or platform, that can be utilized by the applications 520 or other software components / modules.

[0119] Applications 520 include built-in applications 540 and third-party applications 542. Examples of representative built-in applications 540 may include, but are not limited to, a contacts application, a browser application, a book reader application, a location application, a media application, a messaging application, or a game application. Third-party applications 542 are applications that are installed on an ANDROID or IOS device by an entity other than the vendor of the particular platform. TM It may include applications developed using the Software Development Kit (SDK), TM The third-party application 542 may be mobile software running on a mobile operating system such as Android, Windows Phone, or other mobile operating system. The third-party application 542 may invoke API calls 524 provided by the mobile operating system (e.g., operating system 514) to facilitate the functionality described herein.

[0120] Applications 520 may use built-in operating system facilities (e.g., kernel 528, services 530, drivers 532), libraries 516, and frameworks / middleware 518 to create a UI that interacts with a user of the system. Alternatively or additionally, in some systems, interaction with the user may occur through a presentation layer, such as presentation layer 522. In these systems, application / component "logic" can be separated from the aspects of the application / component that interact with the user.

[0121] At least some of the processes described herein may be embodied in computer-readable instructions for execution by one or more processors, such that the operations of the processes may be performed, in part or in whole, by the functional components of one or more computer systems. Accordingly, the computer-implemented processes described herein are, in some circumstances, only illustratively described with reference thereto. However, in other embodiments, at least some of the operations of the computer-implemented processes described herein may be deployed in a variety of other hardware configurations. Accordingly, the computer-implemented processes described herein are not intended to be limited to the systems and configurations described with respect to FIGS. 4 and 5, but may be implemented, in whole or in part, by one or more additional systems and / or components.

[0122] While the flowcharts described herein may depict operations as a sequential process, many of the operations may occur in parallel or simultaneously. Additionally, the order of operations may be rearranged. A process terminates when its operations are completed. A process may correspond to a method, a procedure, an algorithm, etc. The operations of a method may be performed in whole or in part, may be performed in conjunction with some or all of the operations of other methods, and may be performed by any number of different systems, such as the systems described herein, or any portion thereof, such as a processor included in any of the systems.

[0123] As used herein, a component may refer to a device, physical entity, or logic having boundaries defined by functions or subroutine calls, branch points, APIs, or other techniques that provide partitioning or modularization of specialized processing or control functions. A component may be combined with other components through their interfaces to implement a machine process. A component may also be a packaged functional hardware unit designed for use with other components and portions of a program that typically perform a specific function among the associated functions. A component may constitute either a software component (e.g., code embodied on a machine-readable medium) or a hardware component. A "hardware component" is a tangible unit capable of performing certain operations and may be configured or arranged in a certain physical manner. In various exemplary embodiments, one or more hardware components of one or more computer systems (e.g., a stand-alone computer system, a client computer system, or a server computer system) or computer systems (e.g., a processor or group of processors) may be configured by software (e.g., an application or application portion) as a hardware component that operates to perform certain operations described herein.

[0124] It should be understood that the individual steps used in the methods of the present teachings may be performed in any order and / or simultaneously so long as the teachings remain operable. Furthermore, it should be understood that the apparatus and methods of the present teachings may include any number or all of the described embodiments so long as the teachings remain operable.

[0125] The various steps of the methods disclosed herein, or steps performed by the systems disclosed herein, may be performed at the same time or at different times, and / or in the same geographic location or in different geographic locations, e.g., countries. The various steps of the methods disclosed herein may be performed by the same person or different people.

[0126] Various embodiments of systems, devices, and methods have been described herein. These embodiments are provided by way of example only and are not intended to limit the scope of the claimed invention. Furthermore, it should be understood that various features of the described embodiments can be combined in various ways to create numerous additional embodiments. Furthermore, while various materials, dimensions, shapes, configurations, locations, etc. are described for use in the disclosed embodiments, others other than those disclosed may be utilized without departing from the scope of the claimed invention.

[0127] Those skilled in the art will recognize that embodiments may include fewer features than are illustrated in any individual embodiment described above. The embodiments described herein are not intended to be an exhaustive listing of ways in which various features can be combined. Thus, embodiments are not mutually exclusive combinations of features. Rather, embodiments may include combinations of different individual features selected from different individual embodiments, as would be understood by one skilled in the art. Furthermore, elements described with respect to one embodiment may be implemented in other embodiments even if not described in such embodiment, unless otherwise specified. While a dependent claim may refer to a specific combination with one or more other claims in the claims, other embodiments may also include a combination of the dependent claim with the subject matter of other dependent claims, or one or more features with other dependent or independent claims. Such combinations are suggested herein unless it is stated that a specific combination is not intended. Furthermore, including a claim's features in any other independent claim is also intended, even if that claim is not directly dependent on that independent claim.

[0128] Furthermore, references herein to "one embodiment," "an embodiment," or "some embodiments" mean that a particular feature, structure, or characteristic described in connection with an embodiment is included in at least one embodiment of the present teachings. The appearances of the phrase "in one embodiment" in various places in the specification do not necessarily all refer to the same embodiment.

[0129] Any incorporation by reference of the above documents is limited so that no subject matter contrary to the express disclosure herein is incorporated. Any incorporation by reference of the above documents is further limited so that no claims contained in the documents are incorporated herein by reference. Any incorporation by reference of the above documents is further limited so that any definitions provided in the documents are not incorporated herein by reference, unless expressly included herein.

[0130] While the embodiments have been described with reference to certain exemplary embodiments, it will be apparent that various modifications and changes can be made to these embodiments without departing from the broader spirit and scope of the present disclosure. Accordingly, the specification and drawings are to be regarded in an illustrative and not a restrictive sense. The accompanying drawings, which form a part of this specification, show, by way of example, and not of limitation, specific embodiments in which the subject matter may be practiced. The illustrated embodiments have been described in sufficient detail to enable those skilled in the art to practice the teachings disclosed herein. Other embodiments may be utilized and derived, such that structural and logical substitutions and changes may be made without departing from the scope of the present disclosure. Accordingly, this detailed description is not to be construed in a limiting sense, and the scope of various embodiments is defined only by the appended claims, along with the full range of equivalents to which such claims are entitled.

[0131] Although specific embodiments have been illustrated and described herein, it should be understood that any arrangement calculated to accomplish the same purpose may be substituted for the specific embodiment shown. The present disclosure is intended to cover any and all adaptations or modifications of the various embodiments. Combinations of the above embodiments, and other embodiments not specifically described herein, will be apparent to those skilled in the art upon reviewing the above description.

[0132] As used herein, the terms "a" or "an," as is common in patent documents, are used to include one or more, regardless of any other instance or use of "at least one" or "one or more." As used herein, the term "or" is used non-exclusively, or such that "A or B" includes "A but not B," "B but not A," and "A and B," unless otherwise stated. As used herein, the terms "including" and "in which" are used as the plain English equivalents of the terms "comprising" and "wherein," respectively. Also, in the following claims, the terms "comprising" and "comprising" are open-ended, i.e., a system, user equipment (UE), article, composition, formulation, or process that includes elements in addition to the elements recited after such term in a claim is still considered to be within the scope of that claim. Moreover, in the following claims, the terms "first," "second," and "third," etc., are used merely as labels and are not intended to impose numerical requirements on their objects.

Claims

1. 1. A method comprising: a computing system of a life sciences service provider, the computing system including a processing circuit and a memory, acquiring a first amount of data including patient data and a second amount of data including patient metadata, the patient data including genomic information for a plurality of subjects; causing the computing system to store the first amount of data in a local network data repository that is at least one of controlled, maintained, or managed by the life sciences service provider; generating, by the computing system, a first bandwidth modification request to modify an allocation of network resources of a physical communication network to the life sciences service provider from a first amount of network resources to a second amount of network resources, the second amount of network resources being greater than the first amount of network resources; causing the computing system to transfer at least a portion of the second amount of data to a remote data repository while the second amount of network resources is allocated to the life sciences service provider; the computing system determining that the transfer of the at least a portion of the second amount of data to the remote data repository is complete; and generating a second bandwidth modification request by the computing system to modify the allocation of network resources of the physical communication network to the life sciences service provider from the second amount to the first amount; A method comprising:

2. receiving, by the computing system, a request to retrieve a portion of the patient data; determining, by the computing system, one or more portions of the patient metadata that correspond to the portion of the patient data; the computing system sending a request to a database management system to access the portion of the patient data stored by the local network data repository and the one or more portions of the patient metadata stored by the remote data repository; the computing system obtaining the portion of the patient data and the one or more portions of the patient metadata; The method of claim 1 , comprising:

3. a bioinformatics system implemented by the computing system performing an analysis of the portion of the patient data and the one or more portions of the patient metadata; determining, based on the analysis, one or more characteristics of the subject corresponding to the portion of the patient data and the one or more portions of the patient metadata; The method of claim 2 , comprising:

4. the one or more characteristics include one or more genomic variations present in nucleic acid derived from a sample obtained from the subject; 4. The method of claim 3, wherein the nucleic acid corresponds to cell-free deoxyribonucleic acid (DNA) extracted from a bodily fluid sample obtained from the subject.

5. 4. The method of claim 3, wherein the one or more characteristics comprise developing resistance to a treatment provided to the subject in conjunction with a biological condition present in the subject.

6. The method of claim 5 , wherein the biological state corresponds to a form of cancer.

7. 4. The method of claim 3, wherein the analysis comprises determining a treatment recommendation to provide to the subject to treat a biological condition present in the subject.

8. The method of claim 1 , wherein the portion of the patient data is transferred to the local network data repository in addition to transferring at least a portion of the patient metadata to the remote data repository.

9. determining an amount of memory storage space for the computing system to store at least a portion of the patient metadata; said computing system determining that said amount of memory storage space is at least a threshold amount of memory storage space; Including, The method of claim 1 , wherein the first bandwidth modification request is generated based on the amount of memory storage space being at least a threshold amount of memory storage space.

10. 10. The method of claim 1, wherein the second amount of network resources corresponds to a minimum transfer rate of at least a portion of the patient metadata from the life sciences service provider to the remote data repository over the physical communication network.

11. 10. The method of claim 1, wherein the second amount of network resources corresponds to transferring at least a portion of the patient metadata from the life sciences service provider to the remote data repository in less than a threshold amount of time.

12. The method of claim 1 , wherein the first bandwidth modification request and the second bandwidth modification request comprise one or more calls to an application programming interface (API) of a cloud storage service provider.

13. 1. A system comprising: one or more hardware processing units; One or more computer-readable storage media storing computer-executable instructions that, when executed by the one or more hardware processing units, a life sciences service provider obtaining a first amount of data including patient data and a second amount of data including patient metadata, the patient data including genomic information for a plurality of subjects; storing the first amount of data by a local network data repository controlled, maintained, or managed by the life sciences service provider; generating a first bandwidth modification request to modify an allocation of network resources of a physical communication network to the life sciences service provider from a first amount of network resources to a second amount of network resources, the second amount of network resources being greater than the first amount of network resources; transferring at least a portion of the second amount of data to a remote data repository while the second amount of network resources is allocated to the life sciences service provider; determining that the transfer of the at least a portion of the second amount of data to the remote data repository is complete; and generating a second bandwidth modification request to modify the allocation of network resources of the physical communication network to the life sciences service provider from the second amount to the first amount; one or more computer-readable storage media that cause the system to perform operations including A system comprising:

14. The one or more computer-readable storage media store additional computer-executable instructions that, when executed by the one or more hardware processing units, receiving a request to retrieve a portion of the patient data; determining one or more portions of the patient metadata that correspond to the portion of the patient data; sending a request to a database management system to access the portion of the patient data stored by the local network data repository and the one or more portions of the patient metadata stored by the remote data repository; obtaining the portion of the patient data and the one or more portions of the patient metadata; 14. The system of claim 13, further comprising:

15. The one or more computer-readable storage media store additional computer-executable instructions that, when executed by the one or more hardware processing units, a bioinformatics system of the life sciences service provider performing an analysis of the portion of the patient data and the one or more portions of the patient metadata; determining, based on the analysis, one or more characteristics of the subject corresponding to the portion of the patient data and the one or more portions of the patient metadata; 15. The system of claim 14, further comprising:

16. the one or more characteristics include one or more genomic variations present in nucleic acid derived from a sample obtained from the subject; 16. The system of claim 15, wherein the nucleic acid corresponds to cell-free deoxyribonucleic acid (DNA) extracted from a bodily fluid sample obtained from the subject.

17. 16. The system of claim 15, wherein the one or more characteristics comprise developing resistance to a treatment provided to the subject in conjunction with a biological condition present in the subject.

18. The system of claim 17 , wherein the biological state corresponds to a form of cancer.

19. The one or more computer-readable storage media store additional computer-executable instructions that, when executed by the one or more hardware processing units, determining, as part of said analysis, a treatment recommendation to provide to said subject to treat a biological condition present in said subject; 16. The system of claim 15, further comprising:

20. The one or more computer-readable storage media store additional computer-executable instructions that, when executed by the one or more hardware processing units, transferring a portion of the patient data to the local network data repository in conjunction with the transfer of at least a portion of the patient metadata to the remote data repository.

14. The system of claim 13, further comprising:

21. The one or more computer-readable storage media store additional computer-executable instructions that, when executed by the one or more hardware processing units, determining an amount of memory storage space for storing at least a portion of the patient metadata; determining that the amount of memory storage space is at least a threshold amount of memory storage space; causing the system to perform additional operations including The system of claim 13 , wherein the first bandwidth modification request is generated based on the amount of memory storage space being at least a threshold amount of memory storage space.

22. 14. The system of claim 13, wherein the second amount of network resources corresponds to a minimum transfer rate of at least a portion of the patient metadata from the life sciences service provider to the remote data repository over the physical communication network.

23. 14. The system of claim 13, wherein the second amount of network resources corresponds to transferring at least a portion of the patient metadata from the life sciences service provider to the remote data repository in less than a threshold amount of time.

24. The system of claim 13 , wherein the first bandwidth modification request and the second bandwidth modification request comprise one or more calls to an application programming interface (API) of a cloud storage service provider.

25. One or more non-transitory computer-readable storage media storing computer-executable instructions that, when executed by one or more hardware processing units, a life sciences service provider obtaining a first amount of data including patient data and a second amount of data including patient metadata, the patient data including genomic information for a plurality of subjects; storing the first amount of data by a local network data repository controlled, maintained, or managed by the life sciences service provider; generating a first bandwidth modification request to modify an allocation of network resources of a physical communication network to the life sciences service provider from a first amount of network resources to a second amount of network resources, the second amount of network resources being greater than the first amount of network resources; transferring at least a portion of the second amount of data to a remote data repository while the second amount of network resources is allocated to the life sciences service provider; determining that the transfer of the at least a portion of the second amount of data to the remote data repository is complete; and generating a second bandwidth modification request to modify the allocation of network resources of the physical communication network to the life sciences service provider from the second amount to the first amount; One or more non-transitory computer-readable storage media that cause the system to perform operations including:

26. additional computer-executable instructions that, when executed by the one or more hardware processing units, receiving a request to retrieve a portion of the patient data; determining one or more portions of the patient metadata that correspond to the portion of the patient data; sending a request to a database management system to access the portion of the patient data stored by the local network data repository and the one or more portions of the patient metadata stored by the remote data repository; obtaining the portion of the patient data and the one or more portions of the patient metadata; 26. The one or more non-transitory computer-readable storage media of claim 25, which causes the system to perform additional operations including:

27. additional computer-executable instructions that, when executed by the one or more hardware processing units, a bioinformatics system of the life sciences service provider performing an analysis of the portion of the patient data and the one or more portions of the patient metadata; determining, based on the analysis, one or more characteristics of the subject corresponding to the portion of the patient data and the one or more portions of the patient metadata; 27. The one or more non-transitory computer-readable storage media of claim 26, which causes the system to perform additional operations including:

28. the one or more characteristics include one or more genomic variations present in nucleic acid derived from a sample obtained from the subject; 30. The one or more non-transitory computer-readable storage media of claim 27, wherein the nucleic acid corresponds to cell-free deoxyribonucleic acid (DNA) extracted from a bodily fluid sample obtained from the subject.

29. 30. The one or more non-transitory computer-readable storage media of claim 27, wherein the one or more characteristics comprise developing resistance to a treatment provided to the subject in conjunction with a biological condition present in the subject.

30. 30. The one or more non-transitory computer-readable storage media of claim 29, wherein the biological condition corresponds to a form of cancer.

31. additional computer-executable instructions that, when executed by the one or more hardware processing units, determining, as part of said analysis, a treatment recommendation to provide to said subject to treat a biological condition present in said subject; 30. The one or more non-transitory computer-readable storage media of claim 27, which causes the system to perform additional operations including:

32. additional computer-executable instructions that, when executed by the one or more hardware processing units, transferring a portion of the patient data to the local network data repository in conjunction with transferring at least a portion of the patient metadata to the remote data repository.

26. The one or more non-transitory computer-readable storage media of claim 25, which causes the system to perform additional operations including:

33. additional computer-executable instructions that, when executed by the one or more hardware processing units, determining an amount of memory storage space for storing at least a portion of the patient metadata; determining that the amount of memory storage space is at least a threshold amount of memory storage space; causing the system to perform additional operations including 26. The one or more non-transitory computer-readable storage media of claim 25, wherein the first bandwidth modification request is generated based on the amount of memory storage space being at least a threshold amount of memory storage space.

34. 26. The one or more non-transitory computer-readable storage media of claim 25, wherein the second amount of network resources corresponds to a minimum transfer rate of at least a portion of the patient metadata from the life sciences service provider to the remote data repository over the physical communication network.

35. 26. The one or more non-transitory computer-readable storage media of claim 25, wherein the second amount of network resources corresponds to transferring at least a portion of the patient metadata from the life sciences service provider to the remote data repository in less than a threshold amount of time.

36. 26. The one or more non-transitory computer-readable storage media of claim 25, wherein the first bandwidth modification request and the second bandwidth modification request comprise one or more calls to an application programming interface (API) of a cloud storage service provider.

Images