SCRIPT Migration Success Story: Henry Schein MicroMD

Q: How many people were involved in the project? And how long did the process take?

We had a single developer, and it took about three weeks of actual development time. There was additional time spent on going through the test cases for certification. The project spanned about two months.

Q: Why was your SCRIPT migration a priority for your organization?

We feel that the enhanced functionality of discrete/multiple sig, will enhance the e-prescribing functionality.

Note: NCPDP SCRIPT Standard v2017071 now allows for 1,000 characters in the sig field for better clarity of prescriber intent.

Q: How did Surescripts support you both leading up to and during your migration?

Surescripts assigns a project manager, who is always very helpful. They're available for email questions, as well as scheduling bi-weekly meetings to make sure the project moves along smoothly. In all projects, the project manager has always been helpful, in answering any questions and helping.

Q: What was the biggest challenge that you had to overcome with your SCRIPT migration?

Implementing the discrete sig was a bit of a challenge—especially the concept of multiple discrete sigs, as well as verifying the SigText sent is fully built from the discrete.