Topic

FHIR

2 posts about FHIR. Every summary links to the original.

Paid picks we use ourselves. Links carry a referral code — a subscription through one earns us a commission at no extra cost to you.

Newest first

Posts

Anthropic
Advancing Claude in healthcare and the life sciences
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.

Databricks
Building a FHIR-native health data platform on Databricks Lakebase
Healthcare organizations often keep a FHIR server, analytics warehouse, and ETL pipelines separate, replicating clinical data and fragmenting governance. The proposed architecture standardizes incoming HL7v2, C-CDA, X12, and proprietary data into FHIR using Health Samurai converters, terminology normalization, MDM/MPI deduplication, and Implementation Guide validation. Aidbox, Health Samurai's FHIR server and database, runs on Databricks Lakebase, while Moonlink synchronizes operational and analytical formats without ETL. This exposes one governed dataset through Spark, SQL, ML, AI/BI, FHIR API, SMART on FHIR, and SQL on FHIR ViewDefinitions. The architecture supports use cases including EHR optimization, value-based care, member engagement, and compliance capabilities, with insights connected to clinician and billing workflows through SMART on FHIR and CDS Hooks.

The best engineering reads, once a week.

Topic

2 posts about FHIR. Every summary links to the original.

Paid picks we use ourselves. Links carry a referral code — a subscription through one earns us a commission at no extra cost to you.

Newest first

Anthropic
Advancing Claude in healthcare and the life sciences
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.

Databricks
Building a FHIR-native health data platform on Databricks Lakebase
Healthcare organizations often keep a FHIR server, analytics warehouse, and ETL pipelines separate, replicating clinical data and fragmenting governance. The proposed architecture standardizes incoming HL7v2, C-CDA, X12, and proprietary data into FHIR using Health Samurai converters, terminology normalization, MDM/MPI deduplication, and Implementation Guide validation. Aidbox, Health Samurai's FHIR server and database, runs on Databricks Lakebase, while Moonlink synchronizes operational and analytical formats without ETL. This exposes one governed dataset through Spark, SQL, ML, AI/BI, FHIR API, SMART on FHIR, and SQL on FHIR ViewDefinitions. The architecture supports use cases including EHR optimization, value-based care, member engagement, and compliance capabilities, with insights connected to clinician and billing workflows through SMART on FHIR and CDS Hooks.

The best engineering reads, once a week.