<?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>PHI on Sade</title><link>https://sadesing.github.io/tags/phi/</link><description>Recent content in PHI on Sade</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 18 Jan 2026 20:38:51 -0500</lastBuildDate><atom:link href="https://sadesing.github.io/tags/phi/index.xml" rel="self" type="application/rss+xml"/><item><title>When a Name Reveals Too Much</title><link>https://sadesing.github.io/posts/when-a-name-reveals-too-much/</link><pubDate>Sun, 18 Jan 2026 20:38:51 -0500</pubDate><guid>https://sadesing.github.io/posts/when-a-name-reveals-too-much/</guid><description>&lt;p&gt;A court case about a patient’s roommate ended up teaching me more about privacy than I expected.&lt;/p&gt;
&lt;p&gt;The case was &lt;em&gt;Rogers v. NYU Hospitals Center&lt;/em&gt;. A hospital released the name of a patient’s roommate and someone questioned whether this violated HIPAA. The name came up during a legal proceeding and the patient argued it should have been protected. The court disagreed, noting that the name alone did not reveal any medical diagnosis or treatment. A wide range of rehabilitative services were offered at Rusk Institute of Rehabilitation Medicine, so knowing someone was there didn’t tell you anything about their condition. A name by itself wasn’t protected health information in this situation.&lt;/p&gt;</description></item></channel></rss>