<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Patient Portal and PHR Info &#187; E-visits</title>
	<atom:link href="http://www.patientportalguru.com/tag/e-visits/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.patientportalguru.com</link>
	<description>PHR&#039;s and Patient Portals Examined</description>
	<lastBuildDate>Wed, 11 Nov 2009 00:44:50 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Support for E-Visits &#8211; CPT Code 99444 and 98969: 9 of 10 Critical Features of Patient Portals</title>
		<link>http://www.patientportalguru.com/support-for-e-visits-cpt-code-99444-and-98969-9-of-10-critical-features-of-patient-portals/</link>
		<comments>http://www.patientportalguru.com/support-for-e-visits-cpt-code-99444-and-98969-9-of-10-critical-features-of-patient-portals/#comments</comments>
		<pubDate>Thu, 05 Nov 2009 12:00:02 +0000</pubDate>
		<dc:creator>Aaron Carlock</dc:creator>
				<category><![CDATA[Choosing a Patient Portal]]></category>
		<category><![CDATA[CEO]]></category>
		<category><![CDATA[CIO]]></category>
		<category><![CDATA[Director]]></category>
		<category><![CDATA[E-visits]]></category>
		<category><![CDATA[EMR]]></category>
		<category><![CDATA[Features]]></category>
		<category><![CDATA[Patient]]></category>
		<category><![CDATA[Patient Portal]]></category>
		<category><![CDATA[PHR]]></category>
		<category><![CDATA[Vendor]]></category>

		<guid isPermaLink="false">http://www.patientportalguru.com/?p=84</guid>
		<description><![CDATA[Why?
Patients love the convenience of e-visits when available.  The best demographic for e-visits are patients who live far away from their clinics, have kids, or who don&#8217;t want to spend 2-4 hours for a trip to the doctor when all they need is a quick answer or diagnosis for a minor symptom.  Some possible symptoms [...]]]></description>
			<content:encoded><![CDATA[<h2>Why?</h2>
<p>Patients love the convenience of e-visits when available.  The best demographic for e-visits are patients who live far away from their clinics, have kids, or who don&#8217;t want to spend 2-4 hours for a trip to the doctor when all they need is a quick answer or diagnosis for a minor symptom.  Some possible symptoms could be common cold, sinus infections, urinary problems, cough, diarrhea and back pain. </p>
<p>Providing a route for patients to take that does not require them to come to the clinic benefits them and your organization.  Many organizations find that overall utilization drops when e-visits are implemented, some places by as much as 25%.  This makes e-visits a very interesting proposition for insurance companies, although few actually re-imburse for them currently.</p>
<p>E-visits, with the proper functionality, also allow the patient to update their allergies, vital signs, and history information. </p>
<p>E-visits are the way of the future for healthcare since they can help lower costs by decreasing utilization and improving care efficiency.  Patients also enjoy the lower co-pays that e-visits provide.  As more and more patients look to lower their healthcare costs they will increase usage of alternative options like e-visits and nurse only visits.   </p>
<p>Providing e-visits allows the standard healthcare organization to offer a product that can compete on price with the retail clinics that are popping up in strip malls and Walmart.</p>
<h5>Requirements</h5>
<p>A patient portal offering e-visit functionality needs to provide several tools to make the e-visit flow usable.   For starters, most states require that a patient is notified up front that they may be charged for the visit so having a terms and conditions agreement option is critical.  The phr should also allow for the entry of history, allergies, vitals and other information collected during a standard office visit. </p>
<p>Since the information is provided by the patient, the data should not immediately sync in with the permanent chart until reviewed by a clinician or physician.  Since the CMS code 99444 states that a timely response is required workqueue functionality must exist so that the e-visits are reviewed by physicians quickly. </p>
<p>Code 99444 also states that an e-visit can only occur with an existing patient, once in any given seven-day period. </p>
<p><strong>Questions to Ask</strong></p>
<p><em>To Vendors</em></p>
<p style="padding-left: 30px;">Is there integration to process credit card payments?</p>
<p style="padding-left: 30px;">Can questionnaires be customized based on the symptom the patient enters?</p>
<p style="padding-left: 30px;">What kind of logic can be configured to route the e-visit request to the appropriate provider?</p>
<p style="padding-left: 30px;">What tools are available to the provider to work the e-visits quickly and efficiently?</p>
<p style="padding-left: 30px;">Are there customizable restrictions available to help comply with the laws, such as only allowing one e-visit in a seven-day period?  Or are people working the e-visits required to check for compliance?</p>
<p><em>For Patients</em></p>
<p style="padding-left: 30px;">How much does it cost?  (most places charge $30-$35, but the majority of patients feel like they should be cheaper or that they should be free)</p>
<p style="padding-left: 30px;">How long will it take to hear back?</p>
<p style="padding-left: 30px;">Can I get a prescription via an e-visit?</p>
<p style="padding-left: 30px;"> </p>
<p style="padding-left: 30px;"> </p>
]]></content:encoded>
			<wfw:commentRss>http://www.patientportalguru.com/support-for-e-visits-cpt-code-99444-and-98969-9-of-10-critical-features-of-patient-portals/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>
