In part 1 last week of our series on the NCPDP’s new standard for ePrescribing, which becomes effective January 1, we talked about the many new fields contained in version 2017071. In this second installment, we explore the standard’s new two-way communication possibilities. Although all these advantages may not be fully up and running on both side of the e-prescribing network yet, we want to keep you informed about the new standard’s intended benefits – so read on.
To keep your pharmacy system compliant, QS/1 first had to be prepared to update the existing SCRIPT version 10.6 message types to use the new version. The message types available today are NewRx, Refill Request, Refill Response (now known as Renewal Request/Response), and CancelRx. NewRx is the most commonly used message type, and it allows the prescriber to send a prescription electronically to the pharmacy. This may or may not include electronic prescriptions for controlled substances (EPCS) since it varies by prescribing system and whether the prescriber is using EPCS.
New ways to ask electronically
But the new standard includes some new message types. The ones we’re looking forward to most are RxChange, RxFill, and NewRxRequest.
- RxChange: Over the years, one of the most commonly requested features was a way to request a change or clarification from a prescriber on a given prescription. The pharmacy will be able to request a change to another medication (e.g., therapeutic interchange) or request clarification when there are conflicting details or missing information in the NewRx.
- RxFill: This real-time message can be sent to the prescribing system when a prescription has been picked up by the patient. In the current version, prescribers can’t specify when they want to receive RxFill notifications, which can contribute to alert fatigue. In the new version, prescribers can indicate whether they want to see all RxFill notifications (Dispensed, Not Dispensed, and Returned to Stock) or if they only want to be notified when a prescription has not been picked up, indicating the patient may not be compliant or adherent.
- NewRxRequest: This transaction type can be very useful to a pharmacy that discovers a problem during a CMR or MTM encounter for which they do not have a prescription. A NewRxRequest is generated from the pharmacy and sent to an enabled prescriber. The prescriber can approve the NewRxRequest, which is the NewRx message that exists today, or send a NewRxRequest response of Denied if they do not approve (they may want the patient to come in for an office visit before writing a new prescription).
The goal? Less phone tag with prescribers
Currently, if you have a question, you or your staff have to call the prescriber to request information. Speaking to someone on the first call is the exception, not the rule, and you usually have to wait for them to call back. If they had the answers immediately, that would help the process move forward, but in the real world, that rarely happens. Compounding the wait, the staff most likely has to run down the answers and call you back, again. Even if the process only takes a few minutes, time is money, and this can turn into a costly process if you have to repeat it multiple times a day.
It’s important to remember that new functionality in the ePrescribing standard depends on implementation by both sides of the Surescripts® network. But happily, with the new SCRIPT Standard, it’s possible for more information to be included on the e-prescription when it is sent to the pharmacy – and if it isn’t included, you will be able to request it electronically and get back to work filling prescriptions or counseling patients.
See everything QS/1 is saying about the new SCRIPT ePrescribing Standard, including blog post part 1, here.
Comments (0)