Pharmacy Module Invoice Data Specification for Non-Supported 503B Trading Partners

[Deleted User]

Version: 1

Release Date: June 12, 2023

Introduction

ControlCheck (formally known as Bluesight for Controlled Substances) Pharmacy Module ingests purchasing data from hospital trading partners 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.

This is a generic 503b data specification for the ControlCheck Pharmacy Module. Our preferred method for ingesting purchasing data is via EDI feed. However, if your 503b can not support an EDI feed, they can leverage the data specification below to generate exports of hospital purchases for import into ControlCheck. If your 503b cannot meet the requirements specified below or if they are interested in integrating via EDI, please discuss with your implementation specialist or contact help@bluesight.com.

💡 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, however, delivery over SFTP is highly preferred.

Individual files should be generated per facility, although there are specific use cases that would require including multiple facilities. Discuss with your implementation specialist before finalizing hospital groupings.

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

Output Column Name	Required	Data Types	Format	Description	Example
COMPANY_NAME	Y	String		Hospital Account used to make the purchase.	Pacific Medical Center
CUSTOMER_ID	Y	Int		Unique Id of the hospital account used to make the purchase.	555555
INVOICE_ID	Y	Int		Unique invoice identifier issued by the trading partner for the specified purchase.	123456
NDC_CODE	Y	Int		Unique medication identifier for the drug administered.	4094600025
PRODUCT_DESCRIPTION	Y	String		Description of the NDC including drug, strength, and form factor.	fentaNYL 10 mcg/mL prefilled syringe
PRIMARY_PACK_QTY	Y	Int		*The total quantity of units of the NDC sent to the hospital	100
INVOICE_DATE	Y	Date	calendar dates	Date the purchase was delivered to the hospital.

*This date should match the date in which hospital loaded the medications in the narcotics vault. | YYYY-MM-DD hh:mm:ss±hh:mm |

• For PRIMARY_PACK_QTY: This is the total unit count that was sent to the hospital.
  • For instance, a hospital orders 5 cases that contains 20 syringes.
  • The total unit count would be 100 syringes. This should correspond to the total unit count that is loaded into the narcotics vault.