Network bandwidth architecture for computing systems

Abstract

A network bandwidth architecture controls data transfer between a life science service provider, a local network data repository, and a remote data repository. The data transmission may include patient data and patient metadata analyzed by a bioinformatics system of a life science service provider.

Description

Priority Declaration

[0001] This application claims the benefit of priority to U.S. Provisional Patent Application No. 63 / 485,201, filed on February 15, 2023, and entitled “Network Bandwidth Architecture For Bioinformatics System,” which is incorporated herein by reference in its entirety. Technical Field

[0002] Implementations of the present disclosure generally relate to the field of high-performance computer architectures, and more specifically to implementations of high-performance computer architectures for controlling network bandwidth associated with data transmission in various systems (such as media streaming systems, scientific research systems, bioinformatics systems, content production systems, etc.). background

[0003] High-performance computing systems can be used to transmit and perform computations on large amounts of data. For example, bioinformatics can involve the analysis of large amounts of data in an effort to understand the causes of various biological conditions and identify treatments for many of them. In many cases, bioinformatics can involve the computational analysis of genomic data. Genomic data can include nucleotide sequences of genetic material obtained from individual samples. Genomic data from a single individual can correspond to many megabytes of data storage space, while genomic data from groups of different individuals can correspond to hundreds of gigabytes, up to many terabytes of data storage space. In other examples, high-performance computing systems can be used to predict and model scenarios related to meteorological and geological data, as well as in the execution of machine learning algorithms and fraud detection. Due to the large amounts of data accessed and analyzed by bioinformatics systems and other systems that utilize high-performance computing, the storage and transmission of this data can be inefficient in terms of utilized network resources, leading to performance lags. BRIEF DESCRIPTION OF THE DRAWINGS

[0004] Figure 1 Illustrated is an example architecture for transferring patient data and patient metadata between one or more data repositories and a computing system that analyzes the patient data and patient metadata, according to one or more implementations.

[0005] Figure 2 Illustrated is an example framework for increasing allocation of network resources during transfer of patient data and patient metadata from local and remote data repositories, in accordance with one or more implementations.

[0006] Figure 3is a flow chart of an example process for increasing allocation of network resources during transfer of system data and metadata from local and remote data repositories in accordance with one or more implementations.

[0007] Figure 4 is a block diagram illustrating components of a machine 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 example implementations.

[0008] Figure 5 is a block diagram illustrating a representative software architecture that may be used in conjunction with one or more of the hardware architectures described herein, according to one or more example implementations. SUMMARY OF THE INVENTION

[0009] In one or more aspects, the technology described herein relates to a method comprising: obtaining, by a computing system of a life sciences service provider comprising processing circuitry and memory, a first amount of data comprising patient data and a second amount of data comprising patient metadata, the patient data comprising genomic information for a plurality of subjects; causing, by the computing system, the first amount of data to be stored by a local network data repository, the local network data repository being 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 network resources allocated to a physical communications network of the life sciences service provider from the 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, by the computing system, at least a portion of the second amount of data to be transmitted to a remote data repository while allocating the second amount of network resources to the life sciences service provider; determining, by the computing system, that transmission of at least a portion of the second amount of data to the remote data repository is complete; and generating, by the computing system, a second bandwidth modification request to modify the network resources allocated to the physical communications network of the life sciences service provider from the second amount to the first amount.

[0010] In one or more aspects, the technology described herein relates to a method comprising: 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 corresponding 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 one or more portions of patient metadata stored by a remote data repository; and obtaining, by the computing system, the portion of the patient data and the one or more portions of the patient metadata.

[0011] In one or more aspects, the technology described herein relates to a method comprising: performing, by a bioinformatics system implemented by a computing system, an analysis of a portion of patient data and one or more portions of patient metadata; and determining, by the computing system and 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.

[0012] In one or more aspects, the technology described herein relates to a method wherein: one or more features include one or more genomic mutations present in nucleic acid derived from a sample obtained from a subject; and the nucleic acid corresponds to cell-free deoxyribonucleic acid (DNA) extracted from a bodily fluid sample obtained from the subject.

[0013] In one or more aspects, the technology described herein relates to a method wherein one or more characteristics include developing resistance to a treatment provided to a subject in conjunction with a biological condition present in the subject.

[0014] In one or more aspects, the technology described herein relates to a method wherein the biological condition corresponds to a form of cancer.

[0015] In one or more aspects, the technology described herein relates to a method wherein analyzing includes determining a recommendation for a treatment to provide to a subject to treat a biological condition present in the subject.

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

[0017] In one or more aspects, the technology described herein relates to a method comprising: determining, by a computing system, an amount of memory storage space for storing at least a portion of patient metadata; and determining, by the computing system, that the amount of memory storage space is at least a threshold amount of memory storage space; wherein, generating a first bandwidth modification request based on the amount of memory storage space being at least the threshold amount of memory storage space.

[0018] In one or more aspects, the technology described herein relates to a method in which a second amount of network resources corresponds to a minimum transmission rate of at least a portion of patient metadata from a life sciences service provider to a remote data repository via a physical communications network.

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

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

[0021] In one or more aspects, the technology described herein relates to a system comprising: one or more hardware processing units; and one or more computer-readable storage media storing computer-executable instructions that, when executed by the one or more hardware processing units, cause the system to perform operations comprising: obtaining, by a life sciences service provider, a first amount of data comprising patient data and a second amount of data comprising patient metadata, the patient data comprising genomic information for a plurality of subjects; causing the first amount of data to be stored by a local network data repository that is at least one of controlled, maintained, or managed by the life sciences service provider; generating a first bandwidth modification request to modify network resources allocated to a physical communication network of the life sciences service provider from the 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; while allocating the second amount of network resources to the life sciences service provider, causing at least a portion of the second amount of data to be transmitted to a remote data repository; determining that transmission of 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 network resources allocated to the physical communication network of the life sciences service provider from the second amount to the first amount.

[0022] 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, the additional operations including: receiving a request to retrieve a portion of patient data; determining one or more portions of patient metadata corresponding 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 one or more portions of patient metadata stored by a remote data repository; and obtaining the portion of patient data and the one or more portions of patient metadata.

[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, the additional operations including: performing, by a bioinformatics system of a life sciences service provider, an analysis of a portion of patient data and one or more portions of patient metadata; and determining, based on the analysis, one or more characteristics of a subject corresponding to the portion of patient data and the one or more portions of patient metadata.

[0024] In one or more aspects, the technology described herein relates to a system wherein: one or more features include one or more genomic mutations present in nucleic acid derived from a sample obtained from a subject; and the nucleic acid corresponds to cell-free deoxyribonucleic acid (DNA) extracted from a bodily fluid sample obtained from the subject.

[0025] In one or more aspects, the technology described herein relates to a system wherein one or more characteristics include resistance to a treatment provided to a subject in conjunction with a biological condition present in the subject.

[0026] In one or more aspects, the technology described herein relates to a system in which the biological condition corresponds to a form of cancer.

[0027] In one or more aspects, the technology described herein relates to a system in which one or more computer-readable storage media stores 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 an analysis, a recommendation for a treatment to provide to a subject to treat a biological condition present in the subject.

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

[0029] In one or more aspects, the technology described herein relates to a system wherein: 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, the additional operations including: determining an amount of memory storage space for storing at least a portion of patient metadata; and determining that the amount of memory storage space is at least a threshold amount of memory storage space; and 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.

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

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

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

[0033] In one or more aspects, the technology described herein relates to one or more non-transitory computer-readable storage media storing computer-executable instructions that, when executed by one or more hardware processing units, cause a system to perform operations comprising: obtaining, by a life sciences service provider, a first amount of data comprising patient data and a second amount of data comprising patient metadata, the patient data comprising genomic information for a plurality of subjects; causing the first amount of data to be stored by a local network data repository that is at least one of controlled, maintained, or managed by the life sciences service provider; generating a first bandwidth modification request to modify network resources allocated to a physical communication network of the life sciences service provider from the 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; while allocating the second amount of network resources to the life sciences service provider, causing at least a portion of the second amount of data to be transmitted to a remote data repository; determining that transmission of 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 network resources allocated to the physical communication network of the life sciences service provider from the second amount to the first amount.

[0034] In one or more aspects, the technology described herein relates 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, the additional operations including: receiving a request to retrieve a portion of patient data; determining one or more portions of patient metadata corresponding 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 one or more portions of patient metadata stored by a remote data repository; and obtaining the portion of patient data and the one or more portions of patient metadata.

[0035] In one or more aspects, the technology described herein relates 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, the additional operations including: performing, by a bioinformatics system of a life sciences service provider, an analysis of a portion of patient data and one or more portions of patient metadata; and determining, based on the analysis, one or more characteristics of a subject corresponding to the portion of patient data and the one or more portions of patient metadata.

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

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

[0038] In one or more aspects, 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.

[0039] In one or more aspects, the technology described herein relates to one or more non-transitory computer-readable storage media comprising 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 recommendation for a treatment to provide to a subject to treat a biological condition present in the subject.

[0040] In one or more aspects, the technology described herein relates 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 system to perform additional operations, including: transferring a portion of patient data to a local network data repository in conjunction with transferring at least a portion of patient metadata to a remote data repository.

[0041] In one or more aspects, the technology described herein relates 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 system to perform additional operations, the additional operations including: determining an amount of memory storage space for storing at least a portion of 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.

[0042] 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 a minimum transmission rate of at least a portion of patient metadata from the life sciences service provider to the remote data repository via the physical communications network.

[0043] 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 transmitting at least a portion of patient metadata from the life sciences service provider to the remote data repository in less than a threshold amount of time.

[0044] 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 comprise one or more calls to an application programming interface (API) of a cloud storage service provider.

[0045] In one or more aspects, the technology described herein relates to a method comprising: obtaining, by a high-performance computing system comprising processing circuitry and a memory, a first system data volume and a second data volume comprising metadata; causing, by the high-performance computing system, the first system data volume to be stored by a local network data repository; generating, by the high-performance computing system, a first bandwidth modification request to modify the allocation of network resources of a physical communication network from the first network resource volume to a second network resource volume, the second network resource volume being greater than the first network resource volume; while allocating the second network resource volume, causing, by the high-performance computing system, at least a portion of the second data volume to be transmitted to a remote data repository; determining, by the high-performance computing system, that the transmission of at least a portion of the second data volume to the remote data repository is complete; and generating, by the high-performance computing system, a second bandwidth modification request to modify the allocation of network resources of the physical communication network from the second volume to the first volume.

[0046] In one or more aspects, the technology described herein relates to a method comprising: receiving, by a high-performance computing system, a request to retrieve a portion of system data; determining, by the 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 one or more portions of metadata stored by a remote data repository; and obtaining, by the high-performance computing system, the portion of the system data and the one or more portions of metadata.

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

[0048] In one or more aspects, the technology described herein relates to a method wherein system data includes media content, and a high-performance computing system and a 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.

[0049] In one or more aspects, the technology described herein relates to a method wherein 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 or academic institution.

[0050] In one or more aspects, the technology described herein relates to a method in which the system data includes patient data and the metadata includes patient metadata, wherein the patient data includes genomic information for a plurality of subjects.

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

[0052] In one or more aspects, the technology described herein relates to a method wherein: one or more features include one or more genomic mutations present in nucleic acid derived from a sample obtained from a subject; and the nucleic acid corresponds to cell-free deoxyribonucleic acid (DNA) extracted from a bodily fluid sample obtained from the subject.

[0053] In one or more aspects, the technology described herein relates to a method wherein one or more characteristics include developing resistance to a treatment provided to a subject in conjunction with a biological condition present in the subject.

[0054] In one or more aspects, the technology described herein relates to a method wherein the biological condition corresponds to a form of cancer.

[0055] In one or more aspects, the technology described herein relates to a method wherein analyzing includes determining a recommendation for a treatment to provide to a subject to treat a biological condition present in the subject.

[0056] In one or more aspects, the technology described herein relates to a method in which analyzing includes determining recommendations for media content to provide to users of at least one of a media content provider, a communications company, or a content streaming service.

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

[0058] In one or more aspects, the technology described herein relates to a method comprising: determining, by a high-performance computing system, an amount of memory storage space for storing at least a portion of metadata; and determining, by the high-performance computing system, that the amount of memory storage space is at least a threshold amount of memory storage space; wherein, generating a first bandwidth modification request based on the amount of memory storage space being at least the threshold amount of memory storage space.

[0059] In one or more aspects, the technology described herein relates to a method in which the second amount of network resources corresponds to a minimum transmission rate of at least a portion of metadata to a remote data repository via a physical communications network.

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

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

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

[0063] Figure 1 An example architecture 100 is illustrated for transferring data and metadata between one or more data repositories and computing systems for analyzing data and patients, according to one or more implementations. The architecture 100 may include a life sciences service provider 102 and may be used to provide high-performance computing services to the life sciences service provider 102. A high-performance computing system may include a cluster of processors that can perform computations in a massively parallel manner. In at least some instances, a high-performance computing system can perform computations and transfer data volumes that are hundreds, thousands, or even millions of times greater than a typical desktop, laptop, or server system. A high-performance computing system may use thousands, tens of thousands, or even millions of processors to perform computations and may perform up to 10^18 floating-point operations per second.

[0064] Life science service providers 102 may include entities that provide at least one of a product or a service to individuals. Life science service providers 102 may include at least one of an educational organization, a nonprofit organization, a privately owned business, or a publicly owned business. In one or more examples, life science service providers 102 may include entities that develop treatments for one or more biological conditions. For example, life science service providers 102 may include pharmaceutical companies that develop and / or manufacture pharmaceutical substances to treat one or more biological conditions. Additionally, life science service providers 102 may include diagnostic organizations that develop tests to detect the presence of one or more biological conditions in a subject. Life science service providers 102 may also include medical device entities that develop and / or manufacture medical devices to at least one of treat or detect one or more biological conditions. Furthermore, life science service providers 102 may include organizations that perform at least one of the following: develop or manufacture equipment, devices, supplies, or a combination thereof for at least one of detecting or treating one or more biological conditions. In still other examples, life science service providers 102 may include healthcare providers that provide at least one of testing, medical services, or treatments for one or more biological conditions. In various examples, life science 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 related to 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 the function and / or structure of an individual to such an extent that a detectable characteristic of the abnormality is produced or threatened to be produced. A biological condition may be characterized by external and / or internal characteristics, signs, and / or symptoms that indicate a deviation from biological normality in one or more populations. A biological condition may include at least one of one or more diseases, one or more disorders, one or more injuries, one or more syndromes, one or more disabilities, one or more infections, one or more isolated symptoms, or other atypical variations in an individual's biological structure and / or function. Furthermore, as used herein, a treatment may refer to a substance, procedure, routine, device, and / or other intervention that may be administered or performed to alleviate 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 the individual. The substance may include a composition of substances, such as a pharmaceutical composition. The substance can be delivered to the individual by a variety of methods, such as ingestion, injection, absorption, or inhalation. Treatment may also include physical intervention, such as one or more surgeries.

[0066] In at least some examples, life science service provider 102 can at least one of store, access, or analyze data corresponding to multiple subjects 104. In one or more examples, a sample 106 can be extracted from subject 104. Sample 106 can be derived from at least one of a bodily fluid or a tissue obtained from subject 104. At operation 108, sample 106 can undergo at least one of one or more diagnostic tests or one or more analytical tests. In various examples, the one or more diagnostic tests and / or one or more analytical tests performed at operation 108 can be performed to detect one or more biological conditions that may be present in subject 104. In one or more illustrative examples, at least one of the one or more diagnostic tests or one or more analytical tests performed at operation 108 can 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 at operation 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 at operation 108. For example, the patient data 110 may include genomic information, genetic information, metabolomic information, transcriptomic information, fragmentomic information, immune receptor information, methylation information, epigenomic information, and / or proteomic information, immunohistochemistry (IHC), and immunofluorescence (IF).

[0068] As used herein, "fragment set information" can include, among other things, information related to length analysis of DNA or RNA fragments to determine the presence or absence of a tumor and to determine the characteristics of the tumor. In at least some examples, the fragment set information can correspond to nucleosome structure and transcription factor binding sites. In one or more illustrative examples, the fragment set information can include fragment endpoint density, plasma DNA size, endpoints, nucleosome footprints, DNA fragments aligned with base positions in the genome, the number of DNA fragments that start or end at a specific base position in the genome, fragment starting points and lengths associated with a particular condition, heterogeneity patterns of cfDNA localization in cancer, nucleosome occupancy, nucleosome dynamics, chromatin organization, structure and function, chromatin state, consequences of genomic aberrations, and / or DNA epigenetic changes associated with health and disease.

[0069] In addition, "genomic information" can correspond to a nucleic acid sequence derived from sample 106. Genomic information can indicate one or more mutations corresponding to a gene of subject 104. The mutation of a gene of subject 104 can correspond to a difference between the nucleic acid sequence of subject 104 and one or more reference genomes. The reference genome can include a known reference genome, such as hg19. In various examples, the mutation of a gene of subject 104 can correspond to a difference between the germline genes of subject 104 and the reference genome. In one or more further examples, the reference genome can include the germline genome of subject 104. In one or more further examples, the mutation of a gene of subject 104 can include a somatic mutation. The mutation of a gene of subject 104 may be associated with an insertion, deletion, single nucleotide variation, loss of heterozygosity, duplication, amplification, translocation, fusion gene, or one or more combinations thereof. In at least some examples, the genomic information can correspond to a non-coding region of the genome. The non-coding region can be associated with the regulation of one or more genes. In one or more examples, analysis of the non-coding region can detect one or more epigenetic features of one or more patients.

[0070] In one or more illustrative examples, the genomic information included in patient data 110 may include a genomic profile of tumor cells present in one or more subjects 104. In these cases, the genomic information may be derived from 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, which is present due to degradation of tumor cells present in 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. The presence of one or more mutations with respect to the one or more target regions may indicate the presence of tumor cells in one or more subjects 104.

[0071] In one or more illustrative examples, the genetic material analyzed to generate genomic information can be derived from one or more samples 106, including but not limited to tissue samples or tumor biopsies, circulating tumor cells (CTCs), exosomes or endosomes, or from 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 present in an extracellular form in subject 104 (e.g., in blood, serum, plasma, or other bodily fluids such as lymph, cerebrospinal fluid, urine, or sputum), and includes DNA that is not contained within or otherwise bound to cells when isolated from subject 104. Although the DNA is initially present in one or more cells of a large, complex biological organism (e.g., a mammal) or in other cells that colonize the organism (e.g., bacteria), the DNA has been released from the cells into the fluids found in the organism. cfDNA includes, but is not limited to, cell-free genomic DNA of subject 104 (e.g., genomic DNA of a human subject) and cell-free DNA of microorganisms (such as bacteria) residing in subject 104 (whether pathogenic or typically found in common colonization sites (such as the intestine or skin of healthy controls), but does not include cell-free DNA of microorganisms that merely contaminate a bodily fluid sample. Generally, cfDNA can be obtained by obtaining a volume of fluid without performing an in vitro cell lysis step and also includes removing cells present in the fluid (e.g., centrifugation of blood to remove cells).

[0072] Patient metadata 112 may also be generated based on at least one of the one or more diagnostic tests or the one or more analytical tests performed at operation 108. The patient metadata 112 may correspond to the patient data 110 for the individual subject 104. For example, for the individual subject 104, the patient metadata 112 may be generated in conjunction with generating the patient data 110 at operation 108 through the one or more diagnostic tests and / or the one or more analytical tests. 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 associated with generating the patient data 110 at operation 108. In one or more examples, the patient metadata 112 may indicate information about the one or more machines, one or more instruments, one or more medical devices, one or more computing devices, or one or more combinations thereof used to generate the patient data 110, such as a model number, serial number, software version number, technology used to generate the patient data 110, settings used to generate the patient data 110, the date and / or time when the patient data 110 was generated, one or more combinations thereof, and the like.

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

[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 to analyze 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 to analyze 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 the biological condition is present. 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 characteristics of at least a portion of the subject 104 in which at least one form of cancer is present. To illustrate, 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 a sample 106 provided by at least a portion of the subject 104. In one or more additional examples, the bioinformatics system 114 can analyze at least one of the patient data 110 or the patient metadata 112 to identify one or more cohorts corresponding to the plurality of groups of subjects 104. In still other examples, the bioinformatics system 114 can 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 a portion of the subjects 104 relative to one or more biological conditions present in the group of subjects 104. Additionally, the bioinformatics system 114 can analyze at least one of the patient data 110 or the patient metadata 112 to determine a recommendation for treatment for at least a portion of the subjects 104 related to one or more biological conditions present in the group of subjects 104. Furthermore, the bioinformatics system 114 can analyze at least one of the patient data 110 or the patient metadata 112 to determine an amount of progression of a biological condition present in at least a portion of the subjects 104. In at least some examples, the bioinformatics system 114 can 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 subjects 104. In one or more illustrative scenarios, bioinformatics system 114 may analyze at least one of patient data 110 or patient metadata 112 to determine a diagnosis for at least a portion of subject 104 .

[0075] Life sciences service provider 102 may include one or more computing devices 116 that can access bioinformatics system 114. 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. Life sciences service provider 102 may also include and / or be coupled to a local network data repository 118. In one or more examples, local network data repository 118 may include one or more data storage devices located at at least one site of life sciences service provider 102. In various examples, local network data repository 118 may be coupled to at least one of one or more computing devices 116 or bioinformatics system 114 via one or more physical network connections that are at least one of maintained, controlled, or managed by life sciences service provider 102. Local network data repository 118 may store at least one of: at least a portion of patient data 110 or at least a portion of patient metadata 112.

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

[0077] In one or more examples, a virtual communication network 126 can couple the life sciences service provider 102 with the remote data repository 120. The virtual communication network 126 can correspond to a portion of the physical communication network 122 allocated to the life sciences service provider 102 at a given time. For illustration, various portions of the network resources of the physical communication network 122 can be allocated to multiple 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 can change over time. In one or more illustrative examples, the bandwidth of the virtual communication network 126 can be modified based on the amount of data to be transmitted 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 to at least one of files or objects stored by the local network data repository 118 and the remote data repository 120 in response to a request generated by at least one of the computing device 116 or the bioinformatics system 114.

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

[0080] In at least some examples, the memory resources used to store patient data 110 can be larger than the memory resources used to store patient metadata 111. In various examples, the memory resources used to store patient data 110 can be twice as large, five times as large, ten times as large, twenty times as large, 50 times as large, up to 100 times as large, up to 1000 times as large, up to 10,000 times as large, up to 100,000 times as large, or more than the memory resources used to store patient metadata 112. In one or more illustrative examples, patient data 110 can include DNA sequences and expression values ​​for multiple genomic regions (such as tens, hundreds, or thousands of genomic regions) for an individual patient and can consume up to hundreds of gigabytes of memory resources. In one or more additional illustrative examples, the patient metadata 112 for an individual patient can include sample identifiers, batch information, and patient characteristics, which can be stored in a text file consuming approximately hundreds of kilobytes of memory resources, although in at least some cases, the amount of memory resources used to store the patient metadata 112 for an individual patient can be larger, such as on the order of tens to hundreds of megabytes or more.

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

[0082] In various examples, computing device 116 may be configured to generate a request to at least one of: transfer or access at least a portion of patient data 110 and at least a portion of patient metadata 112. The request to at least one of: transfer or access at least a portion of patient data 110 and at least a portion of patient metadata 112 may be generated to analyze at least a portion of patient data 110 and / or at least a portion of patient metadata 112 using bioinformatics system 114. In one or more illustrative examples, the request to at least one of transfer or access at least a portion of patient data 110 and at least a portion of patient metadata 112 may be generated based on one or more application programming interface (API) calls of database management system 128. In response to determining that the number of requests to at least one of transfer or access data stored by local network data repository 118 and by remote data repository 120 exceeds a threshold amount of memory resources, life sciences service provider 102 may send a request to network management system 124 to temporarily increase an amount of network resources of physical communication network 122 allocated by network management system 124 to life sciences service provider 102. In these cases, 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 can be transferred to and / or from the remote data repository 120. In one or more examples, the amount of network resources allocated by the network management system 124 to the physical communication network 122 (such as the virtual communication network 126) of the life sciences service provider 102 can be increased to facilitate transferring and / or accessing at least one of the patient data 110 or the patient metadata 112 at 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 can be reduced. In this manner, the network resources of the network management system 124 are efficiently allocated. That is, because the amount of network resources used to transmit at least a portion of the patient metadata 112, and in some cases, at least a portion of the patient data 110, between the remote data repository 120 and the life sciences service provider 102 is temporarily increased, the architecture 100 avoids allocating network resources that are not utilized by the life sciences service provider 102, and the unused network resources can be allocated to other entities that transmit 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 in some cases, at least a portion of the patient data 110, can be transferred to a remote data repository 120 for storage. In one or more additional examples, at least a portion of the patient metadata 112, and in some cases, at least a portion of the patient data 110, can 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 can be analyzed by the bioinformatics system 114. In one or more additional 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 can be associated with an increase in network resources allocated to the virtual communication network 126, and in cases where the amount of data transferred to the remote data repository 120 for storage is greater than the amount of data accessed for analysis, access to 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 can be transferred for analysis by the bioinformatics system 114 without increasing the network resources allocated to the virtual communication network 126. That is, the amount of data accessed by the bioinformatics system 114 for analysis may be a subset of the data transmitted to the remote data repository 120 for storage.

[0084] Figure 2 An example framework 200 for increasing the allocation of network resources during the transfer of data and metadata from local and remote data repositories is illustrated in accordance with one or more implementations. The framework 200 may include information about Figure 1 The life science service provider 102, computing device 116, local network data repository 118, remote data repository 120, physical communication network 122, network management system 124, and database management system 128 are depicted. Figure 2 In the illustrative example of FIG, life sciences service provider 102 includes a data access and control system 202 that monitors requests to transfer data between life sciences service provider 102 and at least one of local network data repository 118 or remote data repository 120. In one or more examples, data access and control system 202 can analyze requests to transfer data between life sciences service provider 102 and at least one of local network data repository 118 or remote data repository 120 in relation to a threshold data volume. In at least some examples, the threshold data volume can correspond to a data volume that increases the time to transfer the data and / or the data transfer rate to a level that life sciences service provider 102 deems too slow to facilitate efficient computing operations by life sciences service provider 102.

[0085] In various examples, the computing device 116 can generate a local data transfer request 204 to 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 can also generate a remote data transfer request 206 to 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 can correspond to at least one of accessing or storing at least one of the patient data 110 or the patient metadata 112.

[0086] Local data transfer requests 204 and remote data transfer requests 206 can be monitored by data access and control system 202. Data access and control system 202 can analyze local data transfer requests 204 and remote data transfer requests 206 relative to a threshold amount of data to be transferred. If the amount of data to be transferred is at least the threshold amount, data access and control system 202 can generate one or more bandwidth modification requests 208. One or more bandwidth modification requests 208 can indicate a request to indicate an amount of network resources to be allocated to physical communication network 122 of life sciences service provider 102. Additionally, one or more bandwidth modification requests 208 can indicate an amount of time for which network management system 124 is to increase the allocation of network resources of physical communication network 122 to life sciences service provider 102. In this manner, a virtual communication network dedicated to life sciences service provider 102 can be increased. In one or more illustrative examples, one or more bandwidth modification requests 208 can include one or more calls to application programming interface (API) 210. The API 210 may be provided by the network management system 124 and 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 allocate to the life science service provider 102 .

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

[0088] The data access and control system 202 can send a data transfer request 214 to the database management system 128 related to at least one of the local data transfer request 204 or the remote data transfer request 206 that triggered the bandwidth modification request 208. One or more data transfer requests 214 can correspond to additional APIs provided by the database management system 128. In one or more examples, the data access and control system 202 can 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 can 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 allocation of network resources of the physical communication network 122 to the life sciences service provider 102 has occurred.

[0089] In response to one or more data transfer requests 214, database management system 128 may transfer patient data 110 between at least one of local network data repository 118 or remote data repository and life science service provider 102. Additionally, in response to one or more data transfer requests 214, database management system 128 may transfer patient metadata 112 between at least one of local network data repository 118 or remote data repository 120 and life science service provider 102. When transferring data from life science service provider 102 to at least one of local network data repository 118 or remote data repository 120, one or more data transfer requests 214 may indicate a storage location for the data. In one or more illustrative examples, the storage location may indicate one or more specific portions of local network data repository 118 and / or remote data repository 120 or of local network data repository 118 and / or remote data repository 120 where the data being transferred is stored. In a scenario where the life sciences service provider 102 is retrieving data from 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 indicate 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, life sciences service provider 102 may obtain a quantity of patient data 110 and a quantity of patient metadata 112. In various examples, a greater amount of memory resources may be allocated to store patient data 110 than patient metadata 112. In one or more additional examples, life sciences service provider 102 may access patient metadata 112 less frequently than patient data 110. In one or more examples, at least a portion of patient data 110 may be stored by local network data repository 118, and patient metadata 112 may be stored by remote data repository 120. In at least some examples, at least a portion of patient data 110 may be stored by remote data repository 120.

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

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

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

[0094] Figure 3is a flow chart of an example process 300 for increasing the allocation of network resources during the transmission of system data and metadata from local and remote data repositories, according to one or more implementations. 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 that utilizes network resources to at least one of transmit information or store information in at least one of a local data repository or a remote data repository. In one or more examples, the entity may include a service provider, an academic institution, a non-profit entity, a research entity, a commercial enterprise, or one or more combinations thereof. In one or more illustrative examples, the system data may be generated by multiple sensors and include meteorological data, molecular data, transportation-related data (such as data generated by autonomous vehicle sensors), geological data, and the like. The system data may also include media content, communication data, financial data, and the like. The metadata may include timing information associated with the data, source information associated with the data, identification information, priority information, destination information, parameters used to generate the data, and the like.

[0095] In one or more additional illustrative examples, system data and metadata can be associated with a patient being tested for or treated for at least one of one or more biological conditions. The patient data can include genomic information for a plurality of subjects. In one or more examples, the genomic information can be derived from one or more samples obtained from the plurality of subjects. In one or more illustrative examples, the genomic information can be derived from cell-free nucleic acids obtained from one or more body fluid samples of the plurality of subjects. The patient metadata can include information associated with the patient data, such as information about the subject from which the patient data was derived, information about a device for generating at least a portion of the patient data from the sample, information associated with the sample, one or more combinations thereof, and the like.

[0096] Process 300 may also include causing the first amount of system data to be stored in a local data repository at operation 304. The local data repository may be at least one of controlled, maintained, or managed by an entity that utilizes network resources to at least one of transmit information or 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] Additionally, at operation 306, process 300 may include generating a first bandwidth modification request to modify the 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, the amount of memory storage space in the remote data repository to be occupied by the portion of metadata and / or the portion of system data may be determined and analyzed relative 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 system data or the portion of 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 at least one of controls, maintains, or manages the remote data repository. In one or more examples, the second amount of network resources may correspond to a minimum transmission rate for metadata from the service provider to the remote data repository via the physical communication network. In one or more additional examples, the second amount of network resources may correspond to transmitting at least one of the portion of system data or the portion of metadata from the service provider to the remote data repository in less than a threshold amount of time.

[0098] Furthermore, process 300 may include, at operation 308, causing a second amount of data to be transferred to a remote data repository concurrently with allocating the second amount of network resources 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 may be transferred from the entity to the remote data repository during a period of time during which the amount of network resources allocated to the life sciences service provider has been increased 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 a portion of the system data or a portion of the metadata has been stored by the remote data repository, a request may be generated to retrieve a specified portion of the system data and a portion of the metadata corresponding to the specified portion of the system data. In these scenarios, a request may be sent to a 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 entity may then obtain the portion of the system data and the portion of the metadata. In the case where the entity is a life science service provider and / or a research entity, at least one of the system data or the metadata may then be analyzed.

[0100] In at least some examples where the system data includes patient data, an analysis can be performed on a portion of the patient data and a portion of the patient metadata. The analysis can determine one or more characteristics of the subject from which the portion of the patient data and the portion of the patient metadata originate. In one or more examples, the one or more characteristics include one or more genomic mutations present in nucleic acid derived from a sample obtained from the subject. The nucleic acid can 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 resistance to a treatment provided to the subject in conjunction with a biological condition present in the subject. In various examples, the biological condition corresponds to a form of cancer. In one or more additional examples, the analysis can include determining a recommendation for a treatment to be provided to the subject to treat the biological condition present in the subject.

[0101] In one or more additional examples, where the system data includes user data related to users of at least one of a media content provider, a telecommunications company, or a content streaming service, in these scenarios, characteristics of the users can be determined through analysis, and the analysis can include determining recommendations for media content to provide to 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 the network resources of the physical communication network allocated 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 be returned to the previous allocation of network resources before the metadata is transmitted to the remote data repository.

[0103] Figure 4 is a block diagram illustrating components of a machine 400 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, according to one or more example implementations. Specifically, Figure 4A schematic diagram of a machine 400 in the example form of a computer system is shown within which instructions 402 (e.g., software, programs, applications, applet, application program (app), or other executable code) may be executed to cause the machine 400 to perform any one or more of the methodologies discussed herein. Thus, the instructions 402 may be used to implement the 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 manner described. In alternative implementations, the machine 400 may operate as a standalone device or may be coupled (e.g., networked) to other machines. In a networked deployment, the machine 400 may operate in the capacity of a server or a client machine in server-client network environment, or as a peer machine in a peer-to-peer (or distributed) network environment. The machine 400 may include, but is not limited to, 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 cellular phone, a smart phone, a mobile device, a wearable device (e.g., a smart watch), a smart home device (e.g., a smart appliance), other smart devices, a network appliance, a network router, a network switch, a network bridge, or any machine capable of executing instructions 402, sequentially or otherwise, that specify actions to be taken by the machine 400. Furthermore, while only a single machine 400 is shown, the term "machine" should also be understood to include a collection of machines that individually or jointly execute the instructions 402 to perform any one or more of the methodologies discussed herein.

[0104] Machine 400 may include a processor 404, memory / storage 406, and I / O components 408, which may be configured to communicate with each other, such as via a bus 410. In an example implementation, 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 that 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 concurrently. Although Figure 4More than one processor 404 is shown, but the machine 400 may include a single processor 412 having a single core, a single processor 412 having multiple cores (eg, a multi-core processor), more than one processor 412, 414 having a single core, more than one processor 412, 414 having multiple cores, or any combination thereof.

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

[0106] I / O components 408 may include a variety of components to receive input, provide output, generate output, transmit information, exchange information, capture measurements, and the like. The specific I / O components 408 included in a particular machine 400 will depend on the type of machine. For example, a portable machine 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 should be understood that components 408 may include Figure 5 Many other components are not shown in the figure. The grouping of I / O components 408 by function is intended solely to simplify the following discussion and is in no way limiting. In various example implementations, I / O components 408 may include user output components 420 and user input components 422. User output components 420 may include visual components (e.g., displays such as plasma display panels (PDPs), light-emitting diode (LED) displays, liquid crystal displays (LCDs), projectors, or cathode ray tubes (CRTs)), acoustic components (e.g., speakers), tactile components (e.g., vibration motors, resistive mechanisms), other signal generators, and the like. User input components 422 may include alphanumeric input components (e.g., keyboards, touch screens configured to receive alphanumeric input, optical keyboards, or other alphanumeric input components), point-based input components (e.g., mice, touchpads, trackballs, joysticks, motion sensors, or other pointing tools), tactile input components (e.g., physical buttons, touch screens that provide location or force of touch or touch gestures, or other tactile input components), audio input components (e.g., microphones), and the like.

[0107] In another example implementation, the I / O component 408 may include a biometric component 424, a motion component 426, an environmental component 428, or a position component 430, as well as a wide range of other components. For example, the biometric component 424 may include components for detecting expressions (e.g., hand expressions, facial expressions, vocal expressions, body gestures, or eye tracking), measuring biosignals (e.g., blood pressure, heart rate, body temperature, perspiration, or brain waves), identifying people (e.g., voice recognition, retinal recognition, facial recognition, fingerprint recognition, or electroencephalogram-based recognition), etc. The 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 environment component 428 may include, for example, an illumination 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 that detects hazardous gas concentrations or measures pollutants in the atmosphere for safety purposes), or other components that can provide indications, measurements, or signals corresponding to the surrounding physical environment. The location component 430 may include a location 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] Communication can be implemented using a variety of technologies. I / O components 408 may include a communication component 432 operable to couple machine 400 to a network 434 or device 436. For example, communication component 432 may include a network interface component or other suitable device for interfacing with network 434. In other examples, communication component 432 may include a wired communication component, a wireless communication component, a cellular communication component, a near-field communication (NFC) component, a Bluetooth® component (e.g., Bluetooth® Low Energy), a Wi-Fi® component, and other communication components that provide communication via other modalities. Device 436 may be another machine 400 or any of a variety of peripheral devices (e.g., a peripheral device coupled via USB).

[0109] Furthermore, the communication component 432 can detect an identifier or include a component operable to detect an identifier. For example, the communication component 432 can include a radio frequency identification (RFID) tag reader component, an NFC smart tag detection component, an optical reader component (e.g., an optical sensor that detects one-dimensional barcodes such as Universal Product Code (UPC) barcodes, multi-dimensional barcodes such as Quick Response (QR) codes, Aztec codes, Data Matrix, Dataglyph, MaxiCode, PDF417, Ultra Code, UCC RSS-2D barcodes, and other optical codes), or an acoustic detection component (e.g., a microphone for identifying an audio signal from a tag). Furthermore, various information can be derived via the communication component 432, such as location via Internet Protocol (IP) geolocation, location via Wi-Fi® signal triangulation, location via detection of an NFC beacon signal that can indicate a specific location, and the like.

[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 of partitioning or modularization that provide specific processing or control functionality. Components may be combined with other components via their interfaces to perform a machine process. A component may be a packaged functional hardware unit designed for use with other components or may be part of a program that generally performs specific ones of the related functions. A component may constitute 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 some physical manner. In various example implementations, one or more computer systems (e.g., a stand-alone computer system, a client computer system, or a server computer system) or one or more hardware components of a computer system (e.g., a processor or a group of processors) may be configured by software (e.g., an application or portion of an application) as a hardware component that operates to perform certain operations described herein.

[0111] Hardware components may also be implemented mechanically, electronically, or any suitable combination thereof. For example, a hardware component may include dedicated circuitry or logic that is 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 that is temporarily configured by software to perform certain operations. For example, a hardware component may include software executed by general-purpose processor 404 or another programmable processor. Once configured by such software, the hardware component becomes a specific machine (or a specific component of machine 400), uniquely customized to perform the configured functions, and is no longer a general-purpose processor 404. It should be understood that the decision to implement a hardware component mechanically, in dedicated and permanently configured circuitry, or in temporarily configured circuitry (e.g., configured by software) may be driven by cost and time considerations. Therefore, the phrase "hardware component" (or "hardware-implemented component") should be understood to include a tangible entity, whether physically constructed, permanently configured (e.g., hardwired), or temporarily configured (e.g., programmed), that operates in a certain manner or performs certain operations described herein. Considering implementations where hardware components are temporarily configured (e.g., programmed), each hardware component need not be configured or instantiated at any one instance in time. For example, where the hardware components include a general-purpose processor 404 that is configured by software as a special-purpose processor, the general-purpose processor 404 can be configured as different special-purpose processors (e.g., including different hardware components) at different times. The software configures the specific processors 412, 414 or processor 404 accordingly, e.g., to constitute a specific hardware component at one instance in time and to constitute a different hardware component at a different instance in time.

[0112] Hardware components can provide information to other hardware components and receive information from other hardware components. Thus, the described hardware components can be considered to be communicatively coupled. Where more than one hardware component is present simultaneously, communication can be achieved through signal transmission between the two or more hardware components (e.g., via appropriate circuitry and buses). In implementations where more than one hardware component is configured or instantiated at different times, communication between these hardware components can be achieved, for example, by storing and retrieving information in memory structures accessible to more than one hardware component. For example, one hardware component can perform an operation and store the output of the operation in a memory device to which it is communicatively coupled. Another hardware component can then access the memory device at a later time to retrieve and process the stored output.

[0113] Hardware components can also initiate communications with input or output devices and can operate on resources (e.g., collections of information). The various operations of the example methods described herein can be performed at least in part by one or more processors 404, which are temporarily configured (e.g., via software) or permanently configured to perform the relevant operations. Whether temporarily or permanently configured, such processors 404 can constitute processor-implemented components that operate to perform one or more operations or functions described herein. As used herein, "processor-implemented components" refers to hardware components implemented using one or more processors 404. Similarly, the methods described herein can be at least partially implemented by a processor, with specific processors 412, 414, or processor 404 being examples of hardware. For example, at least some of the operations of the methods can be performed by one or more processors 404 or processor-implemented components. In addition, one or more processors 404 can also operate to support the performance of related operations in a "cloud computing" environment or as "software as a service" (SaaS). For example, at least some operations may be performed by a group of computers (for example, a machine 400 including a processor 404), which may be accessed via a network 434 (e.g., the Internet) and via one or more appropriate interfaces (e.g., APIs). The performance of certain operations may be distributed among the processors, not only residing within a single machine 400, but also deployed across many machines. In some example implementations, the processor 404 or a processor-implemented component may be located in a single geographic location (e.g., in a home environment, an office environment, or within a server farm). In other example implementations, the processor 404 or a processor-implemented component may be distributed across many geographic locations.

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

[0115] exist Figure 5 In the example architecture of , software architecture 502 can be conceptualized as a stack of layers, where each layer provides specific functionality. For example, software architecture 502 may include layers such as operating system 514, library 516, framework / middleware 518, application 520, and presentation layer 522. Operationally, application 520 or other components within a layer may invoke API call 524 through the software stack and receive message 526 in response to API call 524. The illustrated layers are representative in nature, and not all software architectures will have all layers. For example, some mobile or special-purpose operating systems may not provide framework / middleware 518, while other operating systems may provide such a layer. Other software architectures may include additional or different layers.

[0116] The operating system 514 can 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 serve as an abstraction layer between the hardware layer and other software layers. For example, the kernel 528 may be responsible for memory management, processor management (e.g., scheduling), component management, networking, security settings, and so on. Services 530 may provide other common services to other software layers. Drivers 532 may be responsible for controlling or interfacing with the underlying hardware. For example, depending on the hardware configuration, drivers 532 may include display drivers, camera drivers, Bluetooth® drivers, flash memory drivers, serial communication drivers (e.g., Universal Serial Bus (USB) drivers), Wi-Fi® drivers, audio drivers, power management drivers, and so on.

[0117] Libraries 516 provide common infrastructure used by applications 520, other components, or at least one of the layers. Libraries 516 provide functionality that allows other software components to perform tasks more easily than by directly interfacing with underlying operating system 514 functionality (e.g., kernel 528, services 530, drivers 532). Libraries 516 may include system libraries 534 (e.g., the C standard library), which may provide functionality such as memory allocation functions, string manipulation functions, and mathematical functions. Furthermore, libraries 516 may include API libraries 536, such as media libraries (e.g., libraries that support the rendering and manipulation of various media formats such as MPEG4, H.264, MP3, AAC, AMR, JPG, and PNG), graphics libraries (e.g., the OpenGL framework for rendering two-dimensional and three-dimensional graphics content on a display), database libraries (e.g., SQLite, which provides various relational database functions), and web libraries (e.g., WebKit, which provides web browsing functionality). Libraries 516 may also include a variety of other libraries 538 to provide numerous other APIs to applications 520 and other software components / modules.

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

[0119] Applications 520 include built-in applications 540 and third-party applications 542. Representative examples of 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 may include applications developed by entities other than the vendor of a particular platform using an ANDROID™ or iOS™ software development kit (SDK) and may be mobile software running on a mobile operating system such as iOS™, ANDROID™, Windows® Phone, or other mobile operating systems. Third-party applications 542 may invoke API calls 524 provided by a mobile operating system (such as operating system 514) to facilitate the functionality described herein.

[0120] Applications 520 can create a UI to interact with the user of the system using built-in operating system functionality (e.g., kernel 528, services 530, drivers 532), libraries 516, and framework / middleware 518. Alternatively or additionally, in some systems, interaction with the user can occur through a presentation layer, such as presentation layer 522. In these systems, the application / component "logic" can be separated from the various 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 executed by one or more processors, such that the operations of the processes may be performed in part or in whole by functional components of one or more computer systems. Thus, in some cases, the computer-implemented processes described herein are examples for reference. However, in other implementations, at least some of the operations of the computer-implemented processes described herein may be deployed on various other hardware configurations. Thus, the computer-implemented processes described herein are not intended to be limited to those described herein. Figure 4 and Figure 5 The systems and configurations described herein may be implemented in whole or in part by one or more additional systems and / or components.

[0122] Although the flowcharts described herein may illustrate operations as a sequential process, many operations may be performed in parallel or concurrently. Furthermore, the order of the operations may be rearranged. When the operations of a process are completed, it is terminated. A process may correspond to a method, procedure, 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 system.

[0123] As used herein, a component may refer to a device, physical entity, or logic with boundaries defined by function or subroutine calls, branch points, APIs, or other techniques for partitioning or modularizing specific processing or control functionality. Components can be combined with other components via their interfaces to execute a machine process. A component can be a packaged functional hardware unit designed for use with other components, or it can be part of a program that generally performs specific functions among related functions. A component can constitute 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 can be configured or arranged in some physical manner. In various example implementations, one or more computer systems (e.g., stand-alone computer systems, client computer systems, or server computer systems) or one or more hardware components of a computer system (e.g., a processor or a group of processors) can be configured by software (e.g., an application or application portion) as a hardware component that operates to perform certain operations described herein.

[0124] Should be understood that, as long as teaching remains operable, the various steps used in the method of this teaching can be performed in any order and / or simultaneously.In addition, should be understood that, as long as this teaching remains operable, the apparatus and method of this teaching can include any number or all of the described implementations.

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

[0126] Various implementations of systems, devices, and methods have been described herein. These implementations are provided as examples only and are not intended to limit the scope of the claimed invention. Furthermore, it should be understood that the various features of the described implementations can be combined in various ways to produce many additional implementations. Furthermore, while various materials, sizes, shapes, configurations, and positions have been described for use with the disclosed implementations, other materials, sizes, shapes, configurations, and positions, etc., other than those disclosed, may be utilized without exceeding the scope of the claimed invention.

[0127] A person of ordinary skill in the relevant art will recognize that an implementation may include fewer features than shown in any individual implementation described above. The implementations described herein are not meant to be an exhaustive presentation of the ways in which various features may be combined. Thus, implementations are not mutually exclusive combinations of features; rather, as understood by a person of ordinary skill in the art, implementations may include combinations of different individual features selected from different individual implementations. Furthermore, unless otherwise stated, elements described with respect to one implementation may be implemented in other implementations even if not described in those implementations. Although a dependent claim may refer in a claim to a specific combination with one or more other claims, other implementations may also include combinations of a dependent claim with the subject matter of each other dependent claim, or combinations of one or more features with other dependent or independent claims. Such combinations are proposed herein unless it is stated that a specific combination is not intended. Furthermore, it is intended that features of one claim be included in any other independent claim even if that claim is not directly dependent upon the independent claim.

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

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

[0130] Although implementations have been described with reference to specific example implementations, it will be apparent that various modifications and changes may be made to these implementations without departing from the broader spirit and scope of the present disclosure. Accordingly, the description and drawings are to be regarded as illustrative and not restrictive. The drawings forming a part of this application show, by way of illustration and not limitation, specific implementations in which the subject matter may be implemented. The implementations shown are described in sufficient detail to enable those skilled in the art to implement the teachings disclosed herein. Other implementations may be used and derived therefrom so that structural and logical substitutions and changes may be made without departing from the scope of the present disclosure. Accordingly, this detailed description should not be construed in a restrictive sense, and the scope of the various implementations is limited solely by the appended claims, along with the full range of equivalents to which such claims are entitled.

[0131] Although specific implementations have been illustrated and described herein, it should be understood that any arrangement calculated to achieve the same purpose may be substituted for the specific implementations shown. This disclosure is intended to cover any and all modifications or variations of the various implementations. Combinations of the above implementations, as well as other implementations not specifically described herein, will be apparent to those skilled in the art after reading the above description.

[0132] In this document, the terms "a" or "an," as is common in patent documents, are used to include one or more than one, independent of any other examples or uses of "at least one" or "one or more." In this document, the term "or" is used to refer to a non-exclusive or, so that, unless otherwise stated, "A or B" includes "A but not B," "B but not A," and "A and B." In this document, the terms "including" and "in which" are used as the plain-English equivalents of the respective terms "comprising" and "wherein." Furthermore, in the appended claims, the terms "including" and "comprising" are open-ended, meaning that systems, user equipment (UEs), articles, compositions, formulations, or processes that include elements other than the elements listed after such terms in a claim are still considered to fall within the scope of the claim. Furthermore, in the appended 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. A method comprising: 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; causing, by the computing system, the first amount of data to be stored by a local network data repository 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 network resources allocated to a physical communication network of the life science 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; concurrently with allocating the second amount of network resources to the life sciences service provider, causing, by the computing system, at least a portion of the second amount of data to be transmitted to a remote data repository; determining, by the computing system, that transmission of the at least a portion of the second amount of data to the remote data repository is complete; and A second bandwidth modification request is generated by the computing system to modify network resources allocated to the physical communication network of the life sciences service provider from the second amount to the first amount.

2. The method according to claim 1, comprising: 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 corresponding to the portion of the patient data; sending, by the computing system, a request to a database management system for access to 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; and The portion of the patient data and the one or more portions of the patient metadata are obtained by the computing system.

3. The method according to claim 2, comprising: performing, by a bioinformatics system implemented by the computing system, an analysis of the portion of the patient data and the one or more portions of the patient metadata; and 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 are determined, by the computing system and based on the analysis.

4. The method according to claim 3, wherein: The one or more characteristics include 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.

5. The method of claim 3, wherein the one or more characteristics comprise 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 condition corresponds to a form of cancer.

7. The method of claim 3, wherein the analyzing comprises determining a recommendation for a treatment to be provided to the subject to treat a biological condition present in the subject.

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

9. The method according to claim 1, comprising: determining, by the computing system, an amount of memory storage space for storing at least a portion of the patient metadata; and determining, by the computing system, that the amount of memory storage space is at least a threshold amount of memory storage space; The first bandwidth modification request is generated based on the amount of the memory storage space being at least a threshold amount of the memory storage space.

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

11. The method of claim 1 , wherein the second amount of network resources corresponds to transmitting 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. A system comprising: one or more hardware processing units; and One or more computer-readable storage media storing computer-executable instructions that, when executed by the one or more hardware processing units, cause the system to perform operations including: obtaining, by a life science service provider, a first data volume comprising patient data and a second data volume comprising patient metadata, the patient data comprising genomic information for a plurality of subjects; causing the first amount of data to be stored by a local network data repository at least one of controlled, maintained, or managed by the life sciences service provider; generating a first bandwidth modification request to modify network resources allocated to a physical communication network of the life science 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; concurrently with allocating the second amount of network resources to the life sciences service provider, causing at least a portion of the second amount of data to be transmitted to a remote data repository; determining that transmission of the at least a portion of the second amount of data to the remote data repository is complete; and A second bandwidth modification request is generated to modify network resources allocated to the physical communication network of the life sciences service provider from the second amount to the first amount.

14. The system according to claim 13, wherein: The one or more computer-readable storage media store additional computer-executable instructions that, when executed by the one or more hardware processing units, cause the system to perform additional operations including: receiving a request to retrieve a portion of the patient data; determining one or more portions of the patient metadata corresponding 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; and The portion of the patient data and the one or more portions of the patient metadata are obtained.

15. The system according to claim 14, wherein: The one or more computer-readable storage media store additional computer-executable instructions that, when executed by the one or more hardware processing units, cause the system to perform additional operations including: performing, by a bioinformatics system of the life sciences service provider, analysis of the portion of the patient data and the one or more portions of the patient metadata; and 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 are determined based on the analysis.

16. The system of claim 15, wherein: The one or more characteristics include 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.

17. The system of claim 15, wherein the one or more characteristics comprise 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 condition corresponds to a form of cancer.

19. The system of claim 15, wherein: The one or more computer-readable storage media store additional computer-executable instructions that, when executed by the one or more hardware processing units, cause the system to perform additional operations including: As part of the analysis, a recommendation is determined for a treatment to be provided to the subject to treat the biological condition present in the subject.

20. The system of claim 13, wherein: The one or more computer-readable storage media store additional computer-executable instructions that, when executed by the one or more hardware processing units, cause the system to perform additional operations including: In conjunction with transmitting at least a portion of the patient metadata to the remote data repository, a portion of the patient data is transmitted to the local network data repository.

21. The system of claim 13, wherein: The one or more computer-readable storage media store additional computer-executable instructions that, when executed by the 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 The first bandwidth modification request is generated based on the amount of the memory storage space being at least a threshold amount of the memory storage space.

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

23. The system of claim 13, wherein the second amount of network resources corresponds to transmitting 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, cause a system to perform operations comprising: obtaining, by a life science service provider, a first data volume comprising patient data and a second data volume comprising patient metadata, the patient data comprising genomic information for a plurality of subjects; causing the first amount of data to be stored by a local network data repository at least one of controlled, maintained, or managed by the life sciences service provider; generating a first bandwidth modification request to modify network resources allocated to a physical communication network of the life science 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; concurrently with allocating the second amount of network resources to the life sciences service provider, causing at least a portion of the second amount of data to be transmitted to a remote data repository; determining that transmission of the at least a portion of the second amount of data to the remote data repository is complete; and A second bandwidth modification request is generated to modify network resources allocated to the physical communication network of the life sciences service provider from the second amount to the first amount.

26. The one or more non-transitory computer-readable storage media of claim 25, comprising additional computer-executable instructions that, when executed by the one or more hardware processing units, cause the system to perform additional operations including: receiving a request to retrieve a portion of the patient data; determining one or more portions of the patient metadata corresponding 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; and The portion of the patient data and the one or more portions of the patient metadata are obtained.

27. The one or more non-transitory computer-readable storage media of claim 26, comprising additional computer-executable instructions that, when executed by the one or more hardware processing units, cause the system to perform additional operations including: performing, by a bioinformatics system of the life sciences service provider, analysis of the portion of the patient data and the one or more portions of the patient metadata; and 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 are determined based on the analysis.

28. The one or more non-transitory computer-readable storage media of claim 27, wherein: The one or more characteristics include 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.

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

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. The one or more non-transitory computer-readable storage media of claim 27, comprising additional computer-executable instructions that, when executed by the one or more hardware processing units, cause the system to perform additional operations including: As part of the analysis, a recommendation is determined for a treatment to be provided to the subject to treat the biological condition present in the subject.

32. The one or more non-transitory computer-readable storage media of claim 25, comprising additional computer-executable instructions that, when executed by the one or more hardware processing units, cause the system to perform additional operations including: In conjunction with transmitting at least a portion of the patient metadata to the remote data repository, a portion of the patient data is transmitted to the local network data repository.

33. The one or more non-transitory computer-readable storage media of claim 25, comprising additional computer-executable instructions that, when executed by the 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; in, 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. The one or more non-transitory computer-readable storage media of claim 25, wherein: The second amount of network resources corresponds to a minimum transmission rate of at least a portion of the patient metadata from the life sciences service provider to the remote data repository via the physical communication network.

35. The one or more non-transitory computer-readable storage media of claim 25, wherein: The second amount of network resources corresponds to transmitting 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. 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 include one or more calls to an application programming interface (API) of a cloud storage service provider.

Images