TEMPORAL BIO DYNAMICS

Brand	Owner	Address	Description
TEMPORAL BIODYNAMICS	Flagship Labs 84, Inc.	55 Cambridge Parkway, Suite 800E Cambridge MA 02142	TEMPORAL BIO DYNAMICS;Software featuring artificial intelligence, computational methods, and machine learning models for data analysis in the fields of healthcare, wellness, system dysregulation, disease, biomedical, and genomic research; software featuring artificial intelligence, computational methods, and machine learning models for the design and characterization of biologic therapeutic products and drug analysis in drug discovery and development; software for the capture, collection, conversion, analysis, communication, processing, receiving, recording, storage and transmission of data, images, information and artificial intelligence in the fields of healthcare, biomedical and genomic research; scientific research, namely, research and analysis services in the fields of artificial intelligence and machine learning analytics and research relating to healthcare, wellness, system dysregulation, disease, and genomics; software incorporating artificial intelligence and machine learning models for collecting, analyzing, assessing, interpreting and predicting medical, health, transcriptional, genetic, genomic, pharmacogenomic, nutrigenomic, microbiomic, metabolomic, proteomic, biochemistry, and biomarker information, associations, conditions, outcomes, effects and risks; scientific research, namely, research and analysis services for the design and characterization of biologic therapeutic products;
	Where the owner name is not linked, that owner no longer owns the brand

Technical Examples

System and method for maintaining temporal data in data storage at the logical device level. Embodiments of the temporal volume manager may provide an interface that allows applications and/or application agents to communicate with the temporal volume manager to manage and keep track of the temporal information on one or more temporal volumes. Embodiments may provide an infrastructure for applications that work on the history of data such as temporal databases, versioning file-systems/repositories, data archives, and streaming media to manage temporal data. In one embodiment, if an application does not want to use the temporal volume directly, application agents may be used to access the temporal volume. Embodiments may provide I/O controlled, application-controlled, and/or periodic checkpointing of temporal data on the temporal volume. One embodiment may provide a mechanism for generating temporal images (e.g. point-in-time and slice-in-time images) of a temporal volume that may have their own independent history.