<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>BISG on Kailas Venkitasubramanian</title>
    <link>/tags/bisg/</link>
    <description>Recent content in BISG on Kailas Venkitasubramanian</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Sun, 15 Sep 2024 00:00:00 +0000</lastBuildDate>
    <atom:link href="/tags/bisg/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Bayesian Improved Surname Geocoding: How It Works and Where We Use It</title>
      <link>/blog/posts/2024-09-15-bayesian-improved-surname-geocoding/</link>
      <pubDate>Sun, 15 Sep 2024 00:00:00 +0000</pubDate>
      <guid>/blog/posts/2024-09-15-bayesian-improved-surname-geocoding/</guid>
      <description>&lt;p&gt;If you work with administrative data long enough, you run into the same wall eventually: the dataset has everything you need except race and ethnicity. Hospital discharge records, voter files, tax records, benefits enrollment data — these are often rich with information about where people live, what services they use, and what outcomes they experience. But ask whether they capture race or ethnicity, and the answer is usually no, or inconsistently, or only in ways that aren&amp;rsquo;t usable.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
