Customer case study # Ambry Genetics governs clinical data and builds a PHI-free environment with Collate [Book a Demo](/contact-sales) 30+ years Of hereditary cancer data brought under one governance platform 11,000+ Data assets governed across six PHI-free MySQL databases in the first production environment 29 PHI tags Classification tags applied across all source data assets through Collate automations ![](data:image/svg+xml,%3csvg%20xmlns=%27http://www.w3.org/2000/svg%27%20version=%271.1%27%20width=%27150%27%20height=%2727%27/%3e)![Ambry Genetics Logo](/_next/image?url=%2Fimages%2FcaseStudy%2Fambry%2Fambry-logo.webp&w=384&q=75) “Using Collate, we were able to define this PHI environment, which involved metadata ingestion for six PHI-free MySQL DBs, a little over 11,000 total data assets. And then through Collate automations, specifically the tag and lineage functions, and with help from our compliance and legal departments in defining the tags and classification categories, we're able to now keep track of all identified PHI data elements and do reconciliations between the real production databases and the PHI-free comparable databases.” \- Dan Kostecki Data Engineer, Ambry Genetics (now part of Tempus AI) Industry Healthcare / Clinical Genetic Diagnostics Technologies MySQL, AWS, GCP, clinical reference databases, bioinformatics pipelines Ambry Genetics, a clinical genetic testing lab now part of Tempus AI with more than three decades of hereditary cancer data, manages cases that are living composites of biological and commercial information, all of which change over time. Keeping that mutable data coherent and compliant across two clinical organizations is not a small task. By adopting Collate's managed OpenMetadata service, Ambry's data engineering team built a clinical data product lifecycle and stood up a governed, de-identified production environment free of Protected Health Information (PHI) spanning 11,000+ data assets. ![](data:image/svg+xml,%3csvg%20xmlns=%27http://www.w3.org/2000/svg%27%20version=%271.1%27%20width=%271000%27%20height=%27563%27/%3e)![The dynamic attributes of a clinical case at Ambry Genetics](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7) ![The dynamic attributes of a clinical case at Ambry Genetics](/_next/image?url=%2Fimages%2FcaseStudy%2Fambry%2Fchallenge.webp&w=2048&q=75) ## Governing clinical data that never stops changing In clinical diagnostics, a patient case is rarely static. At Ambry, a case is a composite of biological data (genetic variants, gene-disease relationships) and non-biological commercial data (ordering physician, billing, reimbursement). Nearly every element can change over time. That mutability, layered on top of strict regulatory obligations, made coherent storage, discovery, and compliance a persistent challenge. Mutable case data Variants are constantly reevaluated as new clinical and academic evidence arrives; gene-disease relationships and underlying reference information (NCBI builds, ClinVar, HGMD, OMIM) also shift. Keeping a single case coherent as its biological facts change is a moving target. Changing commercial attributes Beyond the biology, ordering information changes too. Physicians in the ordering organization, patient billing, and reimbursement details all evolve. Unifying clinical and commercial data in the same case is already difficult and is compounded further by this change over time. PHI handling and regulatory load Clinical data at Ambry and Tempus is subject to CAP and CLIA lab accreditation standards, HIPAA/PHI protections, and FDA electronic-records regulations. Sharing data safely while meeting all of these requirements for protected health information sets a high bar for governance. No safe environment for research and metrics Business units had long requested a completely separate, standalone environment stripped of PHI: de-identified data they could use for research, internal metrics, and analysis without touching patient identifiers. ![](data:image/svg+xml,%3csvg%20xmlns=%27http://www.w3.org/2000/svg%27%20version=%271.1%27%20width=%271000%27%20height=%27563%27/%3e)![Ambry's clinical data product lifecycle on Collate](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7) ![Ambry's clinical data product lifecycle on Collate](/_next/image?url=%2Fimages%2FcaseStudy%2Fambry%2Fsolution-cdp.webp&w=2048&q=75) ## Governed clinical data products with Collate Ambry adopted Collate as the governance layer for a formal clinical data product lifecycle, running from one-line registration through metadata operations, quality, and consumption. The team leaned on its built-in automations to make each new data product coherent and compliant by default. Clinical data product lifecycle Every novel data product starts with a deliberately simple one-line registration, then moves through metadata operations and quality checks. Establishing roles, policies, and stewardship from the outset makes ingestion and creation of subsequent data products easier and lays the groundwork for governance. Lineage, profiler, and auto-classification agents Post-registration, Ambry leans on Collate's profiler, lineage, and auto-classification metadata agents. Lineage is essential for showing exactly where a data product's underlying data was sourced, when it was stored, its data types, and any constraints. Quality and regulatory checks Working with the assigned data steward and data product owner, teams fit quality dimensions to each registered data product and incorporate regulatory adherence directly in Collate, supporting the traceability and accuracy of every product against a FAIR-style framework (Findable, Accessible, Interoperable, Reusable). The PHI-free environment Using Collate, Ambry defined a de-identified, anonymized environment across six PHI-free MySQL databases and 11,000+ assets. With Collate's tag and lineage functions, and with classification and tag categories defined alongside compliance and legal, the team can track all identified PHI elements and reconcile the PHI-free databases against production. ![](data:image/svg+xml,%3csvg%20xmlns=%27http://www.w3.org/2000/svg%27%20version=%271.1%27%20width=%271000%27%20height=%27563%27/%3e)![Ambry's PHI-free environment across six MySQL databases and 11,000+ assets](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7) ![Ambry's PHI-free environment across six MySQL databases and 11,000+ assets](/_next/image?url=%2Fimages%2FcaseStudy%2Fambry%2Fresults-phifree.webp&w=2048&q=75) ## A trusted, PHI-free foundation for clinical research at scale Ambry's team describes the clinical data product concept as a significant improvement in how clinical data is stored, shared, and safely transmitted. The PHI-free environment is the clearest evidence of that shift and has changed how quickly researchers can get to the data they need to deliver new medical discoveries. Faster, safer access for research and metrics The new PHI-free environment empowers teams to quickly pull variant-level data for research, internal metrics, and analysis without risk to protected health information. It has been well received for saving people time in their work. One map of the data domains Data products give Ambry a high-level domain map and single source of truth, where internal domains and subdomains reconcile against their corresponding products, with lineage, classification, and version information supplied through the platform. PHI tracking and production reconciliation Reconciling the PHI-free databases against real production improved data quality checks and data fidelity between the two environments, so teams can trust that what they see in the PHI-free environment matches what production holds. Toward unified Ambry and Tempus governance Ambry is standing up a clinical data governing body and unifying the Ambry and Tempus governance approaches, as part of an ongoing effort to strengthen the functioning and storage of clinical data across their combined organizations. Are you ready to change how data works for you? Get Started Now [Get a Demo](/contact-sales)