Difference between revisions of "E-Prescription"
Max.Stroud (talk | contribs) |
|||
| (One intermediate revision by one other user not shown) | |||
| Line 1: | Line 1: | ||
| + | __TOC__ | ||
| + | |||
| + | ==='''Overview'''=== | ||
| + | |||
An e-prescription is a prescription written through an [[e-prescribing]] software solution. | An e-prescription is a prescription written through an [[e-prescribing]] software solution. | ||
| Line 13: | Line 17: | ||
[http://geekdoctor.blogspot.com/2008/07/surescriptsrxhub-merger.html From Dr John Halamka's Blog - Life as Healthcare CIO] | [http://geekdoctor.blogspot.com/2008/07/surescriptsrxhub-merger.html From Dr John Halamka's Blog - Life as Healthcare CIO] | ||
| − | '''e-Prescribing stakeholders''' | + | ==='''e-Prescribing stakeholders'''=== |
| − | The | + | The provider writing the prescription |
The retail pharmacy or mail order pharmacy | The retail pharmacy or mail order pharmacy | ||
| Line 27: | Line 31: | ||
SureScripts: the connection to most retail pharmacies | SureScripts: the connection to most retail pharmacies | ||
| − | '''Here's the data flow:''' | + | ==='''Here's the data flow:'''=== |
1. A clinician begins to e-Prescribe and electronically queries for the patient's insurance eligibility and the appropriate payer's formulary. Before the merger, both RxHub and SureScripts had eligibility services but RxHub processed the majority of these transactions. | 1. A clinician begins to e-Prescribe and electronically queries for the patient's insurance eligibility and the appropriate payer's formulary. Before the merger, both RxHub and SureScripts had eligibility services but RxHub processed the majority of these transactions. | ||
| Line 33: | Line 37: | ||
2. The clinician queries for medication history to check for drug/drug interactions. RxHub has medication history based upon claims data and SureScripts has the actual dispensed information from the pharmacies (which includes cash, third party claims and $4 generic programs). Before the merger, the clinician's EHR would have to issue separate queries via two separate interfaces to get a complete history. | 2. The clinician queries for medication history to check for drug/drug interactions. RxHub has medication history based upon claims data and SureScripts has the actual dispensed information from the pharmacies (which includes cash, third party claims and $4 generic programs). Before the merger, the clinician's EHR would have to issue separate queries via two separate interfaces to get a complete history. | ||
| − | 3. The | + | 3. The provider completes the prescription. Retail pharmacy transactions are transmitted to SureScripts for delivery to community pharmacies and smaller mail order firms. Mail order transactions served by one of the 3 large PBMs are transmitted to RxHub for fulfillment. Again, two separate interfaces were required. |
As SureScripts-RxHub integrates its services, there will no longer be a need to send out 2 queries for eligibility/formulary, medication history or routing. Also, the two sources of medication history data will be de-duplicated, providing an accurate and usable medication data flow to all stakeholders. | As SureScripts-RxHub integrates its services, there will no longer be a need to send out 2 queries for eligibility/formulary, medication history or routing. Also, the two sources of medication history data will be de-duplicated, providing an accurate and usable medication data flow to all stakeholders. | ||
Latest revision as of 16:11, 17 October 2014
Overview
An e-prescription is a prescription written through an e-prescribing software solution.
e-Prescribing is the practice of writing prescriptions electronically through an EHR or similar type of software application. The e-Prescription can be electronically routed to the patient's pharmacy of choice over the internet via Surescripts. Most e-prescribing software also allows for prescriptions to be transmitted using a fax machine, but this is not considered full e-prescribing.
The CMS definition of e-prescribing does not include prescriptions that are faxed. Only prescriptions that are sent electronically from the e-prescribing system to the pharmacy computer are considered e-prescriptions. (e.g. Surescripts). Under Medicare Part D and the Medicare Improvements for Patients and Providers Act of 2008 (MIPPA),providers who use e-prescribing for Medicare patients will receive a 2% bonus in 2009 and 2010. Over time the amount of the bonus will decrease and in 2012 there will be penalties for not using e-prescribing. Faxed prescriptions are not eligible for the 2% bonus.
For more information - http://www.medpagetoday.com/PracticeManagement/InformationTechnology/tb/11232
e-Prescribing is considered superior to traditional paper prescriptions due to the legibility of the information. An added benefit of e-prescribing is the access to the latest drug interaction information (see DUR) as well as up-to-date payer formularies.
From Dr John Halamka's Blog - Life as Healthcare CIO
e-Prescribing stakeholders
The provider writing the prescription
The retail pharmacy or mail order pharmacy
The payer
The pharmacy benefit manager (PBM), which acts on behalf of the payer to adjudicate claims
RxHub: the connection to most PBMs
SureScripts: the connection to most retail pharmacies
Here's the data flow:
1. A clinician begins to e-Prescribe and electronically queries for the patient's insurance eligibility and the appropriate payer's formulary. Before the merger, both RxHub and SureScripts had eligibility services but RxHub processed the majority of these transactions.
2. The clinician queries for medication history to check for drug/drug interactions. RxHub has medication history based upon claims data and SureScripts has the actual dispensed information from the pharmacies (which includes cash, third party claims and $4 generic programs). Before the merger, the clinician's EHR would have to issue separate queries via two separate interfaces to get a complete history.
3. The provider completes the prescription. Retail pharmacy transactions are transmitted to SureScripts for delivery to community pharmacies and smaller mail order firms. Mail order transactions served by one of the 3 large PBMs are transmitted to RxHub for fulfillment. Again, two separate interfaces were required.
As SureScripts-RxHub integrates its services, there will no longer be a need to send out 2 queries for eligibility/formulary, medication history or routing. Also, the two sources of medication history data will be de-duplicated, providing an accurate and usable medication data flow to all stakeholders.