Pharmacy Module Invoice Data Specification for Non-Supported Trading Partners


Version: 1

Release Date: October 20, 2022


This is the generic Purchases data specification for the ControlCheck (formally known as Bluesight for Controlled Substances) Pharmacy Module. ControlCheck Pharmacy Module ingests purchasing data from hospital trading partners such as wholesalers, 503b compounders, etc. along with load data from the hospital’s controlled substances “vault” software. ControlCheck then compares the two sets of data to ensure that all purchases of controlled substances have a corresponding load event for an equal amount.

ControlCheck Pharmacy Module officially supports the trading partners AmerisourceBergen, McKesson, and Cardinal for which there are individual data specifications. The data specification below is provided so that hospitals or unsupported trading partners can create ControlCheck-compatible data loads for their invoicing data. If your hospital or trading partner cannot meet the following data specification, please discuss with your implementation specialist or contact

<aside> 💡 Note: ControlCheck’s ability to troubleshoot unsupported trading partner data loads is limited and we offer no guarantee that ControlCheck Pharmacy Module will work as intended using data from said trading partners.


File Transport

Invoice files can be uploaded via the ControlCheck user interface. If a trading partner or hospital would prefer to use SFTP they should discuss with their implementation specialist. Trading partners that are interested in utilizing EDI for data transfer should contact the ControlCheck product team for additional information (**********)**********.

File Requirements

  • Files must be formatted as .csv that conform to RFC 4180 and utilize UTF-8 for character encoding
  • File size should not exceed 50 mb
  • The file name should follow the schema and can only contain letters, numbers, and underscores.
    • bluesight_hospitalname_tradingpartner_invoicedate.csv
  • Output column headers must match the values specified below. The order in which those columns appear can be different than the order listed below. However, it is highly recommended that customers follow the order below for consistency and readability.

Invoice Data

Unit_Of_Use_Multiplier Examples