<?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>e-prescribing blog &#187; Basics</title>
	<atom:link href="http://www.eprescribing.org/category/basics/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.eprescribing.org</link>
	<description>All about e-prescribing software</description>
	<lastBuildDate>Tue, 30 Mar 2010 15:48:47 +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>A CCHIT Based Guide to Qualified E-prescribing System &#8211; The First decision</title>
		<link>http://www.eprescribing.org/a-cchit-based-guide-to-qualified-eprescribing-system-the-first-decision/</link>
		<comments>http://www.eprescribing.org/a-cchit-based-guide-to-qualified-eprescribing-system-the-first-decision/#comments</comments>
		<pubDate>Sun, 31 May 2009 02:04:10 +0000</pubDate>
		<dc:creator>George Getty III</dc:creator>
				<category><![CDATA[Basics]]></category>

		<guid isPermaLink="false">http://www.eprescribing.org/a-cchit-based-guide-to-qualified-eprescribing-system-the-first-decision/</guid>
		<description><![CDATA[Now that we’ve taken a look at the whole of what is deemed a qualified e-prescribing system in the eyes of CCHIT, I think its time to get into the weeds a bit and see what those high level requirements really mean.  Just as we have to crawl before we walk, I’m going to address [...]]]></description>
			<content:encoded><![CDATA[<p>Now that we’ve <a href="http://www.electronicprescribing.org/a-cchit-based-guide-to-a-qualified-eprescribing-system-part-i-the-2008-requirements/">taken a look</a> at the whole of what is deemed a qualified e-prescribing system in the eyes of CCHIT, I think its time to get into the weeds a bit and see what those high level requirements really mean.  Just as we have to crawl before we walk, I’m going to address the primary goal of getting a prescription order from your EHR to the pharmacy for fulfillment.  It’s a straightforward requirement, but there are a lot of things you must think about before being ready to e-prescribe.</p>
<p>The reality is that any transactions between your system and the pharmacy system will be handled by a third party delivery service.  This service company is Surescripts RxHub.  Some may be familiar with the history of the company, but for those not, in a nutshell they used to be two companies serving two very different user bases.  Surescripts worked with the retail pharmacies, while Rx Hub worked with the Pharmacy Benefit Managers (in other words, the insurers).   I’m sure Surescripts RxNorm are working towards a unified system, but until then you can still think of Surescripts RxHub as two different systems.</p>
<p>Implementing ePrescribing for the first time will be a lot of development work, so if you wanted to stage the development over time and get more bang for your buck it may be a good idea to start with one group rather than the whole kit and caboodle.</p>
<p><span id="more-21"></span>Fortunately, taking a look at the following CCHIT requirements makes this first decision pretty easy:</p>
<table border="0" cellspacing="0" cellpadding="0" width="500">
<tbody>
<tr>
<td width="111" valign="top"><strong>IO-AM 09.13</strong></td>
<td width="389" valign="top">The system shall provide the ability to send a query to verify prescription drug insurance eligibility and apply response to formulary and benefit files to determine coverage</td>
</tr>
<tr>
<td width="111" valign="top"><strong>IO-AM 09.14</strong></td>
<td width="389" valign="top">The system shall provide the ability to capture and display formulary information from pharmacy or PBM (Pharmacy Benefits Manager) by applying eligibility response</td>
</tr>
<tr>
<td width="111" valign="top"><strong>IO-AM 09.15</strong></td>
<td width="389" valign="top">The system shall provide the ability to send a query for medication history to PBM or pharmacy to capture and display medication list from the EHR</td>
</tr>
</tbody>
</table>
<p>As you can see, CCHIT tries not to be partial for either group in the last two requirements but the simple truth is that the first requirement really points towards implementing a solution through the PBMs. Determining, the eligibility of drug insurance is definitely not a function of a pharmacy; and even if it was wouldn’t it be more efficient to go straight to the source – the insurer?</p>
<p><strong>Stay Tuned</strong></p>
<p>I started this post stating we’re really trying to just get a prescription from your existing EHR into the hands of the fulfiller.  Now, we’re talking about first getting not only the patient’s eligibility information but also changing your EHR to provide formulary information.  If that wasn’t enough, you’ll also be adding a view into the patient’s medication history.  In my next post, I plan on going into more detail just what all of this means and the things you should think about when you’re ready to implement this functionality.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.eprescribing.org/a-cchit-based-guide-to-qualified-eprescribing-system-the-first-decision/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>A CCHIT Based Guide to a Qualified E-prescribing System – Part I (The 2008 requirements)</title>
		<link>http://www.eprescribing.org/a-cchit-based-guide-to-a-qualified-eprescribing-system-part-i-the-2008-requirements/</link>
		<comments>http://www.eprescribing.org/a-cchit-based-guide-to-a-qualified-eprescribing-system-part-i-the-2008-requirements/#comments</comments>
		<pubDate>Sun, 12 Apr 2009 02:55:50 +0000</pubDate>
		<dc:creator>George Getty III</dc:creator>
				<category><![CDATA[Basics]]></category>
		<category><![CDATA[CCHIT]]></category>
		<category><![CDATA[MIPPA]]></category>

		<guid isPermaLink="false">http://www.electronicprescribing.org/a-cchit-based-guide-to-a-qualified-eprescribing-system-part-i-the-2008-requirements/</guid>
		<description><![CDATA[As I mentioned briefly in my previous post, Medicare is providing incentives for practices to implement a “qualified” e-prescribing solution.  The Medicare Improvement for Patients and Providers Act of 2008 (referred to lovingly as MIPPA) describes in detail the schedule of payments for practices (found here), but it falls short on detailing what a qualified [...]]]></description>
			<content:encoded><![CDATA[<p>As I mentioned briefly in my previous post, Medicare is providing incentives for practices to implement a “qualified” e-prescribing solution.  The Medicare Improvement for Patients and Providers Act of 2008 (referred to lovingly as MIPPA) describes in detail the schedule of payments for practices (found <a title="CMS MIPPA Overview" href="http://www.cms.hhs.gov/partnerships/downloads/11399.pdf">here</a>), but it falls short on detailing what a qualified system is.  Instead, the Center for Medicare and Medicaid Services (CMS) points to certification authorities to provide the guidance of qualifying a practice’s system. As the Certification Commission for Healthcare Information Technology(CCHIT) will be the basis for the EHR incentives that come with the healthcare stimulus package, I thought it might be a good exercise to see what they had to say about e-prescribing.</p>
<p><span id="more-14"></span>I started by going to <a title="CCHIT" href="http://cchit.org">CCHIT</a> and downloaded the <a title="final CCHIT Certified 08 Ambulatory EHR criteria and test scripts" href="http://www.cchit.org/files/certification/08/Ambulatory/CCHITAmbulatoryEHR08.zip">final CCHIT Certified 08 Ambulatory EHR criteria and test scripts</a>.  I then used the excel spreadsheet(CCHITCriteriaAMBULATORY08FINAL.xls)  and filtered by category “9. Medications / ePrescribing”.  For the sake of providing a foundational view of ePrescribing, I then further filtered my results to only include the 2008 provisions.  The list contained requirements that The table below illustrates my results:</p>
<table border="0" cellspacing="0" cellpadding="0">
<tbody>
<tr>
<td width="111" valign="top"><strong>IO-AM 09.02</strong></td>
<td valign="top">The system shall provide the ability to display CCD documents, using a subset of the HITSP C32 specification for Allergy and Conditions content information, and file them as intact documents in the EHR</td>
</tr>
<tr>
<td width="111" valign="top"><strong>IO-AM 09.04</strong></td>
<td valign="top">The system shall provide the ability to generate and format CCD documents with narrative sections and structured entries (discrete fields) as specified by the HITSP IS03/C32 specification of the Allergy and Conditions module subset. For 2008, the values within the structured entries do not have to use industry standard vocabularies/terminologies (such as RxNorm or SNOMED-CT)</td>
</tr>
<tr>
<td width="111" valign="top"><strong>IO-AM 09.06</strong></td>
<td valign="top">The system shall provide the ability to send an electronic prescription to pharmacy</td>
</tr>
<tr>
<td width="111" valign="top"><strong>IO-AM 09.09</strong></td>
<td valign="top">The system shall provide the ability to respond to a request for a refill sent from a pharmacy</td>
</tr>
<tr>
<td width="111" valign="top"><strong>IO-AM 09.13</strong></td>
<td valign="top">The system shall provide the ability to send a query to verify prescription drug insurance eligibility and apply response to formulary and benefit files to determine coverage</td>
</tr>
<tr>
<td width="111" valign="top"><strong>IO-AM 09.14</strong></td>
<td valign="top">The system shall provide the ability to capture and display formulary information from pharmacy or PBM (Pharmacy Benefits Manager) by applying eligibility response</td>
</tr>
<tr>
<td width="111" valign="top"><strong>IO-AM 09.15</strong></td>
<td valign="top">The system shall provide the ability to send a query for medication history to PBM or pharmacy to capture and display medication list from the EHR</td>
</tr>
</tbody>
</table>
<p>I was initially confused by the first two entries.  It makes sense that EHRs be able to handle incoming and generate codified Allergy and Conditions to help in safely ordering medications, but I want to focus strictly on ordering the medication in my EHR and getting that prescription to the pharmacy electronically.  The Continuity of Care Document (CCD) is a subject worthy of its own series of posts.</p>
<p>Once I remove the CCD requirements, there are really only five requirements to satisfy in order to claim victory for the 2008 requirement set.  It may seem simple enough, but to satisfy these requirements you will find that the ordering system your granddaddy used (from paper to even existing electronic ordering) will need to be changed considerably.</p>
<p><strong>Stay Tuned</strong></p>
<p>Now that we’ve looked at all that is required to be a qualified e-prescribing system in 2008 according to CCHIT, I plan on detailing what exactly this entails per requirement.  Eventually, I plan on catching us up to the present year by doing the same with the 2009 requirements.  After that, get your flux capacitors fluxing and we’ll even check out what the future holds for us (2010 and beyond).</p>
]]></content:encoded>
			<wfw:commentRss>http://www.eprescribing.org/a-cchit-based-guide-to-a-qualified-eprescribing-system-part-i-the-2008-requirements/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>E-prescribing 101</title>
		<link>http://www.eprescribing.org/eprescribing-101/</link>
		<comments>http://www.eprescribing.org/eprescribing-101/#comments</comments>
		<pubDate>Tue, 17 Mar 2009 20:56:27 +0000</pubDate>
		<dc:creator>George Getty III</dc:creator>
				<category><![CDATA[Basics]]></category>
		<category><![CDATA[MIPPA]]></category>

		<guid isPermaLink="false">http://www.electronicprescribing.org/?p=4</guid>
		<description><![CDATA[Electronic prescribing is not just the ability to send prescriptions electronically to pharmacies. E-prescribing can also increase care quality in a number of ways:

E-prescribing makes sure that the prescriber is providing enough specific information for the pharmacist to fill the prescription, including the name of the drug, the dosage, its physical form, the route, and the [...]]]></description>
			<content:encoded><![CDATA[<p>Electronic prescribing is not just the ability to send prescriptions electronically to pharmacies. E-prescribing can also increase care quality in a number of ways:</p>
<ul>
<li>E-prescribing makes sure that the prescriber is providing enough specific information for the pharmacist to fill the prescription, including the name of the drug, the dosage, its physical form, the route, and the physician&#8217;s instructions.</li>
<li>Electronic prescribing software eliminates the time and effort of trying to understand the prescriber&#8217;s handwriting, as well as the chance of an error in that translation.</li>
<li>E-prescribing significantly reduces the chance that the prescriber&#8217;s intentions are misinterpreted.</li>
<li>E-prescribing is often used in conjuction with clinical decision support to ensure that any drug to drug interactions or drug to diagnosis issues are found and reported to the physician before the prescription order is completed.</li>
</ul>
<p>Electronic prescribing is considered one of the most important areas of Healthcare IT, which is why Medicare created payment incentives for physicians who use a qualified e-prescribing system. In 2009, the incentives are an increase of 2% in revenue for each patient when e-prescribing is used. Due to the 2009 HITECH Act, electronic prescribing is required as part of any EMR (EHR) which qualifies for Medicare reimbursement in 2011.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.eprescribing.org/eprescribing-101/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
	</channel>
</rss>
