National Council for Prescription Drug Programs (NCPDP) publishes standards for the electronic exchange of healthcare information related to pharmacy services.
In this blog we will discuss the SCRIPT Standard used in Electronics Prescribing. This standard covers data exchanges between prescribers, pharmacies, intermediaries and payers.
SCRIPT is a standard data set for the interchange of prescription data and related information in the medical provider community.
So let's talk about the formats used in this standard. There are of two types, XML and EDIFACT. The older versions such as 4.2 are in EDIFACT format.
The newer version such as 10.6 has an XML format option. If you are a member of NCPDP, you can download all their standards and the related implementation guides.
We will show different message types in both XML and EDIFACT format later in this post.
Adeptia is a member of NCPDP and provides full NCPDP Standards Data Dictionary, Process Templates and the Data Mapping rules to route and convert the NCPDP data into any target format. The process templates depends on the type of transaction we are working with, for example here are all the SCRIPT transactions along with their Message IDs and descriptions of the most widely used transactions:
Following are some of the other transmission types:
Advantage of using Adeptia Integration Suite is that it enables your business users or non-technical users to configure the above transactions quickly without having to write code or to read through complex implementation guides. Adeptia has done all the work for you by providing a graphical process designer interface to allow you to configure any SCRIPT process and by giving you access to all the data dictionaries that will help in parsing, validating and converting any NCPDP data to any format. Here is an example of the New Prescription process suggested in the NCPDP Implementation guide and the template flow in Adeptia.
Here is the New RX and Change RX Request/Response Process Flow template in Adeptia.
Now apart from the SCRIPT processes as described above, understanding the SCRIPT data formats and how it relates to each other and more importantly how it can be converted into any another format (let's say a database) is core to a successful implementation of a NCPDP process.
Transport node consists of the following sections:
1. Patient information such as SSN, Name, Address, DoB, Phone.
2. Pharmacy data such as the NCPDPID, NPI, Address and Phone.
3. Prescriber data such as the NPI, Name, Address, Phone.
4. MedicationPrescribed that contains the Drug Description, Dosage/Quantity and instructions.
A SCRIPT message interchange consists of following segments. An interchange is defined as communication between partners in the form of a structured set of messages and service segments.
A sample SCRIPT message in UN/EDIFACT format:
Here the UIH segment uniquely identifies that it is SCRIPT interchange type with NEWRX as the message type. Adeptia provides the full UN/EDIFACT data dictionary to parse and validate SCRIPT data and allows users to map it to any format.
In Adeptia's Data Mapper, simply pull up the particular XML or UN/EDIFACT Schema of the SCRIPT transaction type and map it to the target system. Sample mapping shown below.