<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>CEHR-XGPT Learning Journey on The Build Log</title>
    <link>https://chava.cc/series/cehr-xgpt-learning-journey/</link>
    <description>Recent content in CEHR-XGPT Learning Journey on The Build Log</description>
    <generator>Hugo -- 0.147.7</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 03 Jan 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://chava.cc/series/cehr-xgpt-learning-journey/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Reproducing CEHR-XGPT: A Beginner&#39;s Journey into EHR Foundation Models</title>
      <link>https://chava.cc/posts/reproducing-cehr-xgpt/reproducing-cehr-xgpt/</link>
      <pubDate>Sat, 03 Jan 2026 00:00:00 +0000</pubDate>
      <guid>https://chava.cc/posts/reproducing-cehr-xgpt/reproducing-cehr-xgpt/</guid>
      <description>&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;
&lt;p&gt;In my &lt;a href=&#34;https://chava.cc/posts/ohdsi-development-environment&#34;&gt;previous post&lt;/a&gt;, I set up a local OHDSI development environment with synthetic
data from Synthea. As I continued learning about the OMOP Common Data Model, I became interested in a specific question:
&lt;strong&gt;How can I generate realistic synthetic patient data from an OMOP instance?&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;While searching for approaches, I found &lt;a href=&#34;https://arxiv.org/abs/2509.03643&#34;&gt;CEHR-XGPT&lt;/a&gt; (pronounced &amp;ldquo;seer-ex-gpt&amp;rdquo;),
a foundation model for electronic health records developed by Chao Pang and colleagues at Columbia University.
I think it&amp;rsquo;s a fantastic piece of work—the idea of using time tokens to preserve temporal structure is elegant,
and the fact that a single model can handle feature extraction, prediction, and synthetic generation is impressive.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
