SCRIPT is a standard for exchanging electronic information in the US healthcare sector developed by the NCPDP (National Council for Prescription Drug Programs), see http://www.ncpdp.org. MapForce supports mapping data between files in SCRIPT format and any other format supported by MapForce, including XML, CSV, Microsoft Excel, databases, and others. The supported NCPDP SCRIPT versions are: 8.1, 10.6, 10.10.
The default NCPDP SCRIPT version in MapForce is 10.10.
|Note:||To enable support for NCPDP SCRIPT versions other than the default one, download and install the "NCPDP SCRIPT Configuration Files" package from the Altova download center (https://www.altova.com/mapforce/download/libraries).|
NCPDP SCRIPT can use either the XML format or the UN/EDIFACT format. This documentation is applicable to the UN/EDIFACT version of NCPDP SCRIPT. If you have the NCPDP XML Schemas, MapForce will support mapping data to or from SCRIPT implicitly, using the standard XML mapping commands and validation (to add XML files to the mapping, use the menu command Insert | XML Schema/File).
Note that MapForce does not support sending or accepting SCRIPT messages as part of data communications between SCRIPT parties. The role of MapForce is to read data in SCRIPT format and map it to other formats, or convert data from other formats into SCRIPT format.
NCPDP SCRIPT files in UN/EDIFACT format can be added to the mapping as follows:
1.On the Insert menu, click EDI.
2.Select the "NCPDP SCRIPT" collection, and then select the check box next to the required message type(s).
3.Click OK. You are now prompted to supply an instance file.
4.Do one the following
•If you want to map data from an NCPDP SCRIPT message to some other format, click Browse and select the source SCRIPT file. It is also possible to open files from a URL, see Adding Components from a URL.
•If you want to map data to an NCPDP SCRIPT message, or supply the source file at a later time, click Skip.
At this stage, the structure of the selected NCPDP SCRIPT message(s) is displayed on the mapping (in MapForce terminology, an "EDI Component"). You can now either draw mapping connections to this component (in order to map data to it), or from this component, in order to map data from it. See also: