---
title: "Healthcare"
description: "11 posts about Healthcare, summarised, each linking to the original."
---

# Healthcare
> 11 posts about Healthcare, summarised, each linking to the original.

## Articles

### [How Flo Health built safer, more useful open models with Databricks AI Runtime](https://yomu.fyi/post/how-flo-health-built-safer-more-useful-open-models-with-databricks-ai.md)
- Company: [Databricks](https://yomu.fyi/company/databricks.md)
- Author: Vladislav Nedosekin, András Meczner, Julia Powell, Tejas Sundaresan, Michael Shtelma
- Published: Oct 12, 2026
- Type: Problem & solution

Flo Health, a women’s health app with 81 million monthly active users, aimed to improve generative AI responses for medical safety and usefulness while operating at scale. Relying on general-purpose models created cost, dependency, and domain-expertise limitations, so Flo built a post-training pipeline with Databricks AI Runtime. The team defined 26 AI judges across three categories: 12 medical-safety judges acting as hard constraints, 6 micro judges for nuanced behaviors, and 8 usefulness criteria. Using these judges as a reward signal, they generated over 15,000 synthetic questions from privacy-first principles and applied reinforcement fine-tuning with supervised fine-tuning (SFT) and direct preference optimization (DPO). After fine-tuning on 32 NVIDIA H100 GPUs using PyTorch and Fully Sharded Data Parallel (FSDP), medical safety scores rose from 34% to 61%, usefulness from 42% to 76%, and the combined metric improved nearly threefold to 47%.


### [Agentic antimicrobial resistance surveillance with AWS HealthOmics and Amazon Bedrock AgentCore](https://yomu.fyi/post/agentic-antimicrobial-resistance-surveillance-with-aws-healthomics-and.md)
- Company: [AWS](https://yomu.fyi/company/aws.md)
- Author: Nicolo Cosimo Albanese
- Published: Oct 12, 2026
- Type: Problem & solution

Antimicrobial resistance, estimated to cause 1.27 million direct deaths in 2019, requires surveillance that normally demands bioinformatics skills to turn raw reads into answers. It ingests public SRA data via a Step Functions workflow and Fargate task, then runs a HealthOmics Nextflow pipeline that trims reads, assembles them, and detects resistance genes with AMRFinderPlus using a baked-in database. Results are normalized into the hAMRonization schema and merged idempotently into Iceberg tables on S3 Tables, so reprocessing an isolate updates rows rather than duplicating them. A Strands agent on Amazon Bedrock AgentCore answers plain-language questions by generating Athena queries, with Guardrails keeping responses grounded. The solution is defined entirely in AWS CDK, deploys with a single command, and avoids manual bioinformatics steps, remaining inexpensive when idle.


### [How California built its Behavioral Health Public County Profile on Databricks](https://yomu.fyi/post/how-california-built-its-behavioral-health-public-county-profile-on-da.md)
- Company: [Databricks](https://yomu.fyi/company/databricks.md)
- Author: Michael Smith, Cameron Kahn, Stephen Hsu, Scott Black, Ben McKay, Varun Ganti
- Published: Oct 10, 2026
- Type: Explainer

The California Department of Health Care Services built the Behavioral Health Public County Profile on Databricks, a public dashboard consolidating behavioral health data from all 58 counties for nearly 40 million Californians. Launched on October 1, 2026, following the 2024 passage of Proposition 1, the dashboard supports the new Behavioral Health Services Act (BHSA) tying funding to statewide goals for outcomes, equity, and transparency. The platform uses Spark Declarative Pipelines and Lakeflow Connect for unified data ingestion, Semantic Views for standardized metrics across counties, and serverless compute to process data at scale without infrastructure management. It operates on a FedRAMP-authorized environment meeting federal security standards for health data, with data quality and lineage ensuring every number can be traced to its source. The County Profile enables public comparison of county plans, funding, service delivery, and performance measures, creating a feedback loop between policy intent and measurable outcomes for democratic oversight.


### [Introducing Funke: Native HL7v2 Parsing on Databricks](https://yomu.fyi/post/introducing-funke-native-hl7v2-parsing-on-databricks.md)
- Company: [Databricks](https://yomu.fyi/company/databricks.md)
- Author: Sean Fischer, Chris Mantz, Andy Launchbury
- Published: Oct 9, 2026
- Type: Announcement

HL7v2 is the dominant healthcare messaging standard but is difficult to parse due to its nested, delimiter-encoded structure. Existing workarounds like converting to FHIR or using third-party engines add cost and latency. Funke, the successor to the open-source Smolder library, is a new open-source Python and PySpark library under the Databricks License that parses HL7v2 messages directly into native Spark types, preserving the full hierarchy losslessly. It deploys as a Databricks Asset Bundle with a Declarative Pipeline that uses Auto Loader to ingest raw messages into a Unity Catalog volume, then parses them into structured silver tables following the medallion pattern. The library supports all HL7 message types and versions, includes accessor helpers for extracting fields by segment and component, and ships with a demo using synthetic ADT events to illustrate end-to-end ingestion and gold table creation, including a live census and bed utilization dashboard.


### [How Concurrence governs clinical AI at a trillion-token scale with Unity Gateway](https://yomu.fyi/post/how-concurrence-governs-clinical-ai-at-a-trillion-token-scale-with-uni.md)
- Company: [Databricks](https://yomu.fyi/company/databricks.md)
- Author: Ali Khokhar, John Xing, Tony Shi, Kelly Albano
- Published: Sep 23, 2026
- Type: Explainer

Concurrence processes 100.8 billion input tokens and 11.2 million LLM calls every 30 days, at an annualized rate of 1.2 trillion tokens. To govern these workflows, the company consolidates on Databricks with Lakebase for operational state, Unity Catalog for governance, and Unity Gateway for centralized AI access. Patient data is recorded as immutable events in Delta tables, from which a current patient state—called the world model—is computed while preserving provenance. All agents are tested against simulated patients before deployment; simulation traffic is approximately seven times production traffic, using immutable event history to replay states. Concurrence routes all coding-agent traffic through Unity Gateway, attributing each request to the engineer, and enforces compliance-gated model routing where HIPAA requirements are met first.


### [Amazon launches research initiative with Stanford University to advance AI and science](https://yomu.fyi/post/amazon-launches-research-initiative-with-stanford-university-to-advanc.md)
- Company: [AWS](https://yomu.fyi/company/aws.md)
- Author: Staff writer
- Published: Sep 21, 2026
- Type: Announcement

Amazon and Stanford University have launched the Stanford and Amazon Research Initiative, a formalized framework to advance research in AI, energy, and healthcare. The initiative builds on a deep relationship where currently more than 10 teams across Amazon fund active research and PhD fellowships at Stanford, spanning humanoid robotics, post-quantum cryptography, causal measurement science, and AI-driven radiology. It aims to accelerate the path from breakthrough research to real-world solutions that benefit society at large and broaden participation from diverse scholars. Focus areas will leverage strengths in artificial intelligence, machine learning, automated reasoning, and health, supported by Amazon’s cloud computing and AI services. The collaboration includes joint research projects, PhD fellowships, and interdisciplinary symposia, and was announced at a Stanford event with AWS CEO Matt Garman and Vice Provost David Studdert discussing the impact of university-industry collaborations.


### [Powering clinical research innovation: How TriNetX uses Databricks to accelerate drug development](https://yomu.fyi/post/powering-clinical-research-innovation-how-trinetx-uses-databricks-to-a.md)
- Company: [Databricks](https://yomu.fyi/company/databricks.md)
- Author: Jeff Warnick
- Published: Sep 18, 2026
- Type: Explainer

TriNetX operates a federated real-world health data network spanning more than 230 healthcare organizations and needed infrastructure to make growing volumes of RWD easier to use for clinical research. Databricks now provides the centralized lakehouse architecture, consolidating electronic health record data while supporting custom datasets, consulting, ML models, proprietary algorithms, APIs and self-service access. TriNetX is extending this foundation with a beta Query Assistant for natural-language analysis and a Support Assistant prototype built with Databricks’ Agent Bricks, requiring no programming expertise for the former. In 2025, pharmaceutical clients reduced protocol amendments by up to 50%, while an AI-enhanced site-identification effort achieved a 63% site acceptance rate and nine-day average response time. Other models suggest enrollment conversion could rise from 33% to 85%, with expanded APIs and Genie exploration planned for 2026.


### [Building cloud-native PACS on AWS](https://yomu.fyi/post/building-cloud-native-pacs-on-aws.md)
- Company: [AWS](https://yomu.fyi/company/aws.md)
- Author: ManojKumar MV
- Published: Sep 17, 2026
- Type: Explainer

Multi-hospital networks face rising imaging volumes, siloed on-premises PACS, radiologist routing bottlenecks, and storage that must expand for 7 to 10 years of retention. The proposed pattern uses a hub-and-spoke hybrid architecture: local PACS instances preserve LAN-speed reading, while a centralized AWS archive provides cross-facility discovery, disaster recovery, and lifecycle-managed storage. Modalities send DICOM through C-STORE to local VNA servers, which normalize and compress objects; asynchronous replication sends images to Amazon S3, while Amazon Aurora PostgreSQL stores metadata and routing information. The AWS deployment spans two Availability Zones, places PACS services behind Network Load Balancers, and includes CloudFront and AWS WAF. Storage guidance distinguishes S3 Intelligent-Tiering, Glacier Instant Retrieval, and Glacier Deep Archive according to access frequency and retention needs.


### [Stop Rubber-stamping AI: A Contestable AI Framework for Regulated Industries](https://yomu.fyi/post/stop-rubber-stamping-ai-a-contestable-ai-framework-for-regulated-indus.md)
- Company: [MongoDB](https://yomu.fyi/company/mongodb.md)
- Published: Sep 14, 2026
- Type: Explainer

AI deployed in regulated industries such as healthcare and manufacturing often lacks explainability and contestability, creating a barrier to adoption because responsible humans cannot meaningfully challenge AI outputs. The post presents contestable AI as an architectural pattern where multiple specialist agents debate recommendations, a qualified human reviews and overrides arguments, and the system re-scores in real time. In a clinical scenario, a patient analyzer agent retrieves similar cases, specialists argue for and against care options, and a general practitioner overrides as needed before a care plan is finalized. In manufacturing, a site reader agent ingests equipment sensor labels, two specialist agents debate classifications against a standard ontology, and an engineer overrides with context the model lacked, like a fixture offset. MongoDB’s document model stores the AI arguments, human overrides, confidence scores, and final decision in one retrievable document, supporting single-query decision lineage without joining data across systems.


### [Health Plans: Your BI Tells You MLR Moved. Can Your AI Tell You Why?](https://yomu.fyi/post/health-plans-your-bi-tells-you-mlr-moved-can-your-ai-tell-you-why.md)
- Company: [Databricks](https://yomu.fyi/company/databricks.md)
- Author: Aaron Zavora, Jonathan Thompson
- Published: Sep 11, 2026
- Type: Explainer

Health plan finance teams can see when medical loss ratio (MLR) moves above budget, but the variance alone does not explain which business areas, costs, populations, or providers caused it. Conversational AI is presented as a way for finance leaders to ask follow-up questions across claims, membership, provider, contract, clinical, quality, risk, and financial data without repeatedly commissioning reports. Its usefulness depends on explicit payer context: MLR combines premiums with medical-care components such as pharmacy rebates, IBNR, recoveries, risk adjustment transfers, and provider settlements, while cohort definitions and metric logic vary. Abacus supplies normalized, connected healthcare data and payer-specific business context; Databricks provides governed enterprise data and AI capabilities for conversational analytical experiences. Together, they are described as creating a reusable foundation for tracing executive signals into operational questions across MLR and other payer domains, while leaving action judgment to the organization.


### [Advancing Claude in healthcare and the life sciences](https://yomu.fyi/post/advancing-claude-in-healthcare-and-the-life-sciences.md)
- Company: [Anthropic](https://yomu.fyi/company/anthropic.md)
- Published: Aug 27, 2026
- Type: Announcement

Anthropic announces Claude for Healthcare and expanded Claude for Life Sciences capabilities, adding HIPAA-ready tools for providers, payers, health-tech companies, and individuals managing personal health data. Healthcare connectors cover CMS coverage determinations, ICD-10 codes, the National Provider Identifier Registry, PubMed, and beta integrations with HealthEx, Function, Apple Health, and Android Health Connect; new Agent Skills support FHIR development and prior-authorization review. Life sciences additions connect Claude to Medidata and ClinicalTrials.gov while extending support from preclinical research toward clinical trial operations and regulatory work. The announcement presents Claude Opus 4.5 as a major step in agentic performance on detailed medical and scientific simulations and says its extended-thinking mode improves correctness on honesty evaluations, while emphasizing opt-in permissions, user-controlled access, no training on health data, contextual disclaimers, and referral to healthcare professionals.