POCP Blog

ePrescribing Impact: Medicare Part D Migration to NCPDP SCRIPT version 201701

Share this story:

By Michael Burger, Practice Lead, EHRs and EDI

ePrescribingMedicare Part D will officially adopt NCPDP SCRIPT version 201701 for electronic prescribing (ePrescribing) on January 1, 2020 and will simultaneously retire SCRIPT version 10.6. The move is part of the periodic ePrescribing standards update process, which has been in place for over a decade. Details are in a final rule from the Centers for Medicare and Medicaid Services (CMS), beginning on page 692.

Here is what you need to know about the new Part D standard update.

  1. Who must use the new standard? The changeover applies to prescribers and dispensers who electronically transmit prescription and other information for covered drugs prescribed for Medicare Part D eligible beneficiaries, either directly or through an intermediary. Medicare Advantage plans also must comply.
  2. What transactions are included? In addition to the transactions that were in version 10.6, the following new transactions are included:
  • Prescription drug administration message
  • New prescription requests
  • New prescription response denials
  • Prescription transfer message
  • Prescription fill indicator change
  • Prescription recertification
  • Risk Evaluation and Mitigation Strategy (REMS) initiation request
  • REMS initiation response, REMS request
  • REMS response
  1. Is everyone required to use the new transactions? No. The regulation does not require everyone to perform these new transactions. However, if stakeholders opt to support them, SCRIPT version 201701 is mandatory for prescriptions for Part D beneficiaries. It is important to note that Part D historically has been a bellwether for transaction standards. This means that the commercial segment of the industry is likely to follow suit with what Medicare requires.

Although there are relatively few medications requiring REMS, CMS mentioned that they included REMS-related transactions to promote patient safety and enable REMS requirements to be completed within existing healthcare workflows. This will be critical as the REMS program expands to includes more medications.

  1. What’s the implementation date? The changeover applies to the new Part D contract year beginning on January 1, 2020. Trading partners and business associates can agree to voluntarily use the new standard before the cutover date. CMS noted that the 2020 date will allow time for ONC to sync up the Electronic Health Record (EHR) certification program.
  2. What does it mean? Changeovers to new standards are challenging, no doubt about it. And there’s also no doubt that the migration to a new standard in less than two years will be perceived as lightning fast by many stakeholders, all of whom have full software enhancement roadmaps.

Accelerated though the timeline may seem, the major players in the ePrescribing industry still have the opportunity to plan ahead and move methodically to SCRIPT version 201701 in anticipation of the mandate. This will enable quality assurance testing to happen well in advance, which will make the cutover happen more smoothly. Harmonization of the new ePrescribing standard with the EHR certification program apparently is in the offing, so EHR vendors should pay close attention in order to meet both deadlines.

To be sure, if a stakeholder has implemented SCRIPT already, they will need to move to this version of the standard. In addition to the support of new transactions, migrating to the new SCRIPT standard has many benefits. SCRIPT version 201701 offers clarifications and improvements to existing transactions from previous versions of the standard, which will greatly improve the quality (and patient safety) of ePrescribing. For example, the new standard streamlines the supported quantity units of measure, from hundreds of codes down to a hand full. This one change alone will eliminate thousands of pharmacy-to-prescriber clarification phone calls, and improve patient safety by ensuring that ePrescription orders are concise and unambiguous.

Full implementation of SCRIPT 201701 will depend on a business case for many of the transactions.  That applies to the new transactions as well as the several that existed in version 10.6, which haven’t been adopted by many stakeholders. One transaction for which a use case exists is the pharmacy alerting the prescriber that they have substituted a biosimilar, a requirement in 41 states and Puerto Rico. We understand that several of the large pharmacy chains will be implementing change, cancel and transfer, so a business case exists for those transactions. However, others, such as RxFill, will require a revenue model or incentive.

We applaud CMS for moving ahead in improving interoperability and the computerization of healthcare.  NCPDP SCRIPT version 10.6 was adopted by Part D in 2012, but not officially implemented until March 1, 2015. The world has changed a lot since then.

Want to know more? I’d be happy to share my thoughts. Contact me at michael.burger@pocp.com.

Michael Burger

Michael Burger

Leave a Comment