<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Healthcare Data Strategy | Jason Thomas, PhD</title><link>https://jasonthomas.io/tag/healthcare-data-strategy/</link><atom:link href="https://jasonthomas.io/tag/healthcare-data-strategy/index.xml" rel="self" type="application/rss+xml"/><description>Healthcare Data Strategy</description><generator>Wowchemy (https://wowchemy.com)</generator><language>en-us</language><copyright>© 2021 Jason Thomas, PhD</copyright><lastBuildDate>Mon, 01 Jun 2026 00:00:00 +0000</lastBuildDate><image><url>https://jasonthomas.io/media/icon_hu0b7a4cb9992c9ac0e91bd28ffd38dd00_9727_512x512_fill_lanczos_center_3.png</url><title>Healthcare Data Strategy</title><link>https://jasonthomas.io/tag/healthcare-data-strategy/</link></image><item><title>Regulated Healthcare Data &amp; MLOps Platform</title><link>https://jasonthomas.io/project/regulated-healthcare-data-mlops-platform/</link><pubDate>Mon, 01 Jun 2026 00:00:00 +0000</pubDate><guid>https://jasonthomas.io/project/regulated-healthcare-data-mlops-platform/</guid><description>&lt;p>I lead healthcare data operations and AI/MLOps platform strategy for medical-device R&amp;amp;D, translating product roadmaps, clinical needs, engineering needs, regulatory constraints, and business priorities into reusable data products and platform capabilities.&lt;/p>
&lt;p>Public-safe scope includes:&lt;/p>
&lt;ul>
&lt;li>Building a distributed platform function across data sourcing, curation, annotation, data/ML engineering, infrastructure, MLOps, stewardship, governance, and clinical informatics.&lt;/li>
&lt;li>Translating product roadmaps into data demand/supply models, labeled and unlabeled data requirements, acquisition and annotation priorities, fit-for-purpose criteria, platform roadmaps, investment logic, success metrics, and executive dashboards.&lt;/li>
&lt;li>Supporting 100+ developers, analysts, and product AI/algorithm teams through governed data access, de-identification/privacy controls, observability, audit logging, and reusable data-serving patterns.&lt;/li>
&lt;li>Architecting lakehouse and MLOps foundations for DICOM-linked clinical/imaging data, real-world evidence, and multimodal medical data.&lt;/li>
&lt;li>Establishing practices for lineage, reproducibility, dataset/model versioning, data contracts, train/validation/test governance, quality gates, and blinded held-out evaluation sets.&lt;/li>
&lt;li>Making build-vs-integrate decisions across internal platforms, vendor tools, licensed data, cataloging, warehouse/BI, and lakehouse architecture.&lt;/li>
&lt;/ul>
&lt;p>This work reflects the operating model I am most interested in scaling: data strategy, partnerships, platform engineering, governance, and validation coming together so healthcare AI programs can become durable assets rather than one-off projects.&lt;/p></description></item><item><title>Healthcare Data Partnerships to AI-Ready Assets</title><link>https://jasonthomas.io/project/healthcare-data-partnerships-ai-ready-assets/</link><pubDate>Fri, 15 May 2026 00:00:00 +0000</pubDate><guid>https://jasonthomas.io/project/healthcare-data-partnerships-ai-ready-assets/</guid><description>&lt;p>Healthcare AI programs depend on much more than model development. The hard part is often deciding which labeled and unlabeled data is worth pursuing, how to structure collaboration, and how to make the resulting assets reusable, governed, and fit for training and evaluation.&lt;/p>
&lt;p>My work in this area includes:&lt;/p>
&lt;ul>
&lt;li>Prioritizing data acquisition, annotation, and platform investments by clinical-domain fit, downstream model value, partner readiness, technical feasibility, fit-for-purpose criteria, regulatory constraints, cost, and reuse potential.&lt;/li>
&lt;li>Driving data access paths, data-use agreements/SOWs, contribution standards, licensing decisions, vendor/tooling selection, active-learning and annotation operations, pricing and staged-pilot paths, and release/reuse planning.&lt;/li>
&lt;li>Aligning data contributors, clinical experts, data stewards, platform engineers, AI/algorithm teams, regulatory stakeholders, and business leaders around durable data products.&lt;/li>
&lt;li>Establishing public-safe operating patterns for de-identification, provenance, access, quality, data lifecycle ownership, and governance.&lt;/li>
&lt;/ul>
&lt;p>The goal is to turn collaborations into data assets that can feed multiple programs over time: product AI, algorithm validation, real-world evidence, post-market surveillance, clinical informatics, and future multimodal/physical-AI workflows.&lt;/p></description></item></channel></rss>