Pharmacy claims, e-prescribing, and transfers
NCPDP Telecommunication, Batch, SCRIPT, and Prescription Transfer definitions for the AnyToAny Engine, for the versions listed below. Validate, convert, and integrate pharmacy EDI with the same single-pass engine that runs Redix X12 processing.
- Telecommunication D.0
- Batch 1.1
- SCRIPT
- Prescription Transfer
Four NCPDP standards
| Standard | Redix definitions | Primary use |
|---|---|---|
| Telecommunication | 5.1, D.0 | Real-time, point-of-sale pharmacy claims and eligibility |
| Batch | 1.1 | Batch claim submission and response for high-volume adjudication |
| SCRIPT (e-prescribing) | 5.0, 8.1, 10.6 | Prescription routing between prescribers, pharmacies, and PBMs |
| Prescription Transfer | 1.0, 2.0 | Pharmacy-to-pharmacy transfer, fixed and variable formats |
Listed definitions versus current standards. The SCRIPT versions listed here are legacy definitions, not a claim of current Medicare Part D e-prescribing coverage. Part D is transitioning from SCRIPT 2017071 to 2023011; 2023011 is required from January 1, 2028. The current adopted pharmacy claim standard pairs Telecommunication D.0 with Batch 1.2, while the Batch 1.1 definition listed here is legacy. Ask Redix to confirm the exact version and transaction coverage for your project; availability of additional definitions must be confirmed.
NCPDP to any target format, and back
Format to format (AnyToAny + NCPDP)
- NCPDP Telecommunication, Batch, SCRIPT, and Prescription Transfer
- X12 and UN/EDIFACT
- Fixed-length flat files
- CSV and proprietary formats
XML generation (AnyToXML + NCPDP)
- Each NCPDP standard to XML
- Schema and DTD validation
- Custom XML structures
Built for PBMs, payers, and pharmacy networks
Pharmacy claims
Process real-time and batch pharmacy claims with Telecommunication and Batch support for PBM integration.
E-prescribing
Process prescription messages between prescribers, pharmacies, and PBMs, for the SCRIPT versions listed above.
Prescription transfers
Move prescriptions between pharmacies with Prescription Transfer support.
Data integration
Turn NCPDP data into XML, flat files, or database tables for analytics and reporting.
Visual mapping between NCPDP and other formats
- Drag-and-drop mapping between formats
- Link NCPDP to X12 transactions
- Generate conversion maps automatically
- Test with sample data
See the GUI Mapper.
How the module is licensed
AnyToAny Engine
Required. The core engine: single-pass processing, IFD/OFD definitions, and the runtime.
NCPDP Module
This module. Telecommunication, Batch, SCRIPT, and Prescription Transfer definitions, with sample transaction files.
GUI Mapper / HIPAA Package
Recommended. Visual mapping and HIPAA X12 integration for complete pharmacy workflows.
Talk to us about pharmacy EDI
Tell us your standards, versions, and volumes. We confirm coverage and show a working conversion on a de-identified sample.