<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: HIT Amendments Expected in Senate Economic Stimulus Bill</title>
	<atom:link href="http://www.nuckleslaw.com/software-negotiations-expert/hit-amendments-expected-in-senate-economic-stimulus-bill/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.nuckleslaw.com/software-negotiations-expert/hit-amendments-expected-in-senate-economic-stimulus-bill/</link>
	<description>Buyer-Side Secrets Revealed</description>
	<lastBuildDate>Sat, 04 Feb 2012 00:56:53 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Jana Aagaard</title>
		<link>http://www.nuckleslaw.com/software-negotiations-expert/hit-amendments-expected-in-senate-economic-stimulus-bill/comment-page-1/#comment-34</link>
		<dc:creator>Jana Aagaard</dc:creator>
		<pubDate>Fri, 06 Feb 2009 18:09:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.nuckleslaw.com/software-negotiations-expert/?p=133#comment-34</guid>
		<description>IT vendors may want to look at one specific requirement of the stimulus package privacy provisions and think about the impact it will have on the IT industry.  Section 4405(c) of the House bill and 13405(c) of the Senate bill eliminates the &quot;treatment, payment, and health care operations&quot; exemption from the requirements for providing an accounting of disclosures by a covered entity to a patient if the covered entity uses an electronic health record (EHR).  In addition, HR1 reduces the chronological scope of the accounting from 6 to 3 years (a big step in the right direction).  

Do EHR products today have the capacity to generate and store for 3 years the following information on every disclosure made by a physician or hospital?  the date of the disclosure; the name of the person who received the PHI and the address, if known; a brief description of what PHI was disclosed; a brief statement of the purpose of the disclosure.

Can EHRs actually capture the distinctions between a disclosure of PHI from a hospital to a health plan, for example, for treatment purposes as opposed to quality assurance purposes (health care operations)?  Is it realistic for a physician or hospital to store the requisite data on every patient for 3 years?  These are questions that covered entity providers are currently wrestling with, because few to no IT EHR products have such capabilities.</description>
		<content:encoded><![CDATA[<p>IT vendors may want to look at one specific requirement of the stimulus package privacy provisions and think about the impact it will have on the IT industry.  Section 4405(c) of the House bill and 13405(c) of the Senate bill eliminates the &#8220;treatment, payment, and health care operations&#8221; exemption from the requirements for providing an accounting of disclosures by a covered entity to a patient if the covered entity uses an electronic health record (EHR).  In addition, HR1 reduces the chronological scope of the accounting from 6 to 3 years (a big step in the right direction).  </p>
<p>Do EHR products today have the capacity to generate and store for 3 years the following information on every disclosure made by a physician or hospital?  the date of the disclosure; the name of the person who received the PHI and the address, if known; a brief description of what PHI was disclosed; a brief statement of the purpose of the disclosure.</p>
<p>Can EHRs actually capture the distinctions between a disclosure of PHI from a hospital to a health plan, for example, for treatment purposes as opposed to quality assurance purposes (health care operations)?  Is it realistic for a physician or hospital to store the requisite data on every patient for 3 years?  These are questions that covered entity providers are currently wrestling with, because few to no IT EHR products have such capabilities.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.721 seconds -->

