Patient Care: Pyxis ES Data Extract Documentation
Version: 1
Release Date: March 10, 2023
Introduction
This is the data specification and directions for accessing and automating the information ControlCheck (formally known as Bluesight for Controlled Substances) requires for PyxisES dispensing systems. ControlCheck utilizes a canned PyxisES report. Customers are strongly encouraged to used the canned report and follow the below steps provided as the fastest path to a compliant data feed. Customers may opt to author their own query to extract data a different way as long as the output meets the criteria provided by the canned PyxisES report. The customer is solely responsible for any issues involving a custom query or report.
ControlCheck ingests PyxisES data from hospitals along with administration data from the hospital’s electronic medical record. ControlCheck then compares the two sets of data to ensure that all dispenses of controlled substances have a corresponding administration for an equal amount. The data specification below is provided so that hospitals can create ControlCheck-compatible data loads for their dispensing data. If your hospital cannot meet the following data specification, please discuss with your implementation specialist or contact help@kitcheck.com.
File Transport
PyxisES files can be uploaded via the ControlCheck user interface, however, delivery over SFTP is highly preferred. File transfers should occur once per day, in the middle of the night, containing Pyxis data from the previous day.
Recommended file transfer times are from 0400-0600 to ensure 1) data has migrated to the appropriate servers and 2) that Bluesight is able to process files in a timely manner prior to customer auditing. Additionally, it is recommended that the ADC file(s) can be sent at least 30 minutes after the EMR file for optimized processing and data ingestion.
Individual files should be generated per facility although there are certain 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_IDNname_hospitalname_pyxisES_eventdate.csv
Pre-Implementation & Data Validation File
During implementation, your implementation specialist will request a historical extract of data. This is a one-time request that will be manually uploaded into the application. The historical file upload would not depend on the SFTP being fully setup. Potentially some requirements may be different during testing/validation such as file size, naming, and date range.
Generating PyxisES Report
- Login to your Pyxis ES Application
- Navigate to the report list
- Select the “All Device Event Report”
- Name it as mentioned above and schedule it to run the morning for the prior day data. Start and End Date would be 24 hours prior - 00:00:00 to 23:59:59. Set up the delivery settings as a file type of .csv
- Send the file delivery location to your SFTP team to configure the SFTP client to pick up and deliver to ControlCheck daily.
