What you need to know to implement RXTransparent Compliance solution and facilitate seamless integration.

Already understand integration?

RXTransparent Link to Customer Resources

Click this icon to start the process.

Data Integration Terminology

  • Invoice Data: information normally found on an invoice, i.e., invoice number, invoice date, retail price, extended price, etc.
  • Shipment Data: information related to the shipment of products, i.e., shipment date, quantity shipped, ship-to location, etc.
  • Historical Data: all invoice and shipment data going back to 1/1/2015.
  • EDI (Electronic Data Interchange): a set of formatting standards for data that is often transferred between parties.
  • EDI 810: the EDI standard for invoice data.
  • EDI 856: the EDI standard for shipment data.
  • VAN (Value Added Network ): a “middleman” who facilitates the transfer of data in EDI format between parties. While EDI is technically a format and not a method of transmission, data in EDI format is normally assumed to be transferred through a VAN.
  • SFTP (Secure File Transfer Protocol):   a secure means of transferring a data file from one party to another.
  • GS1: a set of standards for transferring data from one party to another. Also refers to the organization behind those standards.  GS1 leverages barcode technology to connect data transactions to physical shipments and allows products to be serialized at the lowest saleable unit.
  • EPCIS (Electronic Product Code Information Services):  the technical standard for transferring GS1 formatted data.

Capturing Data

Data is transferred to RXTransparent in a format called electronic data interchange (EDI).   Data in EDI format can be transferred through SFTP or a VAN.

RXTransparent can employ one of three methods for capturing data:

  1. Secure File Transfer Protocol (SFTP): With this method, RXTransparent provides a unique login to our vendor server where data can be dropped. This is the preferred and most effective method for integration.
  2. Value-Added Network (VAN): With a VAN, usually a third party vendor is in place to add a layer of complication to the process. However, with permission to request your statement and invoice data from the third party vendor, a liaison can be established that will allow RXTransparent to integrate your data into the platform.
  3. Portal Access: If an SFTP or a VAN cannot be established, RXTransparent can also retrieve information through portal access. Access to the specific online resource used by healthcare facility to log into a vendor data platform will be required. In this case, it will be necessary to create a new username unique to RXTransparent that will provide access to all customer accounts. Retrieving data via a portal is a fragile process used as a last resort.

856 and 810 Data

The EDI specifications define how different types of data are handled. These different types of data are given code numbers. Full RXTransparent functionality requires access to two types of EDI transaction data:

      • 856 (shipment data): Advanced Shipment Notice (ASN). This is the 3T data required by the FDA. This EDI code transmits only shipment information regarding products sent and only partially fulfills the reporting criteria necessary for the RXTransparent platform. For DSCSA, vendors are packing all 3T data into this format because it will fit.
      • 810 (invoice data): This format transmits the specific invoice data that includes information such as invoice number, ordering date and pricing data.

Why does RXTransparent need invoice data?

As a DSCSA compliance solution built specifically for hospital dispensers, invoice information is needed to facilitate the handling of business processes surrounding this data. The two formats, 856 and 810, tie together to facilitate a number of RXTransparent functions:

      • Facilitates the advanced search protocol inherent in the platform.
      • Accommodates incident reporting.
      • Complies with the FDA guidelines for DSCSA security for invoice reconciliation.
      • Allows for error correction when processing invoice data vs. shipment data.

In short, invoice data fulfills the requirements of law and is also necessary to achieve full functionality of the RXTransparent platform.

Cloud Environment

Cloud Environment

Intellectual Property


This database repository is a cross references of the entire National Library of Medicine and FDA Orange Book and Purple Book repositories.  This database allows RXTransparent users to easily manage data within the platform and in relation to external partner data.


By integrating blockchain technology into the DSCSA compliance platform,  RXTransparent utilizes blockchain for non-repudiation and chain-of-custody pedigree tracking.  We will soon be pioneering the concept of a centralized private ledger between supply chain trading parties.

Our commitment is to exceed your expectations for ease of use and efficiency.

Learn more about implementing RXTransparent: