<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/atom10full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><feed xmlns="http://www.w3.org/2005/Atom" xmlns:openSearch="http://a9.com/-/spec/opensearchrss/1.0/" xmlns:georss="http://www.georss.org/georss"><id>tag:blogger.com,1999:blog-3380636</id><updated>2009-11-05T10:27:36.955-06:00</updated><title type="text">HIPAA Blog</title><subtitle type="html">A discussion of medical privacy issues buried in political arcana</subtitle><link rel="http://schemas.google.com/g/2005#feed" type="application/atom+xml" href="http://hipaablog.blogspot.com/feeds/posts/default" /><link rel="alternate" type="text/html" href="http://hipaablog.blogspot.com/" /><link rel="hub" href="http://pubsubhubbub.appspot.com/" /><link rel="next" type="application/atom+xml" href="http://www.blogger.com/feeds/3380636/posts/default?start-index=26&amp;max-results=25" /><author><name>Jeff</name><uri>http://www.blogger.com/profile/12067054401696214042</uri><email>noreply@blogger.com</email></author><generator version="7.00" uri="http://www.blogger.com">Blogger</generator><openSearch:totalResults>1477</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>25</openSearch:itemsPerPage><link rel="self" href="http://feeds.feedburner.com/blogspot/HIPAAblog" type="application/atom+xml" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com" /><entry><id>tag:blogger.com,1999:blog-3380636.post-5339887591612354929</id><published>2009-11-05T10:19:00.002-06:00</published><updated>2009-11-05T10:27:36.966-06:00</updated><title type="text" /><summary type="text">Interesting Georgia personal representative decision: Well, interesting if you're a HIPAA geek.  The Georgia Supreme Court has ruled that a spouse of a deceased person is that person's "personal representative" for HIPAA purposes.  It seems the complicating factor in Alvista Healthcare Center v. Miller was the fact that the information was being sought by the surviving wife who was pursuing a </summary><link rel="replies" type="application/atom+xml" href="http://hipaablog.blogspot.com/feeds/5339887591612354929/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=3380636&amp;postID=5339887591612354929" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/3380636/posts/default/5339887591612354929" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/3380636/posts/default/5339887591612354929" /><link rel="alternate" type="text/html" href="http://hipaablog.blogspot.com/2009/11/interesting-georgia-personal.html" title="" /><author><name>Jeff</name><uri>http://www.blogger.com/profile/12067054401696214042</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd="http://schemas.google.com/g/2005" name="OpenSocialUserId" value="10410990454614681449" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-3380636.post-7755636926684919629</id><published>2009-11-03T10:57:00.003-06:00</published><updated>2009-11-03T10:59:34.733-06:00</updated><title type="text" /><summary type="text">Data Breach experience: Here's an interesting first-person perspective of a data breach victim.  Understandable (if not really balanced) concerns about the ability of research organizations to use data without consent.</summary><link rel="replies" type="application/atom+xml" href="http://hipaablog.blogspot.com/feeds/7755636926684919629/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=3380636&amp;postID=7755636926684919629" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/3380636/posts/default/7755636926684919629" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/3380636/posts/default/7755636926684919629" /><link rel="alternate" type="text/html" href="http://hipaablog.blogspot.com/2009/11/data-breach-experience-heres.html" title="" /><author><name>Jeff</name><uri>http://www.blogger.com/profile/12067054401696214042</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd="http://schemas.google.com/g/2005" name="OpenSocialUserId" value="10410990454614681449" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-3380636.post-7470716414642557333</id><published>2009-11-02T11:40:00.002-06:00</published><updated>2009-11-02T11:43:34.703-06:00</updated><title type="text" /><summary type="text">Survey: As I mentioned  below, SoftwareAdvice is taking a survey on EMR adoption.  They've decided to hold the survey open until Thursday, November 5th to see if they can compile more data.  You can take the survey here.</summary><link rel="replies" type="application/atom+xml" href="http://hipaablog.blogspot.com/feeds/7470716414642557333/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=3380636&amp;postID=7470716414642557333" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/3380636/posts/default/7470716414642557333" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/3380636/posts/default/7470716414642557333" /><link rel="alternate" type="text/html" href="http://hipaablog.blogspot.com/2009/11/survey-as-i-mentioned-below.html" title="" /><author><name>Jeff</name><uri>http://www.blogger.com/profile/12067054401696214042</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd="http://schemas.google.com/g/2005" name="OpenSocialUserId" value="10410990454614681449" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-3380636.post-3836796193843357751</id><published>2009-11-02T10:44:00.002-06:00</published><updated>2009-11-02T11:30:40.890-06:00</updated><title type="text" /><summary type="text">Miami HIPAA/ID Theft sentencing: As noted below, the Miami ID theft ring at Palmetto General Hospital resulted in two convictions of a medical records employee and an outside accomplice.  The hospital employee got 2 years and 5 days (?) and the accomplice got 11 months in jail.Via BNA (subscription required).</summary><link rel="replies" type="application/atom+xml" href="http://hipaablog.blogspot.com/feeds/3836796193843357751/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=3380636&amp;postID=3836796193843357751" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/3380636/posts/default/3836796193843357751" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/3380636/posts/default/3836796193843357751" /><link rel="alternate" type="text/html" href="http://hipaablog.blogspot.com/2009/11/miami-hipaaid-theft-sentencing-as-noted.html" title="" /><author><name>Jeff</name><uri>http://www.blogger.com/profile/12067054401696214042</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd="http://schemas.google.com/g/2005" name="OpenSocialUserId" value="10410990454614681449" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-3380636.post-1449604632505717894</id><published>2009-10-31T09:44:00.002-05:00</published><updated>2009-10-31T10:01:35.598-05:00</updated><title type="text" /><summary type="text">Red Flags Update: I didn't see this until this morning, but knew it was coming.  Sunday is November 1, the date the much-delayed Red Flags Rule would become enforceable against "creditors" (financial institutions, which obviously ought to implement identity theft prevention programs, have been under the Red Flags Rule for about a year).  And when the eve of enforcement rolls around, FTC punts.  </summary><link rel="replies" type="application/atom+xml" href="http://hipaablog.blogspot.com/feeds/1449604632505717894/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=3380636&amp;postID=1449604632505717894" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/3380636/posts/default/1449604632505717894" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/3380636/posts/default/1449604632505717894" /><link rel="alternate" type="text/html" href="http://hipaablog.blogspot.com/2009/10/red-flags-update-i-didnt-see-this-until.html" title="" /><author><name>Jeff</name><uri>http://www.blogger.com/profile/12067054401696214042</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd="http://schemas.google.com/g/2005" name="OpenSocialUserId" value="10410990454614681449" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-3380636.post-6876940908895870721</id><published>2009-10-30T09:48:00.002-05:00</published><updated>2009-10-30T09:50:28.797-05:00</updated><title type="text" /><summary type="text">Cost-efficient technology: HIPAA issues abound, obviously, but there sure are some good iPhone and smartphone apps that doctors and patients can use that deliver a big bang for the buck.</summary><link rel="replies" type="application/atom+xml" href="http://hipaablog.blogspot.com/feeds/6876940908895870721/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=3380636&amp;postID=6876940908895870721" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/3380636/posts/default/6876940908895870721" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/3380636/posts/default/6876940908895870721" /><link rel="alternate" type="text/html" href="http://hipaablog.blogspot.com/2009/10/cost-efficient-technology-hipaa-issues.html" title="" /><author><name>Jeff</name><uri>http://www.blogger.com/profile/12067054401696214042</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd="http://schemas.google.com/g/2005" name="OpenSocialUserId" value="10410990454614681449" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-3380636.post-2124640308288479646</id><published>2009-10-29T08:54:00.002-05:00</published><updated>2009-10-29T09:01:39.751-05:00</updated><title type="text" /><summary type="text">Red Flags and Small Businesses: To stop ID theft, businesses need to follow the Red Flags Rule.  TJMaxx and other high-profile breaches show that.  But is it even more important for small businesses to follow the Red Flags Rule?  Some say so.Pro: small businesses have less technology, so lower technological defenses against ID theft.  They also tend to be more likely to fall victim to social </summary><link rel="replies" type="application/atom+xml" href="http://hipaablog.blogspot.com/feeds/2124640308288479646/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=3380636&amp;postID=2124640308288479646" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/3380636/posts/default/2124640308288479646" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/3380636/posts/default/2124640308288479646" /><link rel="alternate" type="text/html" href="http://hipaablog.blogspot.com/2009/10/red-flags-and-small-businesses-to-stop.html" title="" /><author><name>Jeff</name><uri>http://www.blogger.com/profile/12067054401696214042</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd="http://schemas.google.com/g/2005" name="OpenSocialUserId" value="10410990454614681449" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-3380636.post-8290326600892787014</id><published>2009-10-28T13:38:00.002-05:00</published><updated>2009-10-28T13:46:02.492-05:00</updated><title type="text" /><summary type="text">Arkansas Snoopin' update: Sentences have been handed down in the Little Rock, Arkansas snoopin' case, which involved the brutal murder of Ann Pressly, a Little Rock news anchor.  A doctor and two hospital employees were caught accessing the medical records of the victim, and have each been sentenced to a year's probation, plus fines and community service.</summary><link rel="replies" type="application/atom+xml" href="http://hipaablog.blogspot.com/feeds/8290326600892787014/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=3380636&amp;postID=8290326600892787014" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/3380636/posts/default/8290326600892787014" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/3380636/posts/default/8290326600892787014" /><link rel="alternate" type="text/html" href="http://hipaablog.blogspot.com/2009/10/arkansas-snoopin-update-sentences-have.html" title="" /><author><name>Jeff</name><uri>http://www.blogger.com/profile/12067054401696214042</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd="http://schemas.google.com/g/2005" name="OpenSocialUserId" value="10410990454614681449" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-3380636.post-898759780810760384</id><published>2009-10-28T11:14:00.002-05:00</published><updated>2009-10-28T11:18:04.810-05:00</updated><title type="text" /><summary type="text">EHR Adoption Due to Stimulus Bill Provisions: Have the EHR provisions in the so-called Stimulus Bill impacted your decision and/or timing about adopting electronic medical records?  The folks at SoftwareAdvice are surveying folks to see if the statutory changes caused healthcare providers to take action, or just go looking. Go take the survey if you have any insights.</summary><link rel="replies" type="application/atom+xml" href="http://hipaablog.blogspot.com/feeds/898759780810760384/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=3380636&amp;postID=898759780810760384" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/3380636/posts/default/898759780810760384" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/3380636/posts/default/898759780810760384" /><link rel="alternate" type="text/html" href="http://hipaablog.blogspot.com/2009/10/ehr-adoption-due-to-stimulus-bill.html" title="" /><author><name>Jeff</name><uri>http://www.blogger.com/profile/12067054401696214042</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd="http://schemas.google.com/g/2005" name="OpenSocialUserId" value="10410990454614681449" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-3380636.post-4452997827071454922</id><published>2009-10-28T08:41:00.002-05:00</published><updated>2009-10-28T08:45:13.165-05:00</updated><title type="text" /><summary type="text">5 Vulnerabilities that Lead to Identity Theft: Interesting article in InfoWeek's Dark Reading on areas to watch for ID theft.  I thought it would be about specific items and behaviors that could pose risks, but it's more global than that.  Interestingly, #5 is "Healthcare."</summary><link rel="replies" type="application/atom+xml" href="http://hipaablog.blogspot.com/feeds/4452997827071454922/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=3380636&amp;postID=4452997827071454922" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/3380636/posts/default/4452997827071454922" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/3380636/posts/default/4452997827071454922" /><link rel="alternate" type="text/html" href="http://hipaablog.blogspot.com/2009/10/5-vulnerabilities-that-lead-to-identity.html" title="" /><author><name>Jeff</name><uri>http://www.blogger.com/profile/12067054401696214042</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd="http://schemas.google.com/g/2005" name="OpenSocialUserId" value="10410990454614681449" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-3380636.post-9028619573603415901</id><published>2009-10-26T10:20:00.002-05:00</published><updated>2009-10-26T10:25:55.886-05:00</updated><title type="text" /><summary type="text">Curb Your Enthusiasm: The digitization of medical records is not the cure-all some claim it will be.  As with just about every other component of the health reform debate, nothing will be as good (the public option will end the uninsured problem), bad (death panels will kill grandma), or efficient (cutting fraud and abuse will save $500 billion) as the most vocal proponents/critics say.  Here, </summary><link rel="replies" type="application/atom+xml" href="http://hipaablog.blogspot.com/feeds/9028619573603415901/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=3380636&amp;postID=9028619573603415901" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/3380636/posts/default/9028619573603415901" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/3380636/posts/default/9028619573603415901" /><link rel="alternate" type="text/html" href="http://hipaablog.blogspot.com/2009/10/curb-your-enthusiasm-digitization-of.html" title="" /><author><name>Jeff</name><uri>http://www.blogger.com/profile/12067054401696214042</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd="http://schemas.google.com/g/2005" name="OpenSocialUserId" value="10410990454614681449" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-3380636.post-3937923532180839645</id><published>2009-10-22T09:54:00.001-05:00</published><updated>2009-10-22T09:55:23.934-05:00</updated><title type="text" /><summary type="text">Cost of a (non-HIPAA) Data Breach: FTC fines ChoicePoint $275,000 for 2008 breach.</summary><link rel="replies" type="application/atom+xml" href="http://hipaablog.blogspot.com/feeds/3937923532180839645/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=3380636&amp;postID=3937923532180839645" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/3380636/posts/default/3937923532180839645" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/3380636/posts/default/3937923532180839645" /><link rel="alternate" type="text/html" href="http://hipaablog.blogspot.com/2009/10/cost-of-non-hipaa-data-breach-ftc-fines.html" title="" /><author><name>Jeff</name><uri>http://www.blogger.com/profile/12067054401696214042</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd="http://schemas.google.com/g/2005" name="OpenSocialUserId" value="10410990454614681449" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-3380636.post-268784505774232846</id><published>2009-10-21T07:34:00.002-05:00</published><updated>2009-10-21T07:39:41.270-05:00</updated><title type="text" /><summary type="text">Hospital bans Facebook:  New England Baptist Hospital has banned its employees from using Facebook at work over privacy and time-wasting concerns.  The second concern is definitely apt; as for the first, that's probably punishing the medium when the message is the potential problem.  It's an interesting dilemma for all businesses, but the privacy/patient information issue is particularly relevant</summary><link rel="replies" type="application/atom+xml" href="http://hipaablog.blogspot.com/feeds/268784505774232846/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=3380636&amp;postID=268784505774232846" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/3380636/posts/default/268784505774232846" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/3380636/posts/default/268784505774232846" /><link rel="alternate" type="text/html" href="http://hipaablog.blogspot.com/2009/10/hospital-bans-facebook-new-england.html" title="" /><author><name>Jeff</name><uri>http://www.blogger.com/profile/12067054401696214042</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd="http://schemas.google.com/g/2005" name="OpenSocialUserId" value="10410990454614681449" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-3380636.post-1512950225124876024</id><published>2009-10-20T08:57:00.001-05:00</published><updated>2009-10-20T08:58:40.994-05:00</updated><title type="text" /><summary type="text">Red Flag Reduction Reax: Some disagree with the new legislation to exempt small providers from the Red Flags Rule.</summary><link rel="replies" type="application/atom+xml" href="http://hipaablog.blogspot.com/feeds/1512950225124876024/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=3380636&amp;postID=1512950225124876024" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/3380636/posts/default/1512950225124876024" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/3380636/posts/default/1512950225124876024" /><link rel="alternate" type="text/html" href="http://hipaablog.blogspot.com/2009/10/red-flag-reduction-reax-some-disagree.html" title="" /><author><name>Jeff</name><uri>http://www.blogger.com/profile/12067054401696214042</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd="http://schemas.google.com/g/2005" name="OpenSocialUserId" value="10410990454614681449" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-3380636.post-2322992002369585346</id><published>2009-10-19T08:03:00.003-05:00</published><updated>2009-10-19T08:05:57.240-05:00</updated><title type="text" /><summary type="text">Second Life: Interesting article on Children's Memorial Hospital in Chicago's use of Second Life for training and peer support for disabled patients.  I'm still not very sure how to purposefully navigate through Second Life: I have an identity there and an avatar that looks nothing like me, thankfully, but have never had any successful interactions there.  Is there a "Second Life for Dummies" </summary><link rel="replies" type="application/atom+xml" href="http://hipaablog.blogspot.com/feeds/2322992002369585346/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=3380636&amp;postID=2322992002369585346" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/3380636/posts/default/2322992002369585346" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/3380636/posts/default/2322992002369585346" /><link rel="alternate" type="text/html" href="http://hipaablog.blogspot.com/2009/10/second-life-interesting-article-on.html" title="" /><author><name>Jeff</name><uri>http://www.blogger.com/profile/12067054401696214042</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd="http://schemas.google.com/g/2005" name="OpenSocialUserId" value="10410990454614681449" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-3380636.post-1973294505897886780</id><published>2009-10-15T09:48:00.004-05:00</published><updated>2009-10-22T07:50:43.408-05:00</updated><title type="text" /><summary type="text">RED FLAGS UPDATE:In case you're following the Red Flags issue (the latest FTC compliance date was shifted to November 1), here's some big, big news: The House Financial Services Committee has quickly (and without Republican objection) moved forward a bill that would fully exempt healthcare, legal, and accounting firms with fewer than 20 employees from the definition of "creditor" under the Red </summary><link rel="replies" type="application/atom+xml" href="http://hipaablog.blogspot.com/feeds/1973294505897886780/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=3380636&amp;postID=1973294505897886780" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/3380636/posts/default/1973294505897886780" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/3380636/posts/default/1973294505897886780" /><link rel="alternate" type="text/html" href="http://hipaablog.blogspot.com/2009/10/red-flags-update-in-case-youre.html" title="" /><author><name>Jeff</name><uri>http://www.blogger.com/profile/12067054401696214042</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd="http://schemas.google.com/g/2005" name="OpenSocialUserId" value="10410990454614681449" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-3380636.post-5666083811603939564</id><published>2009-10-06T11:57:00.001-05:00</published><updated>2009-10-06T11:59:58.914-05:00</updated><title type="text" /><summary type="text">Express Scripts: a 2008 successful hacker into the pharmacy benefits management company's data base might have exposed personal information 700,000 people.</summary><link rel="replies" type="application/atom+xml" href="http://hipaablog.blogspot.com/feeds/5666083811603939564/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=3380636&amp;postID=5666083811603939564" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/3380636/posts/default/5666083811603939564" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/3380636/posts/default/5666083811603939564" /><link rel="alternate" type="text/html" href="http://hipaablog.blogspot.com/2009/10/express-scripts-2008-successful-hacker.html" title="" /><author><name>Jeff</name><uri>http://www.blogger.com/profile/12067054401696214042</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd="http://schemas.google.com/g/2005" name="OpenSocialUserId" value="10410990454614681449" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-3380636.post-5843044526647448289</id><published>2009-10-06T09:29:00.004-05:00</published><updated>2009-10-06T11:38:03.126-05:00</updated><title type="text" /><summary type="text">FTC Endorsement Rule: In light of the (unconstitutional) FTC guidance published yesterday requiring bloggers to disclose any compensation for endorsement, let me state that anyone listed under the "Advertisers" to the left has paid for that spot. Most of the "Links" are unpaid, but some might've plied me with liquor. Rest assured, the grand total of what I've been paid in cash for posts or links </summary><link rel="replies" type="application/atom+xml" href="http://hipaablog.blogspot.com/feeds/5843044526647448289/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=3380636&amp;postID=5843044526647448289" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/3380636/posts/default/5843044526647448289" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/3380636/posts/default/5843044526647448289" /><link rel="alternate" type="text/html" href="http://hipaablog.blogspot.com/2009/10/ftc-endorsement-rule-in-light-of.html" title="" /><author><name>Jeff</name><uri>http://www.blogger.com/profile/12067054401696214042</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd="http://schemas.google.com/g/2005" name="OpenSocialUserId" value="10410990454614681449" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-3380636.post-96722370166887390</id><published>2009-10-05T13:50:00.002-05:00</published><updated>2009-10-05T13:55:58.802-05:00</updated><title type="text" /><summary type="text">70,000,000 Records; Is That a Lot?  The National Archives hosts a database that allows veterans to request copies of their medical records and discharge data.  One of the hard drives went out, so the Archives sent it to the contractor to fix.  The contractor couldn't fix, so it sent it to another contractor to recycle.  Unfortunately, nobody scrubbed the data off of the drive, which may hold </summary><link rel="replies" type="application/atom+xml" href="http://hipaablog.blogspot.com/feeds/96722370166887390/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=3380636&amp;postID=96722370166887390" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/3380636/posts/default/96722370166887390" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/3380636/posts/default/96722370166887390" /><link rel="alternate" type="text/html" href="http://hipaablog.blogspot.com/2009/10/70000000-records-is-that-lot-national.html" title="" /><author><name>Jeff</name><uri>http://www.blogger.com/profile/12067054401696214042</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd="http://schemas.google.com/g/2005" name="OpenSocialUserId" value="10410990454614681449" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-3380636.post-1227973822822611736</id><published>2009-10-05T13:45:00.001-05:00</published><updated>2009-10-05T13:48:04.649-05:00</updated><title type="text" /><summary type="text">Not what we intended: Congressmen react to Secretary Sibelius' "no harm" standard for notifying of data breach.  Apparently, that's too loose a standard for the Congressmen, who did not intend for HHS to give away such a big escape hatch for data breachers.</summary><link rel="replies" type="application/atom+xml" href="http://hipaablog.blogspot.com/feeds/1227973822822611736/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=3380636&amp;postID=1227973822822611736" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/3380636/posts/default/1227973822822611736" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/3380636/posts/default/1227973822822611736" /><link rel="alternate" type="text/html" href="http://hipaablog.blogspot.com/2009/10/not-what-we-intended-congressmen-react.html" title="" /><author><name>Jeff</name><uri>http://www.blogger.com/profile/12067054401696214042</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd="http://schemas.google.com/g/2005" name="OpenSocialUserId" value="10410990454614681449" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-3380636.post-2222103249029490471</id><published>2009-10-05T07:38:00.001-05:00</published><updated>2009-10-05T07:40:22.305-05:00</updated><title type="text" /><summary type="text">Data breach for physicians: Here's a twist.  Yeah, it's the same old story of the stolen laptop, but this time the information was physician info (including some social security numbers), lost by an insurance company.</summary><link rel="replies" type="application/atom+xml" href="http://hipaablog.blogspot.com/feeds/2222103249029490471/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=3380636&amp;postID=2222103249029490471" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/3380636/posts/default/2222103249029490471" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/3380636/posts/default/2222103249029490471" /><link rel="alternate" type="text/html" href="http://hipaablog.blogspot.com/2009/10/data-breach-for-physicians-heres-twist.html" title="" /><author><name>Jeff</name><uri>http://www.blogger.com/profile/12067054401696214042</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd="http://schemas.google.com/g/2005" name="OpenSocialUserId" value="10410990454614681449" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-3380636.post-5310531515419448663</id><published>2009-10-01T16:55:00.001-05:00</published><updated>2009-10-01T16:57:14.238-05:00</updated><title type="text" /><summary type="text">Bookmark this Permalink: HHS has published its instructions for submitting a notice of a data breach involving PHI here.  Count the number of affected individuals and follow the instructions.</summary><link rel="replies" type="application/atom+xml" href="http://hipaablog.blogspot.com/feeds/5310531515419448663/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=3380636&amp;postID=5310531515419448663" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/3380636/posts/default/5310531515419448663" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/3380636/posts/default/5310531515419448663" /><link rel="alternate" type="text/html" href="http://hipaablog.blogspot.com/2009/10/bookmark-this-permalink-hhs-has.html" title="" /><author><name>Jeff</name><uri>http://www.blogger.com/profile/12067054401696214042</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd="http://schemas.google.com/g/2005" name="OpenSocialUserId" value="10410990454614681449" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-3380636.post-2955934420227099219</id><published>2009-09-25T22:18:00.003-05:00</published><updated>2009-09-25T22:24:41.830-05:00</updated><title type="text" /><summary type="text">Business Associate Agreements:  The HITECH provisions of HIPAA contain some big changes for business associates, as well as some changes to business associate agreements.  But the specifics aren't that well defined.  What should you do?  Should you amend your existing BAAs?  Should you adopt a new form of BAA for new relationships, but keep the existing form to see what happens?  Well, according </summary><link rel="replies" type="application/atom+xml" href="http://hipaablog.blogspot.com/feeds/2955934420227099219/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=3380636&amp;postID=2955934420227099219" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/3380636/posts/default/2955934420227099219" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/3380636/posts/default/2955934420227099219" /><link rel="alternate" type="text/html" href="http://hipaablog.blogspot.com/2009/09/business-associate-agreements-hitech.html" title="" /><author><name>Jeff</name><uri>http://www.blogger.com/profile/12067054401696214042</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd="http://schemas.google.com/g/2005" name="OpenSocialUserId" value="10410990454614681449" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-3380636.post-3104107272624163713</id><published>2009-09-24T09:26:00.002-05:00</published><updated>2009-09-24T09:33:16.790-05:00</updated><title type="text" /><summary type="text">New York: Here's a story (subscription required) about a NY scam similar to the Miami scam mentioned Tuesday.  A lawyer and seven employees of a public hospital were arrested for running a scam where medical information of auto accident victims was taken by the hospital employees and sold to the lawyer, who used the information to file personal injury suits and get the patients unnecessary care </summary><link rel="replies" type="application/atom+xml" href="http://hipaablog.blogspot.com/feeds/3104107272624163713/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=3380636&amp;postID=3104107272624163713" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/3380636/posts/default/3104107272624163713" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/3380636/posts/default/3104107272624163713" /><link rel="alternate" type="text/html" href="http://hipaablog.blogspot.com/2009/09/new-york-heres-story-subscription.html" title="" /><author><name>Jeff</name><uri>http://www.blogger.com/profile/12067054401696214042</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd="http://schemas.google.com/g/2005" name="OpenSocialUserId" value="10410990454614681449" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-3380636.post-8766414732740389851</id><published>2009-09-24T09:16:00.004-05:00</published><updated>2009-09-25T22:14:11.122-05:00</updated><title type="text" /><summary type="text">Social Media in Healthcare: I'll be speaking again next year at Q1 Production's 2nd Annual Healthcare New Media Marketing Conference, this time in Chicago. June 14-15, 2010. I'll be discussing the legal implications of using social media in healthcare, particularly in healthcare marketing.On that note, here's a story about a hospital system and a physician recruiting agency using Facebook and </summary><link rel="replies" type="application/atom+xml" href="http://hipaablog.blogspot.com/feeds/8766414732740389851/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=3380636&amp;postID=8766414732740389851" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/3380636/posts/default/8766414732740389851" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/3380636/posts/default/8766414732740389851" /><link rel="alternate" type="text/html" href="http://hipaablog.blogspot.com/2009/09/social-media-in-healthcare-ill-be.html" title="" /><author><name>Jeff</name><uri>http://www.blogger.com/profile/12067054401696214042</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd="http://schemas.google.com/g/2005" name="OpenSocialUserId" value="10410990454614681449" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total></entry></feed>
